Ticketmatic experienced a notice incident on October 8, 2016, lasting 15m. The incident has been resolved; the full update timeline is below.
Update timeline
- investigating Oct 08, 2016, 06:07 AM UTC
There is a possible service disruption causing part of the internal api calls to fail. Investigating.
- identified Oct 08, 2016, 06:15 AM UTC
An internal service failed over and was put in read-only mode, we are restoring the service now.
- resolved Oct 08, 2016, 06:23 AM UTC
The service seems fully operational again, we keep following up
- postmortem Aug 03, 2018, 05:32 PM UTC
We have identified the root cause of the outage. Our internal caching service experienced problems and an automatic failover was triggered to restore functionality. Failover occured quickly and without problems. But due to a bad endpoint configuration, our system did not use the new service and could not start up. The configuration is now fixed, future failovers will not cause this problem anymore.