Outage history

Midjourney Outage History

Recent incidents Midjourney has published, newest first, with how long each one lasted.

0in the last 30 days
0in the last 90 days
16h 38mlongest outage
18 Jun 2026most recent

Showing 40 published incidents back to 30 May 2024.

  1. Minor18 Jun 20261h 30m

    Jobs are queuing

  2. Minor5 Jun 202611 min

    v8 jobs queueing

  3. Minor19 May 202636 min

    Jobs are queueing

  4. Critical13 May 20269 min

    Discord Bot is down

  5. Minor10 May 20263h 56m

    V8 jobs running slow

  6. Minor7 May 202614h 49m

    Jobs are backed up

  7. Minor26 Feb 202611 min

    Some job types are seeing long delays

  8. Major19 Feb 202625 min

    Elevated error rate across editor, video creation and similar features

  9. Critical12 Feb 202615 min

    Job processing issue

  10. Minor12 Feb 202633 min

    Jobs are running slowly

  11. Major14 Oct 20251h 32m

    Jobs are seeing long delays

  12. Critical11 Oct 20254h 15m

    Jobs are queueing

  13. Major19 Sep 20254h 5m

    Several job types are experiencing delays

  14. Major1 Jul 20252h 26m

    Job submission errors due to a provider issue

  15. Critical26 Jun 202524 min

    Service Outage

  16. Critical12 Jun 20253h 40m

    Service outage

  17. Critical20 May 202516h 38m

    Errors with image generation

  18. Critical16 May 20252h 46m

    Service is unavailable

  19. Minor7 May 20253h 21m

    Turbo jobs queueing

  20. Critical29 Apr 202540 min

    Midjourney Outage

  21. Major17 Mar 20253h 7m

    Image generation errors

  22. Critical14 Feb 20259 min

    Job processing outage

  23. Minor12 Feb 202542 min

    Website slowness

  24. Critical24 Jan 202516 min

    Images not showing in discord

  25. Informational15 Jan 20251h 6m

    Billing of some jobs delayed

  26. Critical13 Jan 20252h 2m

    Availability issues with image generation

  27. Major24 Oct 20244h 8m

    Service Issues

  28. Critical26 Sep 20241h 21m

    Job processing slowdown

  29. Major10 Sep 20241h 53m

    /describe not working

  30. Minor8 Jul 202412 min

    Image generation queues backing up

  31. Minor23 Jun 20242h 25m

    Jobs failing to complete at 96%

  32. Informational20 Jun 202417 min

    Reframe Zoom does not maintain the correct aspect ratio

  33. Informational20 Jun 20246h 16m

    `/describe` is down

  34. Minor19 Jun 202428 min

    `/describe` is down

  35. Informational13 Jun 202435 min

    Login sessions are resetting on web

  36. Minor12 Jun 20243h 10m

    Website slowdown

  37. Informational7 Jun 20241 min

    Room images shown in create

  38. Minor6 Jun 202426 min

    Fast and Relax Jobs may be delayed in processing

  39. Minor4 Jun 202441 min

    Increased error rate due to Discord incident

  40. Major30 May 202441 min

    --sref + outpaints/pans are broken

What this record shows

Midjourney’s record goes back a long way and is sparse in recent months, which is a good sign rather than a gap in the data. Its incidents cluster around image-generation capacity and the Discord bot, the two places where load actually bites.

Much of what users report as Midjourney being down is the bot failing to respond in Discord. That can be a genuine platform incident, but it is just as often a Discord-side problem or a permissions issue in a particular server — neither of which would appear on this list.

Fast and Relax generation are reported as separate components, so a problem with one does not necessarily mean the other stopped.

How to read the durations

Each entry runs from when Image AI opened the incident to when it was marked resolved. That is a generous measure: an incident is usually opened once the problem is confirmed and closed after it has been stable for a while, so the window is wider than the period in which most people were actually affected.

Severity comes from the provider. Only major and critical entries count against the uptime figure on the Midjourney status page, because a minor incident normally means degraded performance for some users rather than the service being unavailable.

This list is limited to what the provider has published and still exposes. Providers cap how far their public feed reaches, so an empty stretch further back means the record has aged out, not that nothing happened.

🔗 Keep checking