edoobox Outage History

12 incidents recorded over the last 365 days, 12 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live edoobox status99.95% uptime history

Every Recorded edoobox Incident

edoobox incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 11, 2026edoobox APP1 Server Outage (Nine)This incident has been resolved.1h 5mResolved
Jul 20, 2026Booking Process DisruptionThis incident has been resolved.2h 56mResolved
Jul 2, 2026edoobox APP2 Server Outage (Google)This incident has been resolved.3h 7mResolved
May 21, 2026edoobox APP1 Server Outage (Nine)This incident has been resolved.11h 42mResolved
May 20, 2026edoobox APP1 Server Outage (Nine)This incident has been resolved.3h 14mResolved
May 20, 2026edoobox APP1 Server Outage (Nine)This incident has been resolved.25 minResolved
May 20, 2026edoobox APP1 Server Outage (Nine)This incident has been resolved.20 minResolved
Apr 3, 2026Regional Network Disruption DetectedThis incident has been resolved.3h 7mResolved
Jan 3, 2026APP2 SSL Certificate IssueThis incident has been resolved.31 minResolved
Dec 15, 2025Caching APP2This incident has been resolved.1h 59mResolved
Nov 18, 2025CloudflareThis incident has been resolved.7h 16mResolved
Nov 8, 2025edoobox APP2 Server Outage (Google)This incident has been resolved.2h 22mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next edoobox incident opens instead, at the point where knowing still changes what you do.

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

How to Read This edoobox Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before edoobox acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single edoobox outage in this window ran 11h 42m, against a mean recovery of 3h 10m. If you depend on edoobox in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.