Laporan pengguna
0
Mendekati normal. 0 dalam satu jam terakhir. Biasanya sekitar 0 per jam.
Damn, is it down?
Semua layanan / Cloud & developer
infoblox.com · Cloud & developer
The vendor's status page lists scheduled maintenance. Our own checks and user reports have not confirmed a problem. Status resmi: Service Under Maintenance
Perkiraan perbaikan: Not enough Infoblox history yet; similar Cloud & developer outages lasted 2 h (median, typically 48 min–11 h; 80 outages).
Diagnosis langsung
Menunjukkan lapisan yang paling mungkin (layanan, ISP atau areamu, DNS, atau Wi-Fi-mu) dan memberi dua langkah untuk dicoba.
Tekan Jalankan tesBrowsermu menguji situs tersebut, server kami, dan dua resolver DNS publik. Kami tidak pernah menyimpan IP-mu; hanya hitungan anonim per jaringan dan wilayah.
Reachable from all 4 regions we check from.
Tidak ada laporan dalam 24 jam terakhir.
Titik mewakili seluruh negara bagian, provinsi, atau negara, bukan lokasi persis. Kami tidak pernah menyimpan alamat IP. Setiap laporan dengan tempat yang diketahui dapat muncul di peta. Diperbarui setiap menit.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Mendekati normal. 0 dalam satu jam terakhir. Biasanya sekitar 0 per jam.
Dapat dijangkau
Last checked 5 min ago. Last stored result reached it in 1028 ms.
Pemeliharaan
Service Under Maintenance Halaman status resmi
| Waktu (UTC) | Laporan | Garis dasar | Latensi | Pengecekan gagal |
|---|---|---|---|---|
| 04:45 | 0 | 0.0 | 518 ms | 0 |
| 05:00 | 0 | 0.0 | 677 ms | 0 |
| 05:15 | 0 | 0.0 | 717 ms | 0 |
| 05:30 | 0 | 0.0 | 823 ms | 0 |
| 05:45 | 0 | 0.0 | 879 ms | 0 |
| 06:00 | 0 | 0.0 | 681 ms | 0 |
| 06:15 | 0 | 0.0 | 760 ms | 0 |
| 06:30 | 0 | 0.0 | 823 ms | 0 |
| 06:45 | 0 | 0.0 | 711 ms | 0 |
| 07:00 | 0 | 0.0 | 1009 ms | 0 |
| 07:15 | 0 | 0.0 | 663 ms | 0 |
| 07:30 | 0 | 0.0 | 576 ms | 0 |
| 07:45 | 0 | 0.0 | 974 ms | 0 |
| 08:00 | 0 | 0.0 | 734 ms | 0 |
| 08:15 | 0 | 0.0 | 1001 ms | 0 |
| 08:30 | 0 | 0.0 | 911 ms | 0 |
| 08:45 | 0 | 0.0 | 651 ms | 0 |
| 09:00 | 0 | 0.0 | 154 ms | 0 |
| 09:15 | 0 | 0.0 | 802 ms | 0 |
| 09:30 | 0 | 0.0 | 783 ms | 0 |
| 09:45 | 0 | 0.0 | 800 ms | 0 |
| 10:00 | 0 | 0.0 | 746 ms | 0 |
| 10:15 | 0 | 0.0 | 656 ms | 0 |
| 10:30 | 0 | 0.0 | 902 ms | 0 |
| 10:45 | 0 | 0.0 | 667 ms | 0 |
| 11:00 | 0 | 0.0 | 1090 ms | 0 |
| 11:15 | 0 | 0.0 | 683 ms | 0 |
| 11:30 | 0 | 0.0 | 649 ms | 0 |
| 11:45 | 0 | 0.0 | 759 ms | 0 |
| 12:00 | 0 | 0.0 | 782 ms | 0 |
| 12:15 | 0 | 0.0 | 864 ms | 0 |
| 12:30 | 0 | 0.0 | 525 ms | 0 |
| 12:45 | 0 | 0.0 | 722 ms | 0 |
| 13:00 | 0 | 0.0 | 678 ms | 0 |
| 13:15 | 0 | 0.0 | 930 ms | 0 |
| 13:30 | 0 | 0.0 | 706 ms | 0 |
| 13:45 | 0 | 0.0 | 786 ms | 0 |
| 14:00 | 0 | 0.0 | 680 ms | 0 |
| 14:15 | 0 | 0.0 | 747 ms | 0 |
| 14:30 | 0 | 0.0 | 847 ms | 0 |
| 14:45 | 0 | 0.0 | 677 ms | 0 |
| 15:00 | 0 | 0.0 | 560 ms | 0 |
| 15:15 | 0 | 0.0 | 480 ms | 0 |
| 15:30 | 0 | 0.0 | 747 ms | 0 |
| 15:45 | 0 | 0.0 | 1004 ms | 0 |
| 16:00 | 0 | 0.0 | 939 ms | 0 |
| 16:15 | 0 | 0.0 | 598 ms | 0 |
| 16:30 | 0 | 0.0 | 717 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 12 days of data so far, so the 90-day numbers fill in over time.
[Operational Impact] NIOS-X As a Service Scheduled Maintenance
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 service interruption of approximately 30 seconds. Event Start Time: November 14, 2:30 AM UTC Event…
[Operational Impact] NIOS-X As a Service Unscheduled Maintenance
NIOS-X as a service will undergo unscheduled maintenance on November 14, 2026. During the maintenance window, underlying AWS nodes in AWS Asia Pacific (Sydney) and AWS US East (Ohio) will be rotated. Impact: Service endpoints in the North America (https://portal.infoblox.com) and Europe (https://portal.eu.infoblox.com) connecting to the following service locations may experience interruptions of…
Pemeliharaan terencana bukan gangguan. Waktu dan kata-katanya berasal dari vendor. Outage Weather →
Belum ada catatan gangguan untuk Infoblox. Gangguan selama 10 menit atau lebih mendapat halaman sendiri di sini.
Satu laporan per layanan setiap 10 menit dari jaringan ini. Tanpa akun.
Dapatkan email saat Infoblox down dan saat pulih kembali. Gratis. Konfirmasi lewat email, berhenti berlangganan kapan saja.
Mau di kanal tim? Kirim peringatan Infoblox ke Slack, Discord, atau webhook — gratis.
Infoblox terdaftar di kategori Cloud & developer kami dan dicek di infoblox.com.
Infoblox menerbitkan halaman status resmi di status.infoblox.com; jika dapat kami baca, tingkat insidennya ikut diperhitungkan dalam status yang ditampilkan di sini.
Masalah umum pada layanan Cloud & developer: galat API, deploy atau build gagal, serta dashboard atau konsol yang down.
Uptime terukur dari pengecekan kami: 100% selama 12 hari pengecekan. Tidak ada insiden publik yang tercatat sejak pemantauan dimulai 12 hari lalu.
Waktu respons selama 24 jam terakhir: rata-rata 748 ms, rentang 154–1378 ms dari 179 pengecekan yang berhasil.
The vendor's status page lists scheduled maintenance. Our own checks and user reports have not confirmed a problem. Status resmi: Service Under Maintenance
Kami belum mencatat insiden publik Infoblox sejak pemantauan dimulai 12 hari lalu.
Dari pengecekan kami sendiri: 100% selama 12 hari pengecekan.
Rata-rata 748 ms selama 24 jam terakhir (154–1378 ms).
Ya, di https://status.infoblox.com.
Biasanya masalahnya lokal: coba browser lain atau aplikasinya, beralih antara Wi-Fi dan data seluler, lalu hapus cache. Untuk layanan Cloud & developer, perhatikan galat API, deploy atau build gagal, serta dashboard atau konsol yang down. Jika banyak orang melaporkan Infoblox di sini secara bersamaan, masalahnya ada di pihak Infoblox.
Cara kami mendeteksi dan memverifikasi gangguan · Sanggah laporan ini · Kami meninjau sanggahan dalam 24 jam.
Community comments
Share what you are seeing with Infoblox. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.