Scaleway
Status impact color legend
  • Black impact: None
  • Yellow impact: Minor
  • Red impact: Major
  • Blue impact: Maintenance

[COCKPIT] Cockpit Scaleway Logs have high latencies on fr-par

Incident Report for Scaleway

Resolved

The status is still in progress and the follow-up is done on the https://status.scaleway.com/incidents/m2jj2crt1sfn status, which will now be the reference status.

Our engineers are still working to resolve this situation
Posted May 16, 2024 - 09:54 CEST

Update

Slowdowns have resumed since 17:00.

Our team is currently investigating.
Posted May 07, 2024 - 17:42 CEST

Update

Some customers may find it impossible to display their data. Our teams are currently investigating the situation.
Posted May 03, 2024 - 20:16 CEST

Update

A bad index was found and fixed, services are back to normal. Will monitor.
Posted May 03, 2024 - 16:09 CEST

Update

We are continuing to investigate this issue.
Posted May 03, 2024 - 16:08 CEST

Update

Latency is back to normal for most query but query_range are still high latency, investigating
Posted May 02, 2024 - 17:52 CEST

Investigating

Cockpit Logs cluster at fr-par is suffering and have high latencies.

Query to Scaleway generated logs may have timeouts

Our engineers are working on it
Posted May 02, 2024 - 16:33 CEST
This incident affected: Elements - Products (Kubernetes Kapsule, Serverless Functions and Containers, Jobs, Databases, Observability).
← Current Status Powered by Atlassian Statuspage