Vendor Status Watch

← all vendors

Apify status history

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

1incidents, last 30 days
8incidents, last 90 days
31incidents on record
Incidents per week, last 12 weeks:

How long do Apify incidents last?

2.5 hmedian incident duration31 measured
22.0 h90th percentile1 in 10 ran longer
2.6 hmedian, major/critical only13 incidents

From 31 incidents with a vendor-posted start and resolve time. Longest on record: Degraded performance of Google SERP Proxy — 37.5 h (2026-08-03 23:56 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 (31)

StartedIncidentStatusImpactDuration
2026-08-20 14:05 UTCDegraded Actor performanceresolvednone2 h 08 min
2026-08-13 15:38 UTCDegraded performance of SHADER proxy groupresolvedminor22 h 26 min
2026-08-07 21:00 UTCDegraded performance of Google SERP Proxyresolvedminor21 h 59 min
2026-08-03 23:56 UTCDegraded performance of Google SERP Proxyresolvedmajor37 h 33 min
2026-07-26 06:53 UTCIncreased error rate on Actor Standby endpointsresolvedminor1 h 04 min
2026-07-21 14:49 UTCDegraded performance of API operations due to slow database operationsresolvedcritical11 h 49 min
2026-07-21 06:52 UTCHigh number of Actor run migrationsresolvedminor5 h 01 min
2026-07-17 14:04 UTCDegraded SERP performanceresolvedminor6 h 03 min
2026-06-04 15:07 UTCDegraded performance of webhooksresolvedminor1 h 59 min
2026-05-15 11:48 UTCDegraded performance of API, Console, and Proxyresolvedminor17 h 39 min
2026-05-14 05:20 UTCProxy degradationresolvedcritical2 h 00 min
2026-05-06 20:08 UTCMCP: Failing OAuth sing-in from clients using CIMD with loopback redirectsresolvedminor12 h 18 min
2026-05-05 13:50 UTCOutage of Key-value storeresolvedcritical44 min
2026-05-01 11:23 UTCDegraded Console UI and API performanceresolvedminor33 min
2026-04-29 12:35 UTCOutage of API and Actorsresolvedmajor2 h 38 min
2026-04-08 10:01 UTCApify API Degraded Performanceresolvedmajor23 h 14 min
2026-03-11 12:48 UTCSecurity Incident Notification – March 6, 2026resolvednone20 h 46 min
2026-03-06 17:27 UTCDegraded Datacenter Proxy Performanceresolvedminor1 h 37 min
2026-01-27 04:10 UTCDegraded residential proxy performanceresolvedminor5 h 27 min
2026-01-21 15:17 UTCApify Console temporarily unvailableresolvedcritical2 min
2026-01-12 08:22 UTCapify.com/store disruptedresolvedminor36 min
2026-01-09 20:26 UTCCustomer support chat unavailableresolvednone46 min
2025-12-31 10:31 UTCDegraded perfromance of residential proxy networkresolvedmajor18 min
2025-12-11 14:56 UTCCreating new Actors from Actor templates in UI is unavailableresolvedminor2 h 29 min
2025-10-29 19:06 UTCUnintended breaking change in Actor run API endpointresolvedminor1 h 14 min
2025-10-20 14:42 UTCDegraded Actor runs performanceresolvedcritical16 h 47 min
2025-10-20 07:00 UTCPlatform outageresolvedmajor7 h 40 min
2025-10-14 16:35 UTCApify docs is not loading properlyresolvedmajor2 min
2025-09-24 23:16 UTCActors cannot be builtresolvedcritical2 h 32 min
2025-09-15 12:38 UTCIssue with apify/send-mail Actorresolvednone0 min
2025-09-09 11:17 UTCProblems with running newly-built Actors.resolvedmajor3 h 49 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 Apify with the template

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

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