CodaUnable to receive emails from Coda
This incident has been resolved.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The issue has been resolved
Resolved
This incident has been resolved.
Resolved
Between <15:34 UTC> to <19:12 UTC>, we experienced realtime update functionality degraded performance for Trello. We have mitigated the problem and are investigating the root cause. The issue has been resolved and the service is operating normally.
Resolved
This incident has been resolved.
Resolved
This issue is now fixed. All published documents are now available in GOV.UK 'finders'.
Resolved
We are all set! All affected services are now operational. Users will now be able to create documents from existing templates, as well as open template and CLI lists. We will continue monitoring services. If you continue to experience issues with this, please contact our Support team
Resolved
This incident has been resolved.
Resolved
The number of concurrent processes was reduced which has resolved the issue. The Publishing API is processing requests at normal rates again.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Issues where some API calls configured to use api.opsgenie.com/eu were intermittently returning a 404 error with the message 'no Route matched with those values' should now be resolved. API calls to api.eu.opsgenie.com and api.opsgenie.com (without /eu) were not affected at this time.
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
### SUMMARY On February 11, 2025, between 15:41 and 16:26 UTC, Atlassian customers using Bitbucket Cloud experienced workspace access errors \(HTTP 404\) when attempting to access the website, API, and Git over HTTPS/SSH. The event was triggered by a failure in our feature flagging service, which inadvertently blocked some users from core services. The incident was detected within eight minutes by automated monitoring and was resolved 45 minutes later once a change to a feature flag configuration had been fully deployed. ### **IMPACT** A subset of Bitbucket Cloud users were unable to access their workspace. When trying to access their Bitbucket cloud repository through the website, API, or CLI, these users would have seen a 404 error message. ### **ROOT CAUSE** An upstream failure in a feature flagging service resulted in Bitbucket’s application logic not working correctly. This resulted in access errors for a subset of customers. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity. While we have a number of testing and preventative processes in place, this specific failure scenario wasn’t identified during testing. We are prioritizing the following improvement actions designed to avoid repeating this type of incident: * Fixing the root cause of the bug in our feature flag service * Improving Bitbucket’s fallback mechanisms and handling of errors in feature flags * Improving test coverage and war gaming failures with core dependencies. We apologize to customers whose services were impacted during this incident; we are taking immediate 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
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've applied the fix, the incident has been resolved. We will continue to monitor error reports related to this issue throughout the day.
Resolved
We fixed the degraded performance and all our systems are back online and functional.
Resolved
This incident has been resolved.
Resolved
Thank you for your patience. Slack has resolved the main messaging outage for all users and is continuing to restore other features. We've observed that our automation Slack actions are now functioning properly. If your automations were affected, we recommend checking the run history and manually retrying them to resend your Slack messages.
Resolved
This incident has been resolved.
Resolved
We're all set! PandaDoc is working properly and the incident has been fully resolved. If you continue to experience issues with this, please contact our Support team (https://support.pandadoc.com/en/articles/9715061-how-to-contact-pandadoc-support).
Resolved