Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Jan 12, 2026

  1. GitHubIncident with Copilot

    On January 8th, 2025, between approximately 00:00 and 1:30 UTC, the Copilot service experienced a degradation of the Grok Code Fast 1 model due to an issue with our upstream provider. Users encountered elevated error rates when using Grok Code Fast 1. Approximately 4.5% of requests failed across all users during this time. No other models were impacted.<br /><br />The issue was resolved by a mitigation put in place by our provider.

    Resolved

  2. GitHubDisruption with some GitHub services

    From January 5, 2026, 00:00 UTC to January 10, 2026, 02:30 UTC, customers using the AI Controls public preview feature experienced delays in viewing Copilot agent session data. Newly created sessions took progressively longer to appear, initially hours, then eventually exceeding 24 hours. Since the page displays only the most recent 24 hours of activity, once processing delays exceeded this threshold, no recent data was visible. Session data remained available in audit logs throughout the incident.<br /><br />Inefficient database queries in the data processing pipeline caused significant processing latency, creating a multi-day backlog. As the backlog grew, the delay between when sessions occurred and when they appeared on the page increased, eventually exceeding the 24-hour display window.<br /><br />The issue was resolved on January 10, 2026, 02:30 UTC, after query optimizations and a database index were deployed. We are implementing enhanced monitoring and automated testing to detect inefficient queries before deployment to prevent recurrence.

    Resolved

  3. RD StationFalha na aprovação de Templates no RD Station Conversas

    A Falha na aprovação de Templates do RD Station Conversas foi resolvida com sucesso. Caso você note que sua conta ainda contém alguma inconsistência, por favor, entre em contato com nosso Time de Suporte através da nossa Central de Ajuda "através da nossa Central de Ajuda": http://ajuda.rdstation.com/..

    Resolved

  4. New RelicData and UI Irregularities - US and EU regions

    Our teams have resolved two concurrent service interruptions affecting data ingestion and query services. On January 12th, 2026, a subset of customers in the US and EU regions may have experienced latency or timeouts when querying data in New Relic. Teams implemented a fix, restoring affected query performance at 17:29 UTC. Separately, a subset of customers in the US and EU regions may have experienced errors when sending data to New Relic. This interruption could have resulted in potential data drops for data sent during this timeframe, depending on client-side retry settings, and may have generated false alert notifications regarding host reporting status. This interruption appears related to a disruption with a New Relic third-party edge service provider. To remediate, our teams have shifted traffic to an alternate cloud provider and have seen recovery of impacted services.

    Resolved

  5. ZapierSome app images are not rendering correctly in Zapier's App Directory

    Our team has implemented a fix, and all app images are now displaying correctly in Zapier's App Directory. If you're still seeing some broken images, please refresh your browser's cache and cookies, then load the page again. Many thanks for your patience! The support team is always happy to help if you have any questions: zapier.com/get-help "zapier.com/get-help": http://zapier.com/get-help

    Resolved

  6. KinstaMyKinsta APM service disruption

    After further monitoring, our Engineers have confirmed this incident is fully resolved. Thank you for your patience throughout this.

    Resolved

Jan 11, 2026

  1. monday.comInvestigating connectivity issues across accounts and devices

    **What Happened:** On January 5th \(09:19 AM EST\), customers on our US server began to experience around 8 minutes of difficulty loading boards, followed by 23 minutes of system downtime due to an application-level issue, totaling a 31-minute incident. There was no data loss or security risk to our customers during this incident, and EMEA and APAC servers were not impacted by the platform access issue. ‌ **What caused it:** A recent code change in our left pane feature created an overload on our system, which as a result, affected data retrieval. ‌ **How we responded:** Our monitoring system promptly identified the issue, triggering an immediate response from our engineering team. While working to resolve the issue, the loading issue turned into a full platform downtime. Our team resolved the issue by scaling our data layer servers and restoring normal service by 09:50 AM EST. ‌ **What we're doing to prevent recurrence:** We will implement a new performance process in our pre-production environment that enables us to proactively identify and prevent similar issues, thereby minimizing their impact on our customers. To enhance system resilience, we are implementing additional layers of automated testing and protection, including strengthening our error detection and recovery processes. ‌ We know that any access disruption to your [monday.com](http://monday.com) workflows impacts your productivity, and we're sorry for any frustration or inconvenience caused.  We remain committed to continuously improving the platform's reliability, resiliency, and protecting your work platform’s uptime goals. ‌ Your engineering team at [monday.com](http://monday.com)

    Resolved

Jan 10, 2026

  1. Intercom - EUIntercom is down in the EU

    Intercom was down in the EU from 08.23 UTC until 08:36 UTC. All services are back to normal operations. 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

  2. GitHubIncident with Actions

    On January 6, 2026 between 12:55 UTC and 17:04 UTC, the ability to download Actions artifacts from GitHub’s web interface was degraded. During this time, all attempts to download artifacts from the web interface failed. Artifact downloads via the REST API and GitHub CLI were unaffected.<br /><br />This was due to a client-side change that was deployed to optimize performance when navigating between pages in a repository. We mitigated the incident by reverting the change. <br /><br />We are working to improve testing of related changes and to add monitoring coverage for artifact downloads through the web interface to reduce our time to detection and prevent similar incidents from occurring in the future.

    Resolved

Jan 9, 2026

  1. PandaDocSupport messenger outage

    We're all set! PandaDoc is working properly and the incident has been fully resolved. If you continue to experience issues with this, please contact our Support team (https://support.pandadoc.com/en/articles/9715061-how-to-contact-pandadoc-support).

    Resolved

Older incidents