Vendor Status Watch

← all vendors

Percy status history

Current state: operational — “All Systems Operational” per https://status.percy.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

1incidents, last 30 days
4incidents, last 90 days
20incidents on record
Incidents per week, last 12 weeks:

How long do Percy incidents last?

0 minmedian incident duration20 measured
12.5 h90th percentile1 in 10 ran longer
4.2 hmedian, major/critical only6 incidents

From 20 incidents with a vendor-posted start and resolve time. Longest on record: Degraded Build Performance — 17.8 h (2025-09-09 10:00 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (20)

StartedIncidentStatusImpactDuration
2026-09-10 23:55 UTCWe are observing few build failures for customers on Windows terminalresolvedmajor59 min
2026-07-13 02:00 UTCPercy builds were degraded for ~50 mins due to an existing Google Cloud Provider incident [7.30 AM PDT to 8.20 AM PDT on 13th July]resolvedminor0 min
2026-07-06 14:30 UTCPercy customers were facing intermittent login issues from 7:45 pm PDT to 10:14 PM PDT on 6th Julyresolvedminor0 min
2026-06-29 11:30 UTCA subset of Percy builds experienced slowness from 4:15 PM PDT to 5 PM PDT [29th June]resolvedminor0 min
2026-05-29 11:30 UTCIntermittent API issue causing missing snapshots or build creationresolvedmajor0 min
2026-05-18 18:00 UTCIntermittent Login Issues Impacting Some Customersresolvednone0 min
2026-05-11 11:30 UTCPercy builds processing taking longer than usualresolvedminor0 min
2026-05-05 02:30 UTCPercy on Automate failuresresolvedminor12 h 30 min
2026-04-15 16:39 UTCAI features unavailable on Percy buildsresolvedminor1 h 52 min
2026-03-25 01:30 UTCIntermittent Login failure for some usersresolvedminor12 h 00 min
2026-02-07 21:00 UTCIntermittent degraded visual diffs on Percy (Safari on iPhone)resolvednone0 min
2026-01-27 20:00 UTCAPI failures for percy buildsresolvedmajor8 h 49 min
2026-01-09 10:00 UTCUnable to access Percy dashboardresolvedminor0 min
2025-11-18 11:55 UTCWe are experiencing Percy build failures due to ongoing Cloudflare outageresolvedcritical7 h 22 min
2025-10-22 17:00 UTCPercy is experiencing degraded rendering, leading to incorrect Visual differences [Underlying Cloudflare issue]resolvednone0 min
2025-10-20 17:37 UTCPercy Review Agent is experiencing degraded performance and partial outageresolvedminor2 h 07 min
2025-10-20 13:30 UTCDegraded Performance Due to AWS US-East-1 / LaunchDarkly Outageresolvedmajor0 min
2025-10-20 07:00 UTCDegraded Performance Due to AWS US-East-1resolvedmajor13 h 00 min
2025-10-14 08:00 UTCDegradation with Percy Web buildsresolvednone0 min
2025-09-09 10:00 UTCDegraded Build Performanceresolvedminor17 h 45 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Percy with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "percy"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}