Percy Outage History

Percy is up right now

Pingoru has recorded 50 incidents for Percy: 15 in the last 12 months and 2 in the last 90 days.

Source: status.percy.io

50incidents recorded
15last 12 months
2last 90 days
5 hourstypical duration
Incidents per month
024AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Percy in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202612 of 720 (0%)
May 2026431 of 744 (4%)
June 202610 of 720 (0%)
July 2026216 of 744 (2%)
August 202600 of 744 (0%)
September 202621 of 720 (0%)
October 202600 of 589 (0%)

Incidents, newest first

Minor February 27, 2025 Percy API faced degradation for brief period 12m Percy

Started Feb 27, 2025, 06:05 AM UTC· resolved Feb 27, 2025, 06:18 AM UTC

  1. investigating Feb 27, 2025, 09:50 AM UTC

    We faced a degradation of the service for a brief period for certain users, we have observed few builds failing intermittently during this brief period.

  2. identified Feb 27, 2025, 09:52 AM UTC

    We have identified the issue.

  3. monitoring Feb 27, 2025, 09:52 AM UTC

    The fix has been rolled out and we are monitoring it.

  4. resolved Feb 27, 2025, 09:53 AM UTC

    The issue has been resolved.

Read the full incident report →

Notice February 27, 2025 Incorrect snapshot with access denied message visible for few Percy builds 7h

Started Feb 27, 2025, 01:00 AM UTC· resolved Feb 27, 2025, 08:00 AM UTC

  1. resolved Feb 27, 2025, 09:15 AM UTC

    We are observing access denied snapshot on few Percy builds. We have identified the root cause, deployed a fix and monitoring it.

Read the full incident report →

Minor January 2, 2025 Incorrect snapshots with SSL error being shown when using Safari on Desktop as a browser 10h 29m Percy, Rendering infrastructure

Started Jan 02, 2025, 12:00 AM UTC· resolved Jan 02, 2025, 10:29 AM UTC

  1. investigating Jan 02, 2025, 05:23 AM UTC

    We are currently investigating this issue, and have identified a potential fix.

  2. monitoring Jan 02, 2025, 06:35 AM UTC

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

  3. resolved Jan 02, 2025, 10:29 AM UTC

    This incident has been resolved.

Read the full incident report →