Batch API degraded since March 4 — stuck at 0 progress, expiring after partial completion

We’ve been experiencing Batch API degradation since March 4, 2026. The issue started with abnormally slow processing and has escalated to batches making zero progress.

Timeline:

1. March 4, 12:43 UTC — Batch batch_69a828e39a4081908428434be28a1df6 (60 requests) completed successfully. Last known good batch.
2. March 4, 13:45 UTC — Batch batch_69a83760285c81909fb8f58a466b4309 (102 requests) started processing noticeably slower than usual. Only completed 50/102 requests before expiring after the 24-hour window. No errors reported — just ran out of time.
3. March 5, 14:15 UTC — Resubmitted as batch batch_69a98fe7451c81908a36e4f41e902944 (102 requests). Sat at 0/102 with no progress. Manually cancelled.
4. March 5, 19:25 UTC — Resubmitted again as batch batch_69a9d8b5a29881909e073eef0d4f68b5 (60 requests, smaller payload). Currently stuck at 0/60 completed, 0 failed. No errors, no progress.

Pattern:

• Started as slow processing (March 4), now escalated to zero progress (March 5)
• No error messages returned on any batch — they either silently expire or sit indefinitely at 0
• Smaller batches (60 requests) completed fine on March 4 but are now also stuck
• Using /v1/responses endpoint with structured output

Environment:

• Endpoint: /v1/responses
• Request sizes: 60–102 requests per batch
• JSONL format validated, same format that completed successfully on March 3–4

Is anyone else seeing similar degradation since March 4? Is there a known issue with batch queue processing?