ChatGPT API incidents in October 2026

Slowdowns and failures our checks confirmed, newest first. Shorter slow spells only show on the live status page.

    1. Slower than usualAmsterdam

      , lasted 2 hours · peak 2.91 s, usually 1.14 s

      What happened →
    1. Slower than usualMontreal

      , lasted 90 minutes · peak 1.86 s, usually 1.12 s

      What happened →
    1. Slower than usualAmsterdam, Mumbai, Singapore, Tokyo, Montreal

      , lasted 5.5 hours · peak 3.56 s, usually 1.58 s

      What happened →
    2. Slower than usualMontreal

      , lasted 90 minutes · peak 1.84 s, usually 1.12 s

      What happened →
    1. DegradedAmsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal

      , lasted 2 hours · peak 3.22 s, usually 1.20 s

      What happened →
    2. Slower than usualSan Francisco

      , lasted 90 minutes · peak 1.83 s, usually 1.10 s

      What happened →
    1. Slower than usualMumbai, San Francisco, Singapore, Montreal

      , lasted 2 hours · peak 2.51 s, usually 1.56 s

      What happened →
    2. Slower than usualAmsterdam, San Francisco, Tokyo

      , lasted 90 minutes · peak 2.27 s, usually 1.20 s

      What happened →

ChatGPT API status right now

How fast is your API around the world?

Run a free speed test from multiple cities and find out where your users are waiting. No setup, no account required.

Test my API

No account required · Takes about 30 seconds.