2026-02-04 Dataset Staleness in Sydney Region
Feb 4, 21:43 UTCFeb 5, 01:02 UTC
Duration
3h 19m
Impact
Critical
Root cause
Not disclosed
Observe, 90 days
10 incidents
Affected
Not listed by the vendor.
Final update
This incident has been resolved.
Timeline
- Resolved · Feb 5, 01:02 UTC
This incident has been resolved.
- Monitoring · Feb 5, 00:17 UTC
We have worked with Snowflake to resolve the upstream outage, and the Sydney (AU-1) region has now recovered. Query capabilities and monitors are returning to normal, and we have confirmed that no data loss occurred during this event. We are currently monitoring the environment to ensure continued stability.
- Identified · Feb 4, 23:02 UTC
We have identified the root cause of the service disruption in the Sydney (AU-1) region as an upstream outage with Snowflake. This is currently impacting data ingestion, resulting in dataset staleness; however, no data loss is occurring. Additionally, users will find that monitors are not firing and query capabilities are currently unavailable. Our engineering team is actively working to mitigate these impacts, and we will provide further updates as the recovery progresses.
- Investigating · Feb 4, 21:43 UTC
Observe is experiencing some dataset staleness in the Deployment. Users may experience higher ingest latency/data staleness. No data loss is occurring. We have identified the root cause and will provide further updates as we learn more.
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