AblyAbly.com (Website Only) intermittent connection issues
Cloudflare is indicating that the incident is resolved, and all Ably services appear to be operating normally. We will continue to monitor the situation.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
Cloudflare is indicating that the incident is resolved, and all Ably services appear to be operating normally. We will continue to monitor the situation.
Resolved
This incident has been resolved and the monitors have been re-enabled at this time.
Resolved
We're all set! PandaDoc is working properly and the incident has been fully resolved. If you continue to experience any issues with this, please reach out to us at support@pandadoc.com.
Resolved
15:00 UTC - We are currently investigating increased latency for Realtime endpoints in our Europe (Ireland) region. 15:25 UTC - Latencies are back to expected levels and the service is operating as normal.
Resolved
This incident has been resolved.
Resolved
A misconfiguration by our database vendor prevented our database from restarting successfully. The misconfiguration was identified and remedied. Campaigns scheduled to send during the outage are now sent. Loop emails scheduled to send during the outage are now sent. Transactional emails or API calls made during the outage window need to be retried.
Resolved
This incident has been resolved. The team saw similarities with a previous incident that affected the US2 cluster and acted swiftly to mitigate and prevent further impact. Overall the impact was very small: a few connections saw small delays receiving messages for a very short time.
Resolved
All channels should be back to normal now.
Resolved
### **SUMMARY** On September 10, 2024, between 6:34 PM UTC and 7:19 PM UTC, some Atlassian customers experienced an issue preventing users from connecting to Bitbucket Cloud via SSH. The issue arose from a change in how we determined IP allow lists, which inadvertently blocked access for customers with these controls enabled. The incident was promptly identified through our monitoring systems, and our teams initiated response protocols to mitigate the issue. ### **IMPACT** The incident only affected customers who had IP whitelisting enabled on their Bitbucket Cloud accounts. These customers experienced difficulties connecting via SSH due to the unintended blocking caused by a change in the IP allow list computation. The service interruption lasted approximately 45 minutes, during which time affected users were unable to access their repositories through SSH. ### **ROOT CAUSE** A change to IP allow list evaluation was incompatible with a new Bitbucket Cloud networking configuration. This inadvertently blocked SSH access for customers with specific allow lists restrictions enabled. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** To restore the SSH service, the team quickly rolled back the release responsible for the IP allow list issue. We know that outages impact your productivity. We are prioritizing the following improvement actions to avoid repeating this type of incident: * Improve monitoring coverage of IP allowlisting; * Add additional tests and deployment validation checks for changes to IP allowlist configurations. We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability. Atlassian Customer Support
Resolved
This incident is now resolved. Thanks for bearing with us!
Resolved
This issue has been resolved.
Resolved
This issue has been resolved.
Resolved
This issue has been resolved.
Resolved
This issue has been resolved.
Resolved
This incident has been resolved.
Resolved
This issue has been resolved.
Resolved
This issue has been resolved.
Resolved
This issue has been resolved.
Resolved
We have resolved the stability issue on our site, and performance is back to normal. We appreciate your patience.
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
This incident has been resolved.
Resolved
This incident has been resolved.
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
Some customers might have encountered issues loading the data or automations tab. This issue has been resolved now. We’re sorry for the inconvenience to our customers’ operations.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident is resolved. Thanks for bearing with us!
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
We have resolved the statistics computation issue. Connection counts should be correct again and remain accurate going forward. Daily message volume counters will still show inflated usage until the end of the day; customers that are concerned about potential throttling due to breaching daily limits can reach out to customer support to ensure access remains uninterrupted.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Issues affecting the NGC Core service have been resolved and the service is operating normally.
Resolved
We have mitigated this issue, and Airtable's service is now operating normally. We apologize for the inconvenience.
Resolved
This incident has been resolved. Please refresh your Datadog web page to resolve the issue completely.
Resolved