User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Health
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps 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. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 2 hr ago. Last stored result reached it in 436 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 12:00 | 0 | 0.0 | 251 ms | 0 |
| 14:00 | 0 | 0.0 | 223 ms | 0 |
| 16:15 | 0 | 0.0 | 328 ms | 0 |
| 18:15 | 0 | 0.0 | 460 ms | 0 |
| 20:15 | 0 | 0.0 | 259 ms | 0 |
| 22:15 | 0 | 0.0 | 393 ms | 0 |
| 00:15 | 0 | 0.0 | 463 ms | 0 |
| 02:30 | 0 | 0.0 | 313 ms | 0 |
| 04:30 | 0 | 0.0 | 313 ms | 0 |
| 06:30 | 0 | 0.0 | 272 ms | 0 |
| 08:45 | 0 | 0.0 | 436 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Claim MD 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 Claim MD goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Claim MD alerts to Slack, Discord or a webhook — free.
Claim MD, at claim.md, is one of the Health services we monitor. Claim.MD helps providers, billers, software vendors, and payers create, submit, validate, and track medical claims with fast EDI transactions and real-time eligibility.
Claim MD publishes an official status page at status.claim.md; when we can read it, its incident level is folded into the status shown here.
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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 335 ms average, 223–463 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Claim MD incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
335 ms on average over the last 24 hours (223–463 ms).
Yes, at https://status.claim.md.
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 Claim MD here at once, the problem is on Claim MD's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Claim MD. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.