Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Cronologia delle interruzioni di Tyk

    51 Tyk incidents · maggio 2023 — official updates, affected components, duration and resolution details.

    Torna allo stato attuale

    USE regione attività degradate

    Inizio 14 agosto 2026 alle ore 17:35 UTC · 1h 10m

    IssuesIncidente minore
    Componenti interessati
    Dashboard
    1. 14 agosto 2026 alle ore 17:35 UTCinvestigating

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

    2. 14 agosto 2026 alle ore 17:55 UTCidentified

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

    3. 14 agosto 2026 alle ore 18:03 UTCmonitoring

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

    4. 14 agosto 2026 alle ore 18:46 UTCresolved

      This incident has been resolved.

    Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

    [StatusCake] https://controller-aws-use1.cloud-ara.tyk.io:37001/health status is Down

    Inizio 9 luglio 2026 alle ore 14:32 UTC · 1m

    OutageIncidente maggiore
    Componenti interessati
    Controller at aws-us-east-1
    1. 9 luglio 2026 alle ore 14:32 UTCinvestigating

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

    2. 9 luglio 2026 alle ore 14:33 UTCresolved

      This incident has been resolved.

    [StatusCake] https://controller-aws-use1.cloud-ara.tyk.io:37001/health status is Down

    Inizio 9 luglio 2026 alle ore 11:56 UTC · 4m

    OutageIncidente maggiore
    Componenti interessati
    Controller at aws-us-east-1
    1. 9 luglio 2026 alle ore 11:56 UTCinvestigating

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

    2. 9 luglio 2026 alle ore 11:59 UTCresolved

      This incident has been resolved.

    [StatusCake] https://controller-aws-use1.cloud-ara.tyk.io:37001/health status is Down

    Inizio 8 luglio 2026 alle ore 17:39 UTC · 4m

    OutageIncidente maggiore
    Componenti interessati
    Controller at aws-us-east-1
    1. 8 luglio 2026 alle ore 17:39 UTCinvestigating

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

    2. 8 luglio 2026 alle ore 17:43 UTCresolved

      This incident has been resolved.

    [StatusCake] https://controller-aws-use1.cloud-ara.tyk.io:37001/health status is Down

    Inizio 1 luglio 2026 alle ore 11:07 UTC · 1m

    OutageIncidente maggiore
    Componenti interessati
    Controller at aws-us-east-1
    1. 1 luglio 2026 alle ore 11:07 UTCinvestigating

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

    2. 1 luglio 2026 alle ore 11:09 UTCresolved

      This incident has been resolved.

    [StatusCake] https://dashboard.cloud-ara.tyk.io status is Down

    Inizio 11 giugno 2026 alle ore 10:58 UTC · 11m

    OutageIncidente maggiore
    Componenti interessati
    Dashboard
    1. 11 giugno 2026 alle ore 10:58 UTCinvestigating

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

    2. 11 giugno 2026 alle ore 11:08 UTCresolved

      This incident has been resolved.

    [StatusCake] https://dashboard.cloud-ara.tyk.io status is Down

    Inizio 20 maggio 2026 alle ore 10:14 UTC · 2m

    OutageIncidente maggiore
    Componenti interessati
    Dashboard
    1. 20 maggio 2026 alle ore 10:14 UTCinvestigating

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

    2. 20 maggio 2026 alle ore 10:17 UTCresolved

      This incident has been resolved.

    [StatusCake] https://controller-aws-use1.cloud-ara.tyk.io:37001/health status is Down

    Inizio 23 aprile 2026 alle ore 11:09 UTC · 2m

    OutageIncidente maggiore
    Componenti interessati
    Controller at aws-us-east-1
    1. 23 aprile 2026 alle ore 11:09 UTCinvestigating

      Test Name: Tyk Cloud Controller aws-us-east-1 Status Code: 503 Status Text: Service was detected as Down. Check Rate: 60

    2. 23 aprile 2026 alle ore 11:11 UTCresolved

      This incident has been resolved.

    [StatusCake] https://controller-aws-euc1.cloud-ara.tyk.io:37001/health status is Down

    Inizio 19 aprile 2026 alle ore 09:53 UTC · 4m

    OutageIncidente maggiore
    Componenti interessati
    Controller at aws-eu-central-1
    1. 19 aprile 2026 alle ore 09:53 UTCinvestigating

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

    2. 19 aprile 2026 alle ore 09:57 UTCresolved

      This incident has been resolved.

    [StatusCake] https://controller-aws-euc1.cloud-ara.tyk.io:37001/health status is Down

    Inizio 17 aprile 2026 alle ore 00:41 UTC · 8m

    OutageIncidente maggiore
    Componenti interessati
    Controller at aws-eu-central-1
    1. 17 aprile 2026 alle ore 00:41 UTCinvestigating

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

    2. 17 aprile 2026 alle ore 00:49 UTCresolved

      This incident has been resolved.

    USE-1 Region Operations Degraded

    Inizio 12 marzo 2026 alle ore 17:45 UTC · 30m

    OutageIncidente maggiore
    Componenti interessati
    DashboardController at aws-us-east-1
    1. 12 marzo 2026 alle ore 17:45 UTCinvestigating

      We are currently investigating this issue.

    2. 12 marzo 2026 alle ore 18:03 UTCmonitoring

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

    3. 12 marzo 2026 alle ore 18:16 UTCresolved

      This incident has been resolved.

    APSE1 Region degraded

    Inizio 1 marzo 2026 alle ore 19:19 UTC · 3h 4m

    IssuesIncidente minore
    Componenti interessati
    DashboardController at aws-ap-southeast-1
    1. 1 marzo 2026 alle ore 19:19 UTCinvestigating

      We are currently investigating this issue

    2. 1 marzo 2026 alle ore 22:23 UTCresolved

      This incident has been resolved.

    https://dashboard.cloud-ara.tyk.io status is degraded

    Inizio 21 gennaio 2026 alle ore 00:05 UTC · 2h 3m

    OutageIncidente maggiore
    Componenti interessati
    Dashboard
    1. 21 gennaio 2026 alle ore 00:05 UTCinvestigating

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

    2. 21 gennaio 2026 alle ore 01:04 UTCidentified

      The issue has been identified and a fix was applied

    3. 21 gennaio 2026 alle ore 02:07 UTCresolved

      This incident has been resolved.

    [StatusCake] https://account.cloud-ara.tyk.io/signup status is Degraded

    Inizio 18 novembre 2025 alle ore 12:38 UTC · 3h 4m

    OutageIncidente maggiore
    Componenti interessati
    Billing
    1. 18 novembre 2025 alle ore 12:38 UTCinvestigating

      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. 18 novembre 2025 alle ore 12:57 UTCidentified

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

    3. 18 novembre 2025 alle ore 15:43 UTCresolved

      This incident has been resolved.

    [StatusCake] https://dashboard.cloud-ara.tyk.io status is Degraded

    Inizio 18 novembre 2025 alle ore 12:02 UTC · 3h 40m

    OutageIncidente maggiore
    Componenti interessati
    Dashboard
    1. 18 novembre 2025 alle ore 12:02 UTCinvestigating

      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. 18 novembre 2025 alle ore 12:59 UTCidentified

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

    3. 18 novembre 2025 alle ore 15:42 UTCresolved

      This incident has been resolved.

    Tyk Cloud - Partial Service Degradation on Tyk Cloud in EU-west-2

    Inizio 2 novembre 2025 alle ore 14:01 UTC · 3h 59m

    Pending
    Componenti interessati
    Controller at aws-eu-west-2DashboardBilling
    1. 2 novembre 2025 alle ore 14:01 UTCidentified

      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. 2 novembre 2025 alle ore 14:33 UTCmonitoring

      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. 2 novembre 2025 alle ore 18:00 UTCresolved

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

    Service Degradation for Customers Due to MongoDB Connection Issues on AP-SOUTHEAST-1

    Inizio 23 ottobre 2025 alle ore 06:30 UTC · 31m

    IssuesIncidente minore
    Componenti interessati
    DashboardController at aws-ap-southeast-1
    1. 23 ottobre 2025 alle ore 08:25 UTCinvestigating

      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. 23 ottobre 2025 alle ore 08:27 UTCresolved

      This incident has been resolved.

    [StatusCake] https://controller-aws-usw2.cloud-ara.tyk.io:37001/health status is Down

    Inizio 3 ottobre 2025 alle ore 01:03 UTC · 15h 13m

    OutageIncidente maggiore
    Componenti interessati
    Controller at aws-us-west-2
    1. 3 ottobre 2025 alle ore 01:03 UTCinvestigating

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

    2. 3 ottobre 2025 alle ore 16:16 UTCresolved

      This incident has been resolved.

    [StatusCake] https://controller-aws-usw2.cloud-ara.tyk.io:37001/health status is Down

    Inizio 19 settembre 2025 alle ore 10:40 UTC · 4m

    OutageIncidente maggiore
    Componenti interessati
    Controller at aws-us-west-2
    1. 19 settembre 2025 alle ore 10:40 UTCinvestigating

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

    2. 19 settembre 2025 alle ore 10:43 UTCresolved

      This incident has been resolved.

    Service Degradation for Trialist Customers Due to Faulty Redis Nodes on US-EAST-1

    Inizio 31 luglio 2025 alle ore 12:23 UTC · 5h 8m

    IssuesIncidente minore
    Componenti interessati
    Controller at aws-us-east-1
    1. 31 luglio 2025 alle ore 12:23 UTCidentified

      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. 31 luglio 2025 alle ore 15:56 UTCmonitoring

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

    3. 31 luglio 2025 alle ore 17:31 UTCresolved

      This incident has been resolved.