Affected components
Update timeline
- investigating Apr 30, 2026, 06:20 AM UTC
An upstream code change impacted the budget functonality for a few minutes.
- investigating Apr 30, 2026, 06:20 AM UTC
An upstream code change caused a brief degradation in Portkey’s budget-related API functionality. During this window, requests depending on budget evaluation or enforcement may have experienced unexpected behavior. Core API routing remained operational, and Logs were not affected. The change has been identified and mitigated. We are continuing to monitor API behavior to ensure full stability.
- resolved Apr 30, 2026, 08:00 AM UTC
The brief degradation affecting budget-related API functionality has been resolved. The issue was caused by an upstream code change and affected requests relying on budget evaluation or enforcement. Core API routing remained available throughout, and Logs were not affected. We have mitigated the change, verified recovery, and will continue monitoring to ensure stability.
Looking to track PortKey downtime and outages?
Pingoru polls PortKey's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when PortKey reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track PortKey alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required