DoYouBuzz Outage History
DoYouBuzz is up right nowPingoru has recorded 5 incidents for DoYouBuzz: 5 in the last 12 months and 1 in the last 90 days.
Incidents, newest first
Minor October 6, 2026 Showcase inaccessible 14m Uptime by service (Showcase), Uptime by service (API)
Started Oct 06, 2026, 02:42 PM UTC· resolved Oct 06, 2026, 02:56 PM UTC
- investigating Oct 06, 2026, 02:42 PM UTC
Showcase et son API sont inaccessibles depuis 16h42. L'équipe est informée et nous vous tiendrons au courant dès que nous aurons du nouveau sur la situation.
- resolved Oct 06, 2026, 02:56 PM UTC
Showcase et son API sont de nouveaux opérationnels depuis 16h56.
Minor July 30, 2026 Temporary issue with Boond app connection 4h 43m Uptime by service (Boond Connector)
Started Jul 30, 2026, 07:30 AM UTC· resolved Jul 30, 2026, 12:13 PM UTC
- investigating Jul 30, 2026, 07:30 AM UTC
Some customers may have lost their access to the Boond app after recent changes.
- resolved Jul 30, 2026, 12:13 PM UTC
We have identified the problem and a workaround has been sent to Showcase admin workspaces impacted. A permanent fix will be made available next week with Boond technical team.
Major May 18, 2026 Network failure 1h 29m Uptime by service (Showcase), Uptime by service (DoYouBuzz), Uptime by service (API), Uptime by service (Boond Connector)
Started May 18, 2026, 12:43 AM UTC· resolved May 18, 2026, 02:12 AM UTC
- investigating May 18, 2026, 12:43 AM UTC
We are experiencing a platform-wide outage.
- resolved May 18, 2026, 02:12 AM UTC
The incident has been resolved. DoYouBuzz is fully operational as of 4:00 AM. A component of the network infrastructure caused a full network outage between 02:43 and 04:00 AM. The automatic failover did not trigger as expected due to the nature of the failure. Our hosting provider's on-call team restored service within 1h15. No data was lost or compromised. Going forward, our hosting provider has committed to faster automated failover (target: under 15 minutes) and a major firewall infrastructure upgrade planned for Q4 2026. We apologize for the disruption.
- resolved May 18, 2026, 02:12 AM UTC
The incident has been resolved. DoYouBuzz is fully operational as of 4:00 AM. A component of the network infrastructure caused a full network outage between 02:43 and 04:00 AM. The automatic failover did not trigger as expected due to the nature of the failure. Our hosting provider's on-call team restored service within 1h15. No data was lost or compromised. Going forward, our hosting provider has committed to faster automated failover (target: under 15 minutes) and a major firewall infrastructure upgrade planned for Q4 2026. We apologize for the disruption.
Major April 29, 2026 Boond - Data access unavailable 3h 5m Uptime by service (Boond Connector)
Started Apr 29, 2026, 06:30 AM UTC· resolved Apr 29, 2026, 09:35 AM UTC
- investigating Apr 29, 2026, 06:30 AM UTC
Customers using the Boond integration are currently unable to use it. This is caused by an infrastructure change on Boond's side that blocked our servers from fetching data. Boond is aware of the issue and actively working on a fix. We will update this page as soon as access is restored or we have more information from Boond.
- resolved Apr 29, 2026, 09:35 AM UTC
The problem has been resolved by Boond. Our infrastructure is now able to fetch datas from Boond.
Major April 16, 2026 Degraded performance – DC download unavailable 1h 30m Uptime by service (Showcase), Uptime by service (DoYouBuzz)
Started Apr 16, 2026, 10:45 AM UTC· resolved Apr 16, 2026, 12:15 PM UTC
- investigating Apr 16, 2026, 10:45 AM UTC
We are currently experiencing an issue preventing DC downloads, resulting in an error message for some users.
- resolved Apr 16, 2026, 12:15 PM UTC
The issue has been identified and fixed. CV downloads are now fully operational. Start time: 12:45 End time: 14:15 Duration: ~1h30 We are reviewing the incident to prevent this from happening again.
- investigating Apr 16, 2026, 12:15 PM UTC
The issue has been identified and fixed. CV downloads are now fully operational. Start time: 12:45 End time: 14:15 Duration: ~1h30 We are reviewing the incident to prevent this from happening again.