CloudClerks.
Log in Deploy a VM
System Status

Live status for every CloudClerks region

Uptime history, active incidents, and scheduled maintenance for the console, API, network, and every region we run.

Scheduled maintenance in progress

sa-east-1 is undergoing planned hardware maintenance. All other regions and services are operating normally.

Updated
Sep 7, 06:12 UTC

Regions & services

45-day history
us-east-1aNorthern Virginia, US
Operational
45 days ago 99.99% uptime Today
eu-west-2bLondon, UK
Operational
45 days ago 99.97% uptime Today
ap-southeast-1Singapore
Operational
45 days ago 99.95% uptime Today
sa-east-1São Paulo, Brazil
Scheduled Maintenance
45 days ago 99.98% uptime Today
Console & APIControl plane, all regions
Operational
45 days ago 99.99% uptime Today
Private Network BackboneInter-region traffic
Operational
45 days ago 100.00% uptime Today
Object StorageAll regions
Operational
45 days ago 99.98% uptime Today
History

Incidents & maintenance

The most recent scheduled maintenance and incidents across all regions, newest first.

Scheduled maintenance - sa-east-1

Scheduled Maintenance
Sep 7, 02:00–06:00 UTC

We're replacing networking hardware in our São Paulo facility to add capacity ahead of regional launch traffic. New VM boots and console access to sa-east-1 may be intermittent during this window; running instances are not affected.

  • In progressSep 7, 02:00 UTCMaintenance window has started. Existing VMs continue to run normally.
  • ScheduledSep 3, 16:40 UTCThis maintenance window has been scheduled and support tickets pre-filed for affected accounts.

Elevated API latency - eu-west-2b

Degraded Performance
Aug 19, 14:12–15:03 UTC

A misconfigured load balancer rule sent a portion of console and API traffic in eu-west-2b through an under-provisioned path, adding 400–900ms to affected requests. VM network traffic was not impacted.

  • ResolvedAug 19, 15:03 UTCLatency has returned to baseline. Root cause identified as a load balancer misconfiguration introduced during a routine rule update; a review has been added to our deploy checklist.
  • MonitoringAug 19, 14:47 UTCReverted the load balancer rule change. Latency is trending back to normal and we're continuing to watch it.
  • IdentifiedAug 19, 14:29 UTCIdentified an incorrect routing rule as the cause. Rolling back the change now.
  • InvestigatingAug 19, 14:12 UTCWe're seeing elevated response times for console and API requests routed through eu-west-2b and are investigating.

Brief connectivity loss - ap-southeast-1

Outage
Aug 3, 09:41–09:56 UTC

A upstream transit provider dropped a peering session, briefly cutting public connectivity to VMs in ap-southeast-1. Instances remained running throughout; only external network reachability was affected.

  • ResolvedAug 3, 09:56 UTCThe peering session has been restored and connectivity confirmed normal from multiple external vantage points.
  • IdentifiedAug 3, 09:48 UTCTraced the loss to a dropped BGP session with one of our upstream transit providers. Failing over to our secondary path.
  • InvestigatingAug 3, 09:41 UTCWe're investigating reports of connectivity loss to VMs in ap-southeast-1.

Degraded console performance

Degraded Performance
Jul 22, 20:05–20:31 UTC

Object storage requests backing console dashboard thumbnails queued up after a batch job consumed more IOPS than expected, slowing dashboard loads for accounts with many volumes.

  • ResolvedJul 22, 20:31 UTCDashboard load times are back to normal. We've moved the batch job to a lower-priority queue so it can't compete with live traffic again.
  • MonitoringJul 22, 20:19 UTCPaused the batch job. Dashboard performance is recovering.
  • InvestigatingJul 22, 20:05 UTCSome accounts may be seeing slow dashboard loads. Looking into it now.