Samepage.io incident

Samepage unavaliable

Major Resolved View vendor source →

Samepage.io experienced a major incident on June 14, 2017, lasting 3h 25m. The incident has been resolved; the full update timeline is below.

Started
Jun 14, 2017, 12:14 PM UTC
Resolved
Jun 14, 2017, 03:40 PM UTC
Duration
3h 25m
Detected by Pingoru
Jun 14, 2017, 12:14 PM UTC

Update timeline

  1. investigating Jun 14, 2017, 12:14 PM UTC

    Samepage is currently unavaliable. We're investigating the issue.

  2. identified Jun 14, 2017, 01:03 PM UTC

    We had to recover some data from backup. Most people should see no problem now. We're continuing to investigate.

  3. resolved Jun 14, 2017, 05:35 PM UTC

    This morning around 5am Pacific Time (11:52 UTC), an incident occurred which caused a temporary failure of certain Samepage administration functions. In order to recover from this failure, we took Samepage offline for approximately 1 hour. At approximately 13:00 UTC the error was corrected and access to Samepage was restored. No customer data inside Samepage was lost or damaged. Samepage is functioning normally now. We have identified a small number of customers where new user registrations may have been affected, and we are reaching out to those customers directly.