Super Publishing Outage History
6 incidents recorded over the last 365 days, 6 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 Super Publishing Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 23, 2026 | Notion outage | 313h 28m | Resolved |
| Sep 30, 2026 | Database maintenance | 30 min | Resolved |
| Aug 27, 2026 | All hosted sites returning 404 | 1573h 19m | Resolved |
| Jul 24, 2026 | Notion sync degraded performance | 1643h 41m | Resolved |
| Jun 23, 2026 | Pages ends up with 404 | 1669h 49m | Resolved |
| Jun 9, 2026 | Some pages ends up with 404 | 2006h 48m | 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 Super Publishing 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 Super Publishing 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 Super Publishing 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 Super Publishing outage in this window ran 83d 14h, against a mean recovery of 50d 1h. If you depend on Super Publishing 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.