Laporan pengguna
0
Mendekati normal. 0 dalam satu jam terakhir. Biasanya sekitar 0 per jam.
Damn, is it down?
Semua layanan / Cloud & developer
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Status resmi: Microsoft 365 outage may impact delivery of passwordless login passwords, support tickets, and support replies to Exchange Online mailboxes.
Sumber: halaman status vendor · Kami tidak berafiliasi dengan PDQ.
Perkiraan perbaikan: Not enough PDQ history yet; similar Cloud & developer outages lasted 2 h (median, typically 48 min–9 h; 83 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 1 hr ago. Last stored result reached it in 145 ms.
Insiden kecil
Microsoft 365 outage may impact delivery of passwordless login passwords, support tickets, and support replies to Exchange Online mailboxes. Halaman status resmi
| Waktu (UTC) | Laporan | Garis dasar | Latensi | Pengecekan gagal |
|---|---|---|---|---|
| Tue 00 | 0 | 0.0 | 174 ms | 0 |
| Tue 02 | 0 | 0.0 | 68 ms | 0 |
| Tue 04 | 0 | 0.0 | 173 ms | 0 |
| Tue 07 | 0 | 0.0 | 148 ms | 0 |
| Tue 09 | 0 | 0.0 | 164 ms | 0 |
| Tue 11 | 0 | 0.0 | 172 ms | 0 |
| Tue 13 | 0 | 0.0 | 163 ms | 0 |
| Tue 15 | 0 | 0.0 | 227 ms | 0 |
| Tue 18 | 0 | 0.0 | 135 ms | 0 |
| Tue 20 | 0 | 0.0 | 163 ms | 0 |
| Tue 22 | 0 | 0.0 | 194 ms | 0 |
| Wed 00 | 0 | 0.0 | 79 ms | 0 |
| Wed 02 | 0 | 0.0 | 122 ms | 0 |
| Wed 05 | 0 | 0.0 | 71 ms | 0 |
| Wed 07 | 0 | 0.0 | 129 ms | 0 |
| Wed 09 | 0 | 0.0 | 201 ms | 0 |
| Wed 12 | 0 | 0.0 | 108 ms | 0 |
| Wed 14 | 0 | 0.0 | 133 ms | 0 |
| Wed 16 | 0 | 0.0 | 214 ms | 0 |
| Wed 18 | 0 | 0.0 | 170 ms | 0 |
| Wed 20 | 0 | 0.0 | 140 ms | 0 |
| Wed 22 | 0 | 0.0 | 192 ms | 0 |
| Thu 01 | 0 | 0.0 | 182 ms | 0 |
| Thu 03 | 0 | 0.0 | 190 ms | 0 |
| Thu 05 | 0 | 0.0 | 68 ms | 0 |
| Thu 07 | 0 | 0.0 | 137 ms | 0 |
| Thu 09 | 0 | 0.0 | 162 ms | 0 |
| Thu 11 | 0 | 0.0 | 139 ms | 0 |
| Thu 13 | 0 | 0.0 | 69 ms | 0 |
| Thu 15 | 0 | 0.0 | 178 ms | 0 |
| Thu 17 | 0 | 0.0 | 151 ms | 0 |
| Thu 19 | 0 | 0.0 | 161 ms | 0 |
| Thu 21 | 0 | 0.0 | 182 ms | 0 |
| Thu 23 | 0 | 0.0 | 166 ms | 0 |
| Fri 01 | 0 | 0.0 | 75 ms | 0 |
| Fri 03 | 0 | 0.0 | 227 ms | 0 |
| Fri 06 | 0 | 0.0 | 179 ms | 0 |
| Fri 08 | 0 | 0.0 | 167 ms | 0 |
| Fri 10 | 0 | 0.0 | 126 ms | 0 |
| Fri 12 | 0 | 0.0 | 143 ms | 0 |
| Fri 14 | 0 | 0.0 | 135 ms | 0 |
| Fri 16 | 0 | 0.0 | 69 ms | 0 |
| Fri 18 | 0 | 0.0 | 195 ms | 0 |
| Fri 20 | 0 | 0.0 | 167 ms | 0 |
| Fri 22 | 0 | 0.0 | 144 ms | 0 |
| Sat 00 | 0 | 0.0 | 166 ms | 0 |
| Sat 01 | 0 | 0.0 | 146 ms | 0 |
| Sat 03 | 0 | 0.0 | 145 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 9 days of data so far, so the 90-day numbers fill in over time.
Connect Planned Maintenance
We will be performing scheduled maintenance on November 17 at 10 PM ET. We expect to complete maintenance by 1 AM ET. (3 Hours) During this timeframe, Connect may be unavailable. Package deployments may also be unavailable. If you have any questions, please let us know at support@pdq.com
Pemeliharaan terencana bukan gangguan. Waktu dan kata-katanya berasal dari vendor. Outage Weather →
Belum ada catatan gangguan untuk PDQ. 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 PDQ down dan saat pulih kembali. Gratis. Konfirmasi lewat email, berhenti berlangganan kapan saja.
Mau di kanal tim? Kirim peringatan PDQ ke Slack, Discord, atau webhook — gratis.
PDQ terdaftar di kategori Cloud & developer kami dan dicek di pdq.com.
PDQ menerbitkan halaman status resmi di status.pdq.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 9 hari pengecekan. Tidak ada insiden publik yang tercatat sejak pemantauan dimulai 9 hari lalu.
Waktu respons selama 24 jam terakhir: rata-rata 149 ms, rentang 69–195 ms dari 12 pengecekan yang berhasil.
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Status resmi: Microsoft 365 outage may impact delivery of passwordless login passwords, support tickets, and support replies to Exchange Online mailboxes.
Kami belum mencatat insiden publik PDQ sejak pemantauan dimulai 9 hari lalu.
Dari pengecekan kami sendiri: 100% selama 9 hari pengecekan.
Rata-rata 149 ms selama 24 jam terakhir (69–195 ms).
Ya, di https://status.pdq.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 PDQ di sini secara bersamaan, masalahnya ada di pihak PDQ.
Cara kami mendeteksi dan memverifikasi gangguan · Sanggah laporan ini · Kami meninjau sanggahan dalam 24 jam.
Komentar komunitas
Share what you are seeing with PDQ. 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.