51 incidente Tyk înregistrate începând din mai 2023, cu actualizări oficiale, componente afectate, durată și informații despre rezolvare.
We are currently investigating an issue preventing to access dashboard on some of the USE1 organisations.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Traducere automată din actualizarea oficială a incidentului.
Test Name: Tyk Cloud Controller aws-us-east-1 Status Code: 0 Status Text: Timeout / Connection Refused Check Rate: 60
This incident has been resolved.
Test Name: Tyk Cloud Controller aws-us-east-1 Status Code: 0 Status Text: Timeout / Connection Refused Check Rate: 60
This incident has been resolved.
Test Name: Tyk Cloud Controller aws-us-east-1 Status Code: 0 Status Text: Timeout / Connection Refused Check Rate: 60
This incident has been resolved.
Test Name: Tyk Cloud Controller aws-us-east-1 Status Code: 0 Status Text: Timeout / Connection Refused Check Rate: 60
This incident has been resolved.
Test Name: Tyk Cloud Dashboard Status Code: 0 Status Text: Timeout / Connection Refused Check Rate: 30
This incident has been resolved.
Test Name: Tyk Cloud Dashboard Status Code: 0 Status Text: Timeout / Connection Refused Check Rate: 30
This incident has been resolved.
Test Name: Tyk Cloud Controller aws-us-east-1 Status Code: 503 Status Text: Service was detected as Down. Check Rate: 60
This incident has been resolved.
Test Name: Tyk Cloud Controller aws-eu-central-1 Status Code: 0 Status Text: Timeout / Connection Refused Check Rate: 60
This incident has been resolved.
Test Name: Tyk Cloud Controller aws-eu-central-1 Status Code: 0 Status Text: Timeout / Connection Refused Check Rate: 60
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue
This incident has been resolved.
We are currently investigating an issue on the dashboard preventing the users to display their organizations correctly.N
The issue has been identified and a fix was applied
This incident has been resolved.
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.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
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.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
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.
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.
Monitoring shows systems are stable. Incident Will be closed now.
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.
This incident has been resolved.
Test Name: Tyk Cloud Controller aws-us-west-2 Status Code: 0 Status Text: Timeout / Connection Refused Check Rate: 60
This incident has been resolved.
Test Name: Tyk Cloud Controller aws-us-west-2 Status Code: 0 Status Text: Timeout / Connection Refused Check Rate: 60
This incident has been resolved.
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.
All redis issues have been fixed and we're monitoring the results
This incident has been resolved.
