Histórico de interrupções do Percy

1. 24 Gwengolo 2026 da 23:42 UTCresolved

   Status: Corrigir liberado com percy/cli v1.32.11 Desde 20:48 UTC em 24 de setembro, npm install @percy/cli falha com: Npm ERR! código EUNSPOPORTEDPROTOCOLO npm ERR! URL não suportado Tipo "patch:": patch:got@ npm% 3A11.8.2#... Com npm 10 e posterior, a instalação pode falhar sem mensagem de erro. Causa: Um pacote de terceiros do qual o Percy CLI depende, @yarnpkg/core, publicou a versão 4.9.2 com um formato de dependência que o npm não pode instalar. Os serviços de Percy não são afetados; apenas novas instalações de CLI são. Corrigir: Nós lançamos uma versão patch de percy/cli v1.32.11 e agora @latest deve instalar corretamente Solução alternativa (para as versões anteriores do cli de percy se for preso): Adicione isso ao pacote root do seu projeto.json: "sobrescritos": { "@yarnpkg/core": "4.9.1" }

Traduzido automaticamente da atualização oficial do incidente.

1. 10 Gwengolo 2026 da 23:55 UTCinvestigating

   Estamos observando poucas falhas de construção para clientes no terminal Windows. O problema principal foi identificado e a correção é implantada. Estamos monitorando ativamente o tráfego para garantir que o tráfego está totalmente resolvido

2. 10 Gwengolo 2026 da 23:56 UTCinvestigating

   O problema foi identificado e a correção é implantada

3. 10 Gwengolo 2026 da 23:58 UTCmonitoring

   Estamos a monitorizar o tráfego

4. 11 Gwengolo 2026 da 00:54 UTCresolved

   Problema está resolvido e não vemos nenhum impacto do cliente

Traduzido automaticamente da atualização oficial do incidente.

1. 13 Gouere 2026 da 16:20 UTCresolved

   Percy builds were degraded for ~50 mins [7.30 AM PDT to 8.20 AM PDT on 13th July] due to an existing Google Cloud Provider incident We have moved our infrastructure from the impacted GCP node pool and are back to normal processing GCP incident details - https://console.cloud.google.com/servicehealth/incidentDetails/projects%2Fpercy-prod%2Flocations%2Fglobal%2Fevents%2FZBYNZVS?project=percy-prod&tab=full-history

1. 7 Gouere 2026 da 05:56 UTCresolved

   Percy customers were facing intermittent login issues from 7:45 pm PDT to 10:14 PM PDT on 6th July We have identified the issue and login functionality has been fully restored

1. 30 Mezheven 2026 da 09:44 UTCresolved

   A subset of Percy builds experienced slowness from 4:15 PM PDT to 5 PM PDT [29th June] The issue is identified and resolved, services are operating normally

1. 29 Mae 2026 da 15:50 UTCresolved

   In the 20 mins duration some customers might have seen some missing snapshots in the build or failures in creating builds themselves with the 401 status code on the Percy CLI logs. We have fixed the issue and monitoring the stack.

1. 20 Mae 2026 da 04:13 UTCresolved

   Percy experienced login failures for a subset of users between 11:54 PM PDT (18 May) – 12:54 AM PDT (19 May) We have identified the issue and login functionality has been fully restored

1. 12 Mae 2026 da 08:56 UTCresolved

   Between 4:30 AM and 9:30 AM PDT on May 11, 2026, some Percy builds took longer than usual to complete due to increased database contention. Builds were not lost - only delayed. The issue has been mitigated and processing times are back to normal. We're investigating the root cause to prevent recurrence in future.

1. 6 Mae 2026 da 13:53 UTCresolved

   Customers using Percy on Automate experienced build failures between May 5th, 8:00 AM PDT and May 6th, 1:30 AM PDT. The issue has now been resolved, and Percy on Automate builds should be functioning as expected

1. 15 Ebrel 2026 da 18:09 UTCinvestigating

   We are currently investigating this issue. The impacted features only include Percy's AI features - all non AI features are fully active and has no disruption or performance degradation but AI features like NL descriptions, AI ignore, Build Summary, Bug classification will not be available for the builds created/processed currently.

2. 15 Ebrel 2026 da 18:10 UTCinvestigating

   We are continuing to investigate this issue. The impacted features only include Percy's AI features - all non AI features are fully active and has no disruption or performance degradation but AI features like NL descriptions, AI ignore, Build Summary, Bug classification will not be available for the builds created/processed currently. All dashboard functions are fully functional and should not affect the standard percy workflow for the clients.

3. 15 Ebrel 2026 da 18:31 UTCmonitoring

   A fix is implemented and deployed. We are monitoring the situation. All builds created after 11:15 PDT should have all AI features available.

4. 15 Ebrel 2026 da 18:31 UTCresolved

   This incident has been resolved.

1. 25 Meurzh 2026 da 14:08 UTCresolved

   Some users might have faced issue while logging in during ~35 min window. No existing sessions were impacted.

1. 16 Cʼhwevrer 2026 da 15:49 UTCresolved

   - Between February 8, 2026 (10:30 AM – 2:30 PM UTC) and February 9, 2026 (12:00 PM – 1:30 PM UTC) some customers may have noticed incorrect visual diffs on Percy (Safari on iPhone) - The issue occurred due to an incorrect screenshot capture where a “connection not private” error page was rendered instead of the expected page - The impact was limited, affecting a very small percentage of builds across a small number of organisations - Our engineering team has identified and addressed the underlying issue - All Percy services are now operating normally We sincerely apologise for any confusion or inconvenience this may have caused

1. 27 Genver 2026 da 21:05 UTCinvestigating

   We are currently investigating this issue.

2. 27 Genver 2026 da 21:08 UTCidentified

   The issue has subsided, we are actively investigating the root cause

3. 27 Genver 2026 da 22:16 UTCmonitoring

   The root cause were identified as related to https://www.cloudflarestatus.com/incidents/3xb30dhqfkw7 - there is no live impact but we are monitoring the situation. We are keeping this open until cloudflare marks the incidence has resolved.

4. 28 Genver 2026 da 04:49 UTCresolved

   Marking this as resolved as original incidence from Cloudflare is marked as resolved.

1. 9 Genver 2026 da 13:43 UTCresolved

   A subset of users were impacted by infinite reloads and unable to access percy dashboard while attempting to access a build URL on percy dashboard - which internally attempted sign in with browserstack.com. The issue is fixed as of 5:30 AM PST and all dashboard access should be working as expected now.

1. 18 Du 2025 da 11:55 UTCinvestigating

   We are currently investigating this issue.

2. 18 Du 2025 da 11:58 UTCidentified

   The downtime is related to ongoing Cloudflare outage - we are monitoring the status

3. 18 Du 2025 da 12:00 UTCidentified

   We are continuing to work on a fix for this issue.

4. 18 Du 2025 da 12:18 UTCmonitoring

   Cloudflare seem to have recovered, we are monitoring the situation.

5. 18 Du 2025 da 12:48 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 18 Du 2025 da 15:44 UTCmonitoring

   percy.io is currently accessible; however, build processing performance is degraded due to an ongoing Cloudflare incident. As a result, active builds are being queued on our infrastructure. We will resume normal build processing once Cloudflare fully resolves the issue.

7. 18 Du 2025 da 17:47 UTCmonitoring

   We have resumed normal operations. Queued Percy builds are now being processed. Build speeds may be slower than usual while we work through the backlog. We have scaled up our infrastructure to clear the backlog as quickly as possible

8. 18 Du 2025 da 19:16 UTCmonitoring

   We have resumed normal operations and cleared up Percy backlog of builds. Build processing speed is back to normalcy

9. 18 Du 2025 da 19:17 UTCresolved

   We have resumed normal operations and cleared up Percy backlog of builds. Build processing speed is back to normalcy

1. 23 Here 2025 da 09:05 UTCresolved

   We are currently experiencing degradation in visual difference impacting Percy builds due to an underlying Cloudflare issue. Affected builds may show snapshots with blank pages or missing assets, which can result in incorrect Visual differences Window : 10:30 PM PDT 22nd Oct - 1.47 AM PDT 23rd Oct

1. 20 Here 2025 da 17:37 UTCinvestigating

   Percy Review Agent (AI features) are currently experiencing issues due to ongoing AWS outage affecting multiple of our vendors. You would likely see the message `AI diff is unavailable on this comparison` as a message on the dashboard if you attempt to use the AI features. We are actively monitoring the situation and would keep this updated.

2. 20 Here 2025 da 17:37 UTCidentified

   The issue has been identified.

3. 20 Here 2025 da 19:26 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 20 Here 2025 da 20:23 UTCresolved

   This incident has been resolved.

1. 20 Here 2025 da 14:11 UTCresolved

   We are currently observing degraded performance from 6.30 AM - 7.45 AM PDT in Percy, primarily affecting build processing times and dashboard responsiveness. Our investigation indicates that this is due to an ongoing AWS US-East-1 regional outage impacting one of our critical third-party services - LaunchDarkly - which we use for configuration management and feature flag delivery. We are actively monitoring the situation and working with teams to mitigate impact. Builds may take longer to start or complete until the upstream issue is resolved.

1. 20 Here 2025 da 20:49 UTCresolved

   We are currently observing degraded performance from 12:20 PM PDT to 1 PM PDT [20th October] in Percy, primarily affecting build processing times and dashboard responsiveness. Our investigation indicates that this is due to an ongoing AWS US-East-1 regional outage impacting one of our critical third-party services . We are actively monitoring the situation and working with teams to mitigate impact. Builds may take longer to start or complete until the upstream issue is resolved.

1. 15 Here 2025 da 07:41 UTCresolved

   On October 14th from 1.30 PM PDT to 8.30 PM PDT (14th October), Percy web experienced a slowness in processing of builds in majority of organisations. This was due to an underlying infrastructure degradation. Our team deployed a fix to address slow build times. All systems are now operating normally. We sincerely apologise for any disruption this may have caused.