Changes / Sentry / Sentry.io elevated number of 500 errors
Sentry: Major incident: Sentry.io elevated number of 500 errors
Summary
Sentry reported a major incident with elevated 500 errors affecting the API, Dashboard and listed US ingestion components from 2026-09-10 15:25 UTC to 2026-09-10 16:26 UTC, lasting 1 h 1 min. Errors appeared during migration to a new control silo region; Sentry rolled back the migration, applied fixes and confirmed full resolution.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Sentry.io elevated number of 500 errors
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-09-10 15:25 UTC
Before: not present
After: 2026-09-10 16:26 UTC
Before: not present
After: API, Dashboard, US Ingestion - Custom Metrics (beta), US Ingestion - US Attachment Ingestion, US Ingestion - US Cron Monitoring, US Ingestion - US Error Ingestion, US Ingestion - US Profile Ingestion, US Ingestion - US Replay Ingestion, US Ingestion - US Size Analysis Ingestion, US Ingestion - US Snapshot Ingestion, US Ingestion - US Span Ingestion, US Ingestion - US Transaction Ingestion
Before: not present
After: During migration to new control silo region we started to observe increased number of 500 errors.
Migration procedure was rolled back.
Before: not present
After: Issue were identified and fixes were applied. We continue to monitor situation
Before: not present
After: Issue fully resolved
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Sentry.io elevated number of 500 errors (this change) Sentry reported a major incident with elevated 500 errors affecting the API, Dashboard and listed US ingestion components from 2026-09-10 15:25 UTC to 2026-09-10 16:26 UTC, lasting 1 h 1 min. Errors appeared during migration to a new control silo region; Sentry rolled back the migration, applied fixes and confirmed full resolution. | Major incident |