All times are shown in UTC
This incident was created automatically by our automated health check system as it has identified a fault. We are now looking into this issue.
A fault in all regions was detected
6th Oct 08:06 PMAn additional fault has been detected in realtime US West Oregon
6th Oct 09:07 PMOur deployment system had a fault and deployed an untested slug globally, resulting in some downtime. Globally, a lot of our services were operational throughout the effected period, and if using our client libraries, a failover region would have been used.
We are looking into ways to prevent issues like this in the future due to faults in our deployments.
Resolved
in about 1 hourThis incident was created automatically by our automated health check system as it has identified a fault. We are now looking into this issue.
Our health check system has reported this issue as resolved.
We will continue to investigate the issue and will update this incident shortly.
Resolved
in about 1 hourAn incident with Heroku is affecting our websites www.ably.io and status.ably.io.
See http://status.heroku.com/incidents/811 for further info.
Our realtime services are unaffected.
Heroku has reported that the issue is now resolved, and our own monitoring systems are reporting the websites being responsive as normal now.
Resolved
in about 1 hourThis incident was created automatically by our automated health check system as it has identified a fault. We are now looking into this issue.
Our health check system has reported this issue as resolved.
We will continue to investigate the issue and will update this incident shortly.
Resolved
in 1 minuteThis incident was created automatically by our automated health check system as it has identified a fault. We are now looking into this issue.
Our health check system has reported this issue as resolved.
We will continue to investigate the issue and will update this incident shortly.
Resolved
in 15 minutesThis incident was created automatically by our automated health check system as it has identified a fault.
After reviewing the logs, during the recycle of all regions, some responses were too slow for our monitoring systems to see that as healthy. As such, this was reported as a fault.
The website is now operational again
All data centres have been upgraded and the website is performing normally
Resolved
in about 1 hourWe are about to start scheduled maintenance on all regions.
There is no anticipated downtime, however each region will be taken off briefly and brought back up online. During this time, all traffic to that region will be re-routed to an alternative region.
All data centres have been upgraded and a new region Frankfurt has been introduced.
Resolved
in about 2 hoursWe have introduced three new regions and six data centres to our cluster, São Paulo, Australia and Singapore.
This will dramatically reduce latencies in Asia and South America moving forwards and is available now to all customers.
Closed
in about 2 hoursThis incident was created automatically by our automated health check system as it has identified a fault. We are now looking into this issue.
Our health check system has reported this issue as resolved.
We will continue to investigate the issue and will update this incident shortly.
We were doing some routine maintenance that resulted in some performance issues in eu-west-1. The service remained up throughout the maintenance.
Resolved
in about 1 hourAfter rolling out 4 additional datacenters in Asia, Europe and South America, we noticed instability globally in a small selection of apps.
Whilst we identify the cause of the issue, we have rolled back to 4 data centres in California, Virginia, Oregon and Europe.
Resolved
in about 12 hoursWe are currently expanding our cluster from 3 regions to 8 regions. Unfortunately we hit some issues during the rollout which resulted in 5 minutes of downtime globally.
Resolved
in 5 minutesThis incident has been created automatically by our monitoring systems as they have identified a fault. We are now looking into the reported issue.
Our monitoring systems have reported this issue is resolved.
We are still investigating the issue and will update this incident shortly.
The issue was intermittent and only effected a small number of users
Resolved
in about 1 hourWe had some scheduled downtime prior to our launch today from 15:00 GMT until 17:00 GMT.
The system is now back up as planned
Resolved
in about 2 hoursSince 13:33 UTC time our reporting systems are incorrectly reporting the website as being down.
This is not the case and the issue is a reporting system issue due to a recent change of DNS.
We should have this resolved shortly.
Resolved
in over 22 years