Today's Trends
minorArchivedSentry

Sentry.io elevated number of 500 errors

  1. Investigating(done)
  2. Trending(skipped)
  3. Workaround available(skipped)
  4. Resolved(done)
  5. Archived

Executive summary

Increased number of 500 errors observed during migration to a new control silo region. Issue was resolved after rollback and monitoring.

No verified workaround yet

This incident was resolved upstream without a reported workaround.

Official fix
Technical root cause

Under active investigation. No report has identified a root cause yet.

Evidence

1 report · 1 StatusShow
  1. [1]
    Status First report
    Sentry.io elevated number of 500 errors(opens official status page in a new tab)

    Identified: During migration to new control silo region we started to observe increased number of 500 errors. Migration procedure was rolled back. Monitoring: Issue were identified and fixes were applied. We continue to monitor situation Resolved: Issue fully resolved

    by sentry status

Timeline

  1. First report on status page

    Sentry.io elevated number of 500 errors

    Source
  2. Official statement

    Identified: During migration to new control silo region we started to observe increased number of 500 errors.

    Source
  3. Status changed

    Status changed: new → archived (resolved more than 14 days ago).