Percy 장애 기록

1. 2026년 9월 24일 오후 11:42 UTCresolved

   상태: percy/cli v1.32.11로 풀어 놓인 고침 이후 20:48 UTC 에 9월 24, npm install @percy/cli 실패 와: ₢ 킹 코드 EUNSUPPORTEDPROTOCOL npm ERR! 지원되지 않은 URL 유형 "패치:": 패치:got@npm%3A11.8.2#... npm 10 이상으로 설치는 오류 메시지가 없습니다. 원인 : Percy CLI가 켜져있는 제 3 자 패키지, @yarnpkg / 코어, npm이 설치 할 수있는 의존성 형식으로 4.9.2을 게시했습니다. Percy의 서비스는 영향을받지 않습니다. 새로운 CLI 설치 만 있습니다. 수정: 우리는 percy/cli v1.32.11의 패치 버전을 발표하고 지금 @latest는 제대로 설치해야 합니다 Workaround (꼬인 경우 이전 percy cli 버전) : 프로젝트의 루트 package.json에 이것을 추가하십시오: 이름 * "@yarnpkg/core": "4.9.1" 기타

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 9월 10일 오후 11:55 UTCinvestigating

   우리는 Windows 맨끝에 고객을 위한 몇몇 건축 실패를 관찰하고 있습니다. 핵심 문제는 식별 및 수정이 배포되었습니다. 교통을 보장하기 위해 교통을 적극적으로 모니터링하고 있습니다

2. 2026년 9월 10일 오후 11:56 UTCinvestigating

   문제가 식별되고 수정이 배포되었습니다

3. 2026년 9월 10일 오후 11:58 UTCmonitoring

   우리는 교통을 감시하고 있습니다

4. 2026년 9월 11일 오전 12:54 UTCresolved

   문제점은 해결되고 우리는 어떤 고객 충격든지 볼 수 없습니다

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 13일 오후 4: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. 2026년 7월 7일 오전 5: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. 2026년 6월 30일 오전 9: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. 2026년 5월 29일 오후 3: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. 2026년 5월 20일 오전 4: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. 2026년 5월 12일 오전 8: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. 2026년 5월 6일 오후 1: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. 2026년 4월 15일 오후 6: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. 2026년 4월 15일 오후 6: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. 2026년 4월 15일 오후 6: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. 2026년 4월 15일 오후 6:31 UTCresolved

   This incident has been resolved.

1. 2026년 3월 25일 오후 2:08 UTCresolved

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

1. 2026년 2월 16일 오후 3: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. 2026년 1월 27일 오후 9:05 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 1월 27일 오후 9:08 UTCidentified

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

3. 2026년 1월 27일 오후 10: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. 2026년 1월 28일 오전 4:49 UTCresolved

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

1. 2026년 1월 9일 오후 1: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. 2025년 11월 18일 오전 11:55 UTCinvestigating

   We are currently investigating this issue.

2. 2025년 11월 18일 오전 11:58 UTCidentified

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

3. 2025년 11월 18일 오후 12:00 UTCidentified

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

4. 2025년 11월 18일 오후 12:18 UTCmonitoring

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

5. 2025년 11월 18일 오후 12:48 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 2025년 11월 18일 오후 3: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. 2025년 11월 18일 오후 5: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. 2025년 11월 18일 오후 7:16 UTCmonitoring

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

9. 2025년 11월 18일 오후 7:17 UTCresolved

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

1. 2025년 10월 23일 오전 9: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. 2025년 10월 20일 오후 5: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. 2025년 10월 20일 오후 5:37 UTCidentified

   The issue has been identified.

3. 2025년 10월 20일 오후 7:26 UTCmonitoring

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

4. 2025년 10월 20일 오후 8:23 UTCresolved

   This incident has been resolved.

1. 2025년 10월 20일 오후 2: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. 2025년 10월 20일 오후 8: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. 2025년 10월 15일 오전 7: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.