Cisco Secure Access incident

[Cisco Secure Access] – DNS response latency in Amsterdam

Minor Resolved View vendor source →

Cisco Secure Access experienced a minor incident on June 23, 2026 affecting DNS, lasting 33m. The incident has been resolved; the full update timeline is below.

Started
Jun 23, 2026, 03:34 PM UTC
Resolved
Jun 23, 2026, 04:08 PM UTC
Duration
33m
Detected by Pingoru
Jun 23, 2026, 03:34 PM UTC

Affected components

DNS

Update timeline

  1. investigating Jun 23, 2026, 03:34 PM UTC

    We are investigating increased DNS response latency affecting DNS resolution services in Amsterdam. Customers using DNS resolution services through Amsterdam may experience delayed DNS responses while we investigate. Our engineering team is actively working to identify the cause and restore normal service performance.

  2. resolved Jun 23, 2026, 04:08 PM UTC

    The increased DNS response latency affecting DNS resolution services in Amsterdam has been resolved. Customers using DNS resolution services through Amsterdam should no longer experience delayed DNS responses related to this issue.Service has been restored to normal operation. We’re Here to Help If you have any questions or need assistance, please contact our support team.