Bizzabo 장애 기록

1. 2026년 9월 1일 오후 3:56 UTCidentified

   우리의 팀은 플랫폼에 대한 연결성에 영향을 미치는 문제를 식별했습니다. 이는 성능과 선적 문제를 발생시킵니다. 우리는 현재 우리의 연결에 변화를 구현하여 안정성 향상 및 정상적인 성능을 복원합니다. 우리는 최고 우선 순위로 이것을 취급하고 더 많은 정보를 사용할 수 있기 때문에 더 많은 업데이트를 공유합니다.

2. 2026년 9월 1일 오후 4:18 UTCmonitoring

   우리는 솔루션을 구현하고 모든 것이 원활하게 실행되도록 상황을 적극적으로 모니터링하고 있습니다. 우리는 일을 가까운 눈을 계속 유지하고 필요한 업데이트를 제공 할 것입니다. 당신의 인내와 이해에 감사드립니다.

3. 2026년 9월 1일 오후 6:05 UTCresolved

   우리는 문제가 해결 된 것을보고 기쁘게 생각합니다. 모든 것이 정상으로 돌아갑니다. 우리는 우리가 문제를 해결하기 위해 일하면서 인내심이 발생하고 인내심을 평가 할 수 있습니다. 더 궁금한 점이나 우려가 있으시면 알려주십시오.

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

1. 2025년 11월 18일 오후 12:02 UTCidentified

   We’ve identified that a broader Cloudflare incident is causing intermittent 503 errors when accessing Bizzabo. Our engineering team is actively implementing mitigations to route around/temporarily disable Cloudflare in affected regions. You can follow the Cloudflare status page here: https://www.cloudflarestatus.com/. Thank you for your understanding, and please don't hesitate to reach out to [email protected] with any additional concerns.

2. 2025년 11월 18일 오후 12:20 UTCmonitoring

   The Bizzabo platform has returned to normal operation. We’re closely monitoring performance and error rates while Cloudflare continues its incident response. If you still experience issues, please contact [email protected]. We’ll share another update shortly.

3. 2025년 11월 18일 오후 12:32 UTCmonitoring

   We have implemented a solution and are actively monitoring the situation to ensure that everything is running smoothly. We will continue to keep a close eye on things and will provide any necessary updates. Thank you for your patience and understanding.

4. 2025년 11월 18일 오후 5:46 UTCresolved

   We're happy to report that the Cloudflare incident has been resolved, and everything is back to normal. We apologize for any inconvenience this may have caused and appreciate your patience. Please let us know if you have any further questions or concerns.

1. 2025년 11월 11일 오전 9:02 UTCidentified

   We have identified the cause of the issue and are working on a fix. We will continue to monitor the situation and provide updates as needed. Thank you for your understanding, and please don't hesitate to reach out to [email protected] with any additional concerns

2. 2025년 11월 11일 오전 10:05 UTCidentified

   We’re seeing recovery across the platform. The system performance is improving. We’ll keep working on the fix and provide the next update as progress continues.

3. 2025년 11월 11일 오전 10:54 UTCidentified

   We’ve concluded our remediation actions and are monitoring for full recovery. Platform metrics show drastic improvement, and we expect performance to return to normal levels. We’ll continue to observe and post the next update shortly.

4. 2025년 11월 11일 오전 11:46 UTCmonitoring

   We have implemented a solution and are actively monitoring the situation to ensure that everything is running smoothly. We will continue to keep a close eye on things and will provide any necessary updates. Thank you for your patience and understanding.

5. 2025년 11월 11일 오후 2:01 UTCresolved

   We're happy to report that the issue has been resolved, and everything is back to normal. We apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the issue. Please let us know if you have any further questions or concerns.

1. 2025년 10월 20일 오전 7:39 UTCidentified

   We’re currently observing a widespread issue with our cloud service provider, AWS, which is affecting portions of our system functionality. Our team is actively monitoring the situation and will provide updates as more information becomes available.

2. 2025년 10월 20일 오전 9:40 UTCmonitoring

   We’re seeing recovery across our services and normal functionality is restored. The underlying AWS issue is largely mitigated, and we’ll continue monitoring for any minor delays until it’s fully solved.

3. 2025년 10월 20일 오후 3:00 UTCidentified

   We’re seeing a recurrence of the AWS incident, which is impacting parts of our platform. Some features may be slow or return errors. We’re actively monitoring and will share updates as recovery progresses.

4. 2025년 10월 20일 오후 3:09 UTCmonitoring

   We are actively monitoring the situation to ensure that everything is running smoothly. We will continue to keep a close eye on things and will provide any necessary updates. Thank you for your patience and understanding.

5. 2025년 10월 20일 오후 4:02 UTCidentified

   We’re seeing a renewed AWS incident impacting parts of our platform. We’re actively monitoring and will update as recovery progresses. For AWS status, see https://health.aws.amazon.com/health/status

6. 2025년 10월 20일 오후 8:43 UTCidentified

   We continue to experience issues related to the AWS service disruption (https://health.aws.amazon.com/health/status). We are continuing to monitor the situation and will provide updates as recovery progresses.

7. 2025년 10월 20일 오후 9:15 UTCmonitoring

   AWS has implemented a solution and we are actively monitoring the situation to ensure that everything is running smoothly. We will continue to keep a close eye on things and will provide any necessary updates. Thank you for your patience and understanding.

8. 2025년 10월 21일 오전 8:19 UTCresolved

   Service has returned to normal and all components are operational. The AWS disruption has been resolved. Thank you for your patience.

1. 2025년 10월 16일 오후 2:03 UTCinvestigating

   We are currently investigating an issue affecting some users attempting to register through sites using the registration widget. Impacted users may see an error message indicating registration failed. While we work to resolve this, affected users can typically complete their registration by clearing their browser’s cache and cookies, or by using a private/incognito window. We will share another update as soon as more information becomes available. Thank you for your patience as we work to restore full functionality.

2. 2025년 10월 16일 오후 5:25 UTCinvestigating

   Our team is still investigating the issue and gathering all relevant information. We will provide updates as soon as possible and appreciate your patience as we work towards a resolution.

3. 2025년 10월 16일 오후 9:19 UTCidentified

   We have identified the cause of the issue and are working on a fix. We will continue to monitor the situation and provide updates as needed. Thank you for your understanding, and please don't hesitate to reach out to [email protected] with any additional concerns

4. 2025년 10월 17일 오전 8:06 UTCresolved

   We're happy to report that the issue has been resolved, and everything is back to normal. We apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the issue. Please let us know if you have any further questions or concerns.

1. 2025년 8월 21일 오후 5:39 UTCinvestigating

   Our team is currently investigating the issue and gathering all relevant information. We will provide updates as soon as possible and appreciate your patience as we work towards a resolution.

2. 2025년 8월 21일 오후 7:12 UTCidentified

   We have identified the cause of the issue and are working on a fix. We will continue to monitor the situation and provide updates as needed. Thank you for your understanding, and please don't hesitate to reach out to [email protected] with any additional concerns

3. 2025년 8월 21일 오후 7:28 UTCidentified

   We have identified that the issue originates outside of Bizzabo, through our Cloudflare service provider. Cloudflare is reporting a system-wide issue, which you can follow here: https://www.cloudflarestatus.com/ We are actively working with our provider to resolve this disruption as quickly as possible.

4. 2025년 8월 21일 오후 7:37 UTCmonitoring

   We have implemented a solution and are actively monitoring the situation to ensure that everything is running smoothly. We will continue to keep a close eye on things and will provide any necessary updates. Thank you for your patience and understanding.

5. 2025년 8월 21일 오후 8:41 UTCresolved

   We're happy to report that the issue has been resolved, and everything is back to normal. We apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the issue. Please let us know if you have any further questions or concerns.

1. 2025년 8월 19일 오후 1:15 UTCinvestigating

   Our team is currently investigating the partial downtime affecting Organizer Dashboards and Event Websites. We are gathering all relevant information to resolve this issue. We will provide updates as soon as possible and appreciate your patience during this time.

2. 2025년 8월 19일 오후 1:20 UTCmonitoring

   We have implemented a solution and are actively monitoring the situation to ensure that everything is running smoothly. We will continue to keep a close eye on things and will provide any necessary updates. Thank you for your patience and understanding.

3. 2025년 8월 19일 오후 2:31 UTCresolved

   This incident has been resolved.

1. 2025년 6월 12일 오후 7:04 UTCidentified

   We are currently experiencing an issue impacting our Reporting Hub. Customers may encounter a "Trouble Loading Data" error when viewing their reports. This issue has been identified as related to an ongoing incident with Google Cloud (https://status.cloud.google.com/). We are actively monitoring the situation and will provide updates as new information becomes available. Thank you for your patience. For any additional concerns, please contact us at [email protected].

2. 2025년 6월 12일 오후 7:29 UTCidentified

   Update: The issue impacting our Reporting Hub is now also affecting our OCA and Klik products. Customers may continue to see a "Trouble Loading Data" error when accessing these services. Google Cloud is actively working on resolving the issue. We will keep monitoring closely and provide updates as they become available. For the latest status, please visit Google's status page (https://status.cloud.google.com/). Thank you for your continued patience. For additional assistance, please contact us at [email protected].

3. 2025년 6월 12일 오후 7:43 UTCidentified

   The update from Google states: "Our engineers have identified the root cause and have applied appropriate mitigations. While our engineers have confirmed that the underlying dependency is recovered in all locations except us-central1, we are aware that customers are still experiencing varying degrees of impact on individual google cloud products. All the respective engineering teams are actively engaged and working on service recovery."

4. 2025년 6월 12일 오후 8:22 UTCidentified

   The update from Google states: "We have identified the root cause and applied appropriate mitigations. Our infrastructure has recovered in all regions except us-central1. Google Cloud products that rely on the affected infrastructure are seeing recovery in multiple locations. Our engineers are aware of the customers still experiencing issues on us-central1 and multi-region/us and are actively working on full recovery."

5. 2025년 6월 12일 오후 9:01 UTCmonitoring

   This is from the Google Team: "We have implemented mitigation for the issue in us-central1 and multi-region/us and we are seeing signs of recovery. We have received confirmation from our internal monitoring and customers that the Google Cloud products are also seeing recovery in multiple regions and are also seeing signs of some recovery in us-central1 and mutli-region/us. We expect the recovery to complete in less than an hour."

6. 2025년 6월 12일 오후 9:43 UTCmonitoring

   From the Google team: "Most of the Google Cloud products have confirmed full service recovery. A few services are still seeing some residual impact and the respective engineering teams are actively working on recovery of those services. We expect the recovery to complete in less than an hour."

7. 2025년 6월 12일 오후 11:32 UTCmonitoring

   Message from the Google team: "The following Google Cloud products are still experiencing residual impact: Google Cloud Dataflow: Customers may experience delays with Dataflow operations as the backlog is clearing up gradually. Vertex AI Online Prediction: Customers may continue to experience elevated 5xx errors with some of the models available in the Model Garden. Personalized Service Health: Updates on the Personalized Service Health are delayed and we recommend customers to continue using Cloud Service Health dashboard for updates."

8. 2025년 6월 13일 오전 12:52 UTCresolved

   We're happy to report that the issue has been resolved, and everything is back to normal. We apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the issue. Please let us know if you have any further questions or concerns.

1. 2025년 4월 16일 오후 2:22 UTCinvestigating

   We are getting reports of the Bizzabo Dashboard performing slowly or producing errors. Our team is currently investigating the issue and gathering all relevant information. We will provide updates as soon as possible and appreciate your patience as we work towards a resolution.

2. 2025년 4월 16일 오후 2:29 UTCmonitoring

   We have implemented a solution and are actively monitoring the situation to ensure that everything is running smoothly. We will continue to keep a close eye on things and will provide any necessary updates. Thank you for your patience and understanding.

3. 2025년 4월 16일 오후 3:46 UTCresolved

   We're happy to report that the issue has been resolved, and everything is back to normal. We apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the issue. Please let us know if you have any further questions or concerns.

1. 2025년 1월 22일 오후 7:08 UTCinvestigating

   Our team is currently investigating an issue that is currently causing instability on the platform, and we are gathering all relevant information. We will provide updates as soon as possible and appreciate your patience as we work towards a resolution.

2. 2025년 1월 22일 오후 7:32 UTCidentified

   We have identified the cause of the issue and are working on a fix. We will continue to monitor the situation and provide updates as needed. Thank you for your understanding, and please don't hesitate to reach out to [email protected] with any additional concerns

3. 2025년 1월 22일 오후 7:46 UTCmonitoring

   We have implemented a solution and are actively monitoring the situation to ensure that everything is running smoothly. We will continue to keep a close eye on things and will provide any necessary updates. Thank you for your patience and understanding.

4. 2025년 1월 22일 오후 9:10 UTCresolved

   We're happy to report that the issue has been resolved, and everything is back to normal. We apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the issue. Please let us know if you have any further questions or concerns.

1. 2024년 12월 20일 오전 1:15 UTCinvestigating

   Our team is currently investigating the issue and gathering all relevant information. We will provide updates as soon as possible and appreciate your patience as we work towards a resolution.

2. 2024년 12월 20일 오전 1:18 UTCinvestigating

   We are continuing to investigate this issue.

3. 2024년 12월 20일 오전 1:33 UTCidentified

   We have identified the cause of the issue and are working on a fix. We will continue to monitor the situation and provide updates as needed. Thank you for your understanding, and please don't hesitate to reach out to [email protected] with any additional concerns

4. 2024년 12월 20일 오전 1:36 UTCmonitoring

   We have implemented a solution and are actively monitoring the situation to ensure that everything is running smoothly. We will continue to keep a close eye on things and will provide any necessary updates. Thank you for your patience and understanding.

5. 2024년 12월 20일 오전 1:46 UTCresolved

   We're happy to report that the issue has been resolved, and everything is back to normal. We apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the issue. Please let us know if you have any further questions or concerns.

1. 2024년 12월 4일 오후 12:42 UTCinvestigating

   Our team is currently investigating the issue and gathering all relevant information. We will provide updates as soon as possible and appreciate your patience as we work towards a resolution.

2. 2024년 12월 4일 오후 1:23 UTCidentified

   We have identified the cause of the issue and are working on a fix. We will continue to monitor the situation and provide updates as needed. Thank you for your understanding, and please don't hesitate to reach out to [email protected] with any additional concerns

3. 2024년 12월 4일 오후 1:28 UTCmonitoring

   We have implemented a solution and are actively monitoring the situation to ensure that everything is running smoothly. We will continue to keep a close eye on things and will provide any necessary updates. Thank you for your patience and understanding.

4. 2024년 12월 4일 오후 2:31 UTCresolved

   We're happy to report that the issue has been resolved, and everything is back to normal. We apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the issue. Please let us know if you have any further questions or concerns.

1. 2024년 9월 18일 오전 11:19 UTCinvestigating

   Our team is currently investigating the issue and gathering all relevant information. We will provide updates as soon as possible and appreciate your patience as we work towards a resolution.

2. 2024년 9월 18일 오전 11:22 UTCinvestigating

   We are continuing to investigate this issue.

3. 2024년 9월 18일 오전 11:23 UTCidentified

   We have identified the cause of the issue and are working on a fix. We will continue to monitor the situation and provide updates as needed. Thank you for your understanding, and please don't hesitate to reach out to [email protected] with any additional concerns

4. 2024년 9월 18일 오전 11:27 UTCmonitoring

   We have implemented a solution and are actively monitoring the situation to ensure that everything is running smoothly. We will continue to keep a close eye on things and will provide any necessary updates. Thank you for your patience and understanding.

5. 2024년 9월 18일 오후 12:31 UTCresolved

   We're happy to report that the issue has been resolved, and everything is back to normal. We apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the issue. Please let us know if you have any further questions or concerns.

1. 2024년 9월 11일 오후 12:46 UTCidentified

   We have identified the cause of the issue and are working on a fix. We will continue to monitor the situation and provide updates as needed. Thank you for your understanding, and please don't hesitate to reach out to [email protected] with any additional concerns

2. 2024년 9월 11일 오후 12:56 UTCmonitoring

   We have implemented a solution and are actively monitoring the situation to ensure that everything is running smoothly. We will continue to keep a close eye on things and will provide any necessary updates. Thank you for your patience and understanding.

3. 2024년 9월 11일 오후 1:59 UTCresolved

   We're happy to report that the issue has been resolved, and everything is back to normal. We apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the issue. Please let us know if you have any further questions or concerns.

1. 2024년 8월 22일 오후 5:57 UTCinvestigating

   Accessing the Bizzabo Dashboard is producing an error. Our team is currently investigating the issue and gathering all relevant information. We will provide updates as soon as possible and appreciate your patience as we work towards a resolution.

2. 2024년 8월 22일 오후 6:01 UTCmonitoring

   We have implemented a solution and are actively monitoring the situation to ensure that everything is running smoothly. We will continue to keep a close eye on things and will provide any necessary updates. Thank you for your patience and understanding.

3. 2024년 8월 22일 오후 7:14 UTCresolved

   We're happy to report that the issue has been resolved, and everything is back to normal. We apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the issue. Please let us know if you have any further questions or concerns.

1. 2024년 5월 2일 오후 5:59 UTCidentified

   We have identified the cause of the issue that is currently not allowing organizers to view their event list. At this time, organizers are able to load into a specific event if they have their event ID. The same API that is used to load event lists are connected to the mobile app, therefore, there is a chance the mobile app will not load. We are currently working on a fix. We will continue to monitor the situation and provide updates as needed. Thank you for your understanding, and please don't hesitate to reach out to [email protected] with any additional concerns.

2. 2024년 5월 2일 오후 6:52 UTCmonitoring

   We have implemented a solution and are actively monitoring the situation to ensure that everything is running smoothly. We will continue to keep a close eye on things and will provide any necessary updates. Thank you for your patience and understanding.

3. 2024년 5월 2일 오후 7:56 UTCresolved

   We're happy to report that the issue has been resolved, and everything is back to normal. We apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the issue. Please let us know if you have any further questions or concerns.

1. 2024년 2월 21일 오후 8:08 UTCinvestigating

   Our team is currently investigating the issue and gathering all relevant information. We will provide updates as soon as possible and appreciate your patience as we work towards a resolution.

2. 2024년 2월 21일 오후 8:16 UTCmonitoring

   We have implemented a solution to resolve the stalled attempts to duplicate events and are actively monitoring the situation to ensure everything runs smoothly. We will keep a close eye on things and provide any necessary updates. Thank you for your patience and understanding.

3. 2024년 2월 21일 오후 9:26 UTCresolved

   We're happy to report that the issue has been resolved, and everything is back to normal. We apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the issue. Please let us know if you have any further questions or concerns.

1. 2024년 2월 20일 오전 7:56 UTCidentified

   We're aware of a current issue affecting both our website and Venue app. We understand this disrupts your experience, and we sincerely apologize for any inconvenience caused. Our technical team has pinpointed the cause within our database and is actively working on a solution. While we can't yet provide a specific timeframe for resolution, we're committed to restoring full functionality as quickly as possible. We'll keep you informed through updates on this channel. Rest assured, your data remains secure throughout this process. Thank you for your patience and understanding as we prioritize a swift resolution.

2. 2024년 2월 20일 오전 8:06 UTCmonitoring

   .

3. 2024년 2월 20일 오전 8:21 UTCmonitoring

   following the service interruption that impacted our website and Venue app, we're happy to confirm that a fix has been successfully implemented. Our technical team pinpointed the issue within our database and worked diligently to resolve it. Currently, we've transitioned to a close monitoring phase to ensure the implemented fix maintains stability and the platform behaves as expected. We'll continue to monitor the situation closely and provide further updates if necessary. Thank you for your continued patience and support

4. 2024년 2월 20일 오전 8:46 UTCresolved

   We're pleased to announce that the recent service interruption affecting our website and Venue app has been fully resolved! Following successful implementation of a fix and thorough monitoring, we can confirm that the platform is now operating as expected. We understand the inconvenience caused and appreciate your patience and understanding throughout this process. We remain committed to delivering a reliable and seamless experience. Thank you for your continued support.

1. 2023년 10월 18일 오전 11:35 UTCinvestigating

   Our team is currently investigating the issue and gathering all relevant information. We will provide updates as soon as possible and appreciate your patience as we work towards a resolution.

2. 2023년 10월 18일 오전 11:44 UTCresolved

   We're happy to report that the issue has been resolved, and everything is back to normal. We apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the issue. Please let us know if you have any further questions or concerns.

1. 2023년 6월 15일 오후 4:24 UTCinvestigating

   We are receiving reports of platform-wide issues with the Bizzabo Organizer Dashboard. The team is investigating.

2. 2023년 6월 15일 오후 4:46 UTCidentified

   We have identified the cause of the issue and are working on a fix. We will continue to monitor the situation and provide updates as needed. Thank you for your understanding, and please don't hesitate to reach out to [email protected] with any additional concerns.

3. 2023년 6월 15일 오후 4:58 UTCmonitoring

   We have implemented a solution and are actively monitoring the situation to ensure that everything is running smoothly. We will continue to keep a close eye on things and will provide any necessary updates. Thank you for your patience and understanding.

4. 2023년 6월 15일 오후 6:10 UTCresolved

   We're happy to report that the issue has been resolved, and everything is back to normal. We apologize for any inconvenience this may have caused and appreciate your patience while we worked to resolve the issue. Please let us know if you have any further questions or concerns.