Incident history

Slowdowns and failures our checks confirmed over the last 7 days, newest first. Shorter slow spells show on each service's own page.

    1. DeepSeek APISlower than usualAmsterdam, Mumbai, Singapore, Tokyo, Montreal

      , lasted 3 hours · peak 1.45 s, usually 817 ms

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

      , lasted 5 hours · peak 3.28 s, usually 1.14 s

      What happened →
    2. Cloudflare ClefSlower than usualMumbai, San Francisco, Singapore, Tokyo, Montreal

      , lasted 6.5 hours · peak 951 ms, usually 515 ms

      What happened →
    3. Claude APIDegradedAmsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal

      , lasted 11 hours · peak 4.98 s, usually 1.53 s

      What happened →
    4. ChatGPT APIDegradedAmsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal

      , lasted 5.5 hours · peak 3.03 s, usually 1.11 s

      What happened →
    5. Claude APISlower than usualAmsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal

      , lasted 11 hours · peak 2.67 s, usually 1.56 s

      What happened →
    1. Cloudflare ClefSlower than usualMontreal

      , lasted 90 minutes · peak 545 ms, usually 266 ms

      What happened →
    2. Cloudflare ClefSlower than usualMontreal

      , lasted 4.5 hours · peak 474 ms, usually 269 ms

      What happened →
    3. Claude APIDegradedAmsterdam, San Francisco, Singapore, Tokyo, Montreal

      , lasted 9.5 hours · peak 2.21 s, usually 968 ms

      What happened →
    4. Mistral APISlower than usualMontreal

      , lasted 2.5 hours · peak 658 ms, usually 345 ms

      What happened →
    5. ChatGPT APIDegradedAmsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal

      , lasted 11 hours · peak 4.25 s, usually 1.07 s

      What happened →
    6. Claude APISlower than usualAmsterdam, San Francisco, Singapore, Tokyo, Montreal

      , lasted 10 hours · peak 2.04 s, usually 972 ms

      What happened →
    7. PyPI JSON APIDegradedMontreal

      , lasted 90 minutes · peak 330 ms, usually 17 ms

      What happened →
    1. ChatGPT APISlower than usualAmsterdam, San Francisco, Montreal

      , lasted 3.5 hours · peak 2.71 s, usually 1.02 s

      What happened →
    2. Claude APISlower than usualAmsterdam, San Francisco, Singapore, Tokyo, Montreal

      , lasted 11.5 hours · peak 2.16 s, usually 984 ms

      What happened →
    3. Claude APISlower than usualAmsterdam, San Francisco, Singapore, Tokyo, Montreal

      , lasted 2 hours · peak 2.13 s, usually 919 ms

      What happened →
    4. ChatGPT APIDegradedAmsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal

      , lasted 11.5 hours · peak 3.48 s, usually 1.31 s

      What happened →
    5. Claude APISlower than usualAmsterdam, San Francisco, Singapore, Tokyo, Montreal

      , lasted 5.5 hours · peak 1.96 s, usually 937 ms

      What happened →
    1. PyPI JSON APIDegradedMontreal

      , lasted 7 hours · peak 327 ms, usually 17 ms

      What happened →
    2. Claude APISlower than usualAmsterdam, San Francisco, Singapore, Tokyo, Montreal

      , lasted 3 hours · peak 2.01 s, usually 928 ms

      What happened →
    3. Claude APISlower than usualAmsterdam, San Francisco, Singapore, Tokyo, Montreal

      , lasted 3 hours · peak 1.72 s, usually 936 ms

      What happened →
    4. Claude APISlower than usualAmsterdam, San Francisco, Singapore, Tokyo, Montreal

      , lasted 2.5 hours · peak 1.85 s, usually 1.04 s

      What happened →
    5. PyPI JSON APIDegradedMontreal

      , lasted 90 minutes · peak 289 ms, usually 19 ms

      What happened →
    1. Claude APISlower than usualAmsterdam, San Francisco, Singapore, Tokyo, Montreal

      , lasted 6 hours · peak 2.48 s, usually 1.04 s

      What happened →
    2. Cloudflare ClefSlower than usualSan Francisco

      , lasted 2 hours · peak 522 ms, usually 322 ms

      What happened →
    3. Claude APISlower than usualAmsterdam, San Francisco, Singapore, Tokyo, Montreal

      , lasted 2 hours · peak 1.74 s, usually 982 ms

      What happened →
    4. Claude APISlower than usualAmsterdam, San Francisco, Singapore, Tokyo, Montreal

      , lasted 4 hours · peak 2.13 s, usually 982 ms

      What happened →
    5. Claude APISome requests failedAmsterdam, San Francisco, Singapore, Tokyo, Montreal

      , lasted 4.5 hours · peak 1.97 s, usually 858 ms

      What happened →
    6. Mistral APISome requests failedAmsterdam, Singapore, Montreal

      , lasted 3 hours · peak 614 ms, usually 357 ms

      What happened →
    7. Claude APISlower than usualAmsterdam, San Francisco, Singapore, Tokyo, Montreal

      , lasted 2.5 hours · peak 2.07 s, usually 868 ms

      What happened →
    1. Claude APISlower than usualAmsterdam, San Francisco, Montreal

      , lasted 90 minutes · peak 1.83 s, usually 982 ms

      What happened →
    2. Cloudflare ClefSlower than usualTokyo

      , lasted 3.5 hours · peak 730 ms, usually 366 ms

      What happened →
    3. Claude APISlower than usualAmsterdam, San Francisco, Singapore, Tokyo, Montreal

      , lasted 5 hours · peak 1.92 s, usually 1.02 s

      What happened →
    4. Claude APISlower than usualAmsterdam, San Francisco, Singapore, Tokyo, Montreal

      , lasted 2.5 hours · peak 1.81 s, usually 1.01 s

      What happened →
    5. Claude APISlower than usualAmsterdam, San Francisco, Singapore, Tokyo, Montreal

      , lasted 4.5 hours · peak 1.77 s, usually 1.05 s

      What happened →
    1. Cloudflare ClefSlower than usualTokyo

      , lasted 90 minutes · peak 558 ms, usually 368 ms

      What happened →
    2. Cloudflare ClefSlower than usualMumbai, Tokyo, Montreal

      , lasted 2.5 hours · peak 1.09 s, usually 553 ms

      What happened →
    3. Claude APIDegradedAmsterdam, San Francisco, Singapore, Tokyo, Montreal

      , lasted 3.5 hours · peak 1.97 s, usually 756 ms

      What happened →
    4. Claude APIDegradedAmsterdam, San Francisco, Singapore, Tokyo, Montreal

      , lasted 4 hours · peak 2.26 s, usually 1.10 s

      What happened →

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.