Public Cloud incident
[BHS1/3][Compute - Instance] - Some instances incident notification
Affected components
Update timeline
- monitoring Mar 24, 2026, 09:22 PM UTC
Service has been fully restored since 24/03/2026 21:15 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 24/03/2026 21:07 UTC Impacted Service(s) : Some instances in the BHS1 and BHS3 regions were temporarily unreachable. Customers Impact : Some customers were temporarily unable to access and use their Public Cloud instances in the specified regions. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Mar 24, 2026, 09:37 PM UTC
We are pleased to inform you that the incident affecting our Compute - Instance in BHS1 and BHS3 regions has been resolved. Start time : 24/03/2026 21:07 UTC End time : 24/03/2026 21:15 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