All Systems Operational
Samepage App Operational
Samepage Website Operational
AWS Operational
AWS cloudFront Operational
AWS ec2-us-west-2 Operational
AWS elb-us-west-2 Operational
AWS rds-us-west-2 Operational
AWS route53 Operational
AWS sqs-us-west-2 Operational
AWS s3-us-west-2 Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Jul 16, 2020

No incidents reported today.

Jul 15, 2020

No incidents reported.

Jul 14, 2020

No incidents reported.

Jul 13, 2020

No incidents reported.

Jul 12, 2020

No incidents reported.

Jul 11, 2020

No incidents reported.

Jul 10, 2020

No incidents reported.

Jul 9, 2020

No incidents reported.

Jul 8, 2020

No incidents reported.

Jul 7, 2020
Resolved - 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.
Jul 7, 19:01 UTC
Jul 6, 2020

No incidents reported.

Jul 5, 2020

No incidents reported.

Jul 4, 2020

No incidents reported.

Jul 3, 2020

No incidents reported.

Jul 2, 2020

No incidents reported.