Zyte Outage History

19 incidents recorded over the last 365 days, 14 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Zyte status100.00% uptime history

Every Recorded Zyte Incident

Zyte incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 28, 2026Web Dashboard and Periodic Jobs are downThis incident has been resolved.41h 17mResolved
Oct 27, 2026Backend Infrastructure UpgradesScheduled maintenance is currently in progress. We will provide updates as necessary.14h 0mScheduled
Sep 13, 2026Zyte API – Performance Degradation for browser renderingThis incident has been resolved.4h 50mResolved
Sep 10, 2026Zyte API – Performance DegradationThis incident has been resolved.26h 23mResolved
Aug 17, 2026Performance degradation in Periodic jobs scheduling and deploymentThis incident has been resolved.3h 36mResolved
Jul 16, 2026Partial Service Degradation of job scheduling in Scrapy CloudThis incident has been resolved.7h 37mResolved
Jun 28, 2026Performance degradation in Periodic jobs schedulingThis incident has been resolved.16h 14mResolved
Jun 27, 2026Zyte Dashboard is inaccessibleThis incident has been resolved.5h 27mResolved
May 19, 2026Issue Displaying Zyte API Statistics in Web DashboardThis incident has been resolved.24h 21mResolved
Apr 14, 2026Zyte API – Performance DegradationThis incident has been resolved.21h 2mResolved
Apr 13, 2026Billing Platform MaintenanceThe scheduled maintenance has been completed.24h 0mScheduled
Feb 26, 2026Scrapy Cloud Jobs API IssueThe issue has been identified and fix will be rolled out soon.125h 13mResolved
Feb 12, 2026Zyte API – Performance DegradationThis incident has been resolved.33h 30mResolved
Jan 29, 2026Scrapy Cloud Partial Service OutageWe experienced a temporary service degradation impacting Scrapy Cloud on January 28th between 23:05 UTC - 23:47 UTC. During this window, you may have observed reduced performance due to an unexpected router outage at…-588 minResolved
Dec 23, 2025Docker Registry UpgradeThe scheduled maintenance has been completed.2h 0mScheduled
Dec 22, 2025Docker Registry UpgradeThe scheduled maintenance has been completed.2h 0mScheduled
Dec 17, 2025Docker Registry UpgradeThe scheduled maintenance has been completed.2h 0mScheduled
Dec 11, 2025Web Dashboard doesn't show Zyte API StatsThis incident has been resolved.7h 8mResolved
Nov 14, 2025Zyte API Account SuspensionThis incident has been resolved.30h 27mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Zyte incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Zyte Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Zyte acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Zyte outage in this window ran 5d 5h, against a mean recovery of 21h 44m. If you depend on Zyte in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.