Is Zyte down?
Zyte is up
Right now
No. No incidents reported.
Last checked (2026-10-10 07:17 UTC) from status.zyte.com · every 180s
For agents
proceed
Proceed.
GET upbutler.com/status/zyte/status.agent.json
MCP: upstream_status {"service":"zyte"}
Zyte API, smart proxy and Scrapy Cloud.
What Zyte says
Operational
Taken as is from Zyte's own status page API. Incident titles and component names below are theirs.
Open status.zyte.comWhat UpButler measured
There is no keyless endpoint of Zyte that says anything useful, so UpButler does not probe it. To check your own Zyte account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.
Zyte components
8 operational
- Web DashboardOperational
- Support CenterOperational
Smart Proxy Manager
- Smart Proxy ManagerOperational
- Smart Proxy Manager - ResidentialOperational
Scrapy Cloud
- Scrapy Cloud - Job Execution and StorageOperational
- Scrapy Cloud - Project DeploymentOperational
- Scrapy Cloud - Periodic Job SchedulingOperational
Zyte API
- Zyte APIOperational
Zyte incidents, last 90 days
- 2026-07-13: no record
- 2026-07-14: no record
- 2026-07-15: no record
- 2026-07-16: no record
- 2026-07-17: no record
- 2026-07-18: no record
- 2026-07-19: no record
- 2026-07-20: no record
- 2026-07-21: no record
- 2026-07-22: no record
- 2026-07-23: no record
- 2026-07-24: no record
- 2026-07-25: no record
- 2026-07-26: no record
- 2026-07-27: no record
- 2026-07-28: no record
- 2026-07-29: no record
- 2026-07-30: no record
- 2026-07-31: no record
- 2026-08-01: no record
- 2026-08-02: no record
- 2026-08-03: no record
- 2026-08-04: no record
- 2026-08-05: no record
- 2026-08-06: no record
- 2026-08-07: no record
- 2026-08-08: no record
- 2026-08-09: no record
- 2026-08-10: no record
- 2026-08-11: no record
- 2026-08-12: no record
- 2026-08-13: no record
- 2026-08-14: no record
- 2026-08-15: no record
- 2026-08-16: no record
- 2026-08-17: no record
- 2026-08-18: no record
- 2026-08-19: no record
- 2026-08-20: no record
- 2026-08-21: no record
- 2026-08-22: no record
- 2026-08-23: no record
- 2026-08-24: no record
- 2026-08-25: no record
- 2026-08-26: no record
- 2026-08-27: no record
- 2026-08-28: no record
- 2026-08-29: no record
- 2026-08-30: no record
- 2026-08-31: no record
- 2026-09-01: no record
- 2026-09-02: no record
- 2026-09-03: no record
- 2026-09-04: no record
- 2026-09-05: no record
- 2026-09-06: no record
- 2026-09-07: no record
- 2026-09-08: no record
- 2026-09-09: no record
- 2026-09-10: no record
- 2026-09-11: no record
- 2026-09-12: no record
- 2026-09-13: no record
- 2026-09-14: no record
- 2026-09-15: no record
- 2026-09-16: no record
- 2026-09-17: no record
- 2026-09-18: no record
- 2026-09-19: no record
- 2026-09-20: no record
- 2026-09-21: no record
- 2026-09-22: no record
- 2026-09-23: no record
- 2026-09-24: no record
- 2026-09-25: no record
- 2026-09-26: no record
- 2026-09-27: no record
- 2026-09-28: no record
- 2026-09-29: no record
- 2026-09-30: no record
- 2026-10-01: no record
- 2026-10-02: no record
- 2026-10-03: no record
- 2026-10-04: no record
- 2026-10-05: no record
- 2026-10-06: no record
- 2026-10-07: no record
- 2026-10-08: no record
- 2026-10-09: no record
- 2026-10-10: no incident reported
Each bar is a day, coloured by the worst incident Zyte reported. It is their incident record, not a measurement of uptime.
No finished incidents on record yet since 2026-10-10. UpButler keeps what Zyte publishes for 90 days from the day it starts tracking a service.
Get alerted when Zyte goes down
No account. One email when Zyte reports an incident, one when it is over. You confirm the address first, and every email has a one-click unsubscribe.
Or follow the RSS feed. On UpButler? Add Zyte as a dependency to route it to Slack, Teams or a webhook.
Status badge
Show Zyte's current status in a README or an internal wiki. It updates by itself.
[](https://upbutler.com/status/zyte)Tell your outage from Zyte's
Declare that your project depends on Zyte. When one of your monitors fails while Zyte has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- zytecurl -s https://upbutler.com/status/zyte/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "zyte",
"verdict": "proceed",
"status": "operational",
"reason": "No incidents reported",
"retryAfterSec": null,
"incident": null,
"probe": null
}Questions
- Is Zyte down right now?
- No. As of 2026-10-10 07:17 UTC, Zyte is up. This page reads the status again every 3 minutes.
- Where does this status come from?
- From Zyte's own status page API at https://status.zyte.com. UpButler reads it once for everyone (not once per visitor) every 3 minutes with conditional requests, and shows it unchanged: incident titles and component names are Zyte's words.
- Can I get an alert when Zyte goes down?
- Yes, without an account: enter your email on this page, confirm the link we send, and you get one email when Zyte reports an incident and one when it is over. There is also an RSS feed at https://upbutler.com/status/zyte/feed.rss. Teams on UpButler can route the same alert to Slack, Teams or a webhook.
- How can my agent or app check Zyte status?
- Fetch https://upbutler.com/status/zyte/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"zyte"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or Zyte's?
- Add "zyte" to the dependencies of your UpButler workspace. When one of your monitors fails while Zyte has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
Also check
UpButler is not affiliated with Zyte. Status and incident text belong to Zyte and are read from their public status source; the probe result is UpButler's own measurement.