Historial de interrupciones de Infoblox

1. July 31, 2026 at 5:29 PM UTCinvestigating

   Actualmente estamos experimentando una red de tráfico DNS para el servicio Infoblox Threat Defense Cloud en nuestro sitio Mumbai. Impacto: Los clientes que intentan conectarse a nuestras direcciones IP Global Anycast 52.119.40.100 y 103.80.4.100 pueden experimentar que el tráfico está siendo redirigido a los próximos sitios más cercanos. No se espera ninguna interrupción del servicio. Nota: Las direcciones IP Global Anycast 52.119.41.100 y 103.80.6.100 siguen funcionando normalmente y no son impactadas por este desvío de tráfico.

2. July 31, 2026 at 7:36 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

3. July 31, 2026 at 7:51 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 14, 2026 at 4:21 PM UTCinvestigating

   Actualmente estamos investigando una cuestión que afecta al DDI Universal en la Europa https://portal.eu.infoblox.com. Impacto: Las demoras pueden ocurrir para cambios de registro DNS realizados en el Portal Infoblox. Esto incluye crear, actualizar y eliminar operaciones que pueden no propagarse a servidores NIOS-X y NIOS-X como servicio. No hay impacto en los servicios de protocolo DNS en este momento. Estamos trabajando activamente para identificar la causa raíz y aplicar una resolución. Seguiremos proporcionando actualizaciones a medida que se disponga de más información. Si está experimentando algún impacto de producción relacionado con este problema, póngase en contacto con Infoblox Support.

2. July 14, 2026 at 5:31 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

3. July 14, 2026 at 5:57 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 9, 2026 at 6:43 AM UTCinvestigating

   Estamos investigando un problema intermitente que afecta el acceso al Portal Infoblox y a la API en la región de la UE (portal.eu.infoblox.com). Algunos clientes pueden experimentar dificultades para acceder tanto al portal como a la API. Nuestro equipo está trabajando activamente para identificar la causa raíz y restaurar el acceso normal lo antes posible.

2. July 9, 2026 at 6:52 AM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

3. July 9, 2026 at 7:07 AM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 30, 2026 at 2:19 PM 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. June 30, 2026 at 8:57 PM UTCinvestigating

   We are continuing to investigate this issue.

3. June 30, 2026 at 10:55 PM UTCidentified

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

4. June 30, 2026 at 11:28 PM UTCmonitoring

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

5. June 30, 2026 at 11:52 PM UTCresolved

   This incident has been resolved.

1. June 8, 2026 at 12:53 PM 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. June 8, 2026 at 1:30 PM 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. June 8, 2026 at 2:31 PM 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. June 8, 2026 at 2:32 PM UTCmonitoring

   We are continuing to monitor for any further issues.

5. June 8, 2026 at 3:29 PM UTCresolved

   This incident has been resolved.

1. June 2, 2026 at 3:15 PM 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. June 2, 2026 at 5:09 PM UTCidentified

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

3. June 2, 2026 at 8:28 PM UTCmonitoring

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

4. June 2, 2026 at 10:49 PM UTCresolved

   This incident has been resolved.

1. May 20, 2026 at 9:02 AM 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. May 20, 2026 at 11:41 AM UTCmonitoring

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

3. May 20, 2026 at 1:04 PM UTCresolved

   This incident has been resolved.

1. May 15, 2026 at 8:05 PM 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. May 15, 2026 at 8:05 PM UTCresolved

   This incident has been resolved.

1. May 12, 2026 at 4:33 PM 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. May 12, 2026 at 5:14 PM 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. May 12, 2026 at 6:11 PM UTCresolved

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

1. April 23, 2026 at 7:06 AM 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. April 22, 2026 at 2:25 PM 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. April 22, 2026 at 2:27 PM UTCresolved

   This incident has been resolved.

1. March 11, 2026 at 1:09 AM 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. March 11, 2026 at 1:30 AM UTCmonitoring

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

3. March 11, 2026 at 1:56 AM UTCmonitoring

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

4. March 11, 2026 at 2:14 AM UTCresolved

   This incident has been resolved.

1. March 2, 2026 at 5:43 AM 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. March 2, 2026 at 10:54 PM 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. March 4, 2026 at 5:46 PM 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. March 19, 2026 at 1:10 AM 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. February 23, 2026 at 3:42 PM 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. February 23, 2026 at 4:01 PM UTCmonitoring

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

3. February 23, 2026 at 5:41 PM UTCresolved

   This incident has been resolved.

1. January 27, 2026 at 7:55 PM 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. January 27, 2026 at 8:23 PM 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. January 27, 2026 at 8:49 PM UTCresolved

   This incident has been resolved.

1. January 27, 2026 at 3:19 PM 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. January 27, 2026 at 3:57 PM 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. January 27, 2026 at 5:29 PM UTCresolved

   This incident has been resolved.

1. January 26, 2026 at 3:48 AM 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. January 26, 2026 at 4:39 AM UTCinvestigating

   We are continuing to investigate this issue.

3. January 26, 2026 at 5:47 AM UTCinvestigating

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

4. January 26, 2026 at 7:19 AM 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. January 26, 2026 at 8:09 AM UTCresolved

   This incident has been resolved.

1. January 23, 2026 at 2:31 PM 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. January 14, 2026 at 5:25 AM 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. December 4, 2025 at 5:44 PM 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. December 4, 2025 at 6:15 PM UTCmonitoring

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

3. December 4, 2025 at 6:46 PM UTCresolved

   This incident has been resolved.