HoneyBook 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 HoneyBook Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 1, 2026 | Mobile push notifications are not being delivered | 85h 10m | Resolved |
| Aug 23, 2026 | Email communication temporarily queued | 1660h 6m | Resolved |
| Jun 24, 2026 | Service Disruptions | 1642h 36m | Resolved |
| Jun 9, 2026 | Automations 2.0 Degraded Performance | 1996h 28m | 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 HoneyBook 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 HoneyBook 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 HoneyBook 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 HoneyBook outage in this window ran 83d 4h, against a mean recovery of 56d 2h. If you depend on HoneyBook 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.