During today's incident, an internal code change was deployed that inadvertently introduced a conflict in our system, resulting in dashboard access being unavailable and webhook triggered flows returning 500 errors.
During the disruption window of 11:54am to 12:18pm, webhooks will have failed to process and will need to be resent. We have identified the customers who were impacted during this period and our team will be reaching out directly to assist with any affected webhook flows.
If you have not been contacted and believe your webhooks may have been affected, please reach out to our Support team who will be happy to help.
We apologise for the disruption and inconvenience caused.
Posted May 26, 2026 - 11:43 UTC
Identified
Dashboard Restored, Investigation Ongoing
The dashboard is back online and should be operational. We are continuing to investigate the wider reach of this incident.
During the disruption, webhooks will have failed to process. We are actively looking into the extent of this impact.
If you are still experiencing any issues, please reach out to our Support team who will be happy to assist.
We will continue to investigate and monitor and provide further updates as they become available.
Thank you for your patience.
Posted May 26, 2026 - 11:35 UTC
Investigating
We are currently investigating reports of users experiencing issues accessing the dashboard.
Posted May 26, 2026 - 11:24 UTC
This incident affected: Dashboard (Dashboard UI) and Process Flows (Core Gateway (Events / Webhooks / API)).