Live  /  Redis  /  Incident

Redis: LangCache Endpoint Issues in GCP us-east4 Region

Redis · redis.ioMinor incidentResolved2026-06-07 13:08 UTC
Public — what happened

Summary

Redis reported a minor incident affecting some LangCache deployments hosted in Google Cloud's us-east4 region, which it described as endpoint issues. The problem began on 2026-06-07 at 13:08 UTC, and Redis said LangCache deployments in other regions and on other cloud providers were not impacted. Redis did not publicly name a cause. It marked the incident resolved on 2026-06-09 at 21:02, ending public updates and saying any remaining fixes would be handled through follow-up work.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Redis against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Redis: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Redis report →

More from Redis

The full archive is on the Redis status & history page.

Related: Redis status & history. SquidGrid is not affiliated with Redis.