Moonshot AI搜索请求出现大量报错
This incident has been resolved.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
This incident has been resolved.
Resolved
All impacted services have now fully recovered.
Resolved
The incident has been resolved, and the service is now operating normally. Thank you for your patience.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
This issue has been resolved.
Resolved
The issue has been resolved.
Resolved
This incident has been resolved.
Resolved
The issue has been fully resolved and everything is functional again.
Resolved
The issue has been resolved. We apologize for any inconvenience caused and thank you for your patience.
Resolved
All impacted services have now fully recovered.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved, and service is operating normally again. Thanks for your patience.
Resolved
All impacted services have now fully recovered.
Resolved
The third party has recovered
Resolved
This incident has been resolved.
Resolved
On September 14, 2026, between 16:10 and 19:01 UTC, some customers using GitHub Actions larger runners experienced longer-than-normal wait times for jobs to start. During this period, <b>5.7%</b> of larger-runner jobs were affected. <br /><br />A routine expansion of our compute capacity exposed a bug in how our provisioning system handled capacity records when selecting where to create runner virtual machines. This slowed the creation of new runners, leaving insufficient runner capacity to start affected jobs promptly. <br /><br />We restored normal provisioning by correcting the affected capacity records. We have fixed the underlying capacity-selection bug to prevent this failure from recurring. We have also added alerts for VM-record creation failures associated with this capacity issue.
Resolved
The incident affecting our authentication provider, WorkOS, has been resolved. For full details regarding the resolution, please visit the WorkOS Status Page at https://status.workos.com/incidents/phs2prf38d75
Resolved
Our login provider has recovered and the Vapi dashboard is fully operational again.
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 no longer seeing issues with Cloud SIEM APIs and Cloud SIEM UI and normal operation has been restored at this time.
Resolved
The issue causing elevated errors triggering deployments has been resolved. Existing deployments and traffic are unaffected and no action is required.
Resolved
The incident is now resolved and the system is full operational.
Resolved
The systems are stable and all services are functioning normally again.
Resolved
The issue has been resolved.
Resolved
Between 20:26 and 21:17 UTC on September 17, 2026, GitHub Copilot experienced degradation affecting several GPT models, including GPT-5.6 Luna, GPT-5.6 Terra, GPT-5.6 Sol, GPT-5.3-Codex, and GPT-6 Astra. Users encountered elevated error rates when using these models.<br /><br />The degradation was caused by an issue with an upstream model provider. GitHub engineers detected the issue through automated monitoring and coordinated with the provider. Our automated model-warning system activated in-product warnings for affected models during the incident. Service returned to normal after the provider implemented a mitigation.
Resolved
This incident has been resolved.
Resolved
The incident has been resolved
Resolved
On September 15, 2026 between 15:30 and 20:00 UTC, some Copilot code reviews on pull requests failed to complete. The cause was increased latency in an internal caching service that GitHub Copilot Code Review relies on to coordinate its review jobs. This caused a timeout in lock acquisition, which interrupted the job. We reverted the change to the internal caching service and restored normal operation by 20:00 UTC.<br /><br />We sincerely apologize for the disruption.
Resolved
### Summary On September 14, 2026, between 15:30 and 17:10 UTC, Atlassian customers using Opsgenie, Jira Service Management, and Compass experienced delays in receiving alert notifications and intermittent failures when using Ops features. The issue was triggered by long-running transactions in a core service, which led to thread pool exhaustion and caused subsequent requests to become unresponsive. The long-running transactions were caused by a configuration change released between September 9, 2026 and September 11, 2026 UTC. The team actively monitored the impact of the change on the system until early September 14, 2026 UTC, and observed no anomalies. However, increasing traffic during US working hours on September 14, 2026, caused these unexpectedly long-running transactions. The incident was detected within one minute by our automated monitoring systems, and full service stabilization occurred after isolating and rolling back the change on September 14, 2026 at 17:10 UTC. ### IMPACT The incident primarily affected Ops features across Opsgenie, Jira Service Management, and Compass for customers hosted in the US region. During the incident, the end-to-end flow for alert creation and notification delivery experienced an average delay of 22 minutes. No alerts or notification payloads were dropped during the incident; all queued events were successfully processed and delivered as services recovered. Additionally, related Ops API endpoints and Web UI flows experienced elevated latency and intermittent errors. The disruption began at 15:30 UTC and was resolved by 17:10 UTC (total duration: 1 hour and 40 minutes). Engineering teams were alerted immediately via backup disaster-alerting pipelines and began mitigation without delay. However, the disruption affected internal notification and coordination flows between cross-functional teams (including Customer Support and Incident Communications), which resulted in delays in publishing external Statuspage updates. ### ROOT CAUSE The incident was triggered when a newly released configuration change made redundant downstream service calls on every page load, causing a traffic spike. The configuration change, released between September 9, 2026, and September 11, 2026, was actively monitored for impact until early September 14, 2026. However, a traffic spike during US working hours caused unexpected issues. The downstream service began rate-limiting requests, and an aggressive retry strategy without sufficient backoff held worker threads open, leading to pool exhaustion and timeouts on incoming critical traffic. ### REMEDIAL ACTIONS PLAN & NEXT STEPS The incident was mitigated by disabling the feature flag that triggered the inter-service rate limiting. We understand reliable access to Atlassian products is critical for your teams. We are prioritizing the following actions to prevent recurrence: - **Improve Service-to-Service Resilience** - Review and adjust rate-limiting configurations between internal services. - Optimize retry strategies to prevent long-running transactions and keep the impact isolated to problematic point. - **Improve Architectural Isolation** - Refine the architecture of this core service to have more isolation between different transactions so that degradations in one transaction type do not impact unrelated critical flows. - **Improve Proactive Alerting** - Add early-warning alerts for thread pool saturation and elevated inter-service rate-limit responses before they impact end users. - Implement backup alerting processes for customer support and incident communication paths 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
Our downstream partner's fix for garbled message bodies on 10DLC SMS to T-Mobile destinations has been confirmed. Impact was limited to 10DLC senders assigned to 501(c)(3) tax-exempt campaigns. Both test and live traffic to T-Mobile destinations are delivering intact. An RCA will follow.
Resolved
This incident has been resolved.
Resolved
Customers using Vercel KMS, Connect, Passport, or the Snowflake V0 Integration may have experienced elevated errors. We have resolved the incident and are continuing to monitor.
Resolved
This incident has been resolved.
Resolved
Issue has been resolved and the network in EUR-IS-2 DC is operating normally.
Resolved
This incident has been resolved.
Resolved
Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC20000213](https://community.snowflake.com/s/article/INC20000213)
Resolved