Home
/
Status
/
Service
Deploy, manage, and scale applications on cloud servers.
Source
auto
Category
Cloud
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Operational
Checked 1h ago
15
Components
0
Active incidents
0
Maintenance
100%
90d uptime
Google login issues
Jun 12, 7:09 PM
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
Showing 1 to 15 of 15 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
Cloud 66 Dependencies Services we use to run Cloud 66 | Operational | Group | Not recorded |
Upstream Dependencies Services you might be using with Cloud 66 | Operational | Group | Not recorded |
Github | Operational | Component | Not recorded |
Google Cloud Platform Google Kubernetes Engine | Operational | Component | Not recorded |
Google Cloud Platform Google Compute Engine | Operational | Component | Not recorded |
Core Systems Build, Deployment and Maintenance Systems | Operational | Component | Not recorded |
Google Cloud Platform Google Cloud Storage | Operational | Component | Not recorded |
BuildGrid Container Build System | Operational | Component | Not recorded |
Google Cloud Platform Google Cloud SQL | Operational | Component | Not recorded |
Google Cloud Platform Google Cloud Networking | Operational | Component | Not recorded |
Realtime Push Systems Live update systems | Operational | Component | Not recorded |
AWS route53 | Operational | Component | Not recorded |
ContainerNet Container networks and DNS | Operational | Component | Not recorded |
Help Scout Email Processing | Operational | Component | Not recorded |
Stripe API | Operational | Component | Not recorded |
Follow outages, degraded components, and maintenance updates in your Uptimus workspace with email, push, and webhook alerts.
Related status pages based on category, adapter type, and operational history.
Cloud 66 is currently marked as Operational in Uptimus based on the latest official status page check.
Supported status page providers are checked continuously by our scraper scheduler. The public page is cached briefly for SEO and performance.
No. Uptimus stores incidents and maintenance windows separately when the upstream provider exposes enough detail.
Yes. Create an Uptimus workspace, follow this provider, and choose email, push, or webhook notifications.
Normalized official status-page data for incidents, maintenance, components, and history.
100%
Known uptime
1 known history days
15
Components tracked
0 outage, 0 degraded
12
Incidents indexed
0 active right now
8
Maintenance windows
0 active or scheduled
Components with the most recent status-page events.
AWS route53
Operational
BuildGrid
Operational
Cloud 66 Dependencies
Operational
ContainerNet
Operational
Core Systems
Operational
1
operational days
0
degraded days
0
outage days
0
maintenance days
89
unknown days
Latest outages and degradations detected from the official status page.
The underlying issue with GCP seems to be resolved, and we are not seeing further issues with the logins and other systems.
This incident has been resolved.
This incident has now been resolved.
The CustomConfig git backend migration has been completed
This incident has been resolved.
This incident has been resolved.
Maestro installations are working as expected again
Issue confirmed to be fixed by GitHub.
This incident has been resolved.
At approximately 07:00 UTC we started to perform a minor system quality-of-life backend update. The update had unintended consequences on an older system component which hadn’t been changed in a while. The component was to do with agent server communications, and it ended up disabled after the update. Although the same component was unaffected during testing in dev/staging and passed UAT, it turned out that there was a necessarily different configuration around rewrites in production that caused the issue. The nature of the update meant that rolling back wasn’t straightforward, so the team resolved to fix the incompatibility in-place, and as such were unable to stop the erroneous “server down” notifications that then went out. The issue was resolved approximate 1 hour later. at 08:00 UTC - after which time servers would have started to appear as “online” again. Subsequent to this outage, the difference in configuration has been added to our operations processes, such that this will not occur again. Our apologies for the inconvenience and concern that this may have created!
Scheduled and completed maintenance windows are separated from incidents.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance of the metrics subsystem is now done.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
Uptimus tracks the official Cloud 66 status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
http://status.cloud66.com
Adapter
STATUSPAGE IO
Alert streams
Incidents, component changes, and maintenance windows.
Public SEO page
Indexable status history for users searching outage information.
Regional reports can be layered on top of official provider status when user signals are available.
Official provider components
Incident and maintenance separation
Workspace alerts and webhooks
