Infoblox incident

Infoblox Threat Defense Service Degradation - DNS resolution issues

Major Resolved View vendor source →

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

Started
Aug 08, 2025, 06:44 PM UTC
Resolved
Aug 08, 2025, 08:09 PM UTC
Duration
1h 24m
Detected by Pingoru
Aug 08, 2025, 06:44 PM UTC

Affected components

DNS Resolution - Virginia, USDNS Resolution - Ohio, USDNS Resolution - California, USDNS Resolution - São Paulo, BrazilDNS Resolution - Toronto, CADNS Resolution - Tokyo, JPDNS Resolution - Singapore, SGDNS Resolution - Sydney, AUDNS Resolution - Mumbai, INDNS Resolution - Hyderabad, IN

Update timeline

  1. investigating Aug 08, 2025, 06:44 PM UTC

    We are investigating an issue affecting DNS resolution in multiple PoP locations. Our team is working diligently to identify the root cause and implement a solution quickly. We apologize for any inconvenience this may be causing. Impact: Some customers that are forwarding DNS traffic to our Global Anycast IP addresses (52.119.40.100 & 103.80.5.100) may experience slight DNS latency issues due to this. Additionally, some NIOS-X servers may Platform Management error status. We will provide updates on the progress of the investigation and resolution.

  2. identified Aug 08, 2025, 07:18 PM UTC

    The issue has been identified, and we are currently working on applying the necessary fix with high priority. We appreciate your patience and will keep you informed of further progress.

  3. monitoring Aug 08, 2025, 07:50 PM UTC

    The identified issue has been addressed, and the fix has been successfully applied. We are currently monitoring the results to ensure stability and effectiveness. Further updates will be shared as we progress.

  4. resolved Aug 08, 2025, 08:09 PM UTC

    We have successfully applied the fix for the reported issue, and post-resolution monitoring confirms that the system is stable and functioning as expected. The incident is now considered resolved. Thank you for your patience and cooperation.