Infoblox incident

DNS resolution issue in multiple PoP locations for our legacy anycast solution (52.119.40.100 & 103.80.5.100)

Minor Resolved View vendor source →

Infoblox experienced a minor incident on July 23, 2025 affecting DNS Resolution - Virginia, US and DNS Resolution - Ohio, US and 1 more component, lasting 1h 37m. The incident has been resolved; the full update timeline is below.

Started
Jul 23, 2025, 02:50 AM UTC
Resolved
Jul 23, 2025, 04:27 AM UTC
Duration
1h 37m
Detected by Pingoru
Jul 23, 2025, 02:50 AM UTC

Affected components

DNS Resolution - Virginia, USDNS Resolution - Ohio, USDNS Resolution - California, USDNS Resolution - Toronto, CADNS Resolution - Singapore, SGDNS Resolution - Sydney, AUDNS Resolution - Frankfurt, DEDNS Resolution - London, GBDNS Resolution - South Africa, ZA

Update timeline

  1. investigating Jul 23, 2025, 02:50 AM UTC

    We are currently investigating an issue affecting DNS resolution across multiple PoP locations. Our team is working diligently to identify the root cause and implement a timely solution. We apologize for any inconvenience this may be causing. Impact: Some customers forwarding DNS traffic to our Global Anycast IP addresses (52.119.40.100 and 103.80.5.100) may experience slight DNS latency. Additionally, some NIOS-X servers may display a Platform Management Error status. We will continue to provide updates as the investigation and resolution progress. If you are experiencing service impact or require further assistance, please contact our support team at https://support.infoblox.com.

  2. monitoring Jul 23, 2025, 04:01 AM UTC

    We have observed that, in addition to the intermittent resolution issues affecting our legacy Anycast solution (52.119.40.100 and 103.80.5.100), similar intermittent DNS resolution issues were also identified on (52.119.41.100 and 103.80.6.100). A fix has been implemented, and we are monitoring the results.

  3. resolved Jul 23, 2025, 04:27 AM UTC

    This incident has been resolved.