Outage in Cronofy

Major outage in US data center

Resolved Major
October 20, 2025 - Started about 17 hours ago - Lasted about 12 hours
Official incident page

Incident Report

Since around 07:15 UTC our US data center has been severely impacted by an ongoing incident in AWS us-east-1, where it is hosted: https://health.aws.amazon.com/health/status AWS have identified a potential root cause for the issue and are working on multiple parallel paths to accelerate recovery. At 09:20 UTC we started seeing signs of recovery. As of 09:30 UTC all high priority tasks were cleared which are those with the most visible user impact. We are unable to scale additional capacity to clear lower priority tasks at present, which are more background processes such as polling calendars (Apple) and housekeeping style tasks. This backlog is being processed, but not at a pace that means we are clearing it as quickly as we would like. All other data centers are fully operational.

One place to monitor all your cloud vendors. Get instant alerts when an outage is detected.

Try IsDown risk-free 14-day free trial · No credit card required
Latest Updates ( sorted recent to last )
RESOLVED about 5 hours ago - at 10/20/2025 09:58PM

On October 20th, AWS's us-east-1 region experienced a significant incident impacting multiple underlying services.

This led to the operation of Cronofy's US data center, which is hosted in this AWS region, being severely impacted. None of Cronofy's other data centers were affected at any time.

The main impact was felt between 07:15 and 09:15 UTC where many critical components struggled to communicate with AWS's services. Performance was severely degraded throughout this period.

We saw some recovery from 09:15 UTC, with the backlog of high priority tasks completed by 09:30 UTC, these are the tasks most likely to have a user-noticeable impact.

Some issues remained, mainly the ability to provision additional servers which has been widely reported by other AWS customers.

However, we had sufficient capacity to clear the backlog of lower priority tasks by 10:20 UTC. Performance of the US data was back to normal from this time, and we continued to monitor.

Throughout the day we ran with an altered configuration to obtain as much capacity as we could from AWS to provide as smooth a service as possible.

Our ability to provision additional capacity was restored at 19:15 UTC.

While the underlying AWS incident is still open, we are considering this incident to be resolved as we have been able to resume normal operations.

A postmortem of the incident will take place and be attached to this incident in the next 48 hours.

If you have any queries in the interim, please contact us at support@cronofy.com.

MONITORING about 13 hours ago - at 10/20/2025 01:40PM

AWS continue to work towards a full resolution.

We remain unable to reliably provision additional capacity in our US data center. However, since the previous message, we have managed to increase the available capacity.

Performance of the US data center continues to be normal, and we will continue to monitor.

MONITORING about 17 hours ago - at 10/20/2025 10:29AM

Since around 07:15 UTC our US data center has been severely impacted by an ongoing incident in AWS us-east-1, where it is hosted: https://health.aws.amazon.com/health/status

At 09:15 UTC we started seeing signs of recovery. As of 09:30 UTC all high priority tasks were cleared which are those with the most visible user impact. Lower priority tasks were cleared by 10:20 UTC.

AWS continue to work towards full resolution.

We remain unable to reliably provision additional capacity in this data center. We have taken steps to ensure we retain the capacity we already have.

Performance of the US data is now back to normal, we continue to monitor whilst the underlying AWS incident is active.

MONITORING about 17 hours ago - at 10/20/2025 09:52AM

Since around 07:15 UTC our US data center has been severely impacted by an ongoing incident in AWS us-east-1, where it is hosted: https://health.aws.amazon.com/health/status

AWS have identified a potential root cause for the issue and are working on multiple parallel paths to accelerate recovery.

At 09:20 UTC we started seeing signs of recovery. As of 09:30 UTC all high priority tasks were cleared which are those with the most visible user impact.

We are unable to scale additional capacity to clear lower priority tasks at present, which are more background processes such as polling calendars (Apple) and housekeeping style tasks. This backlog is being processed, but not at a pace that means we are clearing it as quickly as we would like.

All other data centers are fully operational.

The Status Page Aggregator Built for IT Teams

With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.

Start free trial

No credit card required · Cancel anytime · 4522 services available

Integrations with Slack Microsoft Teams Google Chat Datadog PagerDuty Zapier Discord Webhook