Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Tyk 장애 기록

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

    현재 상태로 돌아가기

    USE-1 Region Operations Degraded

    시작 2026년 8월 14일 오후 5:35 UTC · 1h 10m

    Issues경미한 인시던트
    영향을 받은 구성 요소
    Dashboard
    1. 2026년 8월 14일 오후 5:35 UTCinvestigating

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

    2. 2026년 8월 14일 오후 5:55 UTCidentified

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

    3. 2026년 8월 14일 오후 6:03 UTCmonitoring

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

    4. 2026년 8월 14일 오후 6:46 UTCresolved

      This incident has been resolved.

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

    시작 2026년 7월 9일 오후 2:32 UTC · 1m

    Outage중대한 인시던트
    영향을 받은 구성 요소
    Controller at aws-us-east-1
    1. 2026년 7월 9일 오후 2:32 UTCinvestigating

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

    2. 2026년 7월 9일 오후 2:33 UTCresolved

      This incident has been resolved.

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

    시작 2026년 7월 9일 오전 11:56 UTC · 4m

    Outage중대한 인시던트
    영향을 받은 구성 요소
    Controller at aws-us-east-1
    1. 2026년 7월 9일 오전 11:56 UTCinvestigating

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

    2. 2026년 7월 9일 오전 11:59 UTCresolved

      This incident has been resolved.

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

    시작 2026년 7월 8일 오후 5:39 UTC · 4m

    Outage중대한 인시던트
    영향을 받은 구성 요소
    Controller at aws-us-east-1
    1. 2026년 7월 8일 오후 5:39 UTCinvestigating

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

    2. 2026년 7월 8일 오후 5:43 UTCresolved

      This incident has been resolved.

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

    시작 2026년 7월 1일 오전 11:07 UTC · 1m

    Outage중대한 인시던트
    영향을 받은 구성 요소
    Controller at aws-us-east-1
    1. 2026년 7월 1일 오전 11:07 UTCinvestigating

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

    2. 2026년 7월 1일 오전 11:09 UTCresolved

      This incident has been resolved.

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

    시작 2026년 6월 11일 오전 10:58 UTC · 11m

    Outage중대한 인시던트
    영향을 받은 구성 요소
    Dashboard
    1. 2026년 6월 11일 오전 10:58 UTCinvestigating

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

    2. 2026년 6월 11일 오전 11:08 UTCresolved

      This incident has been resolved.

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

    시작 2026년 5월 20일 오전 10:14 UTC · 2m

    Outage중대한 인시던트
    영향을 받은 구성 요소
    Dashboard
    1. 2026년 5월 20일 오전 10:14 UTCinvestigating

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

    2. 2026년 5월 20일 오전 10:17 UTCresolved

      This incident has been resolved.

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

    시작 2026년 4월 23일 오전 11:09 UTC · 2m

    Outage중대한 인시던트
    영향을 받은 구성 요소
    Controller at aws-us-east-1
    1. 2026년 4월 23일 오전 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. 2026년 4월 23일 오전 11:11 UTCresolved

      This incident has been resolved.

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

    시작 2026년 4월 19일 오전 9:53 UTC · 4m

    Outage중대한 인시던트
    영향을 받은 구성 요소
    Controller at aws-eu-central-1
    1. 2026년 4월 19일 오전 9:53 UTCinvestigating

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

    2. 2026년 4월 19일 오전 9:57 UTCresolved

      This incident has been resolved.

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

    시작 2026년 4월 17일 오전 12:41 UTC · 8m

    Outage중대한 인시던트
    영향을 받은 구성 요소
    Controller at aws-eu-central-1
    1. 2026년 4월 17일 오전 12:41 UTCinvestigating

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

    2. 2026년 4월 17일 오전 12:49 UTCresolved

      This incident has been resolved.

    USE-1 Region Operations Degraded

    시작 2026년 3월 12일 오후 5:45 UTC · 30m

    Outage중대한 인시던트
    영향을 받은 구성 요소
    DashboardController at aws-us-east-1
    1. 2026년 3월 12일 오후 5:45 UTCinvestigating

      We are currently investigating this issue.

    2. 2026년 3월 12일 오후 6:03 UTCmonitoring

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

    3. 2026년 3월 12일 오후 6:16 UTCresolved

      This incident has been resolved.

    APSE1 Region degraded

    시작 2026년 3월 1일 오후 7:19 UTC · 3h 4m

    Issues경미한 인시던트
    영향을 받은 구성 요소
    DashboardController at aws-ap-southeast-1
    1. 2026년 3월 1일 오후 7:19 UTCinvestigating

      We are currently investigating this issue

    2. 2026년 3월 1일 오후 10:23 UTCresolved

      This incident has been resolved.

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

    시작 2026년 1월 21일 오전 12:05 UTC · 2h 3m

    Outage중대한 인시던트
    영향을 받은 구성 요소
    Dashboard
    1. 2026년 1월 21일 오전 12:05 UTCinvestigating

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

    2. 2026년 1월 21일 오전 1:04 UTCidentified

      The issue has been identified and a fix was applied

    3. 2026년 1월 21일 오전 2:07 UTCresolved

      This incident has been resolved.

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

    시작 2025년 11월 18일 오후 12:38 UTC · 3h 4m

    Outage중대한 인시던트
    영향을 받은 구성 요소
    Billing
    1. 2025년 11월 18일 오후 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. 2025년 11월 18일 오후 12:57 UTCidentified

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

    3. 2025년 11월 18일 오후 3:43 UTCresolved

      This incident has been resolved.

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

    시작 2025년 11월 18일 오후 12:02 UTC · 3h 40m

    Outage중대한 인시던트
    영향을 받은 구성 요소
    Dashboard
    1. 2025년 11월 18일 오후 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. 2025년 11월 18일 오후 12:59 UTCidentified

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

    3. 2025년 11월 18일 오후 3:42 UTCresolved

      This incident has been resolved.

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

    시작 2025년 11월 2일 오후 2:01 UTC · 3h 59m

    Pending
    영향을 받은 구성 요소
    Controller at aws-eu-west-2DashboardBilling
    1. 2025년 11월 2일 오후 2: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. 2025년 11월 2일 오후 2: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. 2025년 11월 2일 오후 6: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

    시작 2025년 10월 23일 오전 6:30 UTC · 31m

    Issues경미한 인시던트
    영향을 받은 구성 요소
    DashboardController at aws-ap-southeast-1
    1. 2025년 10월 23일 오전 8: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. 2025년 10월 23일 오전 8:27 UTCresolved

      This incident has been resolved.

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

    시작 2025년 10월 3일 오전 1:03 UTC · 15h 13m

    Outage중대한 인시던트
    영향을 받은 구성 요소
    Controller at aws-us-west-2
    1. 2025년 10월 3일 오전 1:03 UTCinvestigating

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

    2. 2025년 10월 3일 오후 4:16 UTCresolved

      This incident has been resolved.

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

    시작 2025년 9월 19일 오전 10:40 UTC · 4m

    Outage중대한 인시던트
    영향을 받은 구성 요소
    Controller at aws-us-west-2
    1. 2025년 9월 19일 오전 10:40 UTCinvestigating

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

    2. 2025년 9월 19일 오전 10:43 UTCresolved

      This incident has been resolved.

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

    시작 2025년 7월 31일 오후 12:23 UTC · 5h 8m

    Issues경미한 인시던트
    영향을 받은 구성 요소
    Controller at aws-us-east-1
    1. 2025년 7월 31일 오후 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. 2025년 7월 31일 오후 3:56 UTCmonitoring

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

    3. 2025년 7월 31일 오후 5:31 UTCresolved

      This incident has been resolved.