PortKey incident

Brief degradation in budget-related API functionality

Resolved after 1 hour 40 minutes, affecting section-164755 (Saas Control Plane) and section-164755 (Saas Control Plane), on April 30, 2026.

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.

Started
Apr 30, 2026, 06:20 AM UTC
Resolved
Apr 30, 2026, 08:00 AM UTC
Duration
1h 40m
Detected by Pingoru
Apr 30, 2026, 06:20 AM UTC

Affected components

section-164755 (Saas Control Plane)section-164755 (Saas Control Plane)

Update timeline

  1. 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.

  2. 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.

Your product runs on more than PortKey

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →