Deliverect Outage History
5 incidents recorded over the last 365 days, 5 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.
Every Recorded Deliverect Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 26, 2026 | Order processing delaysBetween 13:13 and 13:42 UTC on 26 September, some customers experienced errors or delays with order processing. Our team identified the issue and restored normal service at 13:42 UTC. We are reviewing the incident and… | -174 min | Resolved |
| Sep 18, 2026 | Order processing errorsBetween 16:55 and 17:14 UTC on 15 September, some customers experienced errors or delays with order processing. Our team identified the issue and restored normal service at 17:14 UTC. We are reviewing the incident and… | -3939 min | Resolved |
| Apr 23, 2026 | Menu Pushes FailingThis incident has been resolved. | 1h 0m | Resolved |
| Dec 5, 2025 | Global Cloudflare OutageThe incident has been resolved and our services and products are fully operational again. | 10 min | Resolved |
| Nov 18, 2025 | Intermittent Retail Order Processing InterruptionWe noticed a service interruption impacting our Retail Order Processing and related front-end UIs in several regions. The root cause was identified as a major global outage affecting our critical third-party provider… | 0 min | Resolved |
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 Deliverect 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 Deliverect 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 Deliverect 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 Deliverect outage in this window ran 1h, against a mean recovery of 23 min. If you depend on Deliverect 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.