Skip to content

Outage tracker / CMS.gov / In the US

Is CMS.gov down in the US?

Checks passingin the US, measured from Ashburn and San Jose

All 2 of our probes in the US, in Ashburn and San Jose, read checks passing when they last checked CMS.gov at Nov 5, 2026, 4:48 PM UTC.

Over the last 24 hours we completed 251 checks from Ashburn and San Jose and 251 answered cleanly, 100.00% availability.

Of the 2 other regions we check CMS.gov from, all 2 read checks passing right now.

Email me the next time we see CMS.gov go down

One email when our checks of CMS.gov fail from two or more distant regions, and one when they pass, after you confirm the address. No account, no card.

This is our own reading from outside. It is not CMS.gov's official status.

What our Ashburn and San Jose probes measured

AshburnChecks passing142 checks in 24h, 100.00%
San JoseChecks passing109 checks in 24h, 100.00%

Last checked Nov 5, 2026, 4:48 PM UTC.

CMS.gov from Ashburn and San Jose over the last 30 days

Over the last 30 days, CMS.gov answered our Ashburn probe in 1,088 ms on average, and 1 check in 20 took longer than 2,126 ms.

Over the last 30 days, CMS.gov answered our San Jose probe in 1,458 ms on average, and 1 check in 20 took longer than 2,221 ms.

Ranked by average response time across the 4 cities we check CMS.gov from, Ashburn 1st, San Jose 3rd; Ashburn was fastest at 1,088 ms and Tokyo slowest at 2,377 ms.

From Ashburn and San Jose we ran 772 checks of CMS.gov in 4 days, and 772 answered cleanly: 100.00% availability.

Every one of those days was clean: not one failed check.

In Ashburn local time (EST), CMS.gov was slowest around 5 PM, at 1,575 ms on average over the last 14 days, and quickest around 1 PM, at 682 ms.

Day (UTC)ChecksAvailabilityAverage response
Thu, Nov 5174100.00%1,304 ms
Wed, Nov 4250100.00%1,101 ms
Tue, Nov 3245100.00%1,246 ms
Mon, Nov 2103100.00%1,512 ms

CMS.gov outages measured from the US

Our Ashburn and San Jose probes measured no confirmed CMS.gov outage in the last 90 days.

How the other regions read right now

Of the 2 other regions we check CMS.gov from, all 2 read checks passing right now.

Probe cityRight nowLast 24h
FrankfurtChecks passing100.00% of 97 checks
TokyoChecks passing100.00% of 59 checks

Other countries we check CMS.gov from

How we measured this

The US readings on this page come from RealUptime's own Ashburn and San Jose probes against CMS.gov's public endpoints. They are not user reports, and they are not CMS.gov's own status page.

See CMS.gov's full check readings, the 90-day history by region, or the outage tracker methodology.

The US readings here are taken from that country and show the time of the last one, but CMS.gov has not yet accumulated enough continuous history for us to publish this page to search engines.

Check your own site from Ashburn

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter