Jul 11, 03:34 UTC
Resolved - We have processed the backlog. Jul 11, 03:28 UTC
Monitoring - We have processed the majority of our backlog. We are now recovering the tail of the backlog. Jul 11, 02:37 UTC
Update - We have processed the majority of our backlog. We are now recovering an additional 25M error events ranging from 22:20 to 23:20 UTC, which should complete in the next 2 hours Jul 11, 01:46 UTC
Update - We expect recovery of historical data to be complete within the next 2 hours. Jul 11, 00:56 UTC
Update - We are still working on recovery. New errors should be processed in real time, and we are working on recovering historical data. Jul 11, 00:04 UTC
Update - We have identified the problem and are working on recovery.New errors are being processed in real time and we are in the process of consuming backlogged errors. Jul 10, 23:02 UTC
Identified - We have identified the problem and are working on a fix, ingested errors are delayed and will be processed once the fix is in place. Jul 10, 22:43 UTC
Investigating - We are currently investigating this issue.
We have processed the backlog.
Posted Jul 11, 2026 - 03:34 UTC
We have processed the majority of our backlog. We are now recovering the tail of the backlog.
Posted Jul 11, 2026 - 03:28 UTC
We have processed the majority of our backlog. We are now recovering an additional 25M error events ranging from 22:20 to 23:20 UTC, which should complete in the next 2 hours
Posted Jul 11, 2026 - 02:37 UTC
We expect recovery of historical data to be complete within the next 2 hours.
Posted Jul 11, 2026 - 01:46 UTC
We are still working on recovery. New errors should be processed in real time, and we are working on recovering historical data.
Posted Jul 11, 2026 - 00:56 UTC
We have identified the problem and are working on recovery.
New errors are being processed in real time and we are in the process of consuming backlogged errors.
Posted Jul 11, 2026 - 00:04 UTC
We have identified the problem and are working on a fix, ingested errors are delayed and will be processed once the fix is in place.
Posted Jul 10, 2026 - 23:02 UTC
We are currently investigating this issue.
Posted Jul 10, 2026 - 22:43 UTC
| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | Delayed Error ingestion in our US region | 0 | 8.32 | 12-08-2026 |
| 2 | Delayed Error ingestion in our US region | 0 | 7.62 | 06-08-2026 |
| 3 | Error ingestion delays in US | 0 | 8.88 | 12-08-2026 |
| 4 | Error and profile ingestion issues in US | 0 | 6.14 | 27-07-2026 |
| 5 | Delayed ingestion on us region | 0 | 7.38 | 21-07-2026 |
| 6 | Ingestion and query issues for logs, spans, traces in US | 0 | 7.58 | 01-07-2026 |
| 7 | Ingestion delayed for spans, logs, crons in US region | 0 | 7.45 | 13-07-2026 |
| 8 | Ingestion delays in US | 0 | 7.4 | 13-07-2026 |
| 9 | EU Region Error, Attachment, and Feedback latency | 0 | 5.5 | 20-07-2026 |
| 10 | Span & Transaction ingestion delayed in DE | 0 | 6.95 | 13-08-2026 |