Public Cloud incident
[BHS1][Compute - Instance] - Some instances incident notification
Affected components
Update timeline
- identified Mar 19, 2026, 06:49 PM UTC
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific region. Here are some supplementary details : Start time : 19/03/2026 18:16 UTC Impacted Service(s) : Some instances in the BHS1 region are unreachable. Customers Impact : Some customers are temporarily unable to access and use their instances in the specified region. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Mar 19, 2026, 07:26 PM UTC
We are pleased to inform you that the incident affecting our Compute - Instance offer has been resolved. Start time : 19/03/2026 18:16 UTC End time : 19/03/2026 19:21 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.
Looking to track Public Cloud downtime and outages?
Pingoru polls Public Cloud's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Public Cloud reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Public Cloud alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required