Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Aug 30, 2026

  1. StripeElevated Swish errors

    From 12:46–14:20 UTC, we saw elevated errors on Swish payments due to external impact on the Swish payment processor. This issue is now resolved and has returned to normal.

    Resolved

  2. SnykPartial Broker Service Degradation

    A fix has been applied, and error rates connecting to our broker servers have dropped back to normal levels. Connections via brokered integrations are functioning as expected. We are continuing to monitor performance to ensure full stability.

    Resolved

Aug 29, 2026

  1. StripeElevated Swish errors

    From 18:53 UTC to 19:18 UTC on 2026-08-29, we saw elevated errors on Swish payments due to a service degradation on the Swish side. This is now resolved. We will continue to monitor for any further issues and will provide updates if needed.

    Resolved

Aug 28, 2026

  1. OVHcloud - Public Cloud[GRA1][Compute - Instance] - Instance incident notification

    We would like to inform you that an incident occurred in the GRA1 region. This incident has now been resolved. Please find the details of this incident below : <b>Start time :</b> 28/08/2026 23:03 UTC <b>End time :</b> 28/08/2026 23:11 UTC <b>Impacted Service(s) :</b> Some instances in the GRA1 region were unreachable. <b>Customers Impact :</b> Some customers were temporarily unable to access instances located on the specified region. <b>Root Cause :</b> A service disruption occurred due to an unexpected underlying infrastructure malfunction. We thank you for your understanding and patience throughout this incident.

    Resolved

  2. GitHubIncident with Actions and Pull Requests

    On August 26, 2026, from 21:55 UTC to 23:58 UTC, 2.6% of workflow runs triggered by pull request events were delayed, with the impact rising as high as 25% at its peak. Some users also experienced delays in pull request merge-commit generation, mergeability information, and merge-button availability. Actions and Pull Requests fully recovered by 23:58 UTC; the incident was resolved at 00:26 UTC after normal operation was confirmed. <br /><br />Background jobs that process pull request updates and generate merge commits were impacted by timeouts reaching a single partition of git data. This resulted in a backlog in pull request merge-commit processing, delaying pull request-triggered GitHub Actions workflows and some mergeability information. <br /><br />We reduced workload, shifted traffic away from affected infrastructure, and restored the affected service component to a healthy state. Together, these actions helped drain the backlog and restore normal operations. <br /><br />We are working to improve resource saturation detection and to eliminate customer impact in this scenario by isolating impact, placing better bounds on retries, and strengthening backpressure to make our systems more resilient under load.

    Resolved

  3. AkamaiReporting data availability issues in 'Traffic by Hostname' report

    We can confirm that the issue was mitigated at 23:50 UTC on August 24, 2026 and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a700001PVMc9CAH or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.

    Resolved

  4. LinodeService Issue - US-SEA (Seattle, WA)

    Between approximately 09:51 and 12:18 UTC on August 28, 2028, customers using the Seattle data center \(US-SEA\) were unable to provision new nodes or complete host jobs, whereas customers outside Seattle were unaffected.  The investigation revealed that this was due to a Linux kernel issue that was triggered on a network router due to increased network traffic at this site while a specific BIOS setting was enabled.  This caused system instability and affected job processing in the US-SEA region. To mitigate the impact, the Akamai team disabled a problematic setting and rebooted the affected system, restoring service and moving the situation to a monitoring state by 12:18 UTC on August 28, 2026. As preventive actions, Akamai will audit hardware configurations to ensure the problematic feature is explicitly disabled, and implement enhanced monitoring to detect similar issues in the future.  This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing and any information herein is subject to change.

    Resolved

  5. CloudwaysAWS Middle East (UAE) Outage

    Following the ongoing AWS outage in the ME-Central-1 (UAE) region, we have disabled server provisioning in this region. If you currently have active workloads in ME-Central-1, please migrate them to an alternative region of your choice. Our support team is available if you need guidance or assistance during the migration process. We apologize for the inconvenience and appreciate your cooperation as we take steps to ensure your service reliability.

    Resolved

  6. CloudwaysAWS Middle East (Bahrain) Outage

    Following the ongoing AWS outage in the ME-SOUTH-1 (Bahrain) region, we have disabled server provisioning in this region. If you currently have active workloads in ME-SOUTH-1, please migrate them to an alternative region of your choice. Our support team is available if you need guidance or assistance during the migration process. We apologize for the inconvenience and appreciate your cooperation as we take steps to ensure your service reliability.

    Resolved

  7. KinstaMykinsta file manager issue with uploading larger files

    We have determined that this is caused by an update to our network firewall systems for security. We will continue to explore other options for allowing larger uploads through MyKinsta, but at this time, files larger than 500MB should now only be uploaded via SFTP. If you have any other questions, please contact our support team via chat from your MyKinsta dashboard, or by emailing us at support@kinsta.com.

    Resolved

  8. MongoDB CloudMongoDB Atlas Log Integration service degraded

    Between approximately 14:29 UTC and 15:42 UTC on August 28, 2026, log delivery via Atlas Log Integration was impacted due to an internal service issue. Some users may have encountered delayed or missing logs during this window. Log delivery has since returned to normal. We are implementing measures to reduce the risk of this happening again.

    Resolved

  9. SupabaseProjects failing to load Supautils in multiple regions

    PostgreSQL 15 projects were failing to load /usr/lib/postgresql/15/lib/supautils.so because GLIBC_2.33 is unavailable on affected hosts. This disrupted database access in multiple regions. Rollback is now complete and we are seeing access restored to projects in the affected regions.

    Resolved

  10. BufferDegraded Performance

    Thank you so much for bearing with us today whilst we had some issues earlier. We are pleased to share that things should be working normally again now, with the Buffer dashboard loading successfully, and logins working as desired again, too. We're so sorry for today's disruption and we'll be here to help if you notice any further wonky behaviour.

    Resolved

  11. ZapierTables, Chatbots, and Forms not loading for some customers

    The issue affecting Tables, Chatbots, and Forms has been resolved as of approximately 15:00 UTC. Some users were unable to load existing Tables, Chatbots, or Forms and were redirected to a creation page instead. All affected surfaces — Tables, Forms, Chatbots, and folder/subfolder creation — have been verified and are working normally. No data loss occurred, and Zap runs were not affected. If you're still experiencing issues, contact Support: https://zapier.com/app/get-help Thank you for your patience.

    Resolved

  12. TrueLayerService Disruption Causing Failed Requests

    Between 14:09 UTC and 14:13 UTC, you may have experienced failed requests across all of TrueLayer API's. The issue was caused by a brief disruption at our edge gateway. Service is now fully operational and available. Impact start time: 28/08/2026, 14:09 UTC Impact end time: 28/08/2026, 14:13 UTC Client actions: Retry failed requests

    Resolved

Older incidents