Infoblox 장애 기록

1. 2026년 7월 31일 PM 5:29 UTCinvestigating

   현재 뭄바이 사이트에서 Infoblox Threat Defense Cloud 서비스에 대한 DNS 트래픽 재 루트를 경험하고 있습니다. 충격: 우리의 Global Anycast IP 주소 52.119.40.100 및 103.80.4.100에 연결하는 고객은 다음 가장 가까운 사이트에 다시 접근 할 수 있습니다. 서비스 중단은 예상되지 않습니다. 참고 : Global Anycast IP 주소 52.119.41.100 및 103.80.6.100은 일반적으로 작동하고이 트래픽 reroute에 영향을 미치지 않습니다.

2. 2026년 7월 31일 PM 7:36 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

3. 2026년 7월 31일 PM 7:51 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 14일 PM 4:21 UTCinvestigating

   우리는 현재 유럽에서 Universal DDI에 영향을 미치는 이슈를 조사하고 있습니다 https://portal.eu.infoblox.com. Impact: Delays는 Infoblox Portal에서 만든 DNS 레코드 변경을 위해 발생할 수 있습니다. NIOS-X 서버와 NIOS-X를 서비스로 전파하지 않을 수 있습니다. 이 시간에 DNS 프로토콜 서비스에 영향을 미치지 않습니다. 우리는 뿌리 원인을 확인하고 해결책을 구현하기 위해 적극적으로 노력하고 있습니다. 더 많은 정보로 업데이트를 계속 제공 할 것입니다. 이 문제와 관련된 모든 생산 충격을 경험하는 경우 Infoblox Support에 문의하십시오.

2. 2026년 7월 14일 PM 5:31 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

3. 2026년 7월 14일 PM 5:57 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 9일 AM 6:43 UTCinvestigating

   우리는 EU 지역 (portal.eu.infoblox.com)의 Infoblox Portal 및 API에 액세스하는 간헐적 인 문제점을 조사하고 있습니다. 일부 고객은 포털 및 API에 액세스하는 어려움을 경험할 수 있습니다. 우리 팀은 뿌리 원인을 확인하고 가능한 한 빨리 정상 액세스를 복원하기 위해 적극적으로 노력하고 있습니다.

2. 2026년 7월 9일 AM 6:52 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

3. 2026년 7월 9일 AM 7:07 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 30일 PM 2: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. 2026년 6월 30일 PM 8:57 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 6월 30일 PM 10:55 UTCidentified

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

4. 2026년 6월 30일 PM 11:28 UTCmonitoring

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

5. 2026년 6월 30일 PM 11:52 UTCresolved

   This incident has been resolved.

1. 2026년 6월 8일 PM 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. 2026년 6월 8일 PM 1: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. 2026년 6월 8일 PM 2: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. 2026년 6월 8일 PM 2:32 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 2026년 6월 8일 PM 3:29 UTCresolved

   This incident has been resolved.

1. 2026년 6월 2일 PM 3: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. 2026년 6월 2일 PM 5:09 UTCidentified

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

3. 2026년 6월 2일 PM 8:28 UTCmonitoring

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

4. 2026년 6월 2일 PM 10:49 UTCresolved

   This incident has been resolved.

1. 2026년 5월 20일 AM 9: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. 2026년 5월 20일 AM 11:41 UTCmonitoring

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

3. 2026년 5월 20일 PM 1:04 UTCresolved

   This incident has been resolved.

1. 2026년 5월 15일 PM 8: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. 2026년 5월 15일 PM 8:05 UTCresolved

   This incident has been resolved.

1. 2026년 5월 12일 PM 4: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. 2026년 5월 12일 PM 5: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. 2026년 5월 12일 PM 6:11 UTCresolved

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

1. 2026년 4월 23일 AM 7: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. 2026년 4월 22일 PM 2: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. 2026년 4월 22일 PM 2:27 UTCresolved

   This incident has been resolved.

1. 2026년 3월 11일 AM 1: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. 2026년 3월 11일 AM 1:30 UTCmonitoring

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

3. 2026년 3월 11일 AM 1:56 UTCmonitoring

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

4. 2026년 3월 11일 AM 2:14 UTCresolved

   This incident has been resolved.

1. 2026년 3월 2일 AM 5: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. 2026년 3월 2일 PM 10: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. 2026년 3월 4일 PM 5: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. 2026년 3월 19일 AM 1: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. 2026년 2월 23일 PM 3: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. 2026년 2월 23일 PM 4:01 UTCmonitoring

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

3. 2026년 2월 23일 PM 5:41 UTCresolved

   This incident has been resolved.

1. 2026년 1월 27일 PM 7: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. 2026년 1월 27일 PM 8: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. 2026년 1월 27일 PM 8:49 UTCresolved

   This incident has been resolved.

1. 2026년 1월 27일 PM 3: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. 2026년 1월 27일 PM 3: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. 2026년 1월 27일 PM 5:29 UTCresolved

   This incident has been resolved.

1. 2026년 1월 26일 AM 3: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. 2026년 1월 26일 AM 4:39 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 1월 26일 AM 5: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. 2026년 1월 26일 AM 7: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. 2026년 1월 26일 AM 8:09 UTCresolved

   This incident has been resolved.

1. 2026년 1월 23일 PM 2: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. 2026년 1월 14일 AM 5: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. 2025년 12월 4일 PM 5: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. 2025년 12월 4일 PM 6:15 UTCmonitoring

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

3. 2025년 12월 4일 PM 6:46 UTCresolved

   This incident has been resolved.