Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

May 4, 2026

  1. BuildKiteIncreased latency and error rates

    An increase in requests has lead to the API service being temporarily saturated. We have updated rate limits to ensure this doesn't re-occur and will add further resources if necessary

    Resolved

May 3, 2026

  1. BufferIssue Publishing Posts to Instagram and Threads

    We're pleased to confirm that this incident has been fully resolved. Posting to Instagram and Threads is operating normally, and all affected services have been restored. If you continue to experience problems after retrying, please reach out to our support team. Thank you again for your patience while we worked through this.

    Resolved

  2. NetlifyDelayed Credit Usage Updates

    Some customers may have seen delayed credit usage updates and related notifications between 00:14–01:37 UTC on May 3. The issue has been resolved, and usage information is now up to date.

    Resolved

  3. TrueLayerPLN Payments Degraded Performance

    We experienced an issue with PLN payouts where payment settlement was delayed due to an issue with our PLN banking partner. The issue has been resolved, and payouts are settling as normal. Impact start time: 03/05/2026, 03:48 UTC Impact end time: 03/05/2026, 04:10 UTC Client actions: None

    Resolved

May 2, 2026

May 1, 2026

  1. HashiCorpTerraform 1.15.0 Compatibility Issues

    Our Engineering team has identified a number of critical problems with Terraform 1.15.0 and certain configurations. Terraform 1.15.1 was released today with fixes for known critical issues. If you are experiencing issues with 1.15.0, we recommend you either upgrade to 1.15.1, or downgrade to 1.14.9. If you continue to experience problems with 1.15.1 or 1.14.9, please contact customer support.

    Resolved

  2. HoneycombGap in Activity Log data in the EU region.

    The database failover that caused query issues earlier in the EU (https://status.honeycomb.io/incidents/n855d8kzp32y) has also had knock-on effects on our Activity Log beta feature. Due to recovery issues on the data replication flow used for this mechanism, activity log events will be missing from 12:45 UTC until 19:45 UTC, representing a 5 hour gap in events. We have identified configuration parameters that will be adjusted to reduce the likelihood of such losses in the future.

    Resolved

  3. VantaMissing GitHub data

    The underlying GitHub incidents have been resolved, and remediation steps on Vanta's end are complete.

    Resolved

  4. GitHubDisruption with some GitHub services

    On April 28, 2026, from approximately 12:41 UTC to 17:09 UTC, GitHub Actions jobs using Standard Ubuntu 22 and Ubuntu 24 hosted runners experienced run start delays. Approximately 8% of hosted runner jobs using Ubuntu 22 and Ubuntu 24 experienced delays greater than 5 minutes or failures. Larger and self-hosted runners were not impacted.<br /><br />This was caused by a performance regression introduced in the VM reimage process. That reimage delay lowered the overall capacity of runners available to pick up new jobs. This was mitigated with a rollback to a known good image version.<br /><br />We are addressing the core issue with reimage performance and improving the granularity of reimage telemetry across our services and our compute provider to more quickly diagnose similar issues in the future. Finally, we are evaluating other rollout changes to automatically detect similar regressions.

    Resolved

  5. BunnyConfiguration change delays

    The configuration delay has now been resolved. At around 00:15, we observed a large scale domain sync that caused configuration delays. This was resolved at 06:00 UTC, before the backlog of configuration changes were cleared by 09:30 UTC. Our Engineering team have identified the core issue and will take action to prevent future recurrence of the problem.

    Resolved

  6. ZapierINC-908: Firecrawl outage

    No additional customer reports have been received during the monitoring period. The incident is ready to be closed.

    Resolved

  7. GitHubInvestigating errors on GitHub

    On April 23, 2026 between 14:30 UTC and 15:18 UTC multiple services were degraded on github.com. During this time approximately 1.5% of all web requests resulted in a 5xx status and unicorn pages for github.com users. We also saw elevated error rates across Actions workflow runs, Copilot, Codespaces and Packages, leading to degraded experiences during this timeframe. Codespaces impact peaked at 45% failures for create requests and 65% failures for resume requests. Packages impact was mainly Maven related with 50% failure rates in downloads and 70% failure rates in uploads. Actions experienced a peak of 8% of failed jobs and up to 85% of jobs impacted by run start delays of more than 5 minutes.<br /><br />This was due to a configuration change to an internal billing service that led to a cache being overwhelmed and causing requests to time out. These timeouts cascaded across multiple services and eventually caused requests to queue up and exhaust web request workers.<br /><br />This configuration change was reverted at 14:42 UTC and following this, all services began to see recovery immediately.<br /><br />To prevent this situation in the future, we are taking steps to ensure that failures and timeouts in the billing service don’t cascade to other services causing impact. This includes implementing more aggressive timeouts on callers of these billing services, adding circuit breaker configurations for cache timeouts and using more resilient cache options. We have also decreased max request timeouts within the billing service that caused impact and added more capacity to our cache to prevent traffic spikes from having the same impact.

    Resolved

Apr 30, 2026

Older incidents