Störungsverlauf von Infoblox

1. 31. Juli 2026 um 17:29 UTCinvestigating

   Wir erleben derzeit eine DNS-Traffic-Umleitung für den Infoblox Threat Defense Cloud-Dienst an unserem Standort in Mumbai. Auswirkungen: Kunden, die versuchen, eine Verbindung zu unseren globalen Anycast-IP-Adressen 52.119.40.100 und 103.80.4.100 herzustellen, können feststellen, dass der Datenverkehr zu den nächstgelegenen Standorten umgeleitet wird. Es wird keine Betriebsunterbrechung erwartet. Hinweis: Die Global Anycast IP-Adressen 52.119.41.100 und 103.80.6.100 funktionieren weiterhin normal und sind von dieser Verkehrsumleitung nicht betroffen.

2. 31. Juli 2026 um 19:36 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

3. 31. Juli 2026 um 19:51 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 14. Juli 2026 um 16:21 UTCinvestigating

   Wir untersuchen derzeit ein Problem mit Universal DDI in Europa https://portal.eu.infoblox.com. Auswirkungen: Es kann zu Verzögerungen bei DNS-Datensatzänderungen kommen, die im Infoblox-Portal vorgenommen wurden. Dies umfasst das Erstellen, Aktualisieren und Löschen von Vorgängen, die möglicherweise nicht auf NIOS-X-Server und NIOS-X als Dienst übertragen werden. Es gibt derzeit keine Auswirkungen auf DNS-Protokolldienste. Wir arbeiten aktiv daran, die Ursache zu identifizieren und eine Lösung umzusetzen. Wir werden weiterhin Updates bereitstellen, sobald mehr Informationen verfügbar sind. Wenn Sie Auswirkungen auf die Produktion im Zusammenhang mit diesem Problem haben, wenden Sie sich bitte an den Infoblox-Support.

2. 14. Juli 2026 um 17:31 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

3. 14. Juli 2026 um 17:57 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 9. Juli 2026 um 06:43 UTCinvestigating

   Wir untersuchen ein intermittierendes Problem, das den Zugriff auf das Infoblox-Portal und die API in der EU-Region betrifft (portal.eu.infoblox.com). Einige Kunden können Schwierigkeiten haben, sowohl auf das Portal als auch auf die API zuzugreifen. Unser Team arbeitet aktiv daran, die Ursache zu identifizieren und den normalen Zugriff so schnell wie möglich wiederherzustellen.

2. 9. Juli 2026 um 06:52 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

3. 9. Juli 2026 um 07:07 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 30. Juni 2026 um 14:19 UTCinvestigating

   We are currently investigating an issue affecting the On-Prem and Cloud Discovery Sync jobs. Impact: Delay in populating newly discovered objects in the Infoblox Portal (North America: https://portal.infoblox.com). All other services remain fully operational, and there is no impact to protocol services. We will continue to provide updates as we progress with the investigation and work toward a resolution.

2. 30. Juni 2026 um 20:57 UTCinvestigating

   We are continuing to investigate this issue.

3. 30. Juni 2026 um 22:55 UTCidentified

   The issue has been identified and a fix is being implemented.

4. 30. Juni 2026 um 23:28 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

5. 30. Juni 2026 um 23:52 UTCresolved

   This incident has been resolved.

1. 8. Juni 2026 um 12:53 UTCinvestigating

   We are investigating an issue with some NIOS-X servers in the NA Region "https://portal.infoblox.com" going to "Degraded" status. We are actively working to fix the issue as soon as possible and will provide updates on the situation as we make progress. If you are experiencing a service impact or require further assistance, kindly contact our support team at https://support.infoblox.com/.

2. 8. Juni 2026 um 13:30 UTCinvestigating

   Some customers may encounter service disruptions on their NIOS and NIOS-X servers due to this issue. We are diligently investigating the root cause and working to restore full functionality as quickly as possible.

3. 8. Juni 2026 um 14:31 UTCmonitoring

   A fix has been implemented in both NA Region "https://portal.infoblox.com" and EU Region "https://portal.eu.infoblox.com" and we are monitoring the results.

4. 8. Juni 2026 um 14:32 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 8. Juni 2026 um 15:29 UTCresolved

   This incident has been resolved.

1. 2. Juni 2026 um 15:15 UTCinvestigating

   We are currently investigating an issue affecting the Asset Discovery Sync job, which is causing delays in populating newly discovered objects in the Infoblox Portal (North America): https://portal.infoblox.com. All other services remain fully operational, and there is no impact to protocol services. We will continue to provide updates as we progress with the investigation and work toward a resolution.

2. 2. Juni 2026 um 17:09 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 2. Juni 2026 um 20:28 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 2. Juni 2026 um 22:49 UTCresolved

   This incident has been resolved.

1. 20. Mai 2026 um 09:02 UTCinvestigating

   We are currently investigating an issue affecting the NIOS‑X server Metrics API. Customers may observe delayed or stale metric data being returned through Metrics API calls. We are actively working to mitigate the issue. We will provide further updates as the investigation and resolution progress.

2. 20. Mai 2026 um 11:41 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 20. Mai 2026 um 13:04 UTCresolved

   This incident has been resolved.

1. 15. Mai 2026 um 20:05 UTCinvestigating

   We observed that multiple NIOS-X servers briefly entered a degraded state. There was no service impact, and all services continued to operate normally. The issue was caused by a temporary health-check failure on the hosts. All servers have now fully recovered, and services continue to operate normally. If you experience any issues, please contact Infoblox Support.

2. 15. Mai 2026 um 20:05 UTCresolved

   This incident has been resolved.

1. 12. Mai 2026 um 16:33 UTCinvestigating

   We are investigating an intermittent issue affecting access to the Infoblox Portal in the EU region (portal.eu.infoblox.com) Some customers may experience difficulties accessing the portal. Our team is actively working to identify the root cause and restore normal access as quickly as possible.

2. 12. Mai 2026 um 17:14 UTCmonitoring

   The Infoblox Portal (csp.eu.infoblox.com) is operating normally, and the issue appears to be related to external network connectivity outside the Infoblox infrastructure. We are continuing to investigate and monitor the situation closely.

3. 12. Mai 2026 um 18:11 UTCresolved

   The issue has been resolved, and the affected URLs are now accessible.

1. 23. April 2026 um 07:06 UTCresolved

   Between April 29 and May 6 (UTC) 2026, phased upgrades will be performed on NIOS-X server platform components. These updates will follow the ‘Schedule Software Updates’ configuration set in the Infoblox Portal. Impact: During this period, NIOS-X servers connected to Infoblox Portals North America (https://portal.infoblox.com) and Europe (https://portal.eu.infoblox.com) may intermittently report an unhealthy status, with each occurrence lasting up to 2–3 minutes. All other services will remain unaffected, and there will be no impact on protocol services.

1. 22. April 2026 um 14:25 UTCinvestigating

   We are investigating a partial traffic rerouting issue in Singapore. We apologize for any inconvenience this may cause and assure you that our team is actively working to resolve it as quickly as possible. Impact: Customers attempting to connect to our Global Anycast IP addresses (52.119.40.100 & 103.80.5.100) may experience traffic being rerouted to the nearest locations. Please note that no service interruption is expected. If you are experiencing a service impact or require further assistance, please contact our support team at https://support.infoblox.com/

2. 22. April 2026 um 14:27 UTCresolved

   This incident has been resolved.

1. 11. März 2026 um 01:09 UTCinvestigating

   We are investigating an issue with delay in accessing the Infoblox Portal in North America Region (portal.infoblox.com). We are actively working to fix the issue as soon as possible and will provide updates on the situation as we make progress.

2. 11. März 2026 um 01:30 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 11. März 2026 um 01:56 UTCmonitoring

   We also observed an increase in the number of NIOS‑X servers entering a degraded state during the incident window.

4. 11. März 2026 um 02:14 UTCresolved

   This incident has been resolved.

1. 2. März 2026 um 05:43 UTCinvestigating

   We will be rerouting the DNS traffic from Bahrain site to the nearest sites due to ongoing AWS issue. We apologize for any inconvenience this may cause and traffic will be moved back as soon as the AWS issue is resolved. Impact: Customers attempting to connect to our Global and Regional Anycast IP addresses (52.119.41.100, 52.119.41.61, 103.80.6.100 & 103.80.6.61) may experience traffic being rerouted to the nearest sites. Please note that no service interruption is expected. If you are experiencing a service impact or require further assistance, please contact our support team at https://support.infoblox.com/

2. 2. März 2026 um 22:54 UTCinvestigating

   We will continue to reroute DNS traffic from the Bahrain site to the nearest available PoPs to avoid any service interruption until AWS restores services in the affected region. If you are experiencing a service impact or require further assistance, please contact our support team at https://support.infoblox.com/

3. 4. März 2026 um 17:46 UTCinvestigating

   AWS is still working to restore services in the affected Bahrain region. In the meantime, we will continue rerouting DNS traffic from Bahrain to the nearest available PoPs to prevent any service interruption until AWS has fully recovered the region. If you are experiencing a service impact or require further assistance, please contact our support team at https://support.infoblox.com/

4. 19. März 2026 um 01:10 UTCresolved

   We will continue to reroute DNS traffic from the Bahrain site to the nearest available sites to avoid any service interruption until AWS restores services in the affected region. Please follow the KB article - https://support.infoblox.com/s/article/DNS-Traffic-Rerouting-Due-to-AWS-Issue-in-Bahrain-Region for latest details. If you are experiencing a service impact or require further assistance, please contact our support team at https://support.infoblox.com/

1. 23. Februar 2026 um 15:42 UTCinvestigating

   We are investigating an issue with some NIOS-X servers in the NA Region "https://portal.infoblox.com" going to "Degraded" status. We are actively working to fix the issue as soon as possible and will provide updates on the situation as we make progress. There will be no impact on services enabled on the NIOS-X servers. If you are experiencing a service impact or require further assistance, kindly contact our support team at https://support.infoblox.com/.

2. 23. Februar 2026 um 16:01 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 23. Februar 2026 um 17:41 UTCresolved

   This incident has been resolved.

1. 27. Januar 2026 um 19:55 UTCinvestigating

   We are currently investigating an issue affecting Infoblox endpoint connectivity. Our team is working to identify the root cause and implement a fix as quickly as possible. Impact: Some customers may experience issues accessing Infoblox endpoints page and observe their Infoblox endpoints entering an Unprotected state. However, DNS resolution is expected to continue functioning normally. We will provide further updates as the investigation and resolution progress.

2. 27. Januar 2026 um 20:23 UTCmonitoring

   A fix has been implemented and we are monitoring the results. The issues with accessing the Infoblox Endpoints page and endpoints showing an Unprotected state have been resolved.

3. 27. Januar 2026 um 20:49 UTCresolved

   This incident has been resolved.

1. 27. Januar 2026 um 15:19 UTCinvestigating

   We are currently investigating an issue affecting Infoblox endpoint connectivity. Our team is working to identify the root cause and implement a fix as quickly as possible. Impact: Some customers may experience issues accessing Infoblox endpoints page and observe their Infoblox endpoints entering an Unprotected state. However, DNS resolution is expected to continue functioning normally. We will provide further updates as the investigation and resolution progress.

2. 27. Januar 2026 um 15:57 UTCmonitoring

   A fix has been implemented and we are monitoring the results. The issues with accessing the Infoblox Endpoints page and endpoints showing an Unprotected state have been resolved.

3. 27. Januar 2026 um 17:29 UTCresolved

   This incident has been resolved.

1. 26. Januar 2026 um 03:48 UTCinvestigating

   We are experiencing an issue with Universal DDI in the North America region, where customers may encounter problems with Create, Update, or Delete operations for DNS resource records. As a result, these changes may not propagate correctly to NIOS-X servers.

2. 26. Januar 2026 um 04:39 UTCinvestigating

   We are continuing to investigate this issue.

3. 26. Januar 2026 um 05:47 UTCinvestigating

   We are continuing to investigate the issue. If you are experiencing any production impact related to this issue, please contact Infoblox Support.

4. 26. Januar 2026 um 07:19 UTCmonitoring

   A fix has been deployed, and new DNS record Create, Update, and Delete operations are now propagating correctly to NIOS-X servers. We are continuing to monitor the service. If you are experiencing any production impact, please contact Infoblox Support.

5. 26. Januar 2026 um 08:09 UTCresolved

   This incident has been resolved.

1. 23. Januar 2026 um 14:31 UTCresolved

   This scheduled maintenance is a continuation of the previously announced NIOS-X server platform upgrades from January 19 to January 23 (UTC). For more details, refer to the earlier notification: https://status.infoblox.com/incidents/yzmr4l8wf8f0. To complete the remaining phases of the maintenance, the upgrades will continue during an extended maintenance window between January 27 and January 30 (UTC). The updates will follow the “Schedule Software Updates” configuration set in the Infoblox Portal. Impact: During this period, NIOS-X servers connected to Infoblox Cloud (https://portal.infoblox.com) may report an unhealthy status a couple of times, each lasting up to 2–3 minutes. All other services will remain unaffected, and there will be no impact on protocol services.

1. 14. Januar 2026 um 05:25 UTCresolved

   Between January 19 and 23 (UTC), phased upgrades will be performed on NIOS-X server platform components. These updates will follow the ‘Schedule Software Updates’ configuration set in the Infoblox Portal. Impact: During this period, NIOS-X servers connected to Infoblox Cloud [https://portal.infoblox.com & https://portal.eu.infoblox.com] may report an unhealthy status a couple of times, each lasting up to 2–3 minutes. All other services will remain unaffected, and there will be no impact on protocol services.

1. 4. Dezember 2025 um 17:44 UTCinvestigating

   We are currently investigating an issue where certain domains are not resolving as expected. Initial analysis indicates that this behavior occurred because the domains were included in the security feed, which temporarily impacted their resolution. The domain a01.azurefd.net was present in the feed and has now been removed. If you continue to experience resolution issues for any domain, please follow the steps in the article below to add the affected domains to a custom allow list: https://support.infoblox.com/s/article/4005 We will continue monitoring to ensure stability.

2. 4. Dezember 2025 um 18:15 UTCmonitoring

   With no further anomalies detected, we are moving the case into a monitoring phase.

3. 4. Dezember 2025 um 18:46 UTCresolved

   This incident has been resolved.