Satori incident

Multiple DAC and Management Console Issues

Major Resolved View vendor source →

Satori experienced a major incident on September 24, 2025 affecting Management Console and Satori DAC AWS us-east-1 (N. Virginia) and 1 more component, lasting 1d 6h. The incident has been resolved; the full update timeline is below.

Started
Sep 24, 2025, 10:26 AM UTC
Resolved
Sep 25, 2025, 05:21 PM UTC
Duration
1d 6h
Detected by Pingoru
Sep 24, 2025, 10:26 AM UTC

Affected components

Management ConsoleSatori DAC AWS us-east-1 (N. Virginia)Satori DAC AWS us-west-2 (Oregon)Satori DAC AWS eu-central-1 (Frankfurt)Satori DAC AWS eu-west-1 (Ireland)Satori DAC GCP eu-west2 (London)Satori DAC GCP us-east1 (S. Carolina)Satori DAC AWS ap-southeast-1 (Singapore)Satori DAC Azure eastus-2 (Virginia)Customer Hosted DAC

Update timeline

  1. investigating Sep 24, 2025, 10:26 AM UTC

    Our monitoring systems have detected several failures in DACs and the Management Console.

  2. investigating Sep 24, 2025, 10:28 AM UTC

    We are continuing to investigate this issue.

  3. identified Sep 24, 2025, 10:57 AM UTC

    The issue is likely related to an outage in Google DNS, which is used by Satori services. We are working to identify the scope of the outage and considering failing over to an alternative DNS service.

  4. identified Sep 24, 2025, 11:52 AM UTC

    We are now focused on a DNS registrar issue. We will send an additional update in an hour.

  5. monitoring Sep 24, 2025, 01:34 PM UTC

    We have implemented a fix and are monitoring the results. Some services are up.

  6. monitoring Sep 24, 2025, 01:42 PM UTC

    All services have been restored, however, several users still report an issue resolving Satori domain names. This indicates to DNS updates propagation that may take some time to complete. Users can clear their DNS cache to try and speed up the process.

  7. monitoring Sep 24, 2025, 04:31 PM UTC

    We have confirmed that all systems and services are operational. However, some users still get stale DNS entries due to caching. Clearing local DNS caches may help resolve the issue; however, some DNS caching occurs at layers beyond users' workstations which prolong the impact of the incident. The team is monitoring global DNS propagation and confims some regions are still impacted.

  8. monitoring Sep 25, 2025, 07:27 AM UTC

    We see improvement in global DNS propagation. Customers who are still experiencing issues should open a support ticket.

  9. resolved Sep 25, 2025, 05:21 PM UTC

    This incident has been resolved. Customers who are still experiencing issues should open a support ticket. Clearing the browser or workstation DNS cache is recommended for users who still experience issues.