Live  /  Observe  /  Incident

Observe: 2026-10-05 Delayed or missing data from poller-based integrations

Observe · observeinc.comMajor incidentResolved2026-10-05 22:55 UTC
Public — what happened

Summary

Observe reported a major issue beginning at 21:53 UTC on 2026-10-05 in which data gathered through its polling-based integrations, such as AWS CloudWatch metrics, could arrive late or not at all. The company said other ways of sending data in, including OpenTelemetry logs and traces, Prometheus, Kubernetes and filedrop, were working normally, and customers did not need to take any action. At 22:42 UTC Observe said it had found the cause, though it did not describe it, and had put a mitigation in place that got polling-based collection running again. It then watched for stability and checked on recovery of delayed data before marking the incident resolved at 22:55.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Observe against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Observe: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Observe report →

More from Observe

Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.

The full archive is on the Observe status & history page.

Related: Observe status & history. SquidGrid is not affiliated with Observe.