Ticketleap driftsforstyrrelser

1. 21. oktober 2026 kl. 18.14 UTCmonitoring

   In response to a recently disclosed critical security vulnerability affecting systems worldwide, we have proactively implemented additional security protections across our platforms. These measures may result in intermittent access issues or unexpected errors for some users. Our teams are actively monitoring and adjusting these protections to minimize disruption while maintaining platform security. We appreciate your patience as we work to resolve these.

2. 21. oktober 2026 kl. 20.28 UTCresolved

   This incident has been resolved.

1. 7. oktober 2026 kl. 13.13 UTCresolved

   Aktiveringsplatform (API 'er, Public Web Activations, Admin CMS) lidt af forringet tilgængelighed mellem 8: 08 - 8: 52 AM EDT relateret til en intern DNS-problem med vores tjenester. Spørgsmålet om tilgængelighed blev løst, og undersøgelse for fuldstændig rod årsag og yderligere afbødning er i gang.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 7. oktober 2026 kl. 13.18 UTCinvestigating

   Aktiveringsplatform (API 'er, Public Web Activations, Admin CMS) lidt af forringet tilgængelighed mellem 8: 08 - 8: 52 AM EDT relateret til en intern DNS-problem med vores tjenester. Spørgsmålet om tilgængelighed blev løst, og undersøgelse for fuldstændig rod årsag og yderligere afbødning er i gang.

2. 7. oktober 2026 kl. 13.19 UTCidentified

   Spørgsmålet er blevet identificeret, og et fix er ved at blive gennemført.

3. 7. oktober 2026 kl. 13.19 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

4. 7. oktober 2026 kl. 13.19 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 16. september 2026 kl. 13.35 UTCresolved

   Den 16. september oplevede Blap Ticket en serviceforstyrrelse i 11 minutter forårsaget af en produktionsændring relateret til vores søgeinfrastruktur. Ændringen resulterede i en uventet stigning i databaseforbindelser, som udtømte den tilgængelige forbindelseskapacitet og midlertidigt påvirkede tilgængeligheden af applikationer. Når problemet blev identificeret, vores ingeniør team deaktiveret den berørte konfiguration og genoprettet normal service. Vi gennemgår hændelsen og vil gennemføre passende sikkerhedsforanstaltninger omkring tilslutningsgrænser, kapacitetsovervågning og produktionsændringer for at forhindre, at et lignende problem opstår i fremtiden. Vi undskylder forstyrrelsen og værdsætter din tålmodighed mens vores team arbejdede for at genoprette tjenesten.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 23. juli 2026 kl. 16.59 UTCinvestigating

   The Epic Experiences Store oplever kritiske netværkstilslutningsproblemer, der påvirker tilgængeligheden af service. Vores hold efterforsker.

2. 23. juli 2026 kl. 17.06 UTCinvestigating

   Vi fortsætter med at undersøge dette spørgsmål.

3. 23. juli 2026 kl. 17.54 UTCinvestigating

   Spørgsmålet er relateret til en afbrydelse på cloud infrastruktur udbyder. Vores team følger situationen nøje og forbereder yderligere afbødende tiltag.

4. 23. juli 2026 kl. 18.32 UTCinvestigating

   Butikken er nu online og tjenester er gradvist genoprette. Vores team vil fortsat overvåge situationen.

5. 23. juli 2026 kl. 21.20 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 1. april 2026 kl. 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. december 2025 kl. 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. december 2025 kl. 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. december 2025 kl. 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 kl. 15.28 UTCmonitoring

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

2. 18. november 2025 kl. 15.33 UTCresolved

   This incident has been resolved.

1. 10. november 2025 kl. 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 kl. 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 kl. 21.04 UTCmonitoring

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

3. 21. oktober 2025 kl. 13.27 UTCresolved

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

1. 27. maj 2025 kl. 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.