DeepSeek 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, Mumbai, San Francisco, Singapore, Tokyo, Montreal

      , lasted 2.5 hours · peak 1.46 s, usually 793 ms

      What happened →
    2. Slower than usualAmsterdam, Mumbai, Singapore

      , lasted 90 minutes · peak 1.14 s, usually 746 ms

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

      , lasted 6.5 hours · peak 14.24 s, usually 769 ms

      What happened →
    1. Slower than usualSingapore

      , lasted 90 minutes · peak 810 ms, usually 539 ms

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

      , lasted 2.5 hours · peak 1.33 s, usually 725 ms

      What happened →
    1. Slower than usualSan Francisco, Singapore, Tokyo

      , lasted 3.5 hours · peak 1.09 s, usually 717 ms

      What happened →
    1. Slower than usualMumbai, Singapore, Tokyo

      , lasted 2 hours · peak 1.50 s, usually 631 ms

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

      , lasted 2 hours · peak 1.67 s, usually 741 ms

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

      , lasted 3.5 hours · peak 824 ms, usually 713 ms

      What happened →

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