Tyk Outage History

Tyk is up right now

Pingoru has recorded 50 incidents for Tyk: 17 in the last 12 months and 1 in the last 90 days.

Source: status.tyk.io

50incidents recorded
17last 12 months
1last 90 days
66 minutestypical duration
Incidents per month
024AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Tyk in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202630 of 720 (0%)
May 202610 of 744 (0%)
June 202610 of 720 (0%)
July 202640 of 744 (0%)
August 202611 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 510 (0%)

Incidents, newest first

Minor August 14, 2026 USE-1 Region Operations Degraded 1h 10m Dashboard, <a href="https://health.aws.amazon.com/health/status">AWS ec2-us-east-1</a>

Started Aug 14, 2026, 05:35 PM UTC· resolved Aug 14, 2026, 06:46 PM UTC

  1. investigating Aug 14, 2026, 05:35 PM UTC

    We are currently investigating an issue preventing to access dashboard on some of the USE1 organisations.

  2. identified Aug 14, 2026, 05:55 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Aug 14, 2026, 06:03 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Aug 14, 2026, 06:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 9, 2026 [StatusCake] https://controller-aws-use1.cloud-ara.tyk.io:37001/health status is Down 1m Controller at aws-us-east-1

Started Jul 09, 2026, 02:32 PM UTC· resolved Jul 09, 2026, 02:33 PM UTC

  1. investigating Jul 09, 2026, 02:32 PM UTC

    Test Name: Tyk Cloud Controller aws-us-east-1 Status Code: 0 Status Text: Timeout / Connection Refused Check Rate: 60

  2. resolved Jul 09, 2026, 02:33 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 11, 2026 [StatusCake] https://dashboard.cloud-ara.tyk.io status is Down 10m Dashboard

Started Jun 11, 2026, 10:58 AM UTC· resolved Jun 11, 2026, 11:08 AM UTC

  1. investigating Jun 11, 2026, 10:58 AM UTC

    Test Name: Tyk Cloud Dashboard Status Code: 0 Status Text: Timeout / Connection Refused Check Rate: 30

  2. resolved Jun 11, 2026, 11:08 AM UTC

    This incident has been resolved.

Read the full incident report →

Major April 19, 2026 [StatusCake] https://controller-aws-euc1.cloud-ara.tyk.io:37001/health status is Down 3m Controller at aws-eu-central-1

Started Apr 19, 2026, 09:53 AM UTC· resolved Apr 19, 2026, 09:57 AM UTC

  1. 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

  2. resolved Apr 19, 2026, 09:57 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 1, 2026 APSE1 Region degraded 3h 3m Dashboard, Controller at aws-ap-southeast-1

Started Mar 01, 2026, 07:19 PM UTC· resolved Mar 01, 2026, 10:23 PM UTC

  1. investigating Mar 01, 2026, 07:19 PM UTC

    We are currently investigating this issue

  2. resolved Mar 01, 2026, 10:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 21, 2026 https://dashboard.cloud-ara.tyk.io status is degraded 2h 2m Dashboard

Started Jan 21, 2026, 12:05 AM UTC· resolved Jan 21, 2026, 02:07 AM UTC

  1. investigating Jan 21, 2026, 12:05 AM UTC

    We are currently investigating an issue on the dashboard preventing the users to display their organizations correctly.N

  2. identified Jan 21, 2026, 01:04 AM UTC

    The issue has been identified and a fix was applied

  3. resolved Jan 21, 2026, 02:07 AM UTC

    This incident has been resolved.

Read the full incident report →

Major November 18, 2025 [StatusCake] https://account.cloud-ara.tyk.io/signup status is Degraded 3h 4m Billing

Started Nov 18, 2025, 12:38 PM UTC· resolved Nov 18, 2025, 03:43 PM UTC

  1. investigating Nov 18, 2025, 12:38 PM UTC

    Test Name: Tyk Cloud Accounts Status Code: 500 Status Text: Internal Server Error Check Rate: 30 We are currently experiencing issues affecting our dashboard and billing endpoints. Our team has identified that these disruptions are related to an ongoing incident with our CDN provider, Cloudflare (https://www.cloudflarestatus.com/incidents/8gmgl950y3h7). Impact: - Dashboard access may be unavailable or intermittent - Billing, login and signup endpoints are currently experiencing connectivity issues - Other services remain operational and unaffected What we're doing: Our engineering team is actively monitoring the situation. We are working to implement temporary mitigations where possible. Workaround: At this time, there is no available workaround. We appreciate your patience as we work to resolve this issue. We will continue to provide updates as more information becomes available.

  2. identified Nov 18, 2025, 12:57 PM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Nov 18, 2025, 03:43 PM UTC

    This incident has been resolved.

Read the full incident report →

Major November 18, 2025 [StatusCake] https://dashboard.cloud-ara.tyk.io status is Degraded 3h 40m Dashboard

Started Nov 18, 2025, 12:02 PM UTC· resolved Nov 18, 2025, 03:42 PM UTC

  1. investigating Nov 18, 2025, 12:02 PM UTC

    Test Name: Tyk Cloud Dashboard Status Code: 503 Status Text: Service was detected as Down. Check Rate: 30 We are currently experiencing issues affecting our dashboard and billing endpoints. Our team has identified that these disruptions are related to an ongoing incident with our CDN provider, Cloudflare (https://www.cloudflarestatus.com/incidents/8gmgl950y3h7). Impact: - Dashboard access may be unavailable or intermittent - Billing, login and signup endpoints are currently experiencing connectivity issues - Other services remain operational and unaffected What we're doing: Our engineering team is actively monitoring the situation. We are working to implement temporary mitigations where possible. Workaround: At this time, there is no available workaround. We appreciate your patience as we work to resolve this issue. We will continue to provide updates as more information becomes available.

  2. identified Nov 18, 2025, 12:59 PM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Nov 18, 2025, 03:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 2, 2025 Tyk Cloud - Partial Service Degradation on Tyk Cloud in EU-west-2 3h 58m Dashboard, Controller at aws-eu-west-2, Billing

Started Nov 02, 2025, 02:01 PM UTC· resolved Nov 02, 2025, 06:00 PM UTC

  1. identified Nov 02, 2025, 02:01 PM UTC

    We are currently addressing an issue affecting parts of the Tyk Cloud platform related to database connectivity. Our team has identified the root cause and mitigation steps are in progress. Impact summary: • Existing customer deployments: Serving traffic normally; no impact expected. • New deployments: Functioning as expected. • Redeployments or updates: Operating normally. All systems are currently healthy, and no impact is expected for existing or new customer deployments. We continue to monitor service health closely as the fix is applied and expect full normalization shortly.

  2. monitoring Nov 02, 2025, 02:33 PM UTC

    All systems on the Tyk Cloud platform are currently operating normally. The earlier issue related to database connectivity has been fully mitigated.. Our team continues to closely monitor platform performance to ensure full recovery and stability. If no further issues are observed, this incident will be closed shortly.

  3. resolved Nov 02, 2025, 06:00 PM UTC

    Monitoring shows systems are stable. Incident Will be closed now.

Read the full incident report →

Minor October 23, 2025 Service Degradation for Customers Due to MongoDB Connection Issues on AP-SOUTHEAST-1 30m Dashboard, Controller at aws-ap-southeast-1

Started Oct 23, 2025, 06:30 AM UTC· resolved Oct 23, 2025, 07:00 AM UTC

  1. investigating Oct 23, 2025, 08:25 AM UTC

    We are experiencing MongoDB connection issues in the ap-southeast-1 region. This is affecting the availability of the Control Planes and access to the Tyk Cloud Dashboard for Customers in that region.

  2. resolved Oct 23, 2025, 08:27 AM UTC

    This incident has been resolved.

Read the full incident report →

Major October 3, 2025 [StatusCake] https://controller-aws-usw2.cloud-ara.tyk.io:37001/health status is Down 15h 13m Controller at aws-us-west-2

Started Oct 03, 2025, 01:03 AM UTC· resolved Oct 03, 2025, 04:16 PM UTC

  1. investigating Oct 03, 2025, 01:03 AM UTC

    Test Name: Tyk Cloud Controller aws-us-west-2 Status Code: 0 Status Text: Timeout / Connection Refused Check Rate: 60

  2. resolved Oct 03, 2025, 04:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 31, 2025 Service Degradation for Trialist Customers Due to Faulty Redis Nodes on US-EAST-1 5h 7m Controller at aws-us-east-1

Started Jul 31, 2025, 12:23 PM UTC· resolved Jul 31, 2025, 05:31 PM UTC

  1. identified Jul 31, 2025, 12:23 PM UTC

    We're currently experiencing Redis connection issues in the us-east-1 region due to faulty Kubernetes nodes hosting Redis. This is affecting the availability of MDCB and Gateway services, particularly for some trialist customers whose workloads are running on the impacted nodes. Our team is actively working to mitigate the issue and restore normal service.

  2. monitoring Jul 31, 2025, 03:56 PM UTC

    All redis issues have been fixed and we're monitoring the results

  3. resolved Jul 31, 2025, 05:31 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 13, 2025 [StatusCake] https://account.cloud-ara.tyk.io/signup status is Down 36s Billing

Started May 13, 2025, 09:25 PM UTC· resolved May 13, 2025, 09:25 PM UTC

  1. investigating May 13, 2025, 09:25 PM UTC

    Test Name: Tyk Cloud Accounts Status Code: 0 Status Text: Timeout / Connection Refused Check Rate: 30

  2. resolved May 13, 2025, 09:25 PM UTC

    This incident has been resolved.

Read the full incident report →