Störungsverlauf von Ticketleap

1. 23. Juli 2026 um 16:59 UTCinvestigating

   Im Epic Experiences Store treten kritische Netzwerkverbindungsprobleme auf, die die Verfügbarkeit des Dienstes beeinflussen. Unser Team untersucht.

2. 23. Juli 2026 um 17:06 UTCinvestigating

   Wir werden dieses Problem weiter untersuchen.

3. 23. Juli 2026 um 17:54 UTCinvestigating

   Das Problem hängt mit einem Ausfall des Cloud-Infrastrukturanbieters zusammen. Unser Team verfolgt die Situation genau und bereitet mögliche zusätzliche Minderungsmaßnahmen vor.

4. 23. Juli 2026 um 18:32 UTCinvestigating

   Der Laden ist jetzt online und die Dienste werden schrittweise wiederhergestellt. Unser Team wird die Situation weiterhin beobachten.

5. 23. Juli 2026 um 21:20 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 1. April 2026 um 14:51 UTCresolved

   Activations experienced a brief outage from 9:09 AM EDT to 9:36 AM EDT. This was caused by a network configuration mismatch during a security patch. Recovery was delayed due to a secondary technical block in our deployment pipeline. All systems are now stable

1. 16. Dezember 2025 um 19:54 UTCresolved

   The Mobile CMS experienced brief outages at approximately 10:21 AM EST and 10:29 AM EST, each lasting a few seconds. The issue was due to a performance bottleneck in our user-state data model for ticket-based audiences. During these windows, CMS users may have encountered slowness or temporary downtime. We have identified and planned improvements to help prevent future occurrences.

1. 17. Dezember 2025 um 16:19 UTCresolved

   The SSL certificate for several activation domains was removed from CloudFlare without notice and before its expiration date. We are working with CloudFlare support to determine the reason why the certificate was removed. This issue has been resolved.

1. 5. Dezember 2025 um 14:57 UTCresolved

   An outage with our cloud delivery network (CDN) provider caused clients and customers to not be able to visit our pages. Issue was from 2:56AM EST to 3:12AM EST.

1. 18. November 2025 um 15:28 UTCmonitoring

   An underlying cloud service is experiencing a partial outage. Users may experience intermittent errors. Engineering is monitoring.

2. 18. November 2025 um 15:33 UTCresolved

   This incident has been resolved.

1. 10. November 2025 um 17:53 UTCresolved

   ShowClix had an 18 minute outage this morning. Between 11:24 and 11:42 AM EST engineering noted elevated error rates while processing credit card payments due to an underlying network issue.

1. 20. Oktober 2025 um 16:08 UTCidentified

   An outage with our cloud provider is causing degraded performance on the system including but not limited to sending emails and loading files for some pages.

2. 20. Oktober 2025 um 21:04 UTCmonitoring

   Application errors have largely subsided. Engineering will continue to monitor as cloud services catch up.

3. 21. Oktober 2025 um 13:27 UTCresolved

   As of 6:53 PM EDT last night we reported full recovery.

1. 27. Mai 2025 um 16:04 UTCresolved

   At 8:20 PM EDT replication stopped on a read-only replica database which caused 404 responses when accessing data created or updated after that time. Engineering attempted to restart the database at 10:05 PM. However the process did not restart on its own, leading to connection failures to the replica database for a period of around 6 minutes. At 10:11 PM DEVOPS pulled the affected replica out of rotation which resolved all issues. Practically the effects were that customers and clients experienced “not found” errors when viewing some data (viewing orders, event configurations, etc.) between 8:20PM and 10:05 PM and widespread 500 errors (which render as the broken ticket page) when accessing the application (purchasing tickets, logging in, accessing the admin, etc). between 10:05 and 10:11 PM. This affected all ShowClix, Ticketbooth and white label clients.