Vendor Status Watch

← all vendors

Zyte status history

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

2incidents, last 30 days
6incidents, last 90 days
21incidents on record
Incidents per week, last 12 weeks:

How long do Zyte incidents last?

16.2 hmedian incident duration21 measured
37.3 h90th percentile1 in 10 ran longer
5.7 hmedian, major/critical only4 incidents

From 21 incidents with a vendor-posted start and resolve time. Longest on record: Scrapy Cloud Jobs API Issue — 5.2 days (2026-02-26 03:25 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 (21)

StartedIncidentStatusImpactDuration
2026-09-13 14:28 UTCZyte API – Performance Degradation for browser renderingresolvedminor4 h 50 min
2026-09-10 05:28 UTCZyte API – Performance Degradationresolvedminor26 h 23 min
2026-08-17 09:05 UTCPerformance degradation in Periodic jobs scheduling and deploymentresolvedminor3 h 36 min
2026-07-16 09:32 UTCPartial Service Degradation of job scheduling in Scrapy Cloudresolvedmajor7 h 37 min
2026-06-28 08:12 UTCPerformance degradation in Periodic jobs schedulingresolvedminor16 h 14 min
2026-06-27 18:56 UTCZyte Dashboard is inaccessibleresolvednone5 h 27 min
2026-05-19 11:43 UTCIssue Displaying Zyte API Statistics in Web Dashboardresolvedminor24 h 21 min
2026-04-14 08:51 UTCZyte API – Performance Degradationresolvedminor21 h 02 min
2026-02-26 03:25 UTCScrapy Cloud Jobs API Issueresolvedminor5 d 5 h
2026-02-12 05:08 UTCZyte API – Performance Degradationresolvedminor33 h 30 min
2026-01-28 17:30 UTCScrapy Cloud Partial Service Outageresolvednone0 min
2025-12-11 08:40 UTCWeb Dashboard doesn't show Zyte API Statsresolvedminor7 h 08 min
2025-11-14 08:09 UTCZyte API Account Suspensionresolvedminor30 h 27 min
2025-10-20 10:03 UTCAWS issue impacting our servicesresolvedmajor3 h 52 min
2025-10-01 11:08 UTCService Degradation for Smart Proxy Managerresolvedcritical24 h 59 min
2025-09-17 09:25 UTCZyte API – Performance Degradationresolvedmajor3 h 26 min
2025-08-30 06:55 UTCZyte API – Performance Degradationresolvedminor11 h 41 min
2025-08-26 14:36 UTCDelayed Scrapy Cloud jobs startresolvedminor2 d 1 h
2025-08-21 11:18 UTCProvisioning issue with new signup for Zyte APIresolvedminor4 h 39 min
2025-08-21 03:42 UTCPeriodic Job Scheduling Issueresolvedminor34 h 09 min
2025-08-13 07:05 UTCScrapy Cloud performance degradationresolvedminor37 h 17 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 Zyte with the template

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

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