Minor incident
UpCloud: [SG-SIN1] Managed Object Storage Issue
Oct 6, 2026, 06:58 UTC
started
14:50 UTC
resolved October 13, 2026
7 days 7 h
duration
Affected: APAC-1: Managed Object Storage
Current status of UpCloud: Operational — live UpCloud status
Timeline
- Oct 6, 2026, 06:58 UTCidentifiedWe have identified a service degradation issue affecting Managed Object Storage in our Singapore (SG-SIN1) data center. The issue causes periodic latency spikes and HTTP 503 errors that last 10 to 15 minutes. We have identified the root cause and are actively working to resolve the issue and fully restore service. We apologize for the inconvenience and will provide further updates as soon as possible. If you have any questions, please contact our support team via live chat or email [email protected]
- Oct 6, 2026, 18:13 UTCmonitoringWe have identified the root cause of the service degradation affecting Managed Object Storage in our Singapore (SG-SIN1) data center and have deployed a fix. We currently monitoring the system to ensure long-term stability. Thank you for your patience, and we apologize for any inconvenience caused. If you experience any issues, please contact our support team via live chat or at [email protected].
- Oct 13, 2026, 14:50 UTCresolvedThis incident has been resolved.
Updates as published by UpCloud (original).
Other services with incidents at the same time
- Supabase 07:53 UTC · Increased errors on management api leading to project operation failures
- Qualys 07:47 UTC · IN Platform 1: UI logins and API Authencation failing(IM -12899)
- Brevo 07:47 UTC · Delays affecting email previews and "view in browser" links
- Wasabi Technologies 07:08 UTC · Intermittent Wasabi Console Access
- Kameleoon 07:03 UTC · Kameleoon Main Application Tools Temporarily Unavailable
- Paysafe 06:16 UTC · Service Disruption - QR Code Partner
More UpCloud incidents
- October 23, 2026 UpCloud API and Control Panel Connectivity Issues
- September 28, 2026 [FI-HEL2]: File Storage Issues
- August 11, 2026 Cloud Server Deployment Error
- May 26, 2026 Error with new cloud service deployments