Status and alerts are provided according to service endpoints or API.
Subscribe above to get up to minute alert notifications on any service interruption.
Resolved -
This incident has been resolved.
Jun 20, 15:06 UTC
Investigating -
We are experiencing an instance failure. This may affect resources that have the following pattern in their endpoint: c60
Jun 20, 14:56 UTC
Resolved -
This incident has been resolved.
Jun 15, 10:08 UTC
Investigating -
We’re currently performing periodic maintenance for the Redis Cloud admin console, which may impact your access to it (cloud.redis.io). Your database’s connectivity is not affected.
Jun 15, 09:53 UTC
Resolved -
This incident has been resolved.
Jun 14, 07:31 UTC
Investigating -
We are experiencing an instance failure. This may affect resources that have the following pattern in their endpoint: c1
Jun 14, 06:55 UTC
Resolved -
The global outage on Google Cloud Platform (GCP) has now been fully resolved. All affected Redis Cloud services have now fully recovered.
At no point was database connectivity or availability were affected.
We appreciate your patience and understanding during this incident.
Jun 12, 23:34 UTC
Update -
Google Cloud Platform (GCP) has reported that most affected services have now recovered. As a result, access to the Redis Cloud API, Heroku and Vercel integrations, and the Redis documentation portal is steadily improving.
Database connectivity and availability continue to function normally and remain fully accessible.
We will provide a final update once the issue is fully resolved.
Jun 12, 21:23 UTC
Monitoring -
Redis Cloud is currently experiencing a service disruption due to a global outage reported by Google Cloud Platform (GCP). This is affecting several components of our platform, including:
- Redis Cloud API - Heroku and Vercel integrations - Documentation portal - Scaling and provisioning of new subscriptions
At this time, database connectivity and availability are functioning normally, and remain accessible and unaffected.
We are actively monitoring the situation and working with GCP to resolve the issue. Updates will be posted here as more information becomes available.