Vendor Status Watch

← all vendors

Tyk status history

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

0incidents, last 30 days
5incidents, last 90 days
19incidents on record
Incidents per week, last 12 weeks:

How long do Tyk incidents last?

10 minmedian incident duration19 measured
3.7 h90th percentile1 in 10 ran longer
3 minmedian, major/critical only15 incidents

From 19 incidents with a vendor-posted start and resolve time. Longest on record: [StatusCake] https://controller-aws-usw2.cloud-ara.tyk.io:37001/health status is Down — 15.2 h (2025-10-03 01:03 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 (19)

StartedIncidentStatusImpactDuration
2026-08-14 17:35 UTCUSE-1 Region Operations Degradedresolvedminor1 h 10 min
2026-07-09 14:32 UTC[StatusCake] https://controller-aws-use1.cloud-ara.tyk.io:37001/health status is Downresolvedmajor1 min
2026-07-09 11:56 UTC[StatusCake] https://controller-aws-use1.cloud-ara.tyk.io:37001/health status is Downresolvedmajor3 min
2026-07-08 17:39 UTC[StatusCake] https://controller-aws-use1.cloud-ara.tyk.io:37001/health status is Downresolvedmajor3 min
2026-07-01 11:07 UTC[StatusCake] https://controller-aws-use1.cloud-ara.tyk.io:37001/health status is Downresolvedmajor1 min
2026-06-11 10:58 UTC[StatusCake] https://dashboard.cloud-ara.tyk.io status is Downresolvedmajor10 min
2026-05-20 10:14 UTC[StatusCake] https://dashboard.cloud-ara.tyk.io status is Downresolvedmajor2 min
2026-04-23 11:09 UTC[StatusCake] https://controller-aws-use1.cloud-ara.tyk.io:37001/health status is Downresolvedmajor2 min
2026-04-19 09:53 UTC[StatusCake] https://controller-aws-euc1.cloud-ara.tyk.io:37001/health status is Downresolvedmajor3 min
2026-04-17 00:41 UTC[StatusCake] https://controller-aws-euc1.cloud-ara.tyk.io:37001/health status is Downresolvedmajor7 min
2026-03-12 17:45 UTCUSE-1 Region Operations Degradedresolvedmajor30 min
2026-03-01 19:19 UTCAPSE1 Region degradedresolvedminor3 h 03 min
2026-01-21 00:05 UTChttps://dashboard.cloud-ara.tyk.io status is degradedresolvedmajor2 h 02 min
2025-11-18 12:38 UTC[StatusCake] https://account.cloud-ara.tyk.io/signup status is Degradedresolvedmajor3 h 04 min
2025-11-18 12:02 UTC[StatusCake] https://dashboard.cloud-ara.tyk.io status is Degradedresolvedmajor3 h 40 min
2025-11-02 14:01 UTCTyk Cloud - Partial Service Degradation on Tyk Cloud in EU-west-2resolvednone3 h 58 min
2025-10-23 06:30 UTCService Degradation for Customers Due to MongoDB Connection Issues on AP-SOUTHEAST-1resolvedminor30 min
2025-10-03 01:03 UTC[StatusCake] https://controller-aws-usw2.cloud-ara.tyk.io:37001/health status is Downresolvedmajor15 h 13 min
2025-09-19 10:40 UTC[StatusCake] https://controller-aws-usw2.cloud-ara.tyk.io:37001/health status is Downresolvedmajor3 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 Tyk with the template

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

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