User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Telecom
xmatters.com · Telecom
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 1153 ms · 7 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 04:30 | 0 | 0.0 | 248 ms | 0 |
| 04:45 | 0 | 0.0 | 685 ms | 0 |
| 05:00 | 0 | 0.0 | 410 ms | 0 |
| 05:15 | 0 | 0.0 | 684 ms | 0 |
| 05:30 | 0 | 0.0 | 1016 ms | 0 |
| 05:45 | 0 | 0.0 | 468 ms | 0 |
| 06:00 | 0 | 0.0 | 869 ms | 0 |
| 06:15 | 0 | 0.0 | 530 ms | 0 |
| 06:30 | 0 | 0.0 | 602 ms | 0 |
| 06:45 | 0 | 0.0 | 204 ms | 0 |
| 07:00 | 0 | 0.0 | 1097 ms | 0 |
| 07:15 | 0 | 0.0 | 653 ms | 0 |
| 07:30 | 0 | 0.0 | 1612 ms | 0 |
| 07:45 | 0 | 0.0 | 564 ms | 0 |
| 08:00 | 0 | 0.0 | 922 ms | 0 |
| 08:15 | 0 | 0.0 | 224 ms | 0 |
| 08:30 | 0 | 0.0 | 497 ms | 0 |
| 08:45 | 0 | 0.0 | 884 ms | 0 |
| 09:00 | 0 | 0.0 | 946 ms | 0 |
| 09:15 | 0 | 0.0 | 1195 ms | 0 |
| 09:30 | 0 | 0.0 | 779 ms | 0 |
| 09:45 | 0 | 0.0 | 1337 ms | 0 |
| 10:00 | 0 | 0.0 | 586 ms | 0 |
| 10:15 | 0 | 0.0 | 636 ms | 0 |
| 10:30 | 0 | 0.0 | 217 ms | 0 |
| 10:45 | 0 | 0.0 | 371 ms | 0 |
| 11:00 | 0 | 0.0 | 1774 ms | 0 |
| 11:15 | 0 | 0.0 | 1475 ms | 0 |
| 11:30 | 0 | 0.0 | 778 ms | 0 |
| 11:45 | 0 | 0.0 | 1048 ms | 0 |
| 12:00 | 0 | 0.0 | 650 ms | 0 |
| 12:15 | 0 | 0.0 | 561 ms | 0 |
| 12:30 | 0 | 0.0 | 413 ms | 0 |
| 12:45 | 0 | 0.0 | 1104 ms | 0 |
| 13:00 | 0 | 0.0 | 498 ms | 0 |
| 13:15 | 0 | 0.0 | 993 ms | 0 |
| 13:30 | 0 | 0.0 | 692 ms | 0 |
| 13:45 | 0 | 0.0 | 195 ms | 0 |
| 14:00 | 0 | 0.0 | 548 ms | 0 |
| 14:15 | 0 | 0.0 | 135 ms | 0 |
| 14:30 | 0 | 0.0 | 1002 ms | 0 |
| 14:45 | 0 | 0.0 | 1227 ms | 0 |
| 15:00 | 0 | 0.0 | 1353 ms | 0 |
| 15:15 | 0 | 0.0 | 509 ms | 0 |
| 15:30 | 0 | 0.0 | 1047 ms | 0 |
| 15:45 | 0 | 0.0 | 639 ms | 0 |
| 16:00 | 0 | 0.0 | 829 ms | 0 |
| 16:15 | 0 | 0.0 | 1153 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for xMatters yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when xMatters goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send xMatters alerts to Slack, Discord or a webhook — free.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
If xMatters is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on xMatters's side.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.