Inevent 장애 기록

1. 2026년 10월 21일 오후 1:42 UTCidentified

   10월 21일 수요일 오전 10:00 EDT (14:00 UTC)에, 우리는 우리의 서버에 비상 보안 업데이트를 적용합니다. PHP 프로젝트는 오늘 두 가지 중요한 취약점 (CVE-2026-109618 및 CVE-2026-109619)에 대한 수정을 발표하고 있습니다. 이들은 PHP 자체의 원격 코드 실행 결함, CVSS v4.0 스케일에 9.2 평가. PHP는 대략 7 10 웹 사이트에서, 그리고 문제점은 기업 넓은 비상사태로 대우됩니다. InEvent 플랫폼과 데이터 보안을 유지하기 위해 출시된대로 업데이트 적용 예상할 것: 헝겊 조각을 안전하게 적용하기 위하여, 우리는 갱신이 완료될 때까지 정비 형태로 플랫폼을 끼워넣을지도 모릅니다. 이 시간 동안 InEvent 플랫폼, API, 이벤트 페이지 및 앱은 평소보다 일시적으로 사용할 수 없거나 느리게 될 수 있습니다. 이 창에서 실행되는 이벤트는 영향을 미칠 수 있습니다. 우리는 가능한 한 짧은 유지 보수 창을 유지하고 작업 진행으로 업데이트합니다. 자주 묻는 질문 오늘 실행하고 도움이 필요하면 지원 팀에 문의하십시오. PHP 보안 릴리스에 대한 자세한 내용은 php.net을 방문하십시오.

2. 2026년 10월 21일 오후 1:52 UTCidentified

   수정은 현재 적용되고 우리는 곧 다시 시작합니다.

3. 2026년 10월 22일 오후 1:14 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 9월 30일 오후 3:33 UTCinvestigating

   우리는 일부 관리자가 자동화 된 bi-weekly digest email을 예정보다 자주 얻는 보고서를 찾고 있습니다. digest 이메일 만 영향을받습니다. 다른 모든 이메일 및 플랫폼 기능은 일반적으로 작동됩니다. 추가 다이제스트 이메일을 삭제할 수 있으며 계정에 아무것도 할 필요가 없습니다. 우리는 더 많은 정보가 있기 때문에 또 다른 업데이트를 게시합니다.

2. 2026년 9월 30일 오후 3:44 UTCresolved

   이 문제는 해결됩니다. 자동화된 Bi-weekly digest 이메일이 예정된 것보다 더 자주 전송되는 코드 이슈를 발견했습니다. 다이제스트 이메일은 정상적인 일정에 다시 표시됩니다. 다른 이메일이나 플랫폼 기능은 영향을 미쳤습니다. 추가 다이제스트 이메일을 받으면 삭제할 수 있으며 계정에서 아무것도 할 필요가 없습니다. 불편을 드려 죄송합니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 18일 오후 10:22 UTCidentified

   We are currently investigating degraded performance affecting email sending and intermittent platform responsiveness. Some users may experience delays when sending emails, loading pages, or refreshing certain areas of the platform. In some cases, recently created email drafts or interface updates may take longer than expected to appear. Our engineering team has identified increased platform load and email queue processing as contributing factors. To stabilize the environment, we have temporarily paused part of the email sending daemon while we optimize the related database queries and processing flow. Event registration and core platform data continue to be processed. If an item does not appear immediately in the interface, we recommend waiting a few moments and refreshing the page. We are actively monitoring the platform and will provide another update as soon as additional information is available.

2. 2026년 6월 18일 오후 10:53 UTCmonitoring

   Platform performance has improved after the earlier traffic spike subsided. Email queue processing has been re-enabled, and we are continuing to monitor database load and platform responsiveness. During the incident, elevated traffic caused increased database utilization, which resulted in slower query processing and intermittent delays across some platform requests. Current load levels are stable, and the platform is operating within acceptable thresholds. Our engineering team will continue monitoring the environment and optimizing the affected database queries and email processing flow.

3. 2026년 6월 19일 오전 12:50 UTCresolved

   This incident has been resolved.

1. 2024년 11월 20일 오후 6:50 UTCresolved

   Incident Summary We experienced a slowdown in the API’s ability to issue new tokens. This caused delays for some users attempting to generate tokens. Current Status The underlying issue has been identified and resolved. Changes have been applied, and we are actively monitoring the system to ensure stability. Users experiencing issues are advised to refresh their browsers, which should resolve the problem. Next Steps We will continue to monitor the performance and ensure that the service remains stable. A post-incident analysis will be conducted, and a full report will be made available. Thank you for your patience. If you experience further issues, please contact our support team.

1. 2024년 5월 9일 오후 10:28 UTCresolved

   We have identified an issue with our email provider when sending payment emails and we recently deployed a fix. New emails will be sent right away and emails from the past 72 hours that were not sent yet have been added to our queue and are being sent now.

1. 2024년 4월 2일 오전 9:34 UTCresolved

   We have identified slowness when opening certain modules of the UK Server Region and we have deployed a fix to the problem. A small percentage of users may have received a "Bad Gateway" response when connecting between 11:00 AM and 11:05 AM (CET) to the Virtual Lobby of the UK Server.

1. 2024년 3월 19일 오후 3:53 UTCresolved

   We had an issue with AWS auto scaling module that caused our servers to take longer than expected to reach the desired scaling point and that caused our servers to stop responding for a period of 5 minutes (the time that it took to reach the desired scaling point). This behavior is out of the ordinary and we have several scaling procedures running every day. Our team is investigating what caused this momentary issue and will apply a fix.

1. 2023년 3월 29일 오전 8:40 UTCinvestigating

   We are investigating an issue with Mux (mux.com) Streaming Platform that is rejecting new InEvent Live Studio streams due to an outage on their end. Our recommendation for now is to use Video Conferencing or RTMP modes for customers that need to stream content. Once we have updates from Mux, we will update this incident report.

2. 2023년 3월 29일 오전 8:40 UTCinvestigating

   We are still waiting for Mux support to contact us.

3. 2023년 3월 29일 오전 9:17 UTCidentified

   Mux has identified the issue and deployed a fix. We will be monitoring the results and update this report soon.

4. 2023년 3월 29일 오전 9:21 UTCresolved

   This incident has been resolved.

1. 2023년 3월 9일 오전 10:00 UTCinvestigating

   We are investigating an issue with the European Servers that are causing a response delay and Gateway Timeouts on certain requests.

2. 2023년 3월 9일 오전 10:05 UTCidentified

   We have identified a DNS issue that caused our server requests to queue and severely delay their responses on API requests. The API microservices had to wait more than anticipated for a DNS resolution and that caused timeouts with a Gateway Timeout HTTP error. We have deployed another DNS server to be used and this may take up to 30 minutes to take effect and requests starts to normalize. We will be monitoring the resolution development.

3. 2023년 3월 9일 오전 10:09 UTCmonitoring

   The DNS servers are now responsive and our Load Balancer is now draining pending requests and flushing old requests in favor of new ones. New API calls will be handled normally and we will be monitoring the results.

4. 2023년 3월 9일 오전 10:19 UTCmonitoring

   We are continuing to monitor the servers. The API calls are now 100% responsive and without degraded performance.

5. 2023년 3월 9일 오전 10:25 UTCresolved

   This incident has been resolved. Our European Servers are fully operational.

1. 2023년 1월 27일 오후 10:15 UTCinvestigating

   We have identified an issue on Mux's CDN that's affecting all Live Studio streams. Streams that lasts for more than an hour might have AV Synchronization issues due to an internal issue on Mux's servers.

2. 2023년 1월 27일 오후 10:16 UTCresolved

   This issue has been resolved.

1. 2022년 12월 16일 오후 7:19 UTCinvestigating

   This incident happened on Postmark's end. For further information, please go to https://status.postmarkapp.com/incidents/277086

2. 2022년 12월 16일 오후 7:19 UTCinvestigating

   We are continuing to investigate this issue.

3. 2022년 12월 17일 오전 7:23 UTCresolved

   This incident has been resolved.

1. 2022년 9월 21일 오전 7:04 UTCresolved

   There was an issue with our Subnet Traffic Control policy in our public AWS VPC that was blocking HTTP and HTTPS traffic. Once we identified the issue and applied the fixes, there was a delay that lasted for around 30 minutes to apply the new policy to all our subnets.

1. 2022년 7월 28일 오후 5:33 UTCinvestigating

   Our subprocessor Postmark is having issues delivering emails. Although delayed, all emails will still be delivered. We will update this incident when new information arises.

2. 2022년 7월 28일 오후 7:31 UTCresolved

   This incident has been resolved.

1. 2022년 2월 25일 오후 9:42 UTCinvestigating

   The Virtual Lobby is unresponsive and we are investigating the reason. The rest of the platform is working normally.

2. 2022년 2월 25일 오후 9:42 UTCresolved

   We have identified the issue and fixed it. The Virtual Lobby should now open normally on Desktop and also on Mobile devices.

3. 2022년 2월 25일 오후 9:43 UTCpostmortem

   This issue was caused due to a code deployment we did to add support to custom Push Notifications with dynamic content \(first-name, last-name, email, etc\). This code had, in some circumstances, a loop that would cause your browser tab to crash and freeze completely. We reverted this code and we will evaluate another way to build dynamic content to Push Notifications.

1. 2021년 11월 16일 오후 5:58 UTCinvestigating

   We are checking with Google the status of the issue. For now, we recommend switching to the Native WebSockets option under Event > Tools.

2. 2021년 11월 16일 오후 5:58 UTCinvestigating

   We are continuing to investigate this issue.

3. 2021년 11월 16일 오후 6:06 UTCmonitoring

   We have implemented a fix which allows you to connect to the Virtual Lobby with limited connectivity. While Google Firebase is offline, we recommend to switch to InEvent native websockets under Settings > Tools.

4. 2021년 11월 16일 오후 6:08 UTCmonitoring

   Google Firebase issue can also be seen here on this page https://status.firebase.google.com/

5. 2021년 11월 16일 오후 6:21 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 2021년 11월 16일 오후 6:23 UTCresolved

   The issue has been mitigated and the service has been restored. https://status.firebase.google.com/incidents/Xed5fGf9USDWdzsqN4GX

7. 2021년 11월 16일 오후 6:25 UTCpostmortem

   **Google Firebase** had a major global outage this afternoon that lasted for 6 minutes. This outage impacted our **Virtual Lobby**, but the overall functionality still worked, with limited connectivity to _Chats, Questions, Group Rooms_ and _interactions_. You can check out **Google’s** official statement here: [https://status.firebase.google.com/incidents/Xed5fGf9USDWdzsqN4GX](https://status.firebase.google.com/incidents/Xed5fGf9USDWdzsqN4GX)

1. 2021년 9월 13일 오후 2:48 UTCinvestigating

   We are currently seeing a slow scalability response from the InEvent Firebase socket group. We are currently investigating the issue with Google Firebase team.

2. 2021년 9월 13일 오후 2:55 UTCidentified

   We have identified the slowness from the Firebase product. We are deploying an alternative with the Native websockets, under Company > Tools. We are currently deploying a fix for UI improvements on the Firebase UI console while Firebase is not responsive. Chat may be offline while the fix is being applied, but video and streaming should work normally.

3. 2021년 9월 13일 오후 3:45 UTCidentified

   We currently fixed an autoscaling Redis instance that was not able to redirect the load to a separate system. Redis is used by InEvent to quickly balance its write operations instead of relying only on a traditional SQL database. The following components are still affected: Firebase Web Sockets, which covers the live chat on the Virtual Lobby.

4. 2021년 9월 13일 오후 5:07 UTCmonitoring

   The team has concluded the implementation of all temporary solutions on the platform. This includes creating a timeout option on slow connecting sockets and also disabled Redis as a single connection. The web socket chat will remain with limited chat support on the firebase instance until we add support for per instance local connection, which should happen next week. The Redis cache team will be implementing a new permanent solution end of this week, Friday at the latest.

5. 2021년 9월 13일 오후 9:15 UTCresolved

   This incident has been resolved.

6. 2021년 9월 13일 오후 9:16 UTCpostmortem

   ## What is a “Websocket”? Without getting into too much detail, a **Websocket** is a method of network communication that is used for real time applications. We use **Websocket** for real time communication and interaction, and these are the modules that uses the **Websocket** service: * News Feed; * Inbox; * Session Chat; * Session Q&A; * Networking; * Creation of Group Rooms; * Invitations; * Push Notifications; * Live updates \(session settings changes\); * Networking Roulette; ## Issues with Native Websocket and Regular Websocket \(Google Firebase\) We have two Websocket providers, Google Firebase \(realtime database\) and our own implementation \(Native Websocket\). Today we had a large amount of users connecting at the same time and this caused the Websocket servers to halt. Google Firebase couldn’t scale fast enough and the Native Websockets couldn’t handle the scale either. The issue resulted on users having the “Connecting” popup showing up and never disappearing. ## Issues with Caching Server \(Redis\) We had a major outage with our Caching server \(Redis\) that caused the entire platform and backend to go offline. The Redis server clogged up and couldn’t handle the server scaling and load, and this resulted in an overall failure of the platform. The landing page and login page were still operational. ## Fixes implemented For **Native Websockets** we have implemented a manual scale for now and we will work on the autoscaling mechanism to support a large load in the future. If the connection fails, you will still be able to use the Virtual Lobby normally, with limited interaction. For **Google Firebase** we couldn’t implement a fix. We will try sharding the entire operation into multiple micro services for different modules \(Chat, Q&A, etc\), but since they don’t support replicas, it will be hard to scale on large events. If your event has more than 5,000 users, it’s better to use **Native Websockets**. If the connection fails, you will still be able to use the Virtual Lobby normally, with limited interaction. For **Caching Server \(redis\)** we are still implementing a fix but we did deploy a temporary workload that should replace the caching server for now and keep the platform and the backend stable. This is an internal fix and shouldn’t affect the user experience. ## What to expect for this week The platform backend and all its modules should be operational. In case **Native Websockets** or **Google Firebase** fails, you will still be able to access the platform and the Virtual Lobby, but users will have a limited experience without realtime interactions – chat, Q&A and the other modules listed above will not be operational. We are constantly working on improvements and we will announce when we have both realtime **Websockets** fully functional for large events. Meanwhile, we can guarantee that the backend and the Virtual Lobby will be online – even in case of limited realtime experience.

1. 2021년 7월 28일 오전 3:12 UTCresolved

   AWS had an outage in our North America region and the failover and recovery mechanism took action. During 10:59:30 PM - 11:00:30 PM EDT, the website was slow and unresponsive. This issue has been fixed in 1 minute.

1. 2021년 7월 20일 오후 4:50 UTCresolved

   We encountered issues when using Low Latency with custom domains and we fixed it. The Low Latency Control Room option uses the Amazon AWS IVS technology for Low Latency Streaming (sub 5 seconds) and the 1.3.0 version of its IVS Video.js Player had an issue when working with cross-origin resource sharing (CORS) that resulted in a player with a frozen state (a pitch-black image with a blue play button that didn't work when pressing it). We have updated the player plugin to its newest version (1.3.1) and implemented fixes that will also circumvent CORS issues in the future -- a fallback to the regular iFrame using InEvent's domain in case the custom domain doesn't work (visually indistinguishable for regular users).

2. 2021년 7월 20일 오후 4:50 UTCpostmortem

   **Affected users:** Events with _Custom Domain_ enabled that used _Control Room_ video modes with the _Low Latency_ enabled. **Workaround:** Disable _Custom Domain_ or change the video latency to _Standard_. **Issue description:** We encountered issues when using _Control Room_ video mode with _Low Latency_ enabled and also using a _Custom Domain_ at the same time. The _Low Latency Control Room_ option uses the [Amazon AWS IVS](https://aws.amazon.com/ivs/) technology for Low Latency Streaming \(sub 5 seconds\) and the 1.3.0 version of its IVS Video.js Player had an issue when working with Cross-Origin Resource Sharing \(CORS\) that resulted in a player with a frozen state \(a pitch-black image with a blue play button that didn't work when pressing it\). We are still not sure if this issue was caused by the 1.3.0 version of the player or if it was an underlying issue with the _playlist url_ and the CORS headers sent by their servers. **Fix:** We updated the player plugin to its newest version \(1.3.1\) and implemented fixes that will also circumvent CORS issues in the future. This solution implements a fallback to InEvent's domain in case the _Custom Domain_ doesn't work - the fallback only affects the Video Player and not the actual parent window \(visually indistinguishable for regular users\). We also contacted AWS IVS support for further assistance. Per our throughout test, the player now works with _Custom Domains_ \(either on event level or company level\) on all browsers.

1. 2021년 2월 24일 오후 5:53 UTCinvestigating

   Google is our socket hosting provider and their servers are offline. We are investigating this incident with Google engineers. https://status.firebase.google.com/incident/Console/21001

2. 2021년 2월 24일 오후 9:48 UTCresolved

   This incident has been resolved.

1. 2021년 2월 3일 오후 1:56 UTCinvestigating

   We are currently investigating this issue.

2. 2021년 2월 3일 오후 1:57 UTCmonitoring

   We have identified unhealthy server replicas that were being treated as healthy servers, resulting in poor connectivity to our platform. We have deployed a fix for this issue.

3. 2021년 2월 3일 오후 1:57 UTCresolved

   This incident has been resolved.