DownForAI

Portkey status: API, auth, latency & outage reports

Portkey is operational right now. DownForAI checks Portkey every ~75 minutes across 1 monitored surface, with 0 community reports in the last 24 hours.

Operational
Last probe 3h ago·1 surface
Probe-monitoredMedium confidence
📡 Official status page →📚 Docs →💳 Pricing →
100.0%
24h Uptime
508ms
p50 Network Latency
697ms
p95 Network Latency
0
Incidents (30d)

DownForAI monitors Portkey via a single endpoint — Portkey Web. Current status: operational — all surfaces are responding normally. Measured uptime over the last 24 hours: 100.0%. Median response time (24 h): 508 ms; p95: 697 ms.

No incidents have been logged for Portkey, and no community reports were received in the last 24 hours. Probes run continuously across the configured surfaces.

Data confidence: MediumLast checked 3h 44m ago · 1 monitored surface · 1 with 24 h latency data

Current Status

Operational
Everything works normally
Checked by our probes · 425ms
Verified 3h ago
No major incident reported
No reports in the last 24h

Having issues?

Help other users by reporting if Portkey is not working for you.

0reports in the last 24 hours

Surface Health

Portkey WebOperational
HTTP 200p50 508ms3h ago

Uptime — last 24h

100.0%

Network latency — last 20 probes

Loading…

What DownForAI can verify about Portkey

No confirmed provider-side issue detected
DownForAI currently sees Portkey as operational based on available monitoring signals.
Signal source: official status page · Monitoring confidence: Medium
Still having trouble?

The issue may be account-specific, regional, network-related, or related to authentication, billing, quota, or rate limits.

Incident history (30d)

No incidents recorded in the past 30 days.

Reported symptoms

No user reports for Portkey in the last 24 hours.

Known error signatures

Common failure patterns and how to diagnose them

Provider details

Portkey is an AI gateway and observability platform: requests route through Portkey to 200+ providers with fallbacks, caching, guardrails and logs, hosted or self-hosted, with a status page. On the request path, its incidents can block traffic unless you fail over.

What we monitor
Portkey gatewayRequest path
Dashboard and logsObservability
Upstream providersBehind the gateway
Ecosystem dependencies
Model providers

Fallback alternatives

What to use if this service is down

Portkey is down
LiteLLM or AI Gateway (monitored on DownForAI) are alternative gateways; direct calls bypass it
Easy switch

How we monitor

DownForAI checks monitored AI service surfaces on a rotating schedule, roughly every 75 minutes per surface, from a single centralized probe infrastructure. For services with an official machine-readable status page, we use that official status signal when available. For other services, we perform a basic public-surface check. Some services block datacenter probes; in those cases we mark them as “Monitoring limited” instead of treating a failed probe as a confirmed outage. Status is classified as Operational, Degraded, or Outage. Network latency (check response time) measures how long the monitored endpoint took to respond to our probe — it is not model inference speed, time-to-first-token, or tokens-per-second performance. We are independent of all providers listed and receive no compensation to report any particular status.

Portkey statusEmbed this status badgeREADME · docs ▾
Markdown
[![Portkey status](https://downforai.com/api/badge/portkey.svg)](https://downforai.com/portkey)
HTML
<a href="https://downforai.com/portkey"><img src="https://downforai.com/api/badge/portkey.svg" alt="Portkey status" /></a>

Community Discussion

0/1000
No comments yet. Be the first to share your experience!

Still having issues with Portkey?

Let the community know and help others experiencing the same problem.