Laporan pengguna
0
Mendekati normal. 0 dalam satu jam terakhir. Biasanya sekitar 0 per jam.
Damn, is it down?
Semua layanan / Produktivitas
teams.microsoft.com · Produktivitas
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Status resmi: Microsoft 365 (Business or Enterprise): Service degradation. Affected: Exchange Online: Users may be unable to access their mailbox using Outlook on the web, Outlook desktop (MA...
Sumber: halaman status vendor · Kami tidak berafiliasi dengan Microsoft Teams.
Perkiraan perbaikan: Not enough Microsoft Teams history yet; similar Productivity outages lasted 45 min (median, typically 14 min–4 h; 27 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 6 min ago. Last stored result reached it in 134 ms.
Insiden kecil
Microsoft 365 (Business or Enterprise): Service degradation. Affected: Exchange Online: Users may be unable to access their mailbox using Outlook on the web, Outlook desktop (MAPI), Exch... | Microsoft 365 (Consumer): Users may be unable to access or perform several actions in Microsoft 365 services Halaman status resmi
| Waktu (UTC) | Laporan | Garis dasar | Latensi | Pengecekan gagal |
|---|---|---|---|---|
| 02:45 | 0 | 0.0 | 372 ms | 0 |
| 03:00 | 0 | 0.0 | 177 ms | 0 |
| 03:15 | 0 | 0.0 | 272 ms | 0 |
| 03:30 | 0 | 0.0 | 181 ms | 0 |
| 03:45 | 0 | 0.0 | 204 ms | 0 |
| 04:00 | 0 | 0.0 | 233 ms | 0 |
| 04:15 | 0 | 0.0 | 206 ms | 0 |
| 04:30 | 0 | 0.0 | 136 ms | 0 |
| 04:45 | 0 | 0.0 | 183 ms | 0 |
| 05:00 | 0 | 0.0 | 176 ms | 0 |
| 05:15 | 0 | 0.0 | 161 ms | 0 |
| 05:30 | 0 | 0.0 | 205 ms | 0 |
| 05:45 | 0 | 0.0 | 162 ms | 0 |
| 06:00 | 0 | 0.0 | 154 ms | 0 |
| 06:15 | 0 | 0.0 | 174 ms | 0 |
| 06:30 | 0 | 0.0 | 264 ms | 0 |
| 06:45 | 0 | 0.0 | 187 ms | 0 |
| 07:00 | 0 | 0.0 | 154 ms | 0 |
| 07:15 | 0 | 0.0 | 157 ms | 0 |
| 07:30 | 0 | 0.0 | 158 ms | 0 |
| 07:45 | 0 | 0.0 | 188 ms | 0 |
| 08:00 | 0 | 0.0 | 143 ms | 0 |
| 08:15 | 0 | 0.0 | 159 ms | 0 |
| 08:30 | 0 | 0.0 | 134 ms | 0 |
| 08:45 | 0 | 0.0 | 130 ms | 0 |
| 09:00 | 0 | 0.0 | 143 ms | 0 |
| 09:15 | 0 | 0.0 | 302 ms | 0 |
| 09:30 | 0 | 0.0 | 159 ms | 0 |
| 09:45 | 0 | 0.0 | 151 ms | 0 |
| 10:00 | 0 | 0.0 | 278 ms | 0 |
| 10:15 | 0 | 0.0 | 231 ms | 0 |
| 10:30 | 0 | 0.0 | 149 ms | 0 |
| 10:45 | 0 | 0.0 | 167 ms | 0 |
| 11:00 | 0 | 0.0 | 189 ms | 0 |
| 11:15 | 0 | 0.0 | 157 ms | 0 |
| 11:30 | 0 | 0.0 | 164 ms | 0 |
| 11:45 | 0 | 0.0 | 196 ms | 0 |
| 12:00 | 0 | 0.0 | 138 ms | 0 |
| 12:15 | 0 | 0.0 | 476 ms | 0 |
| 12:30 | 0 | 0.0 | 347 ms | 0 |
| 12:45 | 0 | 0.0 | 101 ms | 0 |
| 13:00 | 0 | 0.0 | 157 ms | 0 |
| 13:15 | 0 | 0.0 | 467 ms | 0 |
| 13:30 | 0 | 0.0 | 133 ms | 0 |
| 13:45 | 0 | 0.0 | 189 ms | 0 |
| 14:00 | 0 | 0.0 | 151 ms | 0 |
| 14:15 | 0 | 0.0 | 134 ms | 0 |
| 14:30 | 0 | 0.0 | 309 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 13 days of data so far, so the 90-day numbers fill in over time.
Belum ada catatan gangguan untuk Microsoft Teams. 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 Microsoft Teams down dan saat pulih kembali. Gratis. Konfirmasi lewat email, berhenti berlangganan kapan saja.
Mau di kanal tim? Kirim peringatan Microsoft Teams ke Slack, Discord, atau webhook — gratis.
Berjalan di: Microsoft Azure
Microsoft Teams terdaftar di kategori Produktivitas kami dan dicek di teams.microsoft.com.
Microsoft Teams menerbitkan halaman status resmi di status.cloud.microsoft; jika dapat kami baca, tingkat insidennya ikut diperhitungkan dalam status yang ditampilkan di sini.
Masalah umum pada layanan Produktivitas: file tidak tersinkron, editor tidak termuat, dan masalah login.
Uptime terukur dari pengecekan kami: 100% selama 13 hari pengecekan. Tidak ada insiden publik yang tercatat sejak pemantauan dimulai 13 hari lalu.
Waktu respons selama 24 jam terakhir: rata-rata 251 ms, rentang 92–1468 ms dari 181 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 (Business or Enterprise): Service degradation. Affected: Exchange Online: Users may be unable to access their mailbox using Outlook on the web, Outlook desktop (MA...
Kami belum mencatat insiden publik Microsoft Teams sejak pemantauan dimulai 13 hari lalu.
Dari pengecekan kami sendiri: 100% selama 13 hari pengecekan.
Rata-rata 251 ms selama 24 jam terakhir (92–1468 ms).
Ya, di https://status.cloud.microsoft/.
Biasanya masalahnya lokal: coba browser lain atau aplikasinya, beralih antara Wi-Fi dan data seluler, lalu hapus cache. Untuk layanan Produktivitas, perhatikan file tidak tersinkron, editor tidak termuat, dan masalah login. Jika banyak orang melaporkan Microsoft Teams di sini secara bersamaan, masalahnya ada di pihak Microsoft Teams.
Cara kami mendeteksi dan memverifikasi gangguan · Sanggah laporan ini · Kami meninjau sanggahan dalam 24 jam.
Community comments
Share what you are seeing with Microsoft Teams. 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.