Suno degradation — 2026-08-11
Server error 500 It began at 2026-08-11 20:03 UTC and recovered at 2026-08-11 20:24 UTC, lasting 21 min. We recorded 7 failing checks during the window.
Check-by-check timeline
- 2026-08-11 19:51 UTCOperational188ms · HTTP 200
- 2026-08-11 19:54 UTCOperational196ms · HTTP 200
- 2026-08-11 19:57 UTCOperational137ms · HTTP 200
- 2026-08-11 20:00 UTCDegraded221ms · HTTP 500Server error 500
- 2026-08-11 20:03 UTCDegraded198ms · HTTP 500Server error 500
- 2026-08-11 20:06 UTCDegraded214ms · HTTP 500Server error 500
- 2026-08-11 20:09 UTCDegraded359ms · HTTP 500Server error 500
- 2026-08-11 20:12 UTCDegraded154ms · HTTP 500Server error 500
- 2026-08-11 20:15 UTCDegraded166ms · HTTP 500Server error 500
- 2026-08-11 20:18 UTCDegraded149ms · HTTP 500Server error 500
- 2026-08-11 20:21 UTCOperational304ms · HTTP 200
- 2026-08-11 20:24 UTCOperational174ms · HTTP 200
- 2026-08-11 20:27 UTCOperational229ms · HTTP 200
- 2026-08-11 20:30 UTCOperational135ms · HTTP 200
- 2026-08-11 20:33 UTCOperational159ms · HTTP 200
- 2026-08-11 20:36 UTCOperational189ms · HTTP 200
- 2026-08-11 20:39 UTCOperational187ms · HTTP 200
Current Suno status and full outage history
How this is measured
Readings are taken every few minutes from outside Suno's network, combining their published status feed with a timed request to the service itself.
An incident opens after two consecutive bad readings and closes after two consecutive good ones, so the recorded duration may be a few minutes wider than the true outage.