Is EIDO Healthcare down?

Last checked 9m ago
Current status
EIDO Healthcare is up

No incidents right now.

Official status page: https://status.eidohealthcare.com · Polled every 5 minutes · 6 components tracked

EIDO Healthcare is operational right now. Last checked 9m ago; the most recent incident resolved 1d ago.

Real-time EIDO Healthcare status, recent outages, and incident history — pulled directly from EIDO Healthcare's official status page at https://status.eidohealthcare.com every 5 minutes. Pingoru tracks 6 EIDO Healthcare services and has captured 24 incidents in the last 90 days (98.70% uptime). Get email, Slack, Discord, or webhook alerts the moment EIDO Healthcare reports a new incident — free for 5 monitors, no credit card.

Users who monitor EIDO Healthcare also follow these Healthcare services: Change Healthcare Dexcom Availity Magnus Health DrFirst WellSky Validic Phreesia Healthie TigerConnect View all 6,000+ providers
EIDO Healthcare uptime 98.70% uptime · past 90 days
Mon Wed Fri
MayJunJulAug
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 3h 18m
    Started Jul 06, 2026, 08:41 AM UTC · Resolved Jul 06, 2026, 12:00 PM UTC
    LondonAustralia
    Timeline · 2 updates
    • investigating · Jul 06, 2026, 08:41 AM UTC

      We are currently investigating this incident.

    • resolved · Jul 06, 2026, 12:00 PM UTC

      This incident has been resolved. The investigation identified an incorrectly configured CNAME record associated with a recent nameserver change. During review, the team discovered that an unintended postfix had been appended to a DNS record responsible for routing traffic between application components and document-generation services. Remedy introduced at 1pm and monitored. Service back to normal.

    Latest: This incident has been resolved. The investigation identified an incorrectly configured CNAME record associated with a recent nameserver change. During review, the team discovered …

  2. Resolved 3h 24m
    Started Jul 06, 2026, 08:35 AM UTC · Resolved Jul 06, 2026, 12:00 PM UTC
    LondonAustralia
    Timeline · 2 updates
    • investigating · Jul 06, 2026, 08:35 AM UTC

      We are currently investigating this incident.

    • resolved · Jul 06, 2026, 12:00 PM UTC

      This incident has been resolved. The investigation identified an incorrectly configured CNAME record associated with a recent nameserver change. During review, the team discovered that an unintended postfix had been appended to a DNS record responsible for routing traffic between application components and document-generation services. Remedy introduced at 1pm and monitored. Service back to normal.

    Latest: This incident has been resolved. The investigation identified an incorrectly configured CNAME record associated with a recent nameserver change. During review, the team discovered …

  3. Resolved
    Started May 14, 2026, 05:00 PM UTC · Resolved May 14, 2026, 05:00 PM UTC
    Timeline · 1 update
    • resolved · May 14, 2026, 05:00 PM UTC

      Type: Maintenance Duration: 4 hours Affected Components: London, Australia May 14, 17:00:01 GMT+0 - Identified - Maintenance is now in progress May 14, 21:00:00 GMT+0 - Completed - Maintenance has completed successfully May 14, 17:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time.

    Latest: Type: Maintenance Duration: 4 hours Affected Components: London, Australia May 14, 17:00:01 GMT+0 - Identified - Maintenance is now in progress May 14, 21:00:00 GMT+0 - Completed -…

Outage history

Past 90 days · 3 incidents View full outage history →