Portkey
AI. Source: Portkey status page.
History starts 2026-08-14 13:50 UTC, the oldest incident this status page still shows. Figures for the last 90 days cover only the part since then.
- Incidents, last 90 days
- 2+
- Median to mitigation
- not reported
- Median to resolution
- 1h 25m
- p95 to resolution
- 2h 10m
- Naming an upstream provider
- 0%
- With a postmortem on the status page
- 0%
What failed, last 90 days
| Exhausted memory, disk, CPU, queues, connection pools or quotas | 1 |
| Login, tokens, certificates or credentials failed | 1 |
Tagged by claude-haiku-5-5 from each incident's updates. See the methodology.
Incidents per month
Hatched months are before the recorded history starts.
All recorded incidents
Control Plane Slowness
Affected: Saas Control Plane, AI Gateway
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
degraded
We're seeing control plane slowness and dashboard failures. Data plane queries to control plane (for non-cached queries) were failling intermittently.
-
degraded
The trend is stabilizing, we're monitoring
-
degraded
Seeing higher spikes for slowness and failed requests again, we're triangulating the root cause,
-
degraded
We've identified the root cause for the slowness. This looks like a cache overload issue on the control plane.
-
resolved
We've resolved the issue, and are monitoring now
Excerpts are shortened. Read the full incident on Portkey's status page.
JWKS URLs Inaccessible
Affected: Saas Control Plane, AI Gateway
Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
degraded
Some JWKS URLs are inaccessible from the Management plane infrastructure. The team is working to identify the root cause.
-
resolved
All services are up, we're monitoring and will publish an analysis soon.
Excerpts are shortened. Read the full incident on Portkey's status page.