Is EIDO Healthcare down?
Last checked 9m agoNo incidents right now.
Free · no credit card
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.
Recent outages & incidents
Past 90 days- 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 …
-
- 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 …
-
-
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 -…
-
- Started Jul 06, 2026, 08:41 AM UTC · Resolved Jul 06, 2026, 12:00 PM UTC · 3h 18m
- Started Jul 06, 2026, 08:35 AM UTC · Resolved Jul 06, 2026, 12:00 PM UTC · 3h 24m
- Started May 14, 2026, 05:00 PM UTC · Resolved May 14, 2026, 05:00 PM UTC · —