Zyte status history
Current state: operational — “All Systems Operational” per https://status.zyte.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Zyte incidents last?
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)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-13 14:28 UTC | Zyte API – Performance Degradation for browser rendering | resolved | minor | 4 h 50 min |
| 2026-09-10 05:28 UTC | Zyte API – Performance Degradation | resolved | minor | 26 h 23 min |
| 2026-08-17 09:05 UTC | Performance degradation in Periodic jobs scheduling and deployment | resolved | minor | 3 h 36 min |
| 2026-07-16 09:32 UTC | Partial Service Degradation of job scheduling in Scrapy Cloud | resolved | major | 7 h 37 min |
| 2026-06-28 08:12 UTC | Performance degradation in Periodic jobs scheduling | resolved | minor | 16 h 14 min |
| 2026-06-27 18:56 UTC | Zyte Dashboard is inaccessible | resolved | none | 5 h 27 min |
| 2026-05-19 11:43 UTC | Issue Displaying Zyte API Statistics in Web Dashboard | resolved | minor | 24 h 21 min |
| 2026-04-14 08:51 UTC | Zyte API – Performance Degradation | resolved | minor | 21 h 02 min |
| 2026-02-26 03:25 UTC | Scrapy Cloud Jobs API Issue | resolved | minor | 5 d 5 h |
| 2026-02-12 05:08 UTC | Zyte API – Performance Degradation | resolved | minor | 33 h 30 min |
| 2026-01-28 17:30 UTC | Scrapy Cloud Partial Service Outage | resolved | none | 0 min |
| 2025-12-11 08:40 UTC | Web Dashboard doesn't show Zyte API Stats | resolved | minor | 7 h 08 min |
| 2025-11-14 08:09 UTC | Zyte API Account Suspension | resolved | minor | 30 h 27 min |
| 2025-10-20 10:03 UTC | AWS issue impacting our services | resolved | major | 3 h 52 min |
| 2025-10-01 11:08 UTC | Service Degradation for Smart Proxy Manager | resolved | critical | 24 h 59 min |
| 2025-09-17 09:25 UTC | Zyte API – Performance Degradation | resolved | major | 3 h 26 min |
| 2025-08-30 06:55 UTC | Zyte API – Performance Degradation | resolved | minor | 11 h 41 min |
| 2025-08-26 14:36 UTC | Delayed Scrapy Cloud jobs start | resolved | minor | 2 d 1 h |
| 2025-08-21 11:18 UTC | Provisioning issue with new signup for Zyte API | resolved | minor | 4 h 39 min |
| 2025-08-21 03:42 UTC | Periodic Job Scheduling Issue | resolved | minor | 34 h 09 min |
| 2025-08-13 07:05 UTC | Scrapy Cloud performance degradation | resolved | minor | 37 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
}