Laporan pengguna
0
Mendekati normal. 0 dalam satu jam terakhir. Biasanya sekitar 0 per jam.
Damn, is it down?
Semua layanan / AI
phenom.com · AI
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Status resmi: Potential performance degradation with Phenom Scheduling Services due to Microsoft Exchange Incident
Sumber: halaman status vendor · Kami tidak berafiliasi dengan Phenom.
Perkiraan perbaikan: Not enough Phenom history yet; similar AI outages lasted 27 min (median, typically 9 min–2 h; 41 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 9 min ago. Last stored result reached it in 317 ms.
Insiden kecil
Potential performance degradation with Phenom Scheduling Services due to Microsoft Exchange Incident Halaman status resmi
| Waktu (UTC) | Laporan | Garis dasar | Latensi | Pengecekan gagal |
|---|---|---|---|---|
| Tue 02 | 0 | 0.0 | 465 ms | 0 |
| Tue 04 | 0 | 0.0 | 368 ms | 0 |
| Tue 06 | 0 | 0.0 | 372 ms | 0 |
| Tue 09 | 0 | 0.0 | 414 ms | 0 |
| Tue 11 | 0 | 0.0 | 355 ms | 0 |
| Tue 13 | 0 | 0.0 | 254 ms | 0 |
| Tue 15 | 0 | 0.0 | 345 ms | 0 |
| Tue 17 | 0 | 0.0 | 450 ms | 0 |
| Tue 20 | 0 | 0.0 | 411 ms | 0 |
| Tue 22 | 0 | 0.0 | 356 ms | 0 |
| Wed 00 | 0 | 0.0 | 372 ms | 0 |
| Wed 02 | 0 | 0.0 | 252 ms | 0 |
| Wed 05 | 0 | 0.0 | 439 ms | 0 |
| Wed 07 | 0 | 0.0 | 300 ms | 0 |
| Wed 09 | 0 | 0.0 | 425 ms | 0 |
| Wed 11 | 0 | 0.0 | 412 ms | 0 |
| Wed 13 | 0 | 0.0 | 374 ms | 0 |
| Wed 16 | 0 | 0.0 | 363 ms | 0 |
| Wed 18 | 0 | 0.0 | 204 ms | 0 |
| Wed 20 | 0 | 0.0 | 393 ms | 0 |
| Wed 22 | 0 | 0.0 | 383 ms | 0 |
| Thu 00 | 0 | 0.0 | 426 ms | 0 |
| Thu 02 | 0 | 0.0 | 450 ms | 0 |
| Thu 05 | 0 | 0.0 | 295 ms | 0 |
| Thu 07 | 0 | 0.0 | 347 ms | 0 |
| Thu 09 | 0 | 0.0 | 307 ms | 0 |
| Thu 11 | 0 | 0.0 | 419 ms | 0 |
| Thu 13 | 0 | 0.0 | 305 ms | 0 |
| Thu 15 | 0 | 0.0 | 324 ms | 0 |
| Thu 17 | 0 | 0.0 | 257 ms | 0 |
| Thu 19 | 0 | 0.0 | 243 ms | 0 |
| Thu 21 | 0 | 0.0 | 327 ms | 0 |
| Thu 23 | 0 | 0.0 | 372 ms | 0 |
| Fri 00 | 0 | 0.0 | 352 ms | 0 |
| Fri 02 | 0 | 0.0 | 501 ms | 0 |
| Fri 04 | 0 | 0.0 | 371 ms | 0 |
| Fri 06 | 0 | 0.0 | 379 ms | 0 |
| Fri 08 | 0 | 0.0 | 326 ms | 0 |
| Fri 10 | 0 | 0.0 | 413 ms | 0 |
| Fri 12 | 0 | 0.0 | 334 ms | 0 |
| Fri 14 | 0 | 0.0 | 316 ms | 0 |
| Fri 16 | 0 | 0.0 | 382 ms | 0 |
| Fri 18 | 0 | 0.0 | 340 ms | 0 |
| Fri 19 | 0 | 0.0 | 332 ms | 0 |
| Fri 20 | 0 | 0.0 | 352 ms | 0 |
| Fri 21 | 0 | 0.0 | 362 ms | 0 |
| Fri 23 | 0 | 0.0 | 376 ms | 0 |
| Sat 01 | 0 | 0.0 | 320 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 8 days of data so far, so the 90-day numbers fill in over time.
Scheduled maintenance
Phenom will be performing scheduled maintenance to optimize the performance of platform services in the Production environments of the US, Canada, India, Ireland and CR regions, and in the Staging environments of the Ireland and India regions. Please be advised that there will be scheduled downtime during which users may experience intermittent issues while accessing the accessing career sites…
Pemeliharaan terencana bukan gangguan. Waktu dan kata-katanya berasal dari vendor. Outage Weather →
Belum ada catatan gangguan untuk Phenom. 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 Phenom down dan saat pulih kembali. Gratis. Konfirmasi lewat email, berhenti berlangganan kapan saja.
Mau di kanal tim? Kirim peringatan Phenom ke Slack, Discord, atau webhook — gratis.
Phenom terdaftar di kategori AI kami dan dicek di phenom.com.
Phenom menerbitkan halaman status resmi di status.phenom.com; jika dapat kami baca, tingkat insidennya ikut diperhitungkan dalam status yang ditampilkan di sini.
Masalah umum pada layanan AI: respons lambat atau gagal, galat batas penggunaan, dan API timeout.
Uptime terukur dari pengecekan kami: 100% selama 8 hari pengecekan. Tidak ada insiden publik yang tercatat sejak pemantauan dimulai 8 hari lalu.
Waktu respons selama 24 jam terakhir: rata-rata 362 ms, rentang 316–501 ms dari 15 pengecekan yang berhasil.
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Status resmi: Potential performance degradation with Phenom Scheduling Services due to Microsoft Exchange Incident
Kami belum mencatat insiden publik Phenom sejak pemantauan dimulai 8 hari lalu.
Dari pengecekan kami sendiri: 100% selama 8 hari pengecekan.
Rata-rata 362 ms selama 24 jam terakhir (316–501 ms).
Ya, di https://status.phenom.com.
Biasanya masalahnya lokal: coba browser lain atau aplikasinya, beralih antara Wi-Fi dan data seluler, lalu hapus cache. Untuk layanan AI, perhatikan respons lambat atau gagal, galat batas penggunaan, dan API timeout. Jika banyak orang melaporkan Phenom di sini secara bersamaan, masalahnya ada di pihak Phenom.
Cara kami mendeteksi dan memverifikasi gangguan · Sanggah laporan ini · Kami meninjau sanggahan dalam 24 jam.
Komentar komunitas
Share what you are seeing with Phenom. 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.