Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Jul 7, 2026

  1. CrowdinFalse Downtime Report for Crowdin Translate [Resolved]

    Resolution We've resolved a status page reporting issue and removed an incident record that incorrectly showed 7 hours and 53 minutes of downtime for Crowdin Translate. The service was fully operational the entire time — there was no actual downtime or user impact. What Happened? The false "Major Outage" status was triggered by an automation notification glitch. Two conflicting updates (DOWN and UP) arrived at the exact same time. Due to a race condition, the system processed the DOWN alert but ignored the simultaneous UP notification, leaving the status page stuck in an incorrect state.

    Resolved

  2. SentryIncoherent number of processed logs

    Between July 6th 20:25 UTC and July 7th 12:25 UTC, a wrong configuration change was deployed causing over-sampling of logs, spans and metrics. The configuration change is now reverted and the issue is fixed.

    Resolved

  3. LovableCustom Domain Configurations Failing

    Custom domains added recently were failing to fully activate because their security certificates could not be issued. This has now been resolved, and affected domains should complete setup normally; if a domain still is not active, removing and re-adding it will retry the process.

    Resolved

  4. LiveKitElevated connection failures in Japan

    Users connecting to our Japan region experienced elevated connection failures between approximately 18:18 and 18:43 UTC, caused by a network disruption affecting connectivity between our Tokyo data centres. Connectivity was restored by 18:43 UTC. Update (July 7): After the initial recovery, one replacement media server in Tokyo came online serving only IPv6. From approximately 22:00 UTC on July 6, connections routed to this server failed for clients on networks without IPv6 connectivity. The server was removed from service at 10:30 UTC on July 7, and connection success rates in Japan have returned to normal.

    Resolved

  5. TrueLayerPLN Payments Degraded Performance

    We experienced a degraded performance on PLN payouts where clients may have seen failures of payments. The issue has been resolved and payments are settling as normal. Impact start time: 07/07/2026, 02:00 UTC Impact end time: 07/07/2026, 02:40 UTC Client actions: None

    Resolved

Jul 6, 2026

  1. SentrySpans, logs and metrics ingestion stopped

    US ingestion is back to normal. EU ingestion is still delayed, but we are now recovering. We have created a new Statuspage incident for tracking EU, follow that for further updates: https://status.sentry.io/incidents/7tfjf5k3m0g3

    Resolved

  2. PlanetScaleDevelopment branches with MySQL Vectors not serving

    All impacted branches are recovered. PlanetScale upgraded development Vitess branches with Vectors enabled from MySQL 8.0.x to 8.4.x. PlanetScale runs an internal fork containing support for PlanetScale's MySQL Vectors indexes. A bug in the 8.4.x version of our Vectors builds resulted in the upgrade immediately failing on startup. Because Vitess development branches only have one instance - the primary - impacted development branches did not have a primary during the impact window. The incident was resolved by reverting impacted branches to their previous MySQL version. PlanetScale will fix the bug in the MySQL Vectors 8.4.x build before re-attempting the upgrade at a later date.

    Resolved

  3. RD StationIndisponibilidade RD Station CRM

    A indisponibilidade na navegação e acesso ao RD Station CRM 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. BufferBuffer MCP returning a 404 Error

    Our team was able to resolve the underlying issue. The MCP is once again working as expected! We appreciate your (and your Agent's) patience as we resolved this.

    Resolved

  5. GitHubDelays in copilot budget limits resets for some users

    On July 1, 2026, between approximately 00:00 UTC and 13:04 UTC, some GitHub Copilot customers whose budget was exhausted before the monthly reset remained incorrectly blocked from paid Copilot usage after the new billing month began, even though their budgets had reset. Some budget changes also took longer than usual to apply. Only customers with an exhausted budget were affected, which limited the impact.<br /><br />This was caused by a caching issue at the monthly reset: for some users, a pre-reset "budget exhausted" status was re-saved and served even though their budget had reset, so they stayed blocked. We had built a safeguard ahead of the reset to prevent this, but it did not take effect because an internal configuration service did not load its settings correctly. We resolved the incident by deploying a change that discards the outdated status and recomputes access from current budget data independently of that configuration, and by working through the backlog of budget updates.<br /><br />To prevent recurrence, we are ensuring pre-reset status cannot survive the monthly budget reset, adding alerting for this failure mode, and increasing capacity to absorb the monthly surge of budget updates.

    Resolved

  6. GitHubDisruption with some GitHub services - Signup Flow

    Between 15:19 UTC and 15:49 UTC on June 30, 2026, users were unable to complete the signup flow for GitHub.com/signup. Approximately 62% of new user signups failed for about 30 minutes during this window.<br /><br />This was caused by a configuration change to the signup flow that unintentionally blocked users from completing signup.<br /><br />We mitigated the incident by reverting the change, which restored successful signups. To reduce the likelihood and impact of similar issues, we are adopting staged, incremental rollouts for changes on the signup path, improving our ability to test these changes before they reach production, and adding checks to verify signup health before and during any change that affects this flow.

    Resolved

  7. BigCommerceIssue with B2B Edition

    Commerce engineers have resolved the issue impacting B2B Edition from 4:25 pm UTC to 5:05 pm UTC and all services are fully operational.

    Resolved

  8. Help ScoutAutomatic Workflows not running

    Between ~05:06–12:46 UTC some conversations were not processed by automatic workflows, as a result some conversations may not have expected automated actions performed on them. The issue is now resolved and automatic workflows are working normally. Affected conversations will require manual action(s) to be taken. If you'd like extra support, please email our team: help@helpscout.com

    Resolved

Older incidents