User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
portkey.ai · AI
Is Portkey down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → portkey.ai—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
Our checks
Reaching it
Last checked 7 min ago. Last stored result reached it in 141 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 00 | 0 | 0.0 | 103 ms | 0 |
| Tue 02 | 0 | 0.0 | 67 ms | 0 |
| Tue 04 | 0 | 0.0 | 143 ms | 0 |
| Tue 06 | 0 | 0.0 | 123 ms | 0 |
| Tue 07 | 0 | 0.0 | 116 ms | 0 |
| Tue 09 | 0 | 0.0 | 136 ms | 0 |
| Tue 11 | 0 | 0.0 | 123 ms | 0 |
| Tue 13 | 0 | 0.0 | 122 ms | 0 |
| Tue 15 | 0 | 0.0 | 108 ms | 0 |
| Tue 17 | 0 | 0.0 | 138 ms | 0 |
| Tue 20 | 0 | 0.0 | 94 ms | 0 |
| Tue 22 | 0 | 0.0 | 144 ms | 0 |
| Wed 00 | 0 | 0.0 | 54 ms | 0 |
| Wed 02 | 0 | 0.0 | 164 ms | 0 |
| Wed 05 | 0 | 0.0 | 155 ms | 0 |
| Wed 07 | 0 | 0.0 | 147 ms | 0 |
| Wed 09 | 0 | 0.0 | 126 ms | 0 |
| Wed 11 | 0 | 0.0 | 110 ms | 0 |
| Wed 14 | 0 | 0.0 | 124 ms | 0 |
| Wed 16 | 0 | 0.0 | 122 ms | 0 |
| Wed 18 | 0 | 0.0 | 102 ms | 0 |
| Wed 21 | 0 | 0.0 | 151 ms | 0 |
| Wed 23 | 0 | 0.0 | 126 ms | 0 |
| Thu 01 | 0 | 0.0 | 65 ms | 0 |
| Thu 03 | 0 | 0.0 | 186 ms | 0 |
| Thu 05 | 0 | 0.0 | 145 ms | 0 |
| Thu 07 | 0 | 0.0 | 136 ms | 0 |
| Thu 09 | 0 | 0.0 | 50 ms | 0 |
| Thu 11 | 0 | 0.0 | 119 ms | 0 |
| Thu 13 | 0 | 0.0 | 61 ms | 0 |
| Thu 15 | 0 | 0.0 | 290 ms | 0 |
| Thu 18 | 0 | 0.0 | 100 ms | 0 |
| Thu 20 | 0 | 0.0 | 157 ms | 0 |
| Thu 22 | 0 | 0.0 | 144 ms | 0 |
| Fri 00 | 0 | 0.0 | 53 ms | 0 |
| Fri 02 | 0 | 0.0 | 50 ms | 0 |
| Fri 04 | 0 | 0.0 | 167 ms | 0 |
| Fri 06 | 0 | 0.0 | 134 ms | 0 |
| Fri 08 | 0 | 0.0 | 80 ms | 0 |
| Fri 09 | 0 | 0.0 | 146 ms | 0 |
| Fri 10 | 0 | 0.0 | 121 ms | 0 |
| Fri 11 | 0 | 0.0 | 122 ms | 0 |
| Fri 13 | 0 | 0.0 | 111 ms | 0 |
| Fri 15 | 0 | 0.0 | 161 ms | 0 |
| Fri 17 | 0 | 0.0 | 51 ms | 0 |
| Fri 19 | 0 | 0.0 | 114 ms | 0 |
| Fri 21 | 0 | 0.0 | 141 ms | 0 |
| Fri 23 | 0 | 0.0 | 141 ms | 0 |
Reliability
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Portkey badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Portkey yet. Outages of 10 minutes or more get their own page here.
Having trouble with Portkey?
One report per service every 10 minutes from this network. No account.
Follow Portkey
Get an email when Portkey goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Portkey alerts to Slack, Discord or a webhook — free.
About Portkey
We track Portkey (portkey.ai) as part of the AI group. Democratize and productionize Gen AI across your entire org with Portkey's suite of AI gateway, observability, guardrails, and prompt management modules.
Portkey publishes an official status page at status.portkey.ai; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 114 ms average, 50–167 ms range across 14 successful checks.
Questions
Is Portkey down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Portkey last down?
We have not recorded a public Portkey incident since monitoring began 8 days ago.
What is Portkey's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Portkey respond?
114 ms on average over the last 24 hours (50–167 ms).
Does Portkey have an official status page?
Yes, at https://status.portkey.ai.
Portkey not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Portkey here at once, the problem is on Portkey's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Portkey. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.