PortKey incident

Cache Collision (Now Resolved)

Minor Resolved View vendor source →

PortKey experienced a minor incident on July 22, 2025 affecting Portkey (SaaS AI Gateway), lasting —. The incident has been resolved; the full update timeline is below.

Started
Jul 22, 2025, 11:32 PM UTC
Resolved
Jul 22, 2025, 11:32 PM UTC
Duration
—
Detected by Pingoru
Jul 22, 2025, 11:32 PM UTC

Affected components

Portkey (SaaS AI Gateway)

Update timeline

  1. resolved Jul 22, 2025, 11:32 PM UTC

    While working to fix some caching issues yesterday, we inadvertently introduced a bug that caused erroneous cache collisions. This issue may have affected your requests that had cache enabled. If you were using different metadata or cache namespaces, your requests were properly isolated and unaffected from this bug. Please Note: - The collisions did not happen between cache partitions - The collisions did not happen across accounts The issue has been fully reverted as of Jul 23, 2025 3:23 UTC. Our team is actively monitoring the system to ensure stability. We are sorry for this!