If you have any questions about past incidents or scheduled maintenance, please don't hesitate to message our support team on live chat or email.
Bookwhen tracks incidents to keep you informed about any issues that may have affected the platform. This helps you understand any disruptions and their resolution.
This article provides information on previous Bookwhen platform incidents and how they were addressed.
Current Incidents
Scheduled Maintenance
No upcoming maintenance is planned.
Past Incidents
August 29, 2025
Post-event Email Broadcast Issue
Issue ❗️
We are currently experiencing a technical issue with our email provider, Postmark, which is affecting the deliverability of broadcast emails to Microsoft domains such as Outlook and Hotmail. Emails sent to Office 365 addresses are delivering as expected.
This issue specifically impacts users of our Post-Event Email feature. Postmark’s Engineering and Deliverability teams are actively investigating and working to resolve the situation.
We apologise for the inconvenience and appreciate your patience.
Sept 1, 13:08 BST
August 17, 2025
Bookwhen processing delays
Resolved ✅
Our Engineering Team has now resolved this incident. We sincerely apologise for any inconvenience caused. Please let us know if you face any further issues (support@bookwhen.com).
Aug 17, 16:41 BST
Issue ❗️
There was a delay in processing requests which, unfortunately, affected several parts of our system (emails, event reminders, Zoom meeting updates and waiting lists.). When an engineer noticed, they intervened immediately, and the backed-up jobs started processing.
Aug 17, 14:45 BST
October 29, 2024
Bookwhen is temporarily down in some places
Resolved ✅
Our engineering Team has now resolved this incident. We sincerely apologise for any inconvenience caused. Please let us know if you face any further issues (support@bookwhen.com).
Oct 29, 11:07 GMT
Issue ❗️
We are aware of a technical issue which has resulted in an outage of Bookwhen. Admins and customers cannot access Bookwhen.com - our team are aware and working hard to resolve this issue and restore service.
Oct 29, 10:28 GMT
