Is It Down? microsoft.com
UP
Current
200
HTTP Code
91
Response ms
100%
Uptime (20)
8
Outages
Response Time Last 20 Checks
UP DOWN
Recent Checks (Last 20 Pings)
| Time (America/New_York) | Status | HTTP Code | Response (ms) | |
|---|---|---|---|---|
| 20:53:49 · 12.05.2026 | UP | 200 | 91 | |
| 20:40:05 · 12.05.2026 | UP | 200 | 90 | |
| 20:20:07 · 12.05.2026 | UP | 200 | 442 | |
| 20:00:07 · 12.05.2026 | UP | 200 | 96 | |
| 19:40:06 · 12.05.2026 | UP | 200 | 428 | |
| 19:20:06 · 12.05.2026 | UP | 200 | 88 | |
| 19:00:07 · 12.05.2026 | UP | 200 | 433 | |
| 18:40:06 · 12.05.2026 | UP | 200 | 449 | |
| 18:20:07 · 12.05.2026 | UP | 200 | 450 | |
| 18:00:07 · 12.05.2026 | UP | 200 | 429 | |
| 17:40:06 · 12.05.2026 | UP | 200 | 422 | |
| 17:20:07 · 12.05.2026 | UP | 200 | 441 | |
| 17:00:08 · 12.05.2026 | UP | 200 | 91 | |
| 16:40:07 · 12.05.2026 | UP | 200 | 429 | |
| 16:20:08 · 12.05.2026 | UP | 200 | 432 | |
| 16:00:07 · 12.05.2026 | UP | 200 | 442 | |
| 15:40:06 · 12.05.2026 | UP | 200 | 464 | |
| 15:20:07 · 12.05.2026 | UP | 200 | 493 | |
| 15:00:10 · 12.05.2026 | UP | 200 | 429 | |
| 14:40:06 · 12.05.2026 | UP | 200 | 103 |
20:53:49
12.05.2026
UP HTTP 200 · 91ms
20:40:05
12.05.2026
UP HTTP 200 · 90ms
20:20:07
12.05.2026
UP HTTP 200 · 442ms
20:00:07
12.05.2026
UP HTTP 200 · 96ms
19:40:06
12.05.2026
UP HTTP 200 · 428ms
19:20:06
12.05.2026
UP HTTP 200 · 88ms
19:00:07
12.05.2026
UP HTTP 200 · 433ms
18:40:06
12.05.2026
UP HTTP 200 · 449ms
18:20:07
12.05.2026
UP HTTP 200 · 450ms
18:00:07
12.05.2026
UP HTTP 200 · 429ms
17:40:06
12.05.2026
UP HTTP 200 · 422ms
17:20:07
12.05.2026
UP HTTP 200 · 441ms
17:00:08
12.05.2026
UP HTTP 200 · 91ms
16:40:07
12.05.2026
UP HTTP 200 · 429ms
16:20:08
12.05.2026
UP HTTP 200 · 432ms
16:00:07
12.05.2026
UP HTTP 200 · 442ms
15:40:06
12.05.2026
UP HTTP 200 · 464ms
15:20:07
12.05.2026
UP HTTP 200 · 493ms
15:00:10
12.05.2026
UP HTTP 200 · 429ms
14:40:06
12.05.2026
UP HTTP 200 · 103ms
Last Detected Downtime
error:0A000438:SSL routines::tlsv1 alert internal error
All Recorded Outages
| Time (America/New_York) | HTTP | Response (ms) | Error | |
|---|---|---|---|---|
| 2026-05-06 03:40:09 | 301 | 2923 | ||
| 2026-05-05 17:00:09 | 301 | 2235 | ||
| 2026-05-04 17:00:12 | 301 | 6047 | ||
| 2026-05-04 16:40:08 | 301 | 2385 | ||
| 2026-05-04 07:00:12 | 301 | 5101 | ||
| 2026-05-03 16:00:11 | 301 | 4448 | ||
| 2026-05-03 15:40:09 | 301 | 3156 | ||
| 2026-05-03 10:40:10 | 301 | 4059 |
03:40:09
06.05.2026
DOWN
HTTP 301 · 2923ms
17:00:09
05.05.2026
DOWN
HTTP 301 · 2235ms
17:00:12
04.05.2026
DOWN
HTTP 301 · 6047ms
16:40:08
04.05.2026
DOWN
HTTP 301 · 2385ms
07:00:12
04.05.2026
DOWN
HTTP 301 · 5101ms
16:00:11
03.05.2026
DOWN
HTTP 301 · 4448ms
15:40:09
03.05.2026
DOWN
HTTP 301 · 3156ms
10:40:10
03.05.2026
DOWN
HTTP 301 · 4059ms
Recently Checked Sites
| Website | Status | HTTP | Response | Uptime | |
|---|---|---|---|---|---|
| DOWN | 6001 ms | 0% |
|||
| DOWN | 42 ms | 0% |
|||
| UP | 200 | 602 ms | 87.5% |
||
| UP | 200 | 60 ms | 100% |
||
| DOWN | 406 | 461 ms | 0% |
||
| UP | 200 | 4487 ms | 100% |
||
| UP | 200 | 46 ms | 100% |
||
| UP | 200 | 145 ms | 100% |
||
| UP | 200 | 332 ms | 15% |
||
| UP | 200 | 85 ms | 100% |
About This Check
We send an HTTP HEAD request from our Frankfurt, Germany server to microsoft.com. A response of HTTP 200–399 within 10 seconds = UP. Any timeout, DNS failure, or error code = DOWN. A rolling history of the last 20 checks is stored and displayed above.
If the site shows UP here but you can't access it, the issue is local flush your DNS cache (ipconfig /flushdns on Windows / sudo dscacheutil -flushcache on macOS) or try a different network.
For community-reported outage data and user comments, check DownDetector microsoft.com.