Störungsverlauf von Bizzabo

1. 1. September 2026 um 15:56 UTCidentified

   Unser Team hat ein Problem identifiziert, das sich auf die Konnektivität zur Plattform auswirkt und zu Leistungs- und Ladeproblemen führt. Wir implementieren derzeit Änderungen an unserer Verbindung, um die Stabilität zu verbessern und die normale Leistung wiederherzustellen. Wir behandeln dies als oberste Priorität und werden weitere Updates teilen, sobald weitere Informationen verfügbar sind.

2. 1. September 2026 um 16:18 UTCmonitoring

   Wir haben eine Lösung implementiert und überwachen die Situation aktiv, um sicherzustellen, dass alles reibungslos läuft. Wir werden die Dinge weiterhin genau im Auge behalten und alle notwendigen Updates bereitstellen. Vielen Dank für Ihre Geduld und Ihr Verständnis.

3. 1. September 2026 um 18:05 UTCresolved

   Wir freuen uns, berichten zu können, dass das Problem gelöst wurde und alles wieder normal ist. Wir entschuldigen uns für alle Unannehmlichkeiten, die dies verursacht haben könnte, und schätzen Ihre Geduld, während wir daran gearbeitet haben, das Problem zu lösen. Bitte lassen Sie uns wissen, wenn Sie weitere Fragen oder Bedenken haben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 18. November 2025 um 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. 18. November 2025 um 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. 18. November 2025 um 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. 18. November 2025 um 17: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. 11. November 2025 um 09: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. 11. November 2025 um 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. 11. November 2025 um 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. 11. November 2025 um 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. 11. November 2025 um 14: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. 20. Oktober 2025 um 07: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. 20. Oktober 2025 um 09: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. 20. Oktober 2025 um 15: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. 20. Oktober 2025 um 15: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. 20. Oktober 2025 um 16: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. 20. Oktober 2025 um 20: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. 20. Oktober 2025 um 21: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. 21. Oktober 2025 um 08:19 UTCresolved

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

1. 16. Oktober 2025 um 14: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. 16. Oktober 2025 um 17: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. 16. Oktober 2025 um 21: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. 17. Oktober 2025 um 08: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. 21. August 2025 um 17: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. 21. August 2025 um 19: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. 21. August 2025 um 19: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. 21. August 2025 um 19: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. 21. August 2025 um 20: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. 19. August 2025 um 13: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. 19. August 2025 um 13: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. 19. August 2025 um 14:31 UTCresolved

   This incident has been resolved.

1. 12. Juni 2025 um 19: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. 12. Juni 2025 um 19: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. 12. Juni 2025 um 19: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. 12. Juni 2025 um 20: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. 12. Juni 2025 um 21: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. 12. Juni 2025 um 21: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. 12. Juni 2025 um 23: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. 13. Juni 2025 um 00: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. 16. April 2025 um 14: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. 16. April 2025 um 14: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. 16. April 2025 um 15: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. 22. Januar 2025 um 19: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. 22. Januar 2025 um 19: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. 22. Januar 2025 um 19: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. 22. Januar 2025 um 21: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. 20. Dezember 2024 um 01: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. 20. Dezember 2024 um 01:18 UTCinvestigating

   We are continuing to investigate this issue.

3. 20. Dezember 2024 um 01: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. 20. Dezember 2024 um 01: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. 20. Dezember 2024 um 01: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. 4. Dezember 2024 um 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. 4. Dezember 2024 um 13: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. 4. Dezember 2024 um 13: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. 4. Dezember 2024 um 14: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. 18. September 2024 um 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. 18. September 2024 um 11:22 UTCinvestigating

   We are continuing to investigate this issue.

3. 18. September 2024 um 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. 18. September 2024 um 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. 18. September 2024 um 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. 11. September 2024 um 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. 11. September 2024 um 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. 11. September 2024 um 13: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. 22. August 2024 um 17: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. 22. August 2024 um 18: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. 22. August 2024 um 19: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. 2. Mai 2024 um 17: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. 2. Mai 2024 um 18: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. 2. Mai 2024 um 19: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. 21. Februar 2024 um 20: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. 21. Februar 2024 um 20: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. 21. Februar 2024 um 21: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. 20. Februar 2024 um 07: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. 20. Februar 2024 um 08:06 UTCmonitoring

   .

3. 20. Februar 2024 um 08: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. 20. Februar 2024 um 08: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. 18. Oktober 2023 um 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. 18. Oktober 2023 um 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. 15. Juni 2023 um 16:24 UTCinvestigating

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

2. 15. Juni 2023 um 16: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. 15. Juni 2023 um 16: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. 15. Juni 2023 um 18: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.