Starting around 0900 UTC today, Samepage suffered memory overload on one of our page editing servers. We failed to detect and correct it for approximately 6 hours. No data was lost on the server-side; however, users' changes to page content were potentially lost under certain conditions. Ordinarily, Samepage client (our desktop application, mobile app, or web session) is caching all page changes in the event of transitory loss of connection to the server. If a user restarts the desktop or mobile app or refreshes the browser session, those changes are lost as the cache is cleared. Due to the extended outage of that one server, we are aware that some customers reported data losses, and we sincerely apologize for this error. Web sessions have already been showing a warning if a user attempts to refresh while changes are still cached. We are adding this to our desktop client to improve user's expectations in the future. In addition, we've implemented additional logging and status notifications to prevent future extended server outages.