Status: Resolved
One of our server nodes in our Kubernetes cluster was running with high CPU for all the pods provisioned on that node. We are unsure the cause at the moment (could be a noisy neighbour, could be hardware issues, etc) but we have removed that node which solved the issue.
Affected components
Status: Resolved
Latency has returned to normal levels.
Affected components
Status: Monitoring
Response times have recovered and we are monitoring the situation.
Affected components
Status: Identified
We are seeing elevated latency on the core Ravelin API. We have identified the issue and you should see latency coming down. We apologise for the issue.
Affected components
Status: Resolved
Our API was generating 500 errors for about six minutes due to a delay in configuration between services
Affected components
Status: Resolved
Our API was generating 500 errors for about six minutes due to a delay in configuration between services
Affected components
Status: Resolved
Our API was generating 500 errors for about six minutes due to a delay in configuration between services
Affected components
Status: Resolved
Our API was generating 500 errors for about six minutes due to a delay in configuration between services
Affected components
Status: Resolved
This incident has been resolved.
Affected components
Status: Resolved
This incident has been resolved.
Affected components