Query Caching - Degraded Performance
This incident has been resolved
This incident has been resolved
This incident has been resolved.
This incident has been resolved and our ticketing system is fully operational. Thank you for your patience.
Between approximately 12:30 UTC and 13:15 UTC, k6 Cloud experienced a service disruption due to issues introduced in a recent API release. During this time, users were unable to access the k6 Cloud application. The issue was mitigated by reverting the release, and service has since been fully restored.
There was a period of write instability yesterday. It was between ~1330 -1730 UTC yesterday. This was due to a scheduled maintenance.
This incident is now resolved. We had intermediary issues with a flaky DNS server that caused random tests to not start properly. Since the DNS server was fixed, we haven't been seeing the issue anymore.
This incident has been resolved.
This incident has been resolved. Thank you for your patience.
This incident has been resolved. Thank you for your patience.
We had a stability issue for a subset of customers in the prod-gb-south-1 region. The impact was between UTC 15:20-16:30 which impacted roughly 30% of queries and rules evaluations. We've applied mitigations, queries should be back to normal.