Confluent CloudNetwork provisioning service in Azure East US region is degraded
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. If you are still experiencing an issue, please let us know in our Etsy Forums (https://community.etsy.com/t5/Technical-Issues/bd-p/bugs).
Resolved
This incident has been resolved.
Resolved
A temporary issue during a Flux-related update caused intermittent SDK session errors. The issue was identified and resolved. 2:00 AM UTC - 13:45 UTC
Resolved
Incident Summary On February 23, 2026, our text-to-speech \(TTS\) service experienced significant performance degradation affecting customers in APAC and US regions for approximately 8 hours. Users experienced elevated latency in both time to first audio \(TTFA\) and real-time factor \(RTF\), resulting in slow response times and choppy or distorted audio output. The incident was triggered by an architectural change in our streaming orchestration infra, which introduced a performance regression in request data flow at very high cluster level concurrencies. We mitigated the incident by rolling back the clusters to the previous stable architecture. Impact Duration: Approximately 8 hours \(February 23, 07:30 UTC - 15:30 UTC\) Symptoms: • Significantly elevated p99 Time to First Audio \(TTFA\), particularly noticeable during peak traffic • Degraded Real-Time Factor \(RTF\) causing choppy, broken, or distorted audio Scope: Customers in APAC and US regions experienced degraded service quality. While traffic levels remained steady, performance regressions were most pronounced during regional peak hours. Timeline \(UTC\) All times are in UTC \(Coordinated Universal Time\). 1. 07:10 UTC - First customer reports of distorted audio in APAC region 2. 08:50 UTC - Infrastructure scaled up in APAC, providing temporary improvement 3. 11:42 UTC - Continued reports of high inter-chunk latencies from APAC users 4. 12:15 UTC - Additional scaling performed with temporary metric improvements 5. 13:00 UTC - Root cause was triaged to the infrastructure change, mitigation developed 6. 14:20 UTC - Proactive rollback initiated in US region ahead of peak traffic 7. 15:30 UTC - Complete migration to stable configuration, service fully restored Root Cause Analysis The incident was caused by a recent infrastructure change to our message streaming layer. We use a PubSub routing layer based off NATS to manage request data flows. We migrated from a lightweight message publishing protocol to a more robust jetstream-based protocol as part of improving our task assignment durability and reliability. While the new protocol provides important guarantees for task assignment, it introduced significant performance overhead in the request processing hotpath at high concurrency. Specifically, the new protocol adds acknowledgment flows for each message, which substantially increased the P99 message publish latency and lowered the total throughput of messages / second through the PubSub. This performance regression directly impacted our ability to stream audio chunks efficiently, causing the elevated TTFA and degraded RTF that customers experienced. The rollback involved migrating workloads back to our stable bare metal worker configuration, which restored normal performance levels. Learnings and Next Steps This incident highlighted several areas for improvement in our infrastructure and operational processes: Enhanced Monitoring: We do actively measure server side TTFA, but not server side RTF. RTF measures are implemented at the modeling layer, which was not affected by this change. Since TTFA perturbation was much smaller than the RTF perturbation, we were slower to detect this degradation. Improvements to our Benchmarking for Rollouts: We have robust benchmarking infrastructure for rollouts, but the scale of this is generally, intentionally, smaller than our production traffic. However, for the purposes of architecture shifts, we will be establishing a way to measure our infrastructure against simulated models to achieve full prod scale tests. Streamlined Rollback Procedures: Rollbacks while preserving prod traffic are currently still a semi-manual process. This delayed our mitigations to take ~1 hour from when we started. We are working improving the automations here that make global rollbacks faster. We sincerely apologize for the impact this incident had on your applications and services. We are committed to learning from this experience and continuously improving the reliability and performance of our TTS platform. If you have any questions or concerns about this incident, please don't hesitate to reach out to our support team.
Resolved
The issue has been resolved
Resolved
This issue has been resolved. Gen3 Alpha Turbo generations queue wait times are normal again.
Resolved
✅ We've resolved an issue affecting Fortnite, Rocket League, Fall Guys and Epic Online Services logins. We're continuing to monitor services to ensure everything remains stable.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Both the application and published content have recovered fully after the fix was released and should be working as expected.
Resolved
We have identified a backlog in our processing queues that is causing delays in coverage report processing. Uploads are still being accepted but results may take longer than expected to appear. Our team is actively working to remediate the issue. No data has been lost. *Update 2026-02-24 5PM PT* The issue has been identified and patched, we will continue to monitor for any changes.
Resolved
The issue with our application and authentication has been resolved. Performance has remained stable following mitigation.
Resolved
Resolved
All impacted services have now fully recovered.
Resolved
All services have returned to normal operation. Queries are executing successfully, and internal traffic between services has been fully restored. We are continuing to monitor the system to ensure stability.
Resolved
We observed minor service degradation in API responses from 11:19 UTC to 11:23 UTC due to an internal server issue, which resulted in an unexpected increase in API failures in the US region. We apologize for any inconvenience caused.
Resolved
A instabilidade no processo de redefinição de senha foi resolvida com sucesso. Caso você note que sua conta ainda contém alguma inconsistência, por favor, entre em contato com nosso Time de Suporte através da nossa Central de Ajuda "através da nossa Central de Ajuda": http://ajuda.rdstation.com/..
Resolved
We investigated reports of slow page loads and timeouts when accessing the web app. Our team has identified and resolved the issue. Performance is now stable, and we'll continue to monitor all services over the next few hours. Thank you for your patience while we resolved this!
Resolved
Just before 3pm on 26th of Feb '26, an incorrect configuration was accidentally deployed to our EU environment which impacted query performance. We quickly identified the issue and released a fix.
Resolved
The delays in SIM card management actions have been resolved. All operations are processing normally.
Resolved
GitHub experienced degraded Copilot policy propagation from enterprise to organizations between February 3 at 21:00 UTC through February 10 at 16:00 UTC. During this period, policy changes could take up to 24 hours to apply. We mitigated the issue on February 10 at 16:00 UTC after rolling back a regression that caused the delays. The propagation queue fully caught up on the delayed items by February 11 at 10:35 UTC, and policy changes now propagate normally.<br /><br />During this incident, whenever an enterprise updated a Copilot policy (including model policies), there were significant delays before those policy changes reached their child organizations and assigned users. The delay was caused by a large backlog in the background job queue responsible for propagating Copilot policy updates.<br /><br />Our investigation determined the incident was caused by a code change shipped on February 3 that increased the number of background jobs enqueued per policy update, in order to accommodate upcoming feature work. When new Copilot models launched on February 5th and 7th, triggering policy updates across many enterprises, the higher job volume overwhelmed the shared background worker queue, resulting in prolonged propagation delays. No policy updates were lost; they were queued and processed once the backlog cleared.<br /><br />We understand these delays disrupted policy management for customers using Copilot at scale and have taken the following immediate steps:<br /><br />1. Restored the optimized propagation path and put tests in place to avoid a regression.<br />2. Ensured upcoming features are compatible with this design. <br />3. Added alerting on queue depth to detect propagation backlogs immediately.<br /><br />GitHub is critical infrastructure for your work, your teams, and your businesses. We are focused on these mitigations and continued improvements so Copilot policy changes propagate reliably and quickly.<br />
Resolved
The Performance Degradation affecting MCP server has been fully resolved. We apologize for the inconvenience caused and appreciate your understanding. If you continue to experience any issues, please reach out to our support team.
Resolved
Our team has identified and resolved the issue, and performance is now stable across the board; therefore, we're closing this out. We'll continue to monitor all services over the next few hours. Thank you for your patience while we resolved this!
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
All services are back to healthy.
Resolved
A fix has been implemented, and we see that our assets become available and reports a healthy status. We’ve been monitoring the situation, and will continue checks
Resolved
We verified that the fix works as expected. Dashboard loads as expected.
Resolved
The identified issue has been fixed. There was an issue with some SumUp services. Our engineering team applied a fix that resolves the issue. You can find up-to-date information here on our status page "status page": https://status.sumup.com.
Resolved
This issue has now been fully resolved. Posts, drafts, and queue counts are updating as expected across both the web app and mobile apps. We’re sorry for the inconvenience this may have caused. If you’re still experiencing any issues, please reach out to us at hello@buffer.com, and our team will be happy to help.
Resolved
This incident has been resolved.
Resolved
Severity Level: High Our engineers have identified the root cause and have resolved the issue. Launches are enabled on the affected regions. In the event you’re unsure as to whether your service is impacted by this incident, please open a support ticket. We’ll get back to you as soon as possible. • https://support.lambdalabs.com/hc/en-us/requests/new To be automatically notified when the status of this incident changes, please click on the “Subscribe to updates” button. Thank you for your patience and understanding during this time.
Resolved
A small number of users may have experienced higher latency or intermittent failures. This has now been resolved.
Resolved
Things have remained stable, and all systems looking good. This issue has been resolved.
Resolved
Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.
Resolved
The incident is now resolved and the system is full operational.
Resolved
Systems have remained stable, and we are confident the issue has been resolved.
Resolved
This incident has been resolved.
Resolved
Workflows are now fully accessible. We've identified and addressed the root cause of the issue. The incident has been fully resolved and Workflows should be working properly. No data was lost.
Resolved