Incidentsby GlyphIngest performance degradation
Sep 3, 22:47 UTCSep 4, 01:35 UTC
Duration
2h 49m
Impact
Major
Root cause
Not disclosed
Observe, 90 days
10 incidents
Affected
Not listed by the vendor.
Final update
This incident has been resolved.
Timeline
- Resolved · Sep 4, 01:35 UTC
This incident has been resolved.
- Monitoring · Sep 3, 23:58 UTC
We are seeing recovery of ingestion and are continuing to monitor it's progress.
- Identified · Sep 3, 22:47 UTC
We have identified a problem with our upstream service provider, AWS that is causing delays in processing data that has been ingested. Our system will queue the data until it is able to be processed and no data loss is expected. Alerts from monitors will be delayed due to the delay in shaping ingested data. See reference to Multiple Services (Oregon) at https://health.aws.amazon.com/health/status
- Investigating · Sep 3, 22:16 UTC
We are continuing to investigate this issue.
- Investigating · Sep 3, 22:15 UTC
We are currently aware of degradation in ingest performance. Impact and resolution are being assessed. We will provide an update as soon as we have additional details.
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