Ticketleap 中断历史

1. 2026年10月21日 UTC 18:14monitoring

   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. 2026年10月21日 UTC 20:28resolved

   This incident has been resolved.

1. 2026年10月7日 UTC 13:13resolved

   启动平台(API、公共网络激活、行政管理系统)在8:08-8:52之间因与我们服务有关的内部DNS问题而出现退化。 可用性问题已经解决,正在调查彻底的根源和进一步缓解.

自动翻译自官方事件更新。

1. 2026年10月7日 UTC 13:18investigating

   启动平台(API、公共网络激活、行政管理系统)在8:08-8:52之间因与我们服务有关的内部DNS问题而出现退化。 可用性问题已经解决,正在调查彻底的根源和进一步缓解.

2. 2026年10月7日 UTC 13:19identified

   这一问题已经确定,一个解决办法正在实施之中.

3. 2026年10月7日 UTC 13:19monitoring

   一项措施已经执行,我们正在监测结果.

4. 2026年10月7日 UTC 13:19resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年9月16日 UTC 13:35resolved

   9月16日,由于与我们搜索基础设施有关的生产配置改变,Leap Ticketing经历了11分钟的服务中断. 这一变化导致数据库连接量出人意料地增加,从而耗尽了现有的连接能力并暂时影响了应用程序的可用性。 问题一经确定,我们的工程队就使受影响的配置失效并恢复正常服务。 我们正在审查这一事件,并将围绕连接限制、能力监测和生产变化实施适当的保障措施,以防止今后发生类似问题。 我们为干扰道歉 并感谢你的耐心 在我们团队努力恢复服务时.

自动翻译自官方事件更新。

1. 2026年7月23日 UTC 16:59investigating

   Epic Investments Store正在经历影响服务提供的关键网络连接问题。 我们的团队正在调查.

2. 2026年7月23日 UTC 17:06investigating

   我们正在继续调查这一问题.

3. 2026年7月23日 UTC 17:54investigating

   这个问题与云基础设施供应商停电有关。 我们的小组正在密切注视局势,并准备可能的额外缓解行动.

4. 2026年7月23日 UTC 18:32investigating

   该商店现已上线,服务正在逐步恢复。 我们的小组将继续监测局势.

5. 2026年7月23日 UTC 21:20resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年4月1日 UTC 14:51resolved

   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. 2025年12月16日 UTC 19:54resolved

   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. 2025年12月17日 UTC 16:19resolved

   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. 2025年12月5日 UTC 14:57resolved

   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. 2025年11月18日 UTC 15:28monitoring

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

2. 2025年11月18日 UTC 15:33resolved

   This incident has been resolved.

1. 2025年11月10日 UTC 17:53resolved

   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. 2025年10月20日 UTC 16:08identified

   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. 2025年10月20日 UTC 21:04monitoring

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

3. 2025年10月21日 UTC 13:27resolved

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

1. 2025年5月27日 UTC 16:04resolved

   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.