SpeechmaticsUsers are experiencing issues signing into portal.speechmatics.com.
This incident has been resolved.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
This incident has been resolved.
Resolved
All good!
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
We are currently investigating this issue.
Resolved
This incident has been resolved.
Resolved
### Summary On January 21, 2025, between 14:02 and 17:49 UTC, Atlassian customers using Bitbucket Cloud were unable to use the website, API, or Pipelines. The event was triggered by write contention in a high traffic database table. The incident was detected within eight minutes. We then worked to both throttle traffic and improve query performance, which allowed services to recover. The total time to resolution was about three hours and 47 minutes. ### **IMPACT** The overall impact was between 14:02 and 17:49 UTC, affecting Bitbucket Cloud. This impacted customers globally, and they were unable to use the website, APIs, or Pipelines services. Git hosting \(SSH\) was unaffected. ### **ROOT CAUSE** The issue was caused by an increase in API traffic triggering write contention on a high-traffic table, resulting in increased CPU usage and degraded database performance. This ultimately impacted the availability of core services \(web, API, and Pipelines\). ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity. While we have several testing and preventative processes in place, this specific issue wasn’t identified because the code path being triggered does not commonly experience this type of traffic. We are prioritizing the following improvement actions to avoid repeating this type of incident: * Running additional maintenance on core database tables * Added throttling on write-heavy operations To improve service resilience and recovery time for our environments, we will implement additional preventative measures such as: * Improving database observability to isolate failures * Continuing to shard data to better distribute traffic load We apologize to customers whose services were impacted by this incident and are taking immediate steps to improve the platform’s performance and availability. Thanks, Atlassian Customer Support
Resolved
This incident has been resolved.
Resolved
The issue has been fully resolved. All affected components are operating normally again.
Resolved
This incident has been resolved.
Resolved
The issue is resolved. Data related to Cost reports and APIs is up to date.
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 have successfully completed the backfill of all missing audit log entries.
Resolved
The Grammarly Editor is back up and running! Thanks for your patience!
Resolved
This incident has been resolved.
Resolved
We’ve implemented a fix and confirmed that the issue is resolved. The service is back to normal. We apologize for the interruption!
Resolved
From 2:30 AM - 6:30 AM UTC some users experienced slow performance loading the Figma file browser view as well as features like comments. We have since resolved the underlying issue and are monitoring closely.
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
For a brief period, all requests to our server were failing.
Resolved
Issue is resolved. Customers could have experienced errors or long load times from 14:21 to 14:24 UTC and 15:32 to 15:31 UTC
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
All services are are up and running and JFrog will provide the required root cause analysis upon request
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 resolved this incident.
Resolved
This incident has been resolved.
Resolved
This incident is now resolved. Thanks for bearing with us!
Resolved
This incident is now resolved. Thanks for bearing with us!
Resolved
Sorry also for not updating the status page before, it looked ephemeral when it first surfaced. The issue was one API node that was having networking issues and was failing to connect to the rest of the systems and was timing out while at it. Only requests routed to this API node were affected, so retries would succeed. It's now been resolved.
Resolved
This incident has been resolved.
Resolved
An incident impacting our website, API, webhooks and metrics has been resolved and all actions should now be operational.
Resolved