FactoryGLM 5.2 unavailable in our EU deployment
GLM 5.2 is available again in EU.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
GLM 5.2 is available again in EU.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved. From 14:15-14:45 UTC customers experienced increased latency when using our Universal 3.5 Pro Realtime model on the US endpoint. The EU endpoint was not affected. Sessions continued to function during this time without any errors.
Resolved
This incident has been resolved.
Resolved
On 25th Aug 2026, some users may have experienced increased latency in email, mobile and slack notifications. The issue has now been resolved, and the service is operating normally for all customers.
Resolved
On 25th Aug 2026, some users may have experienced increased latency in email, mobile and slack notifications. The issue has now been resolved, and the service is operating normally for all customers.
Resolved
Salesforce connections have recovered and authentication errors have returned toward normal levels. Customers should now be able to use their Salesforce integrations normally. We will continue to monitor recovery.
Resolved
This incident has been resolved.
Resolved
Issue resolved since 12:30. Legacy ingestion pipeline is fully operational.
Resolved
We've continued to monitor this incident and can confirm it has now been resolved. We apologise for any inconvenience caused. If you are still facing issues with the service, please reach out to our support team here https://support.speechmatics.com/hc/en-gb.
Resolved
This incident has been resolved.
Resolved
Error alerting is back to normal.
Resolved
A configuration change on our side caused elevated 503 errors when connecting to paused sandboxes in the US region. We reverted the change, and error rates returned to normal at 12:32 UTC. Sandboxes that were already running were not affected, no sandbox data was lost, and any request that failed will succeed on retry. The EU and APAC regions were not affected. If you are still seeing failures, please contact support@e2b.dev: mailto:support@e2b.dev. We apologize for the disruption.
Resolved
On August 13th, 2026, between approximately 14:06 and 15:47 UTC, the Copilot service experienced a degradation of the Claude Fable 5 model due to an issue with our upstream provider. Users encountered elevated error rates, peaking at 43% and averaging 12%. Users who selected Auto or alternative models were unaffected.<br /><br />The issue was resolved by a mitigation put in place by our provider. GitHub is working with our provider to further improve the resiliency of the service to prevent similar incidents in the future.
Resolved
We've been monitoring the situation and everything is working fine again.
Resolved
This incident has been resolved. Incident Management in US Central is operating as normal. Customers can create, view, and query Incidents, and the Incident public API is fully available. Grafana OnCall was not affected at any point during this incident.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
Between 08:45 AM GMT+1 (UTC +01:00) and 02:30 PM GMT+1 (UTC +01:00), some customers in North America experienced issues with workflow actions. This was caused by a data integrity issue. As of 02:30 PM GMT+1 (UTC +01:00), workflow actions are working as expected and the incident is fully resolved. No new actions will be delayed. Some actions that were delayed during the incident are still being processed and may take some time to complete. We have identified all affected actions and are actively processing them. 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've resolved the incident and the affected service is now operational.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Confluent services in the Azure Southeast Asia region are now healthy and operating normally.
Resolved
This incident has been resolved.
Resolved
We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. <b>Start time :</b> 25/08/2026 06:05 UTC <b>End time :</b> 25/08/2026 07:03 UTC <b>Root Cause :</b> A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.
Resolved
This incident has been resolved and the affected services have been restored.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
After the maintenance on our US3 cluster, the regional endpoint api.us3.bfl.ai is no longer valid, however we are still receiving traffic from certain users. Please ensure to only ever use the global api.bfl.ai or regional api.<eu/us>.bfl.ai endpoints as specified in the docs, not cluster specific ones like api.us3.bfl.ai, to avoid using internal domains that may be removed at any time. https://docs.bfl.ai/api_integration/integration_guidelines#api-endpoints-overview
Resolved
Severity Level: Medium Performance has returned to expected levels based on current telemetry and internal testing after monitoring health over the weekend. ----------------------------------------------------------------------------- Again, in the event you’re unsure as to whether your service is still impacted by this, please open a support ticket and 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.
Resolved
Severity Level: Medium The incident has been resolved. Networking in the us-midwest-2 region is confirmed restored after monitoring. ----------------------------------------------------------------------------- Again, in the event you’re unsure as to whether your service is still impacted by this, please open a support ticket and 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.
Resolved
A fix was deployed, and the issue was fully resolved.
Resolved
On August 24, 2026, between 13:33 UTC and 14:04 UTC, 3.8% of Actions runs experienced start delays over 5 minutes with 1.25% of Actions runs failing outright. <br /> <br />The incident was caused by a disk failure on a node hosting one of many service instances responsible for processing runner assignment events. Typically, pods on unhealthy nodes are removed and replaced automatically without impact. In this case, although the node was severely degraded and unable to perform disk operations, it continued sending healthy signals, preventing the system from immediately moving its work elsewhere. During this period, events assigned to the affected component accumulated until an automatic rebalance redirected processing to healthy components at 13:54 UTC. The queue backlog was cleared at 14:00 UTC, and processing returned to normal by 14:04 UTC. <br /><br />To prevent a recurrence, we are improving detection and automated remediation for unhealthy nodes that aren’t fully offline. We are also strengthening application-level resiliency, so stalled consumers are automatically removed quickly and their work reassigned without waiting for the affected node to recover.
Resolved
We haven’t observed any additional issues with the Object Storage service, and will now consider this incident resolved. If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.
Resolved
On August 24, 2026, some JIRA, JSM, and Confluence users may have experienced performance degradation resulting in increased latency in email, mobile, and Slack notifications. The issue has been resolved for newly created notifications, and service is operating normally. There may be older notifications that are being processed, and we expect them to be completed in next few hours.
Resolved
On August 24, 2026, some JIRA, JSM, and Confluence users may have experienced performance degradation resulting in increased latency in email, mobile, and Slack notifications. The issue has been resolved for newly created notifications, and service is operating normally. There may be older notifications that are being processed, and we expect them to be completed in next few hours.
Resolved
The deployment failures affecting the GitLab Agent for Kubernetes (KAS) have been resolved. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22777
Resolved
We have implemented a fix and the issue has been resolved.
Resolved
This incident has been resolved.
Resolved
Between August 24 at 23:38 UTC and August 25 at 00:08 UTC, a subset of customers using Inngest Connect experienced delayed and failed function runs due to an internal networking issue that disrupted connectivity between Connect services. We reverted the change and restored service. Although Connect buffers worker responses, stalled internal API calls delayed acknowledgements and subsequent replies. In some cases, request forwarding failed even after a buffered response had been received. We fixed the root cause, improved Connect’s failure handling, and enhanced our internal observability so we can detect and respond more quickly to similar problems in the future. Affected customers should review failed Connect runs during the incident window and replay them after confirming that doing so is safe and idempotent.
Resolved
This issue has been resolved.
Resolved
On July 14, 2026, between 15:17 and 15:37 UTC, a rollout to GitHub's internal webhook delivery pipeline caused a subset of webhook delivery records to not be written to our webhook deliveries store after being processed and delivered successfully. Affected deliveries would be missing from the webhook delivery UI and API and won’t be available for redelivery. The root cause was an uncoordinated rollout: a change to how delivery records are handed off between pipeline components was deployed before the upstream components producing those records were updated to match. While the rollout was in progress, affected records were silently skipped rather than persisted, with no automatic retry. The impact ended as soon as the rollout was completed. About 2.4M delivery records were skipped (approximately 4% of the 20-minute impact window, 0.04% of a typical 24-hour period). Importantly, 95% of these skipped deliveries reached customer endpoints successfully, only the record of the delivery is missing. Of the ~5% that failed to reach customer endpoints, only ~1.4% (5,463) map to webhooks that retried their deliveries in the past 28 days. To prevent recurrence, we are improving our automated detection of unsafe schema changes and tightening rollout coordination for changes that span multiple components in the pipeline.
Resolved