Sumo LogicProblem with Metrics Searches in North America 1 (US1)
We are no longer seeing issues with Metrics Searches and normal operation has been restored at this time.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
We are no longer seeing issues with Metrics Searches and normal operation has been restored at this time.
Resolved
We are no longer seeing issues with Logs Collection and normal operation has been restored at this time. [Update] Following further investigation, we determined that the previously communicated resolution time was incorrect. The correct resolution time has been updated to 8:20 AM UTC.
Resolved
We are no longer seeing issues with Metrics Searches and normal operation has been restored at this time.
Resolved
We are no longer seeing issues with CSE Processing Pipeline and normal operation has been restored at this time.
Resolved
We are no longer seeing issues with Logs Collection and Metrics Collection and normal operation has been restored at this time.
Resolved
We are no longer seeing issues with Metrics Collection and normal operation has been restored at this time.
Resolved
Hello, Meta has experienced a service disruption that caused a drop in incoming webhook events and a spike in publishing failures to Facebook, Instagram and Threads. The issue affected Hootsuite users between approximately 9:00pm PST – 9:30pm PST. The issue has since been resolved on Facebook's end and services have returned to normal. We are sorry for any inconvenience that this may have caused to you.
Resolved
The issue with Meta’s posts has been fully resolved, and all systems are now operational. We appreciate your understanding and apologise for any disruption this may have caused.
Resolved
The issue has been resolved, and services are operating normally. No further impact is expected. We’re sorry for any disruption this may have caused and thank you for your patience and understanding.
Resolved
We can confirm that Bluesky services are back up and running and fully accessible via the Hootsuite dashboard. Thanks for your patience during this service disruption.
Resolved
It looks like Bluesky has recovered. We're seeing publishing success rates return to normal, and posts to Bluesky should be going through successfully again. Thank you for your patience while this was being investigated. Please let us know if you continue to experience any issues.
Resolved
VM creation and start operations in the us-southcentral1-a and eu-iceland1-a regions have been functioning normally for several hours. Our Engineering teams have addressed the underlying issue and a permanent fix is being prepared for deployment to prevent recurrence. Existing running workloads and resources remained fully operational throughout the incident. We apologize for any inconvenience this may have caused.
Resolved
Some Dashboard requests were blocked with a misleading error message, the issue is resolved.
Resolved
This incident has been resolved, and log delivery has returned to normal. During the incident, some logs may have been delayed or unavailable. While some upstream sources may retry delivery automatically, we cannot guarantee recovery of all missing logs from the affected period. Thank you for your patience while we worked to resolve this.
Resolved
This incident has been resolved.
Resolved
Between 22:06 and 22:12 UTC, a subset of Voice Agent requests returned elevated 4xx errors following a recent deploy. The deploy has been rolled back and the service is operating normally.
Resolved
This incident has been resolved.
Resolved
As noted, an internal migration related to ongoing performance and tech-debt improvements caused errors affecting customers using cycles. Our team identified and reverted the issue quickly, and service has now fully recovered. We appreciate your patience as we worked to resolve things!
Resolved
This incident has been resolved.
Resolved
This issue is now resolved. We're seeing consistent loading across feeds, posts and search. Media should now be appearing as expected.
Resolved
A number of services across Dropbox experienced slower than expected load times between 17:01:50 and 17:42:50 UTC. This included the ability to add members to teams and share content.
Resolved
This issue has been resolved.
Resolved
On May 11th, 2026, between 14:00 UTC and 14:33 UTC, HTTP-based Git read operations were degraded. On average, the error rate was 2.8% and peaked at 7.5% of requests to the service. This was due to resource exhaustion in a networking gateway between GitHub.com’s frontend service for Git operations and a dependency service that performs authentication and authorization. Following the initial spike, the frontend service became stuck in a degraded state in one of our data centers, increasing time to mitigation. <br /><br />We mitigated the incident by scaling the networking gateway and re-deploying the frontend service. <br /><br />To reduce our time to detection and mitigation in the future, we are adding auto-scaling to the networking gateway, and resolving a bug which caused the frontend service to remain degraded.
Resolved
Publishing functionality has remained stable following the mitigation work completed earlier, and we’re no longer seeing customer impact related to this issue. Some customers experienced issues publishing between 12:50 UTC and 16:18 UTC on May 18, 2026. This incident is now resolved. We appreciate your patience while our team worked to restore normal functionality.
Resolved
Between 10:30 UTC and 13:32 UTC on May 16th, some customers in the US and EU regions may have experienced delayed data in queries, charts, and dashboards as well as delayed, missing, or false alert notifications for impacted data related to a service interruption involving a 3rd party cloud provider. The cloud provider resolved the service interruption and impacted services have returned to normal operations.
Resolved
Some Slack users experienced issues where Huddle AI summaries weren't being generated. Users also appeared to be showing as in a huddle after it had ended. We've fixed both issues. Missing summaries were restored, and the system responsible for showing huddle statuses has been refreshed. If you still notice any users appearing stuck in a huddle, please contact Slack Support. We apologize for the inconvenience and any impact this may have had.
Resolved
This incident has been resolved.
Resolved
Systems are back to normal and sending chat messages should be working for all users again. We will continue to monitor the situation closely to ensure stability. We apologize for the inconvenience this may have caused and thank you for your patience throughout.
Resolved
The impact from the issue seems to be over.
Resolved
An issue has been identified, we’re looking into it There’s currently an issue with some SumUp services. Our engineering team is working to fix it right now. You can find up-to-date information here on our status page "status page": https://status.sumup.com.
Resolved
The corrupted log alert configurations have been fixed, unblocking the scheduler Logs Alerts are evaluating and notifying as normal again
Resolved
Following our investigation, we have determined that this issue is related to an existing incident. We are consolidating updates to centralise communication and will close this status page. For progress and resolution details, please follow: <a href="https://status.snyk.io/incidents/h8w8rtczn430">Service Degradation on US-01 (app.snyk.io)</a>.
Resolved
We've continued to monitor the job queues following the additional provisioning of runners to the resource pool and we observe that the queueing is back to normal. This incident is moved to resolved. More details about the incident here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22145
Resolved
The affected clickhouse node is again operational and is accepting queries
Resolved
From 03:00 UTC to 10:30 UTC, processing times for a subset of jobs increased due to degraded performance in the fetch service affecting jobs submitted with the fetch_data configuration. We identified the root cause of the issue and restored the service to full operational status at 10:30 UTC. Following continued monitoring, we can confirm that the incident has now been fully resolved. We apologise for any inconvenience caused. If you continue to experience issues with the service, please contact our support team here https://support.speechmatics.com.
Resolved
The issue with the service provider is resolved and Cloud projects are back to normal functionality. Sorry for the earlier inconvenience.
Resolved
Between May 12 and May 14, 2026, Akamai Cloud Pulse \(ACLP\) experienced two related service interruptions that temporarily disrupted the ingestion and display of telemetry metrics specifically for Managed Databases. * Window 1: May 12, 23:15 UTC – May 13, 00:11 UTC * Window 2: May 14, 06:47 UTC – 07:33 UTC During these windows, customers were unable to view Managed Database performance metrics within the Akamai Cloud Manager dashboards or retrieve them via external API and Collector streams. Metric-based alerting for Managed Databases was also impaired during both impact windows. We are currently evaluating whether the metrics data missing from these windows can be successfully backfilled. Remark: Metrics for other services, as well as the Log function, were unaffected and operated normally. Furthermore, this incident was strictly limited to the observability reporting layer. The performance, availability, and data integrity of customers’ underlying Managed Databases were never impacted. The disruption was caused by a cascading failure initiated by a brief network routing issue. During the initial event, a localized network disruption caused a small percentage of metrics traffic to fail to reach our processing endpoints. While the network disruption was brief, the accumulated backlog of automatic retries from the telemetry sender's built-in retry mechanism created a sudden, massive spike in traffic against the ingest endpoint. This "retry storm" overloaded the specific downstream message-queuing infrastructure responsible for processing and storing Managed Database telemetry. The processing pipeline was unable to handle the surge, causing the components to fail and leading to the complete loss of DBaaS ingestion \(Window 1\). The degraded performance observed two days later \(Window 2\) was the result of a separate, independent infrastructure incident within our telemetry partner's message-queuing service, entirely unrelated to the initial network disruption. To mitigate the issue, our engineering teams, working alongside our telemetry infrastructure partner, intervened to scale up the processing pipeline's configuration to absorb and clear the accumulated retry backlog. Following these actions, Managed Database metrics ingestion returned to normal levels. This summary reflects our current understanding of the incident based on available information. Our investigation is ongoing, and details may change as we learn more.
Resolved
We have implemented a fix. Ingestion and alerting have returned to normal operation
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved