Claim.MD logo

Is Claim.MD Down?

SaaSLive status, outages, and incident history

No. Claim.MD is up right now.

Every monitored Claim.MD system is operational as of November 14, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 7m agoLive · every 60s

Know the moment Claim.MD breaks

Claim.MD is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official Claim.MD status page
How we know: the official Claim.MD status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Claim.MD Status Summary

As of 19:13 UTC on 14 November 2026, Claim.MD is operational. PulsAPI checked Claim.MD's official status page and found 4 of 4 components operational, with no active incidents. The latest incident, "Claim.MD Portal Access", was on Nov 5, 2026 and lasted 53 min.

Cite as: PulsAPI, “Claim.MD status”, checked 14 November 2026, 19:13 UTC. https://www.pulsapi.com/services/claim-md

Claim.MD Component Status

The main Claim.MD systems on this page. All 4 are operational right now.

4operational
API
Operational
Phone System
Operational
SFTP
Operational

1 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Web Portal.

See all of them free

Component statuses may change independently during partial outages.

Recent Claim.MD Outages & Incidents

Incident history from the official Claim.MD status page, including resolution updates.

Claim.MD Portal AccessResolved Nov 5, 2026 · 53 minResolved

**Incident Post-Mortem: Portal Access Disruption** **Root Cause:** Our investigation determined that a failing process within our CI/CD pipeline prevented newly provisioned load balancing servers from starting correctly, resulting in intermittent access issues to the [Claim.MD](http://Claim.MD) portal. **Resolution:** The underlying issue was identified and resolved, and all systems have returned to normal operation. **Preventive Measures:** We are implementing additional redundancy and safeguards within our CI/CD pipeline to improve resilience and prevent similar disruptions in the future. We apologize for the inconvenience and appreciate your patience while our team worked to resolve the issue. --- [2026-11-05T07:04:18.340-07:00] (resolved) The issue affecting access to the Claim.MD portal has been resolved. All systems are now operating normally. We apologize for any inconvenience this may have caused. --- [2026-11-05T06:11:07.892-07:00] (investigating) We are continuing to investigate this issue. --- [2026-11-05T06:10:38.360-07:00] (investigating) We are currently experiencing an issue affecting access to the Claim.MD portal. Our team is actively investigating and working to restore normal access. We will provide updates as more information becomes available.

Portal login issues.Resolved Sep 18, 2026 · 1h 35mResolved

This incident has been resolved. --- [2026-09-18T16:55:24.751-06:00] (monitoring) The issue affecting new logins to the web portal has been identified and resolved. The disruption was caused by a recent system update that unexpectedly interrupted the login process. We are continuing to monitor the system to ensure login functionality remains stable. --- [2026-09-18T16:26:23.804-06:00] (investigating) We are currently experiencing issues with new logins to the web portal, and are investigating the problem.

Claim.MD Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Claim.MD incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history3 days observed
Nov 12100.00% averageNov 14

Live Claim.MD Outage Reports

Problems reported by engineers using Claim.MD. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Claim.MD problems reported yet.

Something wrong with Claim.MD on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Claim.MD

Is Claim.MD down? Its official status page at status.claim.md reports on 4 components, including API, Phone System and SFTP. PulsAPI checks it every few minutes and can alert you when Claim.MD reports an incident.

Claim.MD Status FAQ

Is Claim.MD down right now?

The verdict at the top of this page comes from the latest poll of the official Claim.MD status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Claim.MD is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Claim.MD recovers.

How do I check Claim.MD uptime history?

PulsAPI tracks Claim.MD uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Claim.MD changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Claim.MD outages?

PulsAPI reads the official Claim.MD status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Claim.MD components?

Yes. PulsAPI monitors 4 individual Claim.MD components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Claim.MD goes down?

Yes. Create a free account and subscribe to Claim.MD: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Claim.MD to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Claim.MD problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Claim.MD?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Claim.MD plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Claim.MD with the rest of your stack

4372+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services