Historia awarii Statuscake

We are currently experiencing access issues for users trying to log in to app, this has been identified as an issue with Cloudflare. Monitoring and API access are unaffected and continue to work correctly. users are covered for outages and alerts. Many Cloudflare users are affected, and users will see their Cloudflare managed sites generating downtimes through StatusCake, these are valid and will be related to Cloudflare's inability to serve the pages at current.

Cloudflare have updated their status page indicating that the problem is partially resolved. From a StatusCake perspective, users will be able to log in to the app once more, but may experience increased load times and intermittent page load failures while Cloudflare finalises the fixes.

Cloudflare have communicated that a fix has been implemented. They believe the incident is now resolved. On the StatusCake side we are no longer seeing disruption. We can conclude that our alerting, API and reporting were unaffected by this event.

We are currently investigating, we suspect that this is a temporary routing issue affecting customers in select regions. Affected users may see their tests showing as down if they are monitoring a website outside of Canada using this region. There may also be limited effects on other NA regions.

We have temporarily disabled monitoring from this region while it recovers, this should cease disruption to users

Available information points to a failure with a large comms provider in NA, we have disabled New York and Canada testing regions until the error is resolved on their side. Additionally there is a wide-scale issue with Microsoft & Azure services in Canada which may be related - https://azure.status.microsoft/en-gb/status

The impacted parties have reported resolution and from our side we have re-enabled affected regions

We have received reports from users that some Uptime type tests are failing to run, we are currently investigating this on our side.

We expect some short app outages as we attempt to apply possible fixes, it may not be possible to access the app for 1-2 minutes while these fixes are applied.

We are continuing to investigate the issue, users will now see some periods where it is not possible to access the app. We will keep these as short of possible while we seek a fix.

We apologise for the continued disruption, we continue to investigate this and hope for a resolution shortly.

We've identified and remediated the issue and are monitoring the infrastructure

This incident has been resolved.

The issue has been identified with one of our hosting providers and we're currently working with them to resolve the issue.

Our monitoring location in Stockholm, Sweden (IP: 13.48.238.157) is currently unavailable due to an external block on our outbound connections. As a result, any uptime tests previously assigned to this location will temporarily be run from alternative locations outside of Sweden. We apologise for any inconvenience this may cause to customers relying on Swedish-based monitoring. Our team is actively working to resolve this issue, and we appreciate your understanding and patience during this time. Further updates will be provided as they become available.

The issue with the hosting provider has been resolved and the Stockholm region is now operational.

One of our database providers is currently conducting emergency maintenance due to a critical hardware failure earlier today. We now have an estimated time to resolution of approximately 2 hours. We understand the impact this may have on your services and apologize for the inconvenience. Our team is in close contact with the provider and monitoring the situation closely. We will continue to provide updates as more information becomes available. Thank you for your patience.

Thanks for your patience, the migration is progressing & we expect a resolution in around an hours time.

The migration has been completed and we are seeing systems restored. We are monitoring the situation.

The incident is now resolved, we see all systems returned to full performance. Thanks for bearing with us!

We are currently experiencing an issue affecting some users' ability to access our application. This is due to emergency maintenance being performed by one of our server providers. This may impact accessibility during the migration period. Our team is closely monitoring the situation and working with our provider to resolve the issue as soon as possible. We expect this to be a short disruption.

We are continuing to investigate this issue.

The incident has been resolved, our apologies for the disruption

A networking fault with a provider is causing some customers to receive alerts late, or not at all. We are currently investigating and seeking a resolution.

The issue is resolved. Alerts are now running as normal.

We are currently investigating this issue following reports that some users are unable to access the web app, we hope to have this resolved quickly.

We have identified and resolved the issue, this was related to a temporary networking error, all users will be able to log in to the app successfully once more.

We are investigating an issue where new public reporting pages are not properly applying the CNAME configuration, no existing public reports would be affected, and we will have this resolved asap.

The issue has now been fully resolved

We are currently investigating an issue affecting the creation functions for Uptime & Domain type testing, which may be causing some users to experience difficulties. Additionally, we are aware of availability issues with the StatusCake API. Our team is actively working on resolving these issues and we apologize for any inconvenience this may be causing. We will provide updates as soon as possible.

The issue has been identified and a fix is being implemented

This incident has now been resolved, our apologies for the disruption

We had an incident with a main server provider, which caused the app and some uptime testing reports to trigger false alerts. After commicating with the server provider the issue was found to be routing issues within their London datacentre that caused the app to become inaccessible for a period of time. This then also impacted the systems ability to run uptime tests appropriately. The issue lasted for 1 hour 8 Minutes. The issue has now been resolved.

A primary server provider had unexpected downtime over the weekend, which went unnoticed on their side. As we were not notified about the issues we were unaware that the maintenance windows service had stopped performing correctly for some customers for a period of 2 days. We have now inserted failovers to prevent this happening again, and maintenance windows are back running as normal.

We're seeing some customers getting issues logging into the app, with a bad gateway error. We are currently investigating this and hope to have a resolution as soon as possible

This incident has been resolved, the problem occurred due to an unexpected configuration change with a core provider. We will be reviewing the relevant component for reliability going forwards.

We're facing issues with our primary server provider, which has a major networking issue that is currently being investigated.

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

We are continuing to work on a fix for this issue.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

Our primary server provider has had a major networking breakage that is currently being investigated and fixed. The application and testing services are currently intermittently down.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We've identified an issue with our server provider that is currently facing mass power issues. We're in communication with them to understand the issue, and awaiting an immediate fix to the problem.

A fix has been implemented and we are monitoring the results.

We are continuing to monitor for any further issues.

This incident has been resolved.

Our main server provider is implementing emergency maintenance to fix issues that occured 24 hours ago across their systems. We were told there would be no network downtime but unfortunately they are sufferring from high network loss. We are in communication with them in order to understand the situation and will update further here.

Identified - The server provider has identified the cause of this incident as a power issue and are working in London to restore normal connectivity as soon as possible.

We understand that the datacenter (hosting multiple server providers) has been hit with a power outage. They are currently working with the centre staff to get systems back up and running

The datacenter has restored power, and we are actively monitoring all services to ensure all systems are back up an running.

We are continuing to monitor for any further issues.

This incident has been resolved.

Our main server provider has had a major networking breakage that is currently been investigated and fixed. The application, and testing services are currently down.

We are continuing to work on a fix for this issue.

The networking issue have been initially fixed. We're now monitoring all system to ensure all services are back to normal.

This incident has now been resolved but we will continue to keep monitoring the situation with network latency/degredation.

Due to a global outage with Cloudflare our app is inaccessible at the moment, however all testing capabilities are active. Status Pages will also be inaccessible until a fix is in place.

A fix has been implemented and we are monitoring the results.

We are monitoring a fix in place for customers to access the app, and StatusCake Pages again. We will continue to monitor

The StatusCake App, and Pages are back up and operational. We will continue to monitor.

All services are running as expected.

Due to a global outage of Cloudflare, our services were hit with a number of failing connection, which led to downtime on the StatusCake app, and several StatusCake Pages. The outage did not effect any of our testing suite however, so all alerts, and monitoring remained operational through the event.

An error occurred between 1:00AM - 7:00AM that prevented Push tests to be sent to StatusCake, which led to tests appearing as 'down', The cause was an SSL certificate, which failed to update as expected. The problem has now been resolved and all services are running as normal.

We proactively updated our servers to include a new SSL certificate but unfortunately the provider reverted the changes during a live migration failure. this led to the certificate not being updated, and instead serving an expired certificate. The certificate has now been updated, and push tests are working as expected