Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Feb 28, 2026

  1. KinstaIssue with Analytics data

    The MyKinsta analytics system has continued to operate normally. This issue is now resolved. If you are still experiencing issues while accessing analytics data in MyKinsta please contact our support team. We do apologize for any inconvenience caused by this disruption.

    Resolved

  2. MailerLiteInvestigating Issues

    This incident is now fully resolved, and all systems have returned to normal operations. We sincerely apologize for the inconvenience this caused and deeply appreciate your patience. We are currently conducting a comprehensive post-mortem review to understand the root cause and prevent future occurrences. We are working closely with our partners and will share a detailed incident report with you once the review is complete.

    Resolved

Feb 27, 2026

  1. WriterTemplateHighP95Latency

    The issue affecting API endpoints has been resolved. All systems are now operating normally. We apologize for any inconvenience this may have caused.

    Resolved

  2. GitHubCode view fails to load when content contains some non-ASCII characters

    Starting February 26, 2026 at 22:10 UTC through February 27, 05:50 UTC, the repository browsing UI was degraded and users were unable to load pages for files and directories with non-ASCII characters (including Japanese, Chinese, and other non-Latin scripts). On average, the error rate was 0.014% and peaked at 0.06% of requests to the service. Affected users saw 404 errors when navigating to repository directories and files with non-ASCII names. This was due to a code change that altered how file and directory names were processed, which caused incorrectly formatted data to be stored in an application cache.<br /><br />We mitigated the incident by deploying a fix that invalidated the affected cache entries and progressively rolling it out across all production environments.<br /><br />We are working to improve our pre-production testing to cover non-ASCII character handling, establish better cache invalidation mechanisms, and enhance our monitoring to detect this type of failure mode earlier, to reduce our time to detection and mitigation of issues like this one in the future.

    Resolved

  3. Fly.ioSlow API requests

    This incident has been resolved. All platform and API operations are working normally.

    Resolved

  4. ZapierZaps using notion triggers stopped triggering

    This issue is now resolved. Zaps that using Notion as a trigger should now be receiving all webhooks and triggering properly. If you are still running into into issues, please reach out to Zapier Support: https://zapier.com/get-help

    Resolved

  5. BufferBuffer Service Disruption

    The issue impacting logins, scheduling, and editing updates in Buffer has been fully resolved. Our engineers identified the root cause and implemented a fix. After a period of monitoring, we’ve confirmed that performance is stable and all affected features are functioning normally. Thank you for your patience while we worked through this. If you continue to experience any issues, please reach out to our support team.

    Resolved

  6. WriterBaseten embedding models down

    We have confirmation that service has been restored and have verified on our side.  From ~9:40–10:00 AM PT we may have seen partial failures on document retrieval, RAG indexing, and MCP.

    Resolved

  7. SparkPostMicrosoft Mail Delivery Delays and Temporary Rejections

    Microsoft has confirmed that they made additional changes the night of Thursday, Feb 26th that should have remediated most IP rate limiting and rejection issues. If you are still seeing impacts, please reach out via your normal support channels and our team can investigate and escalate with Microsoft.

    Resolved

  8. OnaElevated conversation errors on Ona Cloud

    The upstream issue with Anthropic has been resolved, and we have confirmed that conversation errors on Ona Cloud have subsided. All systems are fully operational again. Thank you for your patience while this was being addressed.

    Resolved

  9. PaddleIntermittent issues with Retain

    The incident affecting Retain has been resolved, and service has recovered. We will continue monitoring to ensure everything remains stable. If you have any questions, please contact our Customer Support team at sellers@paddle.com "sellers@paddle.com": mailto:sellers@paddle.com.

    Resolved

  10. Liquid WebNetworking Instability

    The network instability affecting a small subset of IP addresses in DC2 and DC3 has been fully resolved. Our network engineers identified the impacted range and implemented the necessary mitigation measures to restore normal connectivity and performance.

    Resolved

  11. ElevenLabsConversation latency

    Gemini model performance has fully recovered; Our cloud provider has informed us that the upstream issue is fully resolved, and we have carefully tracked our metrics to confirm this.

    Resolved

  12. Intercom - USFin Performance Degradation

    This issue should now be resolved and all services are restored to normal functionality. Please don’t hesitate to reach out to team@intercom.io: mailto:team@intercom.io if you have any further questions or if you’re still seeing any unexpected behaviour

    Resolved

  13. TrueLayerGBP Payments Degraded Performance

    We experienced a service degradation with GBP payments due to an issue with our banking partner. Clients may have seen delayed settlement of payins and payouts. Normal service is resumed. Impact start time: 27/02/2026, 09:40 GMT Impact end time: 27/02/2026, 13:08 GMT Client actions: None

    Resolved

  14. TrueLayerPayments Product Degraded Performance

    We experienced a small window of degraded performance affecting Payments. During this time, you may have received 504 responses. All normal services have been restored. Impact start time: 27/02/2026, 13:57 GMT Impact end time: 27/02/2026, 14:01 GMT Client actions: None

    Resolved

  15. BufferIssue Publishing Instagram Reels

    The issue with Instagram Reels and Stories with video has been fully resolved. We appreciate your understanding and apologise for any disruption this may have caused.

    Resolved

  16. GitHubExtended job start delays for larger hosted runners

    On February 20, 2026, between 17:45 UTC and 20:41 UTC, 4.2% of workflows running on GitHub Larger Hosted Runners were delayed by an average of 18 minutes. Standard, Mac, and Self-Hosted Runners were not impacted. <br /><br />The delays were caused by communication failures between backend services for one deployment of larger runners. Those failures prevented expected automated scaling and provisioning of larger hosted runner capacity within that deployment. This was mitigated when the affected infrastructure was recycled, larger runner pools in the affected deployment successfully scaled up, and queued jobs processed. <br /><br />We are working to improve the time to detect and diagnose this class of failures and improve the performance of recovery mechanisms for this degraded network state. In addition, we have architectural changes underway that will enable other deployments to pick up work in similar situations, so there is no customer impact due to deployment-specific infrastructure issues like this.

    Resolved

Feb 26, 2026

  1. PyPIPython Infrastructure Outage

    The incident has been resolved. ## Incident Report: Cluster-wide service outage **Duration**: ~36 minutes \(20:04–20:40 UTC\) **Impact**: Some PSF-hosted services were unavailable, including [python.org](http://python.org), [us.pycon.org](http://us.pycon.org), PyPI stats, [bugs.python.org](http://bugs.python.org), and related services. What was unaffected was our other cluster that manages [PyPI.org](http://PyPI.org) among other services related to PyPI. **Root Cause**: During local development of kubernetes workloads locally there was an incorrect context switch to one of our production clusters. The scale-down commands ran against the production cluster instead of the local environment, iterating through all deployments and setting them to zero replicas. which created cascading failures. **Recovery**: Services were restored with the help of Ee Durbin by bringing up infrastructure in dependency order, original replica counts were recovered from Kubernetes event history. Action items: * Separate kubeconfig files for production vs local, rather than relying on context switching * Research adding admission control or policies to prevent bulk scale-to-zero operations * Document the infrastructure dependency chain and recovery runbook for future incidents Jacob Coffee, PSF Infrastructure Team

    Resolved

  2. GitHubCode search experiencing degraded performance

    Between 2026-02-23 19:10 and 2026-02-24 00:46 UTC, all lexical code search queries in GitHub.com and the code search API were significantly slowed, and during this incident, between 5 and 10% of search queries timed out. This was caused by a single customer who had created a network of hundreds of orchestrated accounts which searched with a uniquely expensive search query. This search query concentrated load on a single hot shard within the search index, slowing down all queries. After we identified the source of the load and stopped the traffic, latency returned to normal.<br /><br />To avoid this situation occurring again in the future, we are making a number of improvements to our systems, including: improved rate limiting that accounts for highly skewed load on hot shards, improved system resilience for when a small number of shards time out, improved tooling to recognize abusive actors, and capabilities that will allow us to shed load on a single shard in emergencies.

    Resolved

  3. ZapierSome app integrations experiencing delayed triggers sporadically

    Our team has restored full functionality and verified system performance is stable. Since there's full functionality, the incident is considered closed. Affected customers have been contacted but no further action is necessary. If you have any other questions, please feel free to reach out to our support team at https://zapier.com/app/get-help

    Resolved

Older incidents