Incidentsby Glyph2025-08-08 - Ingest Latency - US East (N. Virginia)
Aug 8, 14:41 UTCAug 8, 17:11 UTC
Duration
2h 30m
Impact
Informational
Root cause
Not disclosed
Observe, 90 days
10 incidents
Affected
Not listed by the vendor.
Final update
This incident has been resolved.
Timeline
- Resolved · Aug 8, 17:11 UTC
This incident has been resolved.
- Monitoring · Aug 8, 15:57 UTC
The ingest latency has reached normal levels. We will monitor latency for the next hour and close the incident if the levels remain stable.
- Identified · Aug 8, 15:36 UTC
The issue has been identified and the ingest latency is currently decreasing. Long warehouse resume times were causing delays in ingest. The team is working to mitigate the resume times and are taking steps to aid in system recovery.
- Investigating · Aug 8, 14:41 UTC
We’ve identified an issue causing ingest latency in the US East (N. Virginia) region. As a result, some users may experience staleness in isolated datasets and potential delays in triggering alerts on the data. No data loss is expected. Our team is actively investigating the root cause and working to restore normal performance as quickly as possible. We’ll provide updates as we learn more. Thank you for your patience!
More from Observe
Full history2026-10-12 Degraded Function For OPAL Copilot in Slow-lane Customer Instanceslasted 8h 45m2026-10-06 Degraded warehouse resume performancelasted 2h 55m2026-10-05 Delayed or missing data from poller-based integrationslasted 1h 3m2026-09-27 Data Transform and Monitor Processing Delays (US-WEST)lasted 1h 46m2026-09-21 Degradation in AI functionalitylasted 23h 31m2026-09-04 Performance degradation in EUlasted 1h 51m