Sanai incident

Tenants not accessible due to latent DNS Migration issue.

Minor Resolved View vendor source →

Sanai experienced a minor incident on July 20, 2026 affecting US Region – Sanai application and US Region – Sanai API and 1 more component, lasting 1h 16m. The incident has been resolved; the full update timeline is below.

Started
Jul 20, 2026, 05:45 PM UTC
Resolved
Jul 20, 2026, 07:02 PM UTC
Duration
1h 16m
Detected by Pingoru
Jul 20, 2026, 05:45 PM UTC

Affected components

US Region – Sanai applicationUS Region – Sanai APIUS Region – Integrations

Update timeline

  1. investigating Jul 20, 2026, 05:45 PM UTC

    Status: Investigating The suspected impact is that all customer tenants cannot be accessed due to a DNS issue. The team is investigating and will continue to update as progress is made. Affected components US Region – Sanai API (Full outage) US Region – Sanai application (Full outage) US Region – Integrations (Full outage)

  2. identified Jul 20, 2026, 06:20 PM UTC

    Status: Identified We've identified the issue as a failed DNS migration and are currently working to resolve it. Affected components US Region – Sanai API (Full outage) US Region – Sanai application (Full outage) US Region – Integrations (Full outage)

  3. resolved Jul 20, 2026, 07:02 PM UTC

    Status: Resolved DNS functionality has been restored, and all customer tenants are now accessible. Affected components US Region – Sanai application (Operational) US Region – Integrations (Operational) US Region – Sanai API (Operational)