Bizzabo Outage History

Started Sep 01, 2026, 03:56 PM UTC· resolved Sep 01, 2026, 06:05 PM UTC

1. identified Sep 01, 2026, 03:56 PM UTC

   Our team has identified an issue impacting connectivity to the platform, which is causing degraded performance and loading problems. We are currently implementing changes to our connection to improve stability and restore normal performance. We are treating this as a top priority and will share further updates as soon as more information is available.

2. monitoring Sep 01, 2026, 04:18 PM UTC

   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. resolved Sep 01, 2026, 06:05 PM UTC

   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.

Read the full incident report →

Started Nov 18, 2025, 12:02 PM UTC· resolved Nov 18, 2025, 05:46 PM UTC

1. identified Nov 18, 2025, 12:02 PM UTC

   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. monitoring Nov 18, 2025, 12:20 PM UTC

   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. monitoring Nov 18, 2025, 12:32 PM UTC

   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. resolved Nov 18, 2025, 05:46 PM UTC

   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.

Read the full incident report →

Started Nov 11, 2025, 09:02 AM UTC· resolved Nov 11, 2025, 02:01 PM UTC

1. identified Nov 11, 2025, 09:02 AM UTC

   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. identified Nov 11, 2025, 10:05 AM UTC

   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. identified Nov 11, 2025, 10:54 AM UTC

   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. monitoring Nov 11, 2025, 11:46 AM UTC

   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. resolved Nov 11, 2025, 02:01 PM UTC

   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.

Read the full incident report →

Started Oct 20, 2025, 07:39 AM UTC· resolved Oct 21, 2025, 08:19 AM UTC

1. identified Oct 20, 2025, 07:39 AM UTC

   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. monitoring Oct 20, 2025, 09:40 AM UTC

   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. identified Oct 20, 2025, 03:00 PM UTC

   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. monitoring Oct 20, 2025, 03:09 PM UTC

   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. identified Oct 20, 2025, 04:02 PM UTC

   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. identified Oct 20, 2025, 08:43 PM UTC

   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. monitoring Oct 20, 2025, 09:15 PM UTC

   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. resolved Oct 21, 2025, 08:19 AM UTC

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

Read the full incident report →

Started Oct 16, 2025, 02:03 PM UTC· resolved Oct 17, 2025, 08:06 AM UTC

1. investigating Oct 16, 2025, 02:03 PM UTC

   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. investigating Oct 16, 2025, 05:25 PM UTC

   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. identified Oct 16, 2025, 09:19 PM UTC

   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. resolved Oct 17, 2025, 08:06 AM UTC

   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.

Read the full incident report →

Started Aug 21, 2025, 05:39 PM UTC· resolved Aug 21, 2025, 08:41 PM UTC

1. investigating Aug 21, 2025, 05:39 PM UTC

   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. identified Aug 21, 2025, 07:12 PM UTC

   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. identified Aug 21, 2025, 07:28 PM UTC

   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. monitoring Aug 21, 2025, 07:37 PM UTC

   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. resolved Aug 21, 2025, 08:41 PM UTC

   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.

Read the full incident report →

Started Aug 19, 2025, 01:15 PM UTC· resolved Aug 19, 2025, 02:31 PM UTC

1. investigating Aug 19, 2025, 01:15 PM UTC

   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. monitoring Aug 19, 2025, 01:20 PM UTC

   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. resolved Aug 19, 2025, 02:31 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 12, 2025, 07:04 PM UTC· resolved Jun 13, 2025, 12:52 AM UTC

1. identified Jun 12, 2025, 07:04 PM UTC

   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. identified Jun 12, 2025, 07:29 PM UTC

   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. identified Jun 12, 2025, 07:43 PM UTC

   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. identified Jun 12, 2025, 08:22 PM UTC

   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. monitoring Jun 12, 2025, 09:01 PM UTC

   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. monitoring Jun 12, 2025, 09:43 PM UTC

   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. monitoring Jun 12, 2025, 11:32 PM UTC

   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. resolved Jun 13, 2025, 12:52 AM UTC

   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.

Read the full incident report →

Started Apr 16, 2025, 02:22 PM UTC· resolved Apr 16, 2025, 03:46 PM UTC

1. investigating Apr 16, 2025, 02:22 PM UTC

   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. monitoring Apr 16, 2025, 02:29 PM UTC

   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. resolved Apr 16, 2025, 03:46 PM UTC

   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.

Read the full incident report →

Started Jan 22, 2025, 07:08 PM UTC· resolved Jan 22, 2025, 09:10 PM UTC

1. investigating Jan 22, 2025, 07:08 PM UTC

   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. identified Jan 22, 2025, 07:32 PM UTC

   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. monitoring Jan 22, 2025, 07:46 PM UTC

   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. resolved Jan 22, 2025, 09:10 PM UTC

   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.

Read the full incident report →

Started Dec 20, 2024, 01:15 AM UTC· resolved Dec 20, 2024, 01:46 AM UTC

1. investigating Dec 20, 2024, 01:15 AM UTC

   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. investigating Dec 20, 2024, 01:18 AM UTC

   We are continuing to investigate this issue.

3. identified Dec 20, 2024, 01:33 AM UTC

   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. monitoring Dec 20, 2024, 01:36 AM UTC

   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. resolved Dec 20, 2024, 01:46 AM UTC

   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.

Read the full incident report →

Started Dec 04, 2024, 12:42 PM UTC· resolved Dec 04, 2024, 02:31 PM UTC

1. investigating Dec 04, 2024, 12:42 PM UTC

   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. identified Dec 04, 2024, 01:23 PM UTC

   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. monitoring Dec 04, 2024, 01:28 PM UTC

   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. resolved Dec 04, 2024, 02:31 PM UTC

   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.

Read the full incident report →