SquarespaceAcuity Scheduling / Acuity doesn't load for some users
The issue appears isolated to a small set of users located in geographic regions affected by network outages.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
The issue appears isolated to a small set of users located in geographic regions affected by network outages.
Resolved
The backed up emails have been delivered. Please reach out to support@mailchannels.com if you have questions.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved. The incident lasted 20 minutes and had minor impact on users in AP South East when creating new query engines.
Resolved
### **SUMMARY** Between September 10, 2025, at 13:56 UTC and September 11, 2025, at 14:40 UTC, Jira Service Management, Compass Cloud Operations, and Opsgenie customers in the U.S. region experienced degraded performance across web and mobile applications, as well as Alert REST APIs. Certain customers experienced difficulties with alert searches and page loading, particularly on alert-related pages. This incident was initiated by an EBS volume upgrade conducted within the cloud-based managed ElasticSearch clusters. Our automated monitoring systems identified the incident within minutes, and it was resolved after 24 hours and 43 minutes by manually implementing vertical and horizontal scaling measures. ### **IMPACT** Between September 10, 2025, 13:56 UTC and September 11, 2025, 14:40 UTC, some customers in the U.S. region experienced degraded performance in Jira Service Management, Opsgenie, and Compass Cloud. During this time, web and mobile applications, as well as the Alert REST APIs, were impacted. Some customers may have seen issues with alert searches and slow loading of alert pages. During the incident, 22% of customers in the US region experienced failures in web API functionality, 8.6% encountered failures with the REST Alert API, and 1.3% experienced delays in notification delivery. Importantly, there was no loss of data during this event. ### **ROOT CAUSE** The degradation was caused by an EBS volume upgrade in the cloud-based managed ElasticSearch clusters, which necessitated a Blue/Green deployment strategy. One of the ElasticSearch nodes approached its shard size threshold, prompting the upgrade and subsequent deployment. This deployment resulted in elevated latency, increased 4xx HTTP response codes, and timeouts affecting both search and indexing operations. Recovery time exceeded expectations due to the prolonged blue/green deployment. After completion, the ElasticSearch cluster remained unhealthy and did not return to its normal state. Additionally, the switchover to the backup region failed because it was configured similarly in size and setup to the primary cluster. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We understand that outages can affect your productivity. We are prioritizing the following improvement actions to help prevent similar incidents in the future: * Increase ElasticSearch cluster capacity and optimize settings to handle peak search loads efficiently. * Strengthen our high availability \(HA\) and failover architecture to ensure rapid and reliable recovery in the event of primary region failures. * Optimize cluster upgrade and shard rebalancing strategies to prevent similar issues. We apologize to customers whose services were impacted during this incident. We are taking steps to improve the platform’s performance and availability. Thanks, Atlassian Customer Support
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The incident has been resolved.
Resolved
From 8a - 10a GMT there was an issue related to the pick-up time of our non-English language models. This caused an increase in processing time for pre-recorded transcriptions. Our Engineering team has released a fix and all transcriptions should now be processing normally.
Resolved
We have confirmed reports that the latest version of the iOS app (5.69.2) addresses the issue. If you run into login issues, ensure you've updated to the latest version, and reach out if the problem persists.
Resolved
This Incident has been Resoled.
Resolved
Aside from a small window of about five minutes around 12:10pm PT where turnaround times were slightly higher than usual, we have continued to see turnaround times within the expected ranges so we are now closing this issue.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Meta API availability has returned to normal, and we continue to monitor conversion rates closely. We will update this page if any further anomalies occur. Thank you for your patience.
Resolved
The fix has been deployed, and the user interface now correctly displays the capacity for CMK nodepool creation. You can now use either the UI or the CLI to provision new nodepools.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
We have confirmed resolution of this issue and this incident is now resolved.
Resolved
This incident has been resolved
Resolved
A fix has been implemented. This incident is now resolved
Resolved
Our website, Hotjar.com was briefly inaccessible, but service has been restored. Thanks for bearing with us, and we apologize for any inconvenience caused.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
We have identified and resolved the cause of the issue. If you experience any further problems, please contact Support.
Resolved
The editor is now functioning as expected.
Resolved
This incident has been resolved.
Resolved
Our provider has deployed a fix. Error rates have returned to normal. This incident is now resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Google has resolved the issue: https://www.google.com/appsstatus/dashboard/incidents/7Bgq1PUK83NuVZHMZXWd
Resolved
We are glad to inform you that the fix has been implemented and the incident resolved. We will run a problem investigation to understand what happened and how to prevent it from happening again. Thanks for your understanding & sorry for any inconvenience this has caused.
Resolved
The incident with API and Webhooks has been resolved.
Resolved
This incident has been resolved.
Resolved