Is Tyk down?
Last checked 13m agoNo incidents right now.
Tyk is operational right now. Last checked 13m ago; the most recent incident resolved 2d ago.
Real-time Tyk status, recent outages, and incident history — pulled directly from Tyk's official status page at https://status.tyk.io every 5 minutes. Pingoru tracks 18 Tyk services and has captured 10 incidents in the last 90 days (99.54% uptime). Get email, Slack, Discord, or webhook alerts the moment Tyk reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Dashboard
Timeline · 2 updates
- investigating · Jun 11, 2026, 10:58 AM UTC
Test Name: Tyk Cloud Dashboard Status Code: 0 Status Text: Timeout / Connection Refused Check Rate: 30
- resolved · Jun 11, 2026, 11:08 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Dashboard
Timeline · 2 updates
- investigating · May 20, 2026, 10:14 AM UTC
Test Name: Tyk Cloud Dashboard Status Code: 0 Status Text: Timeout / Connection Refused Check Rate: 30
- resolved · May 20, 2026, 10:17 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Controller at aws-us-east-1
Timeline · 2 updates
- investigating · Apr 23, 2026, 11:09 AM UTC
Test Name: Tyk Cloud Controller aws-us-east-1 Status Code: 503 Status Text: Service was detected as Down. Check Rate: 60
- resolved · Apr 23, 2026, 11:11 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Controller at aws-eu-central-1
Timeline · 2 updates
- investigating · Apr 19, 2026, 09:53 AM UTC
Test Name: Tyk Cloud Controller aws-eu-central-1 Status Code: 0 Status Text: Timeout / Connection Refused Check Rate: 60
- resolved · Apr 19, 2026, 09:57 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Controller at aws-eu-central-1
Timeline · 2 updates
- investigating · Apr 17, 2026, 12:41 AM UTC
Test Name: Tyk Cloud Controller aws-eu-central-1 Status Code: 0 Status Text: Timeout / Connection Refused Check Rate: 60
- resolved · Apr 17, 2026, 12:49 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Started Jun 11, 2026, 10:58 AM UTC · Resolved Jun 11, 2026, 11:08 AM UTC · 10m
- Started May 20, 2026, 10:14 AM UTC · Resolved May 20, 2026, 10:17 AM UTC · 2m
- Started Apr 23, 2026, 11:09 AM UTC · Resolved Apr 23, 2026, 11:11 AM UTC · 2m
- Started Apr 19, 2026, 09:53 AM UTC · Resolved Apr 19, 2026, 09:57 AM UTC · 3m
- Started Apr 17, 2026, 12:41 AM UTC · Resolved Apr 17, 2026, 12:49 AM UTC · 7m