Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Mar 3, 2026

  1. ZapierUsers are not able to create new app connections using OAuth flow

    Thank you for your patience as we worked to resolve the issue. We're no longer seeing elevated error rates when customers create app connections, and we can confirm that customers can create new app connections without issue. This issue is now considered resolved, but feel free to reach out to our Support team if you have questions: https://zapier.com/app/get-help

    Resolved

  2. Fly.ioElevated GraphQL API errors

    This incident was caused by a failed Redis node that powers our GraphQL API. We were able to recreate the Redis node and restore service. We are still investigating the root cause of the failure. In the mean time, all API endpoints now appear to be stable and errors have dropped to baseline level.

    Resolved

  3. RD StationErro ao enviar templates

    O ERRO NO ENVIO DE MENSAGENS TEMPLATES no 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. LovableGithub issues

    Due to a GitHub outage, projects that were connected to GitHub could not be edited for a while. Service is now back to normal.

    Resolved

  5. Box[Medium] Issue with Enterprise Reporting

    We recently addressed issues affecting the Enterprise Report feature. We would like to take the opportunity to further explain these issues and the steps we have taken to keep them from happening in the future. On January 2, 2026 between 5:30 AM and 2:33 PM PST, some users may have experienced difficulties while working in Box. During this time, users were unable to generate some types of Enterprise Reports, and Enterprise Reports scheduled during this time interval may have failed. We were able to resolve the issue by rolling back a configuration change that caused the issues for the reporting engine. ‌ **Analysis** Box Enterprise Reports relies on a definition of the schemas that describe the underlying database tables that the engine will consume to generate the reports. As we deliver new products, these schemas may occasionally need to be updated, and we have a standard process and pipeline to deploy these schema. As part of a project to upgrade our pipeline infrastructure, the schema deployment pipeline migrated to a new infrastructure. During the migration process, an external library version upgrade introduced a new default behavior that was not compatible with the existing pipeline. As a result, the Enterprise Reports service could not access the underlying tables in some cases, resulting in a temporary degradation of the service. Additionally, the migration process exposed some observability and guardrails gaps in the pipeline that would have prevented this issue from happening and that extended the impact for a longer period of time. ‌ Once identified, the incompatible library was reverted to the previous version and the system went back to normal. ‌ **Corrective Actions** Box has initiated the following corrective actions: * Introduce a schema validation step in the deployment pipeline so that incompatible schemas cannot be deployed * Enforce the environment promotion process as part of the schema deployment pipeline * Uplift the observability of the pipeline to enable more visibility around the different phases of the deployment process ‌ We are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.  Sincerely, The Box Team

    Resolved

  6. GitHubIncident with Actions

    On February 23, 2026, between 15:00 UTC and 17:00 UTC, GitHub Actions experienced degraded performance. During the time, 1.8% of Actions workflow runs experienced delayed starts with an average delay of 15 minutes. The issue was caused by a connection rebalancing event in our internal load balancing layer, which temporarily created uneven traffic distribution across sites and led to request throttling. <br /><br />To prevent recurrence, we are tuning connection rebalancing behavior to spread client reconnections more gradually during load balancer reloads. We are also evaluating improvements to site-level traffic affinity to eliminate the uneven distribution at its source. We have overprovisioned critical paths to prevent any impact if a similar event occurs before those workstreams finish. Finally, we are enhancing our monitoring to detect capacity imbalances proactively.

    Resolved

  7. GitHubIncident with Copilot

    On February 23, 2026, between 14:45 UTC and 16:19 UTC, the Copilot service was degraded for Claude Haiku 4.5 model. On average, 6% of the requests to this model failed due to an issue with an upstream provider. During this period, automated model degradation notifications directed affected users to alternative models. No other models were impacted. The upstream provider identified and resolved the issue on their end. <br />We are working to improve automatic model failover mechanisms to reduce our time to mitigation of issues like this one in the future.

    Resolved

  8. GitHubIncident with Copilot GPT-5.1-Codex

    On February 20, 2026, between 07:30 UTC and 11:21 UTC, the Copilot service experienced a degradation of the GPT 5.1 Codex model. During this time period, users encountered a 4.5% error rate when using this model. No other models were impacted.<br />The issue was resolved by a mitigation put in place by the external model provider. GitHub is working with the external model provider to further improve the resiliency of the service to prevent similar incidents in the future.

    Resolved

  9. Intercom - USDelays in conversation processing

    Between 12:32 UTC and 13:11 UTC there were intermittent delays in conversation processing of up to a few minutes, across all of Intercom and Fin in the USA hosting region. The cause of the problem has been mitigated and we're immediately working on a deeper fix.

    Resolved

  10. BufferMeta API issue impacting some Instagram posts

    While we continue to see the occasional error message associated with the Meta issue, we have largely seen the posting success rate for Instagram images improve. As such, we're marking this issue as resolved. We'll continue to closely monitor this metric moving forward to ensure stability.

    Resolved

  11. MintlifyInvestigating Deployment Delays

    The deployment backlog has been cleared and documentation updates are processing normally again. The delays were caused by a temporary spike in redeployments, which has now been resolved. We’ll continue monitoring to ensure stability. If you’re still experiencing delays, please reach out to support.

    Resolved

  12. ClickHouse CloudResolved – Operational Impact in ClickPipes

    The operational impact affecting ClickPipes in the us-east-1 region has been fully resolved. All systems are operating normally, including ingestion and operational functionality. We will continue to monitor the platform to ensure ongoing stability. Thank you for your patience.

    Resolved

  13. GitHubIncident with Copilot

    On February 26, 2026, between 09:27 UTC and 10:36 UTC, the GitHub Copilot service was degraded and users experienced errors when using Copilot features including Copilot Chat, Copilot Coding Agent and Copilot Code Review. During this time, 5-15% of affected requests to the service returned errors.<br /><br />The incident was resolved by infrastructure rebalancing.<br /><br />We are improving observability to detect capacity imbalances earlier and enhancing our infrastructure to better handle traffic spikes.

    Resolved

  14. SupabaseDatabase issues in us-east-2

    Root cause has been confirmed to be addressed. Handful of projects still require manual intervention however. We will be reaching out to their respective owners.

    Resolved

  15. Intercom - USFin experiencing delays

    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

  16. New RelicData Irregularities

    We resolved this service interruption and impacted services have returned to normal operation. Between 00:11 UTC and 02:45 UTC on March 3rd, 2026, some customers may have experienced delayed data in queries, charts, and dashboards as well as delayed or missing alert notifications for impacted data.

    Resolved

  17. Fly.ioCertificates issues affecting API and proxy

    Between 19:54 and 20:06 UTC, our Vault cluster serving app certificates was unavailable. This caused various API requests to fail, mainly operations on certificates but also app creates and IP assignments. As the failure mode was Vault requests hanging rather than failing immediately, TLS requests through fly-proxy for domains where the certificate was not cached on the local node remained open for a long time while proxy attempted to fetch the certificate; this caused some connections to fail as too many connection slots were taken up by requests waiting on Vault. The root cause of this incident was a partially completed update to the Vault cluster. We will be implementing safeguards in the proxy for this failure mode, as well as improving certificate storage longer-term.

    Resolved

  18. NeonES-1760167

    Between 00:05 UTC and 00:40 UTC March 03, 2026, some databases in us-east-2 experienced increased cold-start times. This issue is now closed. We apologize for any inconvenience.

    Resolved

  19. SanityAPICDN Elevated Latency

    Resolved: Between 16:00–23:10 UTC, a subset of customers experienced elevated API CDN latency. The issue has been mitigated and performance is back to normal.

    Resolved

  20. UdemyInvestigating site performance issues

    We’ve resolved the issue that prevented course landing pages from loading for Market Place and Personal Plan Grow with Google subscribers. Course landing pages are now loading normally again. We understand this disruption may have impacted your learning plans, and we’re sorry for the inconvenience this caused. This incident did not impact Udemy Business users.

    Resolved

Older incidents