Crons ingestion backlogged
Jan 23, 18:38 UTCJan 24, 00:27 UTC
Duration
5h 49m
Impact
Informational
Root cause
Not disclosed
Sentry, 90 days
30 incidents
Affected
Not listed by the vendor.
Final update
Backlog has been processed and crons should be running as normal
Timeline
- Resolved · Jan 24, 00:27 UTC
Backlog has been processed and crons should be running as normal
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.