All services / Health

medicare.gov · Health

Is Medicare.gov down?

Checks are succeeding and user reports are near the baseline.

What's broken? (optional)
Is it just me?
No problems detected

Live diagnosis

Is it just me?

Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.

Your browser → medicare.gov—
Your browser → us—
Our checksReaching it
Official · ReportsNo status feed · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—

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.

Live outage map

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.

User reports

0

Near baseline. 0 in the last hour. Typical hour is about 0.

Our checks

Reaching it

Last check reached it in 283 ms · 2 min ago.

Official status

No status feed

Medicare.gov does not publish a status feed we can read.

Reports and checks

Reports compared with the typical volume, with check latency and failures overlaid10324 msThu 01Fri 19Sun 13Tue 06Thu 00
ReportsTypical baselineCheck latencyFailed checkTimes in UTC
Numbers behind the chart
Time (UTC)ReportsBaselineLatencyFailed checks
Wed 1200.0324 ms0
Wed 1300.077 ms0
Wed 1400.0131 ms0
Wed 1500.0305 ms0
Wed 1600.0100 ms0
Wed 1700.0136 ms0
Wed 1800.0123 ms0
Wed 1900.0119 ms0
Wed 2000.0259 ms0
Wed 2100.0107 ms0
Wed 2200.0156 ms0
Wed 2300.072 ms0
Thu 0000.0241 ms0

Reliability

Score 100/100 · grade A

100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage

90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 2 days of data so far, so the 90-day numbers fill in over time.

Medicare.gov status badge Embed this status: free live Medicare.gov badge

Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server

Medicare.gov status and 30-day uptime badge

Past outages

No outages on record for Medicare.gov yet. Outages of 10 minutes or more get their own page here.

All Medicare.gov outages · Every recent outage

Having trouble with Medicare.gov?

One report per service every 10 minutes from this network. No account.

What's broken? (optional)

Notes are stored for rate-limit context and are not shown publicly.

About Medicare.gov

Medicare.gov is listed in our Health category and checked at medicare.gov. Live checks and user reports.

Medicare.gov has no official status feed we can read, so this page relies on our own checks and user reports.

Typical issues 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 2 days of checks. No public incidents logged since monitoring began 2 days ago.

Response time over the last 24 hours: 183 ms average, 28–771 ms range across 90 successful checks.

Questions

Is Medicare.gov down right now?

Checks are succeeding and user reports are near the baseline.

When was Medicare.gov last down?

We have not recorded a public Medicare.gov incident since monitoring began 2 days ago.

What is Medicare.gov's uptime?

From our own checks: 100% over 2 days of checks.

How fast does Medicare.gov respond?

183 ms on average over the last 24 hours (28–771 ms).

Does Medicare.gov have an official status page?

Not one we can read. This page uses independent checks of medicare.gov and user reports.

Medicare.gov not working for me but the status is fine. What now?

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 Medicare.gov here at once, the problem is on Medicare.gov's side.