Ticketmatic Outage History
5 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 Ticketmatic Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 21, 2026 | PHP kwetsbaarhedenTicketmatic is volledig online Beste klant, De beveiligingsupdate is geïnstalleerd en getest. Ticketmatic is weer volledig beschikbaar en alle diensten werken normaal. Dank voor uw geduld en begrip. Met vriendelijke… | 2h 30m | Resolved |
| Jun 26, 2026 | Service DisruptionThis incident has been resolved. The platform has been operating normally since approximately 11:00 CEST. The interruption was caused by a data-handling issue that placed excessive load on one of our databases; the… | 2h 46m | Resolved |
| May 7, 2026 | Service DisruptionBetween 9:00 and 10:00 today, part of our back office was unavailable, affecting backoffice users. Customer-facing ticket services were not impacted. The disruption was caused by a security update to our… | 1h 12m | Resolved |
| Apr 1, 2026 | Service DisruptionThis incident has been resolved. | 41 min | Resolved |
| Mar 12, 2026 | Scheduled Infrastructure MaintenanceThe scheduled maintenance has been completed. | 10 min | Scheduled |
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 Ticketmatic 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 Ticketmatic 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 Ticketmatic 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 Ticketmatic outage in this window ran 2h 46m, against a mean recovery of 1h 28m. If you depend on Ticketmatic 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.