Skedda Outage History
4 incidents recorded over the last 365 days, 4 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 Skedda Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 10, 2026 | Degraded access to allbooked.comWe are aware of issues accessing allbooked.com for a subset of venues. This is due to an erroneous listing on a blocklist provider for our allbooked.com domain, which we are working with that provider to unlist as… | 12h 23m | Resolved |
| Feb 25, 2026 | Problems with transactional email delivery to Microsoft consumer inboxes (e.g. hotmail, outlook, live).This incident has been resolved. | 24h 25m | Resolved |
| Dec 5, 2025 | Elevated errors on Skedda's marketing pages (www.skedda.com)Cloudflare is no longer listing the incident on its status page and we have not seen any regression for the past hour, so we're marking this as resolved. | 1h 20m | Resolved |
| Nov 18, 2025 | Elevated Web App ErrorsCloudflare has resolved the underlying incident and we have seen no further issues from our side. | 8h 25m | 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 Skedda 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 Skedda 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 Skedda 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 Skedda outage in this window ran 1d, against a mean recovery of 11h 38m. If you depend on Skedda 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.