Civo.com
All Systems Operational
API ? Operational
90 days ago
99.95 % uptime
Today
Civo.com ? Operational
90 days ago
99.95 % uptime
Today
Ceph ? Operational
90 days ago
100.0 % uptime
Today
Nova ? Operational
90 days ago
99.9 % uptime
Today
Neutron ? Operational
90 days ago
99.95 % uptime
Today
Cinder ? Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
had a major outage
had a partial outage
Past Incidents
Feb 25, 2020

No incidents reported today.

Feb 24, 2020

No incidents reported.

Feb 23, 2020
Resolved - This incident has been resolved.
Feb 23, 20:12 GMT
Monitoring - We now believe that we have all instances back online. We are still monitoring the platform to ensure it remains stable. If you find that your instance still isn't working, if you could reboot it through the Civo account or API, it should bring it back up as expected. Once again we apologise for the inconvenience caused to everyone.
Feb 23, 19:39 GMT
Update - We have started to get the DHCP issue under control now and are slowly bringing back services to the affected instances. This process is taking some time as the system is now getting a lot of requests to process so some instances are taking a longer period than normal to resume. We are still monitoring the situation and are aiming to have everything back to normal ASAP. We apologise to those customers affected by this.
Feb 23, 18:37 GMT
Identified - We've narrowed down the current issue to a DHCP issue with our OpenStack cluster. We're currently trying to find a solution and will update again when we have the platform back running correctly.
Feb 23, 16:45 GMT
Investigating - We're currently seeing some strange networking on our OpenStack cluster. This may completely block connectivity to services/instances or present as a slowdown/outage between instances. We're on the case and will update when we know more.
Feb 23, 13:55 GMT
Feb 22, 2020

No incidents reported.

Feb 21, 2020

No incidents reported.

Feb 20, 2020

No incidents reported.

Feb 19, 2020

No incidents reported.

Feb 18, 2020

No incidents reported.

Feb 17, 2020

No incidents reported.

Feb 16, 2020

No incidents reported.

Feb 15, 2020

No incidents reported.

Feb 14, 2020

No incidents reported.

Feb 13, 2020
Resolved - The compute node has now been stable for a long period so we are going to close this now. We are still going to be investigating why this has happened and will apply any fixes / patches that may be needed from the resulting investigation. Once again we apologise for any inconvenience caused.
Feb 13, 07:11 GMT
Monitoring - We've brought the node back up and are restarting all the affected VMs. We'll keep an eye on this node while we do so and during today in case it has another wobble.
Feb 13, 05:00 GMT
Identified - We have identified the host as an individual compute host and we are now seeing what is causing the issue with this particular host. Only this one host is affected. As soon as we have more information we will update this thread. We apologise for the inconvenience caused.
Feb 13, 04:09 GMT
Investigating - We are currently investigating an issue with one of our compute nodes seemingly locked up. As soon as we have more information we will update this thread.
Feb 13, 03:59 GMT
Feb 12, 2020

No incidents reported.

Feb 11, 2020
Resolved - Everything has been stable now for a good period. We will still keep an eye on this one compute node, however we are going to close the incident as resolved now as all is running as it should on this compute host. We apologise for the inconvenience caused.
Feb 11, 17:50 GMT
Monitoring - We've restarted the compute node and will keep an eye on what's causing the high load if it repeats, but for now normal service has resumed.
Feb 11, 17:01 GMT
Identified - We've fix the API and Civo.com now, but are still working on compute-13.
Feb 11, 15:36 GMT
Update - We think this is actually one compute node from our cluster, that happens to have some of our services (and client services) on it. We're trying to get it to respond, but it appears to have been slammed by something hogging all the CPU cores.
Feb 11, 15:00 GMT
Investigating - Our alerting has just picked up that Civo.com is reporting errors, these are actually coming from our API. We're looking in to it and will update when we know more. We've tested a few client instances and they are OK, although we have had some reports of weirdness in other internal instances.
Feb 11, 14:57 GMT