Cloud 66 Outage History

Cloud 66 is up right now

Cloud 66 had 3 outages in the last 2 years totaling 7h 30m of downtime — averaging 0.1 incidents per month.

There were 3 Cloud 66 outages since January 2, 2025 totaling 7h 30m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: http://status.cloud66.com

Minor August 24, 2026

DigitalOcean servers unable to pull BuildGrid images

Detected by Pingoru
Aug 24, 2026, 04:24 PM UTC
Resolved
Aug 24, 2026, 07:12 PM UTC
Duration
2h 48m
Affected: Google Cloud Platform Google Cloud StorageBuildGrid
Timeline · 1 update
  1. identified Aug 24, 2026, 04:24 PM UTC

    DigitalOcean's IPv6 range appears to be blocked from accessing Google Cloud Storage. This means CSv1 and CSv2 customers who have servers with public IPv6 addresses are currently unable to pull new BuildGrid images onto their servers.

Read the full incident report →

Minor June 12, 2025

Google login issues

Detected by Pingoru
Jun 12, 2025, 07:09 PM UTC
Resolved
Jun 12, 2025, 08:30 PM UTC
Duration
1h 20m
Affected: Google Cloud Platform Google Kubernetes EngineGoogle Cloud Platform Google Compute EngineCore SystemsGoogle Cloud Platform Google Cloud StorageGoogle Cloud Platform Google Cloud SQLGoogle Cloud Platform Google Cloud Networking
Timeline · 2 updates
  1. investigating Jun 12, 2025, 07:09 PM UTC

    Google authentication issues is having issues causing login and access issues for our systems and customers. We are investigating the impact and mitigation strategies.

  2. resolved Jun 12, 2025, 08:30 PM UTC

    The underlying issue with GCP seems to be resolved, and we are not seeing further issues with the logins and other systems.

Read the full incident report →

Minor January 2, 2025

Kubernetes Cluster Scale/Creation

Detected by Pingoru
Jan 02, 2025, 12:24 PM UTC
Resolved
Jan 02, 2025, 03:45 PM UTC
Duration
3h 20m
Affected: Core Systems
Timeline · 4 updates
  1. investigating Jan 02, 2025, 12:24 PM UTC

    We are aware of problems when scaling/creating Kubernetes clusters. This appears to be caused by new rate limits imposed by docker hub. The team are working on a solution.

  2. identified Jan 02, 2025, 12:25 PM UTC

    The issue has been identified and a fix is being implemented.

  3. investigating Jan 02, 2025, 12:25 PM UTC

    We are currently investigating this issue.

  4. resolved Jan 02, 2025, 03:45 PM UTC

    This incident has been resolved.

Read the full incident report →