Omnata incident

Native Applications outage

Critical Resolved View vendor source →

Omnata experienced a critical incident on February 25, 2026 affecting Omnata Sync Engine, lasting 6h 19m. The incident has been resolved; the full update timeline is below.

Started
Feb 25, 2026, 01:36 AM UTC
Resolved
Feb 25, 2026, 07:56 AM UTC
Duration
6h 19m
Detected by Pingoru
Feb 25, 2026, 01:36 AM UTC

Affected components

Omnata Sync Engine

Update timeline

  1. investigating Feb 25, 2026, 01:36 AM UTC

    Several customers have reported that their native applications are not loading due to a missing package version. We have raised a support ticket with Snowflake to investigate.

  2. investigating Feb 25, 2026, 02:25 AM UTC

    The Snowflake engineering team are continuing their investigation

  3. monitoring Feb 25, 2026, 05:10 AM UTC

    Snowflake have advised that the issue should be resolved. We are currently confirming this with customers.

  4. monitoring Feb 25, 2026, 05:46 AM UTC

    Some customers are reporting restoration of service, others are still experiencing downtime. Snowflake have advised that the issue should resolve in remaining accounts over the next two hours.

  5. resolved Feb 25, 2026, 07:56 AM UTC

    This incident has been resolved.

  6. postmortem Feb 26, 2026, 05:01 AM UTC

    RCA provided by Snowflake: > Between 22:59 UTC on February 24 and approximately 04:30 UTC on February 25, 2026, an internal configuration update in Snowflake’s Native Apps platform caused some Native Apps and SPCS-based connectors to fail to activate correctly. This resulted in failed or stuck tasks and telemetry injection failures for a subset of customers in affected regions. The configuration change was rolled back globally, and Native App replication tasks were refreshed. At this time, the platform is operating normally, and any remaining impact for customers with infrequently scheduled refreshes has been addressed by targeted manual refreshes.