UI Features Disabled for Some Accounts
Portkey reported that some UI features did not work for paid accounts. The Saas Control Plane was affected. Portkey identified an internal job as the cause and rolled out a change. The incident is resolved and lasted 48 minutes.
State
Resolved
Started
Lasted
48 min
Worst impact
Degraded
Timeline
5 updatesDegraded
48 min 100%
Updates
Times in UTCAs posted by Portkey
The UI Features are back to normal. Please reach out if you still face challenges.
The UI change has been rolled out and the UI should be coming back to normal now. We're monitoring and will update once this is complete.
The UI change has been rolled out and the UI should be coming back to normal now.
We've identified the root cause as an internal job being run. The UI should return to normal very soon.
We've identified that some feature flags may be missing from the UI for paid customers. We're reviewing this internally.
Affected components
1Portkey in the last 90 days
Full historyIncidents in 90 days
1
Days with an incident
1
Median duration
48 min
This incident
About the median
Follow Portkey
Your coding agent knows when Portkey is down, and tells you when a failure is theirs, not yours. You can also get Portkey incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "portkey" and tell me if Portkey has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=portkey/feed subscribe https://outages.live/feed.xml?providers=portkeyFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane