User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Health
cms.gov · Health
Checks are succeeding and user reports are near the baseline.
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 487 ms · 7 min ago.
No status feed
CMS does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Wed 12 | 0 | 0.0 | 89 ms | 0 |
| Wed 13 | 0 | 0.0 | 224 ms | 0 |
| Wed 14 | 0 | 0.0 | 80 ms | 0 |
| Wed 15 | 0 | 0.0 | 116 ms | 0 |
| Wed 16 | 0 | 0.0 | 158 ms | 0 |
| Wed 17 | 0 | 0.0 | 56 ms | 0 |
| Wed 18 | 0 | 0.0 | 161 ms | 0 |
| Wed 19 | 0 | 0.0 | 91 ms | 0 |
| Wed 20 | 0 | 0.0 | 184 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 CMS 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 CMS goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send CMS alerts to Slack, Discord or a webhook — free.
We track CMS (cms.gov) as part of the Health group. Live checks and user reports.
CMS has no official status feed we can read, so this page relies on our own checks and user reports.
What usually goes wrong with health services: patient portal and member sign-in failures, prescription refills or appointment booking not going through, and app errors.
Measured uptime from our checks: 100% over 1 day of checks. No public incidents logged since monitoring began 1 day ago.
Response time over the last 24 hours: 187 ms average, 39–1208 ms range across 61 successful checks.
Checks are succeeding and user reports are near the baseline.
We have not recorded a public CMS incident since monitoring began 1 day ago.
From our own checks: 100% over 1 day of checks.
187 ms on average over the last 24 hours (39–1208 ms).
Not one we can read. This page uses independent checks of cms.gov and user reports.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For health services, watch for patient portal and member sign-in failures, prescription refills or appointment booking not going through, and app errors. If many people report CMS here at once, the problem is on CMS's side.