All Systems Operational
Scheduler Operational
90 days ago
99.99 % uptime
Today
API Operational
90 days ago
99.99 % uptime
Today
Background Processing Operational
90 days ago
100.0 % uptime
Today
Developer Dashboard Operational
90 days ago
99.99 % uptime
Today
Major Calendar Providers Operational
Apple Operational
Google Operational
Microsoft 365 Operational
Outlook.com Operational
Conferencing Services Operational
GoTo Operational
Zoom Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Scheduled Maintenance
As previously announced in https://status.cronofy.com/incidents/903128h1l0bw, we will be changing to a new provider for our HTTPS certificate. This scheduled maintenance covers the second of three temporary switchovers to the new certificate and it will take place on Tuesday October 22, 2024, between 13:00 - 16:00 UTC.

These temporary switchovers are an opportunity for us to ensure all customers have tested their connectivity with the new certificate and will result in a smooth transition when we permanently switch.

It is highly likely that your browser is already configured to trust any certificates that our new provider, Amazon Certificate Manager (ACM), provides, and so we expect users of the Scheduler to be unaffected by this change.

However, there may be a very small number of our API customers with specific configurations, such as older operating systems, that will need to take action to ensure that our new certificate provider is trusted.

Details about how to test connectivity with the new certificate and how to ensure the new certificate provider is trusted can be found in the original announcement.

If you have any questions, please email support@cronofy.com.

Posted on Oct 15, 2024 - 08:26 UTC
Changing of HTTPS certificate provider Nov 18, 2024 10:00-11:00 UTC
We will be changing to a new provider for our HTTPS certificate on Monday November 18, 2024, after 10:00 UTC.

As with all HTTPS connections, when connecting to one of our endpoints such as https://api.cronofy.com, a certificate is used to verify that you are connecting to us and not to someone trying to impersonate us. Our current certificate is provided by VikingCloud and your system is already configured to trust any certificates they have provided.

On November 18, we will be switching to a certificate provided by Amazon Certificate Manager (ACM). It is highly likely that your browser is also already configured to trust any certificates that ACM provides, and so we expect users of the Scheduler to be unaffected by this change.

However, there may be a very small number of our API customers with specific configurations, such as older operating systems, that will need to take action to ensure that our new certificate provider is trusted. We, therefore, advise all API customers to check that their systems are configured to trust certificates provided by ACM. You can test this by checking that you can load one of the following URLs:
๐Ÿ‡ฆ๐Ÿ‡บย https://certificate-test-au.cronofy.com
๐Ÿ‡จ๐Ÿ‡ฆย https://certificate-test-ca.cronofy.com
๐Ÿ‡ฉ๐Ÿ‡ชย https://certificate-test-de.cronofy.com
๐Ÿ‡ธ๐Ÿ‡ฌย https://certificate-test-sg.cronofy.com
๐Ÿ‡ฌ๐Ÿ‡งย https://certificate-test-uk.cronofy.com
๐Ÿ‡บ๐Ÿ‡ธย https://certificate-test-us.cronofy.com

If you are able to load one of the above URLs successfully then you do not need to take any action.

If it does not load successfully, then you will need to add the Amazon root certificate authorities to your trust store. These can be obtained from https://www.amazontrust.com/repository, they are listed under the Certification Authorities section.

The benefits of making this change are that it increases our operational efficiency and is more secure. Manual renewal processes are replaced with automated ones, ACM is also more secure as private keys are securely protected and stored using strong encryption and key management best practices.

Before we permanently switch to the new certificate, we will have three temporary switchovers. These temporary switchovers are an opportunity for us to ensure all customers have tested their connectivity with the new certificate and will result in a smooth transition when do permanently switch. The temporary switchovers will happen at the following times:

1. Monday October 7, 2024, between 10:00 - 11:00 UTC
2. Tuesday October 22, 2024, between 13:00 - 16:00 UTC
3. Monday November 4, 2024, between 09:00 - 21:00 UTC

Each of the above temporary switchovers will be announced as separate scheduled maintenance on our status page.

If you have any questions, please email support@cronofy.com.

Posted on Aug 14, 2024 - 14:42 UTC
Past Incidents
Oct 15, 2024

No incidents reported today.

Oct 14, 2024

No incidents reported.

Oct 13, 2024

No incidents reported.

Oct 12, 2024

No incidents reported.

Oct 11, 2024

No incidents reported.

Oct 10, 2024

No incidents reported.

Oct 9, 2024

No incidents reported.

Oct 8, 2024

No incidents reported.

Oct 7, 2024
Completed - The scheduled maintenance has been completed. We have now switched back to the previous HTTPS certificate.
Oct 7, 10:59 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 7, 10:00 UTC
Scheduled - As previously announced in https://status.cronofy.com/incidents/903128h1l0bw, we will be changing to a new provider for our HTTPS certificate. This scheduled maintenance covers the first of three temporary switchovers to the new certificate and it will take place on Monday October 7, 2024, between 10:00 - 11:00 UTC.

These temporary switchovers are an opportunity for us to ensure all customers have tested their connectivity with the new certificate and will result in a smooth transition when we permanently switch.

It is highly likely that your browser is also already configured to trust any certificates that ACM provides, and so we expect users of the Scheduler to be unaffected by this change.

However, there may be a very small number of our API customers with specific configurations, such as older operating systems, that will need to take action to ensure that our new certificate provider is trusted.

Details about how to test connectivity with the new certificate and how to ensure the new certificate provider is trusted can be found in the original announcement.

If you have any questions, please email support@cronofy.com.

Oct 4, 10:51 UTC
Oct 6, 2024

No incidents reported.

Oct 5, 2024

No incidents reported.

Oct 4, 2024

No incidents reported.

Oct 3, 2024

No incidents reported.

Oct 2, 2024
Postmortem - Read details
Oct 3, 16:31 UTC
Resolved - US data center performance has remained normal and the incident is resolved.

Around 00:56 UTC inbound traffic to api.cronofy.com and app.cronofy.com began to show signs of performance degradation. This was observed to be an issue routing traffic from our load balancers to their respective target groups and on to our servers.

This resulted in an increase in processing time which, in turn, resulted in some requests timing out.

By 01:04 UTC the issue with the load balancers routing traffic had been resolved and traffic flow returned to usual levels.

A small backlog of requests was worked through by 01:10 UTC and normal operations resumed.

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.

Oct 2, 02:38 UTC
Monitoring - We're continuing to monitor traffic flow but all indicators show that, an increase in incoming traffic being retried remotely aside, as of 01:06 UTC routing had returned to normal.
Oct 2, 02:11 UTC
Identified - Performance has returned to expected levels.

Between 00:56 and 01:04 UTC, traffic making it's way from our load balancers to our servers did not do so in a timely manner. This will have resulted in possible timeouts for requests to api.cronofy.com and app.cronofy.com and potential server errors for API integrators and Scheduler users.

Oct 2, 01:55 UTC
Investigating - We have seen some performance degradation in our US data center.

Initial findings appear similar to those of 26 Sept 2024. Improved monitoring has highlighted this issue earlier and we are in the process of investigating further.

Oct 2, 01:42 UTC
Oct 1, 2024

No incidents reported.