Tyk Cloud Outage History

44 incidents recorded over the last 365 days, 15 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.

Every Recorded Tyk Cloud Incident

Tyk Cloud incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 5, 2026Maintenance in aws-ap-southeast-1We will be conducting a planned maintenance. The process is not expected to incur any downtime for the customer deployments.4h 0mScheduled
Nov 3, 2026Emergency maintenance across all deployment zonesScheduled maintenance is currently in progress. We will provide updates as necessary.12h 0mScheduled
Nov 2, 2026Emergency maintenance across all deployment zonesScheduled maintenance is currently in progress. We will provide updates as necessary.24h 0mScheduled
Oct 7, 2026Maintenance across all deployment zonesThe scheduled maintenance has been completed.12h 0mScheduled
Oct 6, 2026Maintenance across all deployment zonesThe scheduled maintenance has been completed.12h 0mScheduled
Sep 30, 2026Maintenance in aws-us-east-1The scheduled maintenance has been completed.12h 0mScheduled
Sep 30, 2026Maintenance in aws-eu-west-2, aws-eu-central-1, aws-ap-southeast-1 and aws-ap-southeast-2The scheduled maintenance has been completed.12h 0mScheduled
Sep 29, 2026Maintenance in aws-us-west-2The scheduled maintenance has been completed.18h 0mScheduled
Aug 14, 2026USE-1 Region Operations DegradedThis incident has been resolved.1h 10mResolved
Aug 11, 2026Maintenance in aws-eu-west-2The scheduled maintenance has been completed.5h 0mScheduled
Aug 11, 2026Maintenance in aws-eu-west-2The scheduled maintenance has been completed.5h 0mScheduled
Aug 10, 2026Maintenance in aws-us-east-1The scheduled maintenance has been completed.11h 0mScheduled
Aug 6, 2026Maintenance in aws-eu-central-1The scheduled maintenance has been completed.11h 59mScheduled
Aug 5, 2026Maintenance in aws-us-west-2The scheduled maintenance has been completed.12h 0mScheduled
Aug 4, 2026Maintenance in aws-ap-southeast-1The scheduled maintenance has been completed.10h 0mScheduled
Jul 26, 2026Maintenance in aws-us-east-1 and aws-eu-central-1The scheduled maintenance has been completed.5h 0mScheduled
Jul 23, 2026Maintenance across all deployment zonesThe scheduled maintenance has been completed.10h 59mScheduled
Jul 22, 2026Maintenance across all deployment zonesThe scheduled maintenance has been completed.4h 0mScheduled
Jul 13, 2026Internal systems availability and recovery procedures testingThe scheduled maintenance has been completed.3h 30mScheduled
Jul 9, 2026[StatusCake] https://controller-aws-use1.cloud-ara.tyk.io:37001/health status is DownThis incident has been resolved.1 minResolved
Jul 9, 2026[StatusCake] https://controller-aws-use1.cloud-ara.tyk.io:37001/health status is DownThis incident has been resolved.3 minResolved
Jul 8, 2026[StatusCake] https://controller-aws-use1.cloud-ara.tyk.io:37001/health status is DownThis incident has been resolved.3 minResolved
Jul 8, 2026Emergency maintenance in aws-us-west-2, aws-us-east-1, aws-eu-west-2 and aws-ap-southeast-2The scheduled maintenance has been completed.4h 0mScheduled
Jul 6, 2026Emergency maintenance across all deployment zonesThe scheduled maintenance has been completed.4h 0mScheduled
Jul 2, 2026Maintenance in aws-ap-southeast-1The scheduled maintenance has been completed.2h 0mScheduled
Jul 1, 2026Maintenance in aws-ap-southeast-1The scheduled maintenance has been completed.2h 0mScheduled
Jul 1, 2026[StatusCake] https://controller-aws-use1.cloud-ara.tyk.io:37001/health status is DownThis incident has been resolved.1 minResolved
Jun 11, 2026[StatusCake] https://dashboard.cloud-ara.tyk.io status is DownThis incident has been resolved.10 minResolved
Jun 3, 2026Maintenance across all deployment zonesThe scheduled maintenance has been completed.5h 59mScheduled
May 28, 2026Maintenance across all deployment zonesThe scheduled maintenance has been completed.4h 0mScheduled
May 26, 2026Maintenance across all deployment zonesThe scheduled maintenance has been completed.3h 0mScheduled
May 20, 2026[StatusCake] https://dashboard.cloud-ara.tyk.io status is DownThis incident has been resolved.2 minResolved
May 14, 2026Maintenance across all deployment zonesThe scheduled maintenance has been completed.5h 59mScheduled
May 6, 2026Maintenance across all deployment zonesThe scheduled maintenance has been completed.6h 59mScheduled
Apr 23, 2026[StatusCake] https://controller-aws-use1.cloud-ara.tyk.io:37001/health status is DownThis incident has been resolved.2 minResolved
Apr 19, 2026[StatusCake] https://controller-aws-euc1.cloud-ara.tyk.io:37001/health status is DownThis incident has been resolved.3 minResolved
Apr 17, 2026[StatusCake] https://controller-aws-euc1.cloud-ara.tyk.io:37001/health status is DownThis incident has been resolved.7 minResolved
Apr 16, 2026Maintenance across all deployment zonesThe scheduled maintenance has been completed.12h 0mScheduled
Apr 15, 2026Maintenance across all deployment zonesThe scheduled maintenance has been completed.10h 0mScheduled
Mar 12, 2026USE-1 Region Operations DegradedThis incident has been resolved.30 minResolved
Mar 1, 2026APSE1 Region degradedThis incident has been resolved.3h 3mResolved
Jan 21, 2026https://dashboard.cloud-ara.tyk.io status is degradedThis incident has been resolved.2h 2mResolved
Nov 18, 2025[StatusCake] https://account.cloud-ara.tyk.io/signup status is DegradedThis incident has been resolved.3h 4mResolved
Nov 18, 2025[StatusCake] https://dashboard.cloud-ara.tyk.io status is DegradedThis incident has been resolved.3h 40mResolved

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 Tyk Cloud 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 Tyk Cloud 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 Tyk Cloud 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 Tyk Cloud outage in this window ran 1d, against a mean recovery of 5h 52m. If you depend on Tyk Cloud 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.