Ingestion delayed for spans, logs, crons in US region
Jul 13, 00:58 UTCJul 13, 02:56 UTC
Duration
1h 58m
Impact
Critical
Root cause
Not disclosed
Sentry, 90 days
30 incidents
Affected
US Ingestion - US Span IngestionUS Ingestion - US Cron MonitoringAlerting - US Spans AlertingAlerting - US Uptime Monitoring
Final update
Ingestion has caught up and alerts have been restored.
Timeline
- Resolved · Jul 13, 02:56 UTC
Ingestion has caught up and alerts have been restored.
- Monitoring · Jul 13, 02:01 UTC
We have implemented a fix and are monitoring the situation. We expect ingestion to catch up in the next hour, approximately.
- Identified · Jul 13, 01:46 UTC
We have identified the problem and are working to restore ingestion
- Investigating · Jul 13, 00:58 UTC
We are currently investigating the issue.
More from Sentry
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 1810:17 UTC | Delays in spans ingestion | major | 41m |
| Sep 1808:36 UTC | Delayed ingestion of errors in EU | critical | 3h 20m |
| Sep 1016:13 UTC | Ingestion is delayed in US | minor | 57m |
| Sep 1015:25 UTC | Sentry.io elevated number of 500 errors | major | 1h 1m |
| Sep 114:16 UTC | Span ingestion is degraded in US | minor | 6h 14m |
| Sep 108:01 UTC | Sentry requests timing out / 504's | major | 3h 20m |
From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.