Last checked: 5 minutes ago
Get notified about any outages, downtime or incidents for Cronofy and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Cronofy.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
Component | Status |
---|---|
API | Active |
Background Processing | Active |
Developer Dashboard | Active |
Scheduler | Active |
Conferencing Services | Active |
GoTo | Active |
Zoom | Active |
Major Calendar Providers | Active |
Apple | Active |
Active | |
Microsoft 365 | Active |
Outlook.com | Active |
View the latest incidents for Cronofy and check for official updates:
Description: Our Engineering team has resolved the Scheduler issue, and users can now log in again. Please get in touch with [email protected] if you have any further questions.
Status: Resolved
Impact: Major | Started At: Jan. 10, 2022, 3:52 p.m.
Description: We have monitored the issue experienced by the third party and it is now resolved. Please contact [email protected] if you have any further queries.
Status: Resolved
Impact: None | Started At: Dec. 15, 2021, 4:22 p.m.
Description: We have monitored the issue experienced by the third party and it is now resolved. Please contact [email protected] if you have any further queries.
Status: Resolved
Impact: None | Started At: Dec. 15, 2021, 4:22 p.m.
Description: On Friday, December 10th, a critical remote code execution vulnerability (CVE-2021-44228), also known as Log4Shell, was discovered, which affects Apache Log4j versions 2.0-2.14.1. Log4j is a popular logging library in Java and is used in several enterprise applications. Our platform isn't written in Java and therefore isn't vulnerable, we do run some dependencies like Jenkins which are written in Java and have verified they are not vulnerable (as well as not being generally accessible from the internet), and we will update managed services as updates relating to this vulnerability are made available (for example, an update to AWS Elasticsearch was applied yesterday). Our team will continue to monitor our platforms and sub-processors, and we'll update you if there are any updates in relation to this vulnerability. At this point in time, no action is required by Cronofy customers. Please contact [email protected] if you have any further questions.
Status: Resolved
Impact: None | Started At: Dec. 13, 2021, 9 a.m.
Description: On Friday, December 10th, a critical remote code execution vulnerability (CVE-2021-44228), also known as Log4Shell, was discovered, which affects Apache Log4j versions 2.0-2.14.1. Log4j is a popular logging library in Java and is used in several enterprise applications. Our platform isn't written in Java and therefore isn't vulnerable, we do run some dependencies like Jenkins which are written in Java and have verified they are not vulnerable (as well as not being generally accessible from the internet), and we will update managed services as updates relating to this vulnerability are made available (for example, an update to AWS Elasticsearch was applied yesterday). Our team will continue to monitor our platforms and sub-processors, and we'll update you if there are any updates in relation to this vulnerability. At this point in time, no action is required by Cronofy customers. Please contact [email protected] if you have any further questions.
Status: Resolved
Impact: None | Started At: Dec. 13, 2021, 9 a.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.