Reputation incident

Site unavailable

Critical Resolved View vendor source →

Reputation experienced a critical incident on January 13, 2020 affecting Surveys and Profiles API and 1 more component, lasting 4h 36m. The incident has been resolved; the full update timeline is below.

Started
Jan 13, 2020, 05:27 PM UTC
Resolved
Jan 13, 2020, 10:03 PM UTC
Duration
4h 36m
Detected by Pingoru
Jan 13, 2020, 05:27 PM UTC

Affected components

SurveysProfiles APIPlatformFTPReviewsIntegratorSocialActionsInsightsMobile

Update timeline

  1. investigating Jan 13, 2020, 05:27 PM UTC

    On Monday, January 13, 2020, 9:25 AM Pacific Time, Reputation.com determined an issue preventing some users from using the site. This issue impacts users located in North America. We are currently investigating the issue. We apologize for this inconvenience and thank you for your patience as our engineering and operations teams work to address the issue as quickly as possible. We will update this page with the latest information as it becomes available.

  2. investigating Jan 13, 2020, 05:29 PM UTC

    Site interruption is related to our MongoDB instance. Currently on call with MongoDB priority support.

  3. investigating Jan 13, 2020, 06:23 PM UTC

    Our engineering team continues to work to resolve the issues and bring the site up.

  4. identified Jan 13, 2020, 07:33 PM UTC

    Database recovery is still in progress. We have achieved partial recovery and some functionality may be available for most customers. Customers may experience slower than usual response time. We anticipate full recovery within two hours.

  5. identified Jan 13, 2020, 08:09 PM UTC

    Database recovery still in progress.

  6. identified Jan 13, 2020, 08:34 PM UTC

    Database recover still in progress.

  7. identified Jan 13, 2020, 09:04 PM UTC

    We are continuing to work on a fix for this issue.

  8. identified Jan 13, 2020, 09:05 PM UTC

    Database recovery in progress.

  9. identified Jan 13, 2020, 09:30 PM UTC

    Database recovery in progress.

  10. monitoring Jan 13, 2020, 10:00 PM UTC

    Database recovery in progress.

  11. resolved Jan 13, 2020, 10:03 PM UTC

    All functionality has been restored