ActiveCampaignService Interruption: Account Access Issues (APAC & EU)
This incident has been resolved.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
This incident has been resolved.
Resolved
The issue has been resolved and you should be seeing no slowness in the Braintrust Control Plane UI. Please let us know if you have any issues.
Resolved
Problem has been resolved. We saw three nodes fail across three availability zones simultaneously. Impacting databases hosted on those nodes. All databases have been moved to healthy nodes and we're investigating how we can further reduce impact from similar events in the future.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
We can confirm services have continued to remain stable and the issue is now considered resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
All chats on Ona Cloud and Ona Intelligence customers should function as usual. Customers with an Anthropic custom BYOK should also not be impacted anymore.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has now been resolved and the service is now fully operational.
Resolved
This incident has been resolved.
Resolved
All impacted services have now fully recovered.
Resolved
This issue has been resolved as of February 17 at 18:59 UTC.
Resolved
This incident has been resolved.
Resolved
Between 12:30 UTC and 13:45 UTC, some customers were unable to complete plan purchases due to an issue with an upstream provider. Our upstream provider has identified the root cause and confirmed recovery. As a result, new plan purchases are now working as expected. We sincerely appreciate your patience and understanding as we worked to resolve this issue.
Resolved
This issue has been resolved,
Resolved
Between 08:48 AM (UTC +00:00) and 12:20 AM (UTC +00:00), many customers in all affected regions experienced issues with session invalidation. This was caused by a load balancer impairment. As of 12:20 AM (UTC +00:00), our session invalidation is working properly and the incident has been fully resolved. HubSpot conducts a thorough review after each incident to understand the cause and prevent it from happening again. Learn more about HubSpot's commitment to reliability at www.HubSpot.com/reliability. The information on this page reflects our understanding of the incident and impact at the time of the update.
Resolved
We have implemented the fix and the group page in the Admin Hub is now functioning as expected.
Resolved
We have implemented the fix and the group page in the Admin Hub is now functioning as expected.
Resolved
This incident has now been resolved and the service is now fully operational.
Resolved
After close monitoring, we can confirm that the publishing issue with Pinterest has been fully resolved, and all systems are now operational. We appreciate your understanding and apologise for any disruption this may have caused.
Resolved
Between 09:20 UTC and 09:44 UTC on Wed Feb 18 2026, some customers in the USEU region may have experienced delayed data in queries, charts, and dashboards. We have investigated and resolved this service interruption and impacted services have returned to normal operations.
Resolved
### **Summary** On Feb 9, 2026, between 07:12 UTC and 08:05 UTC, Atlassian customers were unable to access Trello. The event was triggered by Trello servers reaching maximum memory limits and a subsequent failure to automatically scale for the traffic. The incident was detected within 5 minutes by automated monitoring systems, engaging Trello teams for resolution. Two parallel mitigation efforts were undertaken to restore access: 1\) manual scaling to address concerns with high utilization of hosts, and 2\) temporarily limiting traffic from free customers. This intervention put Trello systems in a known good state with a total time to resolution of ~53 minutes. ### **IMPACT** The overall impact occurred on Feb 9, 2026 between 07:12 AM UTC and 08:05 AM UTC for Trello customers and caused service disruption for all customers, making Trello inaccessible during that time. Access was restored for paid users approximately 43 minutes after the onset, with full service restoration for free users 10 minutes later. ### **ROOT CAUSE** The issue was cause by increased memory requirements during the transition from the weekend to EU business hours, combined with Auto Scaling group scaling rules based on CPU utilization. Memory allocation on our instances outpaced the CPU usage, which caused processes to hit Out-Of-Memory \(OOM\) errors and crash before reaching CPU usage thresholds that would trigger the auto scaling policies. As a result, Trello went down and users received HTTP 502 errors until the incident was resolved. ### **REMEDIAL ACTION PLAN & NEXT STEPS** We know that outages impact your productivity. While we have a suite of automated infrastructure management in place, this specific issue required manual intervention to restore Trello access to users. To avoid repeating this type of incident, we are prioritizing the following remedial action items: * Pre-scale capacity before EU morning traffic - This change has already been introduced to prevent further incidents while we implement additional safeguards. * Adjust Trello’s Auto Scaling group settings - This change will ensure that unhealthy hosts will be replaced more rapidly and scaling policies will consider memory usage. * Refine Trello host memory commitments - This change will decrease the likelihood of memory overcommitment on hosts and associated OOM errors. * Increase isolation for OOM errors - This change will improve the ability for hosts to recover in the event of a single worker experiencing an OOM error. 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
Restarting specific nodes improved the situation. We'll mark the incident as resolve while we keep monitoring the situation. More information: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21303
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The issue has been resolved and we are no longer seeing any issues with degraded performance.
Resolved
Issues affecting the NGC Core Services has been resolved and the service is operating normally.
Resolved
Normal service has been restored. Payouts are now settling normally. Impact start time: 17/02/2026, 23:04 UTC Impact end time: 17/02/2026, 23:37 UTC Client actions: None
Resolved
This incident has been resolved.
Resolved
The issue has been resolved.
Resolved
As of 10:00 UTC, the issues from OpenAI models is being resolved.
Resolved
This issue is now resolved.
Resolved
Github has resolved their incident
Resolved
This incident has been resolved.
Resolved
On February 11, 2025, between 14:30 UTC and 15:30 UTC, the Copilot service experienced degraded availability for requests to Claude Haiku 4.5. During this time, on average 10% of requests failed with 23% of sessions impacted. The issue was caused by an upstream problem from multiple external model providers that affected our ability to serve requests. <br /><br />The incident was mitigated once one of the providers resolved the issue and we rerouted capacity fully to that provider. We have improved our telemetry to improve incident observability and implemented an automated retry mechanism for requests to this model to mitigate similar future upstream incidents.
Resolved
This incident has been resolved.
Resolved
The issue has been resolved and all services are now fully operational. Thank you for your patience!
Resolved