← HonkWatch.com

Is Infoblox down in Fr. S. Antarctic Lands?

Planned maintenance at Infoblox

People in Fr. S. Antarctic Lands: 0 reports in the last hour Official page: Planned maintenance, checked 2 min ago Our checks: loads from 35 of 35 places

1 notice

Infoblox has planned maintenance. Maintenance on Infoblox Threat Defense (Business Cloud/Advanced) / DNS Resolution - Bahrain. Updated 7 Nov, 20:29 UTC, 2 min ago · Official status page
Report a problem
Change country

Known issues (from Infoblox's status page)

Incidents

  • Traffic Reroute – Bahrain Site (investigating, maintenance impact) Since 19 Mar 2026, 01:11 UTC. Affects DNS Resolution - Bahrain · Details Latest update (19 Mar 2026, 01:11 UTC): Due to an ongoing issue with AWS services in the Bahrain region, Threat Defense DNS traffic originating from the Bahrain site has been temporarily rerouted to the nearest available sites to ensure service continuity. Impact: Customers attempting to connect to our Global and Regional Anycast IP addre

Maintenance

  • [No Operational Impact] Scheduled maintenance of Infoblox Cloud Data Connector (CDC) (planned) 11 Nov, 10:00 UTC to 13 Nov, 10:00 UTC. Affects Infoblox Ecosystem - North America, Infoblox Ecosystem - North America, Infoblox Ecosystem - North America, Infoblox Ecosystem - Europe and 2 more · Details Latest update (3 Nov, 16:43 UTC): Infoblox Cloud Data Connector (CDC) services in North America (https://portal.infoblox.com) and Europe (https://portal.eu.infoblox.com ) will undergo scheduled maintenance starting November 11, 2026. The activity will be performed in phases during the maintenance window. Customers can control the ti
  • Infoblox SaaS Infrastructure Scheduled Maintenance (planned) 12 Nov, 13:00 UTC to 12 Nov, 16:00 UTC. Affects Infoblox Portal - North America, Infoblox Portal - North America · Details Latest update (4 Nov, 08:45 UTC): Infoblox SaaS Infrastructure in North America (https://portal.infoblox.com) will undergo scheduled maintenance starting November 12, 2026. Impact: During the maintenance window, customers may experience failure on Infoblox portal while accessing the “Join Tokens” page and while joining a new On-Prem
  • Infoblox SaaS Infrastructure Scheduled Maintenance (planned) 13 Nov, 08:30 UTC to 13 Nov, 11:30 UTC. Affects Infoblox Portal - North America, Infoblox Portal - North America · Details Latest update (4 Nov, 08:50 UTC): Infoblox SaaS Infrastructure in North America (https://portal.infoblox.com) will undergo scheduled maintenance on November 13, 2026. Impact: During the maintenance window, customers may experience failures when accessing the “Schedule Software Updates” and “Schedule Configuration Updates” pages on t
Show 1 more maintenance window
  • [Operational Impact] NIOS-X As a Service Scheduled Maintenance (planned) 14 Nov, 02:30 UTC to 14 Nov, 11:30 UTC. Affects AWS Africa (Cape Town), AWS Asia Pacific (Hong Kong), AWS Asia Pacific (Hyderabad), AWS Asia Pacific (Mumbai) and 12 more · Details Latest update (6 Nov, 21:53 UTC): NIOS-X as a service in North America (https://portal.infoblox.com) and Europe (https://portal.eu.infoblox.com) will undergo scheduled maintenance on November 14, 2026. During this maintenance, updates will be applied to the DNS service infrastructure. Impact: The update process may result in a DNS s

In Infoblox's own words, as we read them every 7.5 minutes, last 2 min ago. Read Infoblox's status page

Reports from people in Fr. S. Antarctic Lands

Last 24 hours · Fr. S. Antarctic Lands · times in UTC

0 reports

No community reports in the last 24 hours from Fr. S. Antarctic Lands. Having trouble? Add your report.

Status page: maintenance, 2 Nov, 13:37 to now 024 00:0006:0012:0018:00 20:45-20:50 UTC: 34 of 34 places loaded it, typical 774 ms20:50-21:00 UTC: 35 of 35 places loaded it, typical 680 to 778 ms21:00-21:05 UTC: 9 of 9 places loaded it, typical 912 ms21:05-21:10 UTC: 27 of 27 places loaded it, typical 809 ms21:10-21:15 UTC: 34 of 34 places loaded it, typical 801 ms21:15-21:20 UTC: 24 of 24 places loaded it, typical 869 ms21:20-21:25 UTC: 34 of 34 places loaded it, typical 765 ms21:25-21:30 UTC: 23 of 23 places loaded it, typical 880 ms21:30-21:35 UTC: 31 of 31 places loaded it, typical 840 ms21:35-21:45 UTC: 35 of 35 places loaded it, typical 695 to 701 ms21:45-21:50 UTC: 23 of 23 places loaded it, typical 741 ms21:50-21:55 UTC: 18 of 18 places loaded it, typical 846 ms21:55-22:05 UTC: 35 of 35 places loaded it, typical 680 to 764 ms22:05-22:10 UTC: 24 of 24 places loaded it, typical 669 ms22:10-22:15 UTC: 35 of 35 places loaded it, typical 822 ms22:15-22:20 UTC: 34 of 34 places loaded it, typical 712 ms22:20-22:25 UTC: 35 of 35 places loaded it, typical 908 ms22:25-22:30 UTC: 23 of 23 places loaded it, typical 795 ms22:30-22:35 UTC: 35 of 35 places loaded it, typical 754 ms22:35-22:40 UTC: 34 of 34 places loaded it, typical 759 ms22:40-22:45 UTC: 35 of 35 places loaded it, typical 709 ms22:45-22:55 UTC: 34 of 34 places loaded it, typical 719 to 829 ms22:55-23:00 UTC: 35 of 35 places loaded it, typical 725 ms23:00-23:05 UTC: 34 of 34 places loaded it, typical 731 ms23:05-23:10 UTC: 35 of 35 places loaded it, typical 762 ms23:10-23:20 UTC: 34 of 34 places loaded it, typical 758 to 805 ms23:20-23:30 UTC: 35 of 35 places loaded it, typical 760 to 803 ms23:30-23:35 UTC: 34 of 34 places loaded it, typical 716 ms23:35-23:40 UTC: 35 of 35 places loaded it, typical 777 ms23:40-23:50 UTC: 34 of 34 places loaded it, typical 699 to 773 ms23:50-00:00 UTC: 35 of 35 places loaded it, typical 756 to 779 ms00:00-00:05 UTC: 34 of 34 places loaded it, typical 737 ms00:05-00:15 UTC: 35 of 35 places loaded it, typical 675 to 739 ms00:15-00:20 UTC: 34 of 34 places loaded it, typical 824 ms00:20-00:30 UTC: 35 of 35 places loaded it, typical 655 to 720 ms00:30-00:35 UTC: 33 of 33 places loaded it, typical 752 ms00:35-00:45 UTC: 35 of 35 places loaded it, typical 695 to 764 ms00:45-00:50 UTC: 34 of 34 places loaded it, typical 668 ms00:50-01:00 UTC: 35 of 35 places loaded it, typical 700 to 738 ms01:00-01:05 UTC: 34 of 34 places loaded it, typical 743 ms01:05-01:15 UTC: 35 of 35 places loaded it, typical 724 to 862 ms01:15-01:20 UTC: 34 of 34 places loaded it, typical 738 ms01:20-01:30 UTC: 35 of 35 places loaded it, typical 678 to 821 ms01:30-01:35 UTC: 34 of 34 places loaded it, typical 747 ms01:35-01:40 UTC: 35 of 35 places loaded it, typical 724 ms01:40-01:50 UTC: 34 of 34 places loaded it, typical 713 to 728 ms01:50-02:00 UTC: 35 of 35 places loaded it, typical 683 to 781 ms02:00-02:05 UTC: 34 of 34 places loaded it, typical 760 ms02:05-02:15 UTC: 35 of 35 places loaded it, typical 688 to 862 ms02:15-02:20 UTC: 34 of 34 places loaded it, typical 727 ms02:20-02:30 UTC: 35 of 35 places loaded it, typical 680 to 694 ms02:30-02:35 UTC: 34 of 34 places loaded it, typical 770 ms02:35-02:45 UTC: 35 of 35 places loaded it, typical 705 to 717 ms02:45-02:50 UTC: 34 of 34 places loaded it, typical 777 ms02:50-03:00 UTC: 35 of 35 places loaded it, typical 701 to 709 ms03:00-03:05 UTC: 34 of 34 places loaded it, typical 721 ms03:05-03:15 UTC: 35 of 35 places loaded it, typical 695 to 704 ms03:15-03:20 UTC: 34 of 34 places loaded it, typical 738 ms03:20-03:30 UTC: 35 of 35 places loaded it, typical 673 to 705 ms03:30-03:35 UTC: 34 of 34 places loaded it, typical 708 ms03:35-03:45 UTC: 35 of 35 places loaded it, typical 673 to 749 ms03:45-03:50 UTC: 34 of 34 places loaded it, typical 691 ms03:50-04:00 UTC: 35 of 35 places loaded it, typical 717 to 737 ms04:00-04:05 UTC: 34 of 34 places loaded it, typical 753 ms04:05-04:10 UTC: 35 of 35 places loaded it, typical 716 ms04:10-04:20 UTC: 34 of 34 places loaded it, typical 703 to 823 ms04:20-04:30 UTC: 35 of 35 places loaded it, typical 722 to 730 ms04:30-04:35 UTC: 34 of 34 places loaded it, typical 817 ms04:35-04:45 UTC: 35 of 35 places loaded it, typical 721 to 818 ms04:45-04:50 UTC: 34 of 34 places loaded it, typical 725 ms04:50-05:00 UTC: 35 of 35 places loaded it, typical 737 to 769 ms05:00-05:05 UTC: 34 of 34 places loaded it, typical 712 ms05:05-05:15 UTC: 35 of 35 places loaded it, typical 752 to 760 ms05:15-05:20 UTC: 34 of 34 places loaded it, typical 706 ms05:20-05:30 UTC: 35 of 35 places loaded it, typical 686 to 688 ms05:30-05:35 UTC: 34 of 34 places loaded it, typical 695 ms05:35-05:40 UTC: 35 of 35 places loaded it, typical 733 ms05:40-05:50 UTC: 34 of 34 places loaded it, typical 706 to 810 ms05:50-06:00 UTC: 35 of 35 places loaded it, typical 724 to 738 ms06:00-06:05 UTC: 34 of 34 places loaded it, typical 699 ms06:05-06:15 UTC: 35 of 35 places loaded it, typical 679 to 724 ms06:15-06:20 UTC: 34 of 34 places loaded it, typical 829 ms06:20-06:30 UTC: 35 of 35 places loaded it, typical 691 to 697 ms06:30-06:35 UTC: 34 of 34 places loaded it, typical 787 ms06:35-06:45 UTC: 35 of 35 places loaded it, typical 706 to 795 ms06:45-06:50 UTC: 34 of 34 places loaded it, typical 728 ms06:50-07:00 UTC: 35 of 35 places loaded it, typical 683 to 719 ms07:00-07:05 UTC: 33 of 33 places loaded it, typical 799 ms07:05-07:15 UTC: 35 of 35 places loaded it, typical 688 to 741 ms07:15-07:20 UTC: 34 of 34 places loaded it, typical 748 ms07:20-07:25 UTC: 35 of 35 places loaded it, typical 850 ms07:25-07:35 UTC: 34 of 34 places loaded it, typical 711 to 840 ms07:35-07:45 UTC: 35 of 35 places loaded it, typical 727 to 745 ms07:45-07:50 UTC: 34 of 34 places loaded it, typical 720 ms07:50-08:00 UTC: 35 of 35 places loaded it, typical 694 to 742 ms08:00-08:05 UTC: 34 of 34 places loaded it, typical 850 ms08:05-08:15 UTC: 35 of 35 places loaded it, typical 702 to 730 ms08:15-08:20 UTC: 34 of 34 places loaded it, typical 699 ms08:20-08:30 UTC: 35 of 35 places loaded it, typical 713 to 734 ms08:30-08:35 UTC: 34 of 34 places loaded it, typical 738 ms08:35-08:45 UTC: 35 of 35 places loaded it, typical 733 to 790 ms08:45-08:50 UTC: 34 of 34 places loaded it, typical 832 ms08:50-09:00 UTC: 35 of 35 places loaded it, typical 742 to 746 ms09:00-09:10 UTC: 34 of 34 places loaded it, typical 709 to 760 ms09:10-09:15 UTC: 35 of 35 places loaded it, typical 688 ms09:15-09:20 UTC: 31 of 32 places loaded it, typical 731 ms09:20-09:25 UTC: 35 of 35 places loaded it, typical 688 ms09:25-09:30 UTC: 34 of 34 places loaded it, typical 718 ms09:30-09:45 UTC: 35 of 35 places loaded it, typical 703 to 819 ms09:45-09:50 UTC: 34 of 34 places loaded it, typical 859 ms09:50-10:15 UTC: 35 of 35 places loaded it, typical 676 to 776 ms10:15-10:20 UTC: 15 of 15 places loaded it, typical 699 ms10:20-10:30 UTC: 35 of 35 places loaded it, typical 683 to 725 ms10:30-10:40 UTC: 34 of 34 places loaded it, typical 696 to 739 ms10:40-10:45 UTC: 35 of 35 places loaded it, typical 725 ms10:45-10:50 UTC: 34 of 34 places loaded it, typical 746 ms10:50-11:00 UTC: 35 of 35 places loaded it, typical 822 to 836 ms11:00-11:05 UTC: 34 of 34 places loaded it, typical 796 ms11:05-11:15 UTC: 35 of 35 places loaded it, typical 718 to 756 ms11:15-11:20 UTC: 34 of 34 places loaded it, typical 737 ms11:20-11:30 UTC: 35 of 35 places loaded it, typical 760 to 813 ms11:30-11:35 UTC: 34 of 34 places loaded it, typical 835 ms11:35-11:40 UTC: 16 of 16 places loaded it, typical 894 ms11:40-11:45 UTC: 35 of 35 places loaded it, typical 701 ms11:45-11:50 UTC: 34 of 34 places loaded it, typical 717 ms11:50-12:00 UTC: 35 of 35 places loaded it, typical 754 to 869 ms12:00-12:05 UTC: 34 of 34 places loaded it, typical 784 ms12:05-12:15 UTC: 35 of 35 places loaded it, typical 686 to 734 ms12:15-12:20 UTC: 34 of 34 places loaded it, typical 699 ms12:20-12:30 UTC: 35 of 35 places loaded it, typical 721 to 755 ms12:30-12:35 UTC: 34 of 34 places loaded it, typical 772 ms12:35-12:45 UTC: 35 of 35 places loaded it, typical 774 to 844 ms12:45-12:50 UTC: 34 of 34 places loaded it, typical 743 ms12:50-12:55 UTC: 31 of 31 places loaded it, typical 731 ms12:55-13:00 UTC: 35 of 35 places loaded it, typical 683 ms13:00-13:05 UTC: 34 of 34 places loaded it, typical 752 ms13:05-13:15 UTC: 35 of 35 places loaded it, typical 768 to 797 ms13:15-13:20 UTC: 34 of 34 places loaded it, typical 750 ms13:20-13:30 UTC: 35 of 35 places loaded it, typical 726 to 732 ms13:30-13:35 UTC: 34 of 34 places loaded it, typical 747 ms13:35-13:45 UTC: 35 of 35 places loaded it, typical 720 to 737 ms13:45-13:55 UTC: 34 of 34 places loaded it, typical 749 to 829 ms13:55-14:00 UTC: 35 of 35 places loaded it, typical 722 ms14:00-14:05 UTC: 34 of 34 places loaded it, typical 750 ms14:05-14:15 UTC: 35 of 35 places loaded it, typical 705 to 736 ms14:15-14:20 UTC: 34 of 34 places loaded it, typical 853 ms14:20-14:30 UTC: 35 of 35 places loaded it, typical 720 to 764 ms14:30-14:35 UTC: 34 of 34 places loaded it, typical 770 ms14:35-14:45 UTC: 35 of 35 places loaded it, typical 723 to 757 ms14:45-14:50 UTC: 34 of 34 places loaded it, typical 811 ms14:50-15:00 UTC: 35 of 35 places loaded it, typical 701 to 730 ms15:00-15:05 UTC: 34 of 34 places loaded it, typical 739 ms15:05-15:15 UTC: 35 of 35 places loaded it, typical 748 to 766 ms15:15-15:20 UTC: 34 of 34 places loaded it, typical 751 ms15:20-15:30 UTC: 35 of 35 places loaded it, typical 726 to 742 ms15:30-15:35 UTC: 34 of 34 places loaded it, typical 780 ms15:35-15:45 UTC: 35 of 35 places loaded it, typical 737 to 746 ms15:45-15:50 UTC: 34 of 34 places loaded it, typical 760 ms15:50-15:55 UTC: 35 of 35 places loaded it, typical 732 ms15:55-16:05 UTC: 34 of 34 places loaded it, typical 704 to 810 ms16:05-16:15 UTC: 35 of 35 places loaded it, typical 745 to 778 ms16:15-16:20 UTC: 34 of 34 places loaded it, typical 737 ms16:20-16:30 UTC: 35 of 35 places loaded it, typical 720 to 815 ms16:30-16:40 UTC: 34 of 34 places loaded it, typical 725 to 727 ms16:40-16:45 UTC: 35 of 35 places loaded it, typical 749 ms16:45-16:50 UTC: 34 of 34 places loaded it, typical 846 ms16:50-16:55 UTC: 35 of 35 places loaded it, typical 810 ms16:55-17:05 UTC: 34 of 34 places loaded it, typical 790 to 830 ms17:05-17:15 UTC: 35 of 35 places loaded it, typical 702 to 791 ms17:15-17:20 UTC: 34 of 34 places loaded it, typical 841 ms17:20-17:30 UTC: 35 of 35 places loaded it, typical 701 to 718 ms17:30-17:35 UTC: 34 of 34 places loaded it, typical 802 ms17:35-17:45 UTC: 35 of 35 places loaded it, typical 733 to 754 ms17:45-17:50 UTC: 34 of 34 places loaded it, typical 693 ms17:50-18:15 UTC: 35 of 35 places loaded it, typical 693 to 760 ms18:15-18:20 UTC: 33 of 33 places loaded it, typical 843 ms18:20-18:30 UTC: 35 of 35 places loaded it, typical 700 to 728 ms18:30-18:35 UTC: 34 of 34 places loaded it, typical 742 ms18:35-18:40 UTC: 35 of 35 places loaded it, typical 719 ms18:40-18:50 UTC: 34 of 34 places loaded it, typical 712 to 769 ms18:50-19:00 UTC: 35 of 35 places loaded it, typical 753 to 754 ms19:00-19:10 UTC: 34 of 34 places loaded it, typical 754 to 806 ms19:10-19:15 UTC: 35 of 35 places loaded it, typical 851 ms19:15-19:20 UTC: 33 of 33 places loaded it, typical 772 ms19:20-19:30 UTC: 35 of 35 places loaded it, typical 782 to 827 ms19:30-19:35 UTC: 34 of 34 places loaded it, typical 768 ms19:35-19:45 UTC: 35 of 35 places loaded it, typical 784 to 817 ms19:45-19:50 UTC: 34 of 34 places loaded it, typical 830 ms19:50-20:00 UTC: 35 of 35 places loaded it, typical 677 to 742 ms20:00-20:05 UTC: 34 of 34 places loaded it, typical 799 ms20:05-20:15 UTC: 35 of 35 places loaded it, typical 706 to 811 ms20:15-20:20 UTC: 34 of 34 places loaded it, typical 750 ms20:20-20:30 UTC: 35 of 35 places loaded it, typical 814 to 828 ms20:30-20:35 UTC: 3 of 3 places loaded it, typical 1234 ms Typical response time of the places that loaded it, at most 1234 ms

Bars: reports every 15 minutes. Reports alone do not confirm an outage; a flat chart does not prove everything works.

Tinted columns: when Infoblox's status page showed a partial outage, a major outage or maintenance, as we read it every 7.5 minutes; the times are when we saw it, not when the provider posted it. Strip under the bars: how many places loaded infoblox.com in each 5 minutes, of those that checked, and the line under it their typical response time. Any answer from the website counts as loaded, even an error page. Website checks don't test sign-in, payments or every feature. Tinted columns and our checks are worldwide; the bars count reports from Fr. S. Antarctic Lands only.

Latest checks, 20:30-20:35 UTC: 3 of 3 places loaded it, typical 1234 ms.

Report totals as of 7 Nov, 20:31 UTC

Report a problem with Infoblox

Choose where you are, then tap what isn't working. Tapping a problem sends your report; no account needed.

What isn't working? Tap one to send

Anonymous · one report per service per hour. This adds your experience to the chart; the provider is not contacted.

Compare worldwide reports · Other services in Fr. S. Antarctic Lands

Where this status comes from

Provider updates and website checks — Worldwide

The evidence below covers the provider and our available checks. It is not a separate verdict for Fr. S. Antarctic Lands. The report chart above is filtered to Fr. S. Antarctic Lands.

Our own checks of infoblox.com

Every 5 minutes, from our probes

Our checks from 35 cities: all fine.

Tokyo: loaded in 2260 ms Seoul: loaded in 984 ms Hong Kong: loaded in 1234 ms Johannesburg: loaded in 690 ms Lauterbourg: loaded in 97 ms Seattle: loaded in 651 ms New Jersey: loaded in 610 ms Jakarta: loaded in 1039 ms Osaka: loaded in 1219 ms St. Louis: loaded in 863 ms Portsmouth: loaded in 170 ms Warsaw: loaded in 548 ms Delhi: loaded in 1307 ms Frankfurt: loaded in 156 ms Querétaro: loaded in 783 ms Bangalore: loaded in 1135 ms Singapore: loaded in 1276 ms Port Louis: loaded in 1146 ms Cape Town: loaded in 674 ms Toronto: loaded in 550 ms Hamina: loaded in 200 ms New York: loaded in 523 ms Atlanta: loaded in 828 ms Dallas: loaded in 1034 ms São Paulo: loaded in 841 ms Doha: loaded in 850 ms Madrid: loaded in 44 ms Sydney: loaded in 1167 ms Los Angeles: loaded in 996 ms Melbourne: loaded in 1218 ms Santiago: loaded in 1048 ms London: loaded in 402 ms Mumbai: loaded in 679 ms Amsterdam: loaded in 44 ms Tel Aviv: loaded in 689 ms
  • TokyoReachable2260 ms, 2 min ago
  • SeoulReachable984 ms, 2 min ago
  • Hong KongReachable1234 ms, 2 min ago
  • JohannesburgReachable690 ms, 2 min ago
  • LauterbourgReachable97 ms, 2 min ago
  • SeattleReachable651 ms, 2 min ago
  • New JerseyReachable610 ms, 2 min ago
  • JakartaReachable1039 ms, 2 min ago
  • OsakaReachable1219 ms, 2 min ago
  • St. LouisReachable863 ms, 2 min ago
  • PortsmouthReachable170 ms, 2 min ago
  • WarsawReachable548 ms, 2 min ago
  • DelhiReachable1307 ms, 2 min ago
  • FrankfurtReachable156 ms, 3 min ago
  • QuerétaroReachable783 ms, 3 min ago
  • BangaloreReachable1135 ms, 3 min ago
  • SingaporeReachable1276 ms, 3 min ago
  • Port LouisReachable1146 ms, 3 min ago
  • Cape TownReachable674 ms, 3 min ago
  • TorontoReachable550 ms, 3 min ago
  • HaminaReachable200 ms, 3 min ago
  • New YorkReachable523 ms, 3 min ago
  • AtlantaReachable828 ms, 3 min ago
  • DallasReachable1034 ms, 3 min ago
  • São PauloReachable841 ms, 3 min ago
  • DohaReachable850 ms, 3 min ago
  • MadridReachable44 ms, 3 min ago
  • SydneyReachable1167 ms, 3 min ago
  • Los AngelesReachable996 ms, 3 min ago
  • MelbourneReachable1218 ms, 3 min ago
  • SantiagoReachable1048 ms, 3 min ago
  • LondonReachable402 ms, 4 min ago
  • MumbaiReachable679 ms, 4 min ago
  • AmsterdamReachable44 ms, 4 min ago
  • Tel AvivReachable689 ms, 4 min ago

This is separate from the status page: we request infoblox.com and note whether it answers. These automated checks do not sign in or use the app's features.

Parts of Infoblox

Infoblox

Infoblox Threat Defense (Business Cloud/Advanced)

  • DNS Resolution - BahrainMaintenance

144 other parts are working.

Incidents and maintenance

Open incidents

  • Traffic Reroute – Bahrain Site (investigating) Since 19 Mar 2026, 01:11 UTC. Affects DNS Resolution - Bahrain · Details

Maintenance

  • [No Operational Impact] Scheduled maintenance of Infoblox Cloud Data Connector (CDC) (planned) 11 Nov, 10:00 UTC to 13 Nov, 10:00 UTC. Affects Infoblox Ecosystem - North America, Infoblox Ecosystem - North America, Infoblox Ecosystem - North America, Infoblox Ecosystem - Europe and 2 more · Details
  • Infoblox SaaS Infrastructure Scheduled Maintenance (planned) 12 Nov, 13:00 UTC to 12 Nov, 16:00 UTC. Affects Infoblox Portal - North America, Infoblox Portal - North America · Details
  • Infoblox SaaS Infrastructure Scheduled Maintenance (planned) 13 Nov, 08:30 UTC to 13 Nov, 11:30 UTC. Affects Infoblox Portal - North America, Infoblox Portal - North America · Details
  • [Operational Impact] NIOS-X As a Service Scheduled Maintenance (planned) 14 Nov, 02:30 UTC to 14 Nov, 11:30 UTC. Affects AWS Africa (Cape Town), AWS Asia Pacific (Hong Kong), AWS Asia Pacific (Hyderabad), AWS Asia Pacific (Mumbai) and 12 more · Details
Outage history

No problems recorded since 2 Nov 2026.

Last 9030 days

100.00% of the time without a reported outage, since 2 Nov

Of the last 90 days, 0 had a partial or major outage, 6 had maintenance only and 84 have no data. Recent problems are listed in a table further down.

90 days ago30 days agoToday

No problems Partial outage Major outage Maintenance No data yet

Recent problems

No problems recorded since 2 Nov 2026.

What can I try?

Having trouble with Infoblox?

  1. Compare reports from Fr. S. Antarctic Lands and check the latest update above. A quiet chart does not rule out a new or local problem.
  2. Try the service on another device or switch between WiFi and mobile data, if available. If other sites also fail, check your internet provider.
  3. Report a problem with the feature that is failing and the country where you are affected. Submit once; your report appears in the chart.

Reports describe people's experiences. One report alone does not confirm an outage.

Questions about these results

Questions

Is Infoblox down, or is it just me?

Infoblox is doing planned maintenance, so some parts may not work right now. It is probably not just you.

How do we know?

We read the official Infoblox status page and load infoblox.com from our own probes in several cities. People can also report problems here. Their reports appear separately and may reveal issues before a provider update.

How often do we check?

The status page every 7.5 minutes, day and night, and the website every 5 minutes. We keep 90 days of history: a day we have no reading for shows as "no data yet", never as working.

Other services in Domains and DNS

Each card shows that service's own status, not Infoblox's. A problem listed here does not mean Infoblox has one.

See the live outage feed for Fr. S. Antarctic Lands · Find another service