- Level
- confirmed
- Worst impact
- Partial outage
- SambaNova Cloud says
- 2025-04-19 15:37 to 16:18 UTC (41m)
- Down Index
- 18of 100
What to do
Check whether your product depends on SambaNova Cloud. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2025-04-19 17:50 UTC and 2025-04-19 15:30 UTC may need a replay.Subscribe to SambaNova Cloud's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=sambanova works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Root cause
Service was restored and the root cause is known and will be corrected.Read the postmortem
Updates from SambaNova Cloud 1
- resolved
Between approximately 08:37 - 09:18 PDT we suffered an access interruption to Deepseek, Llama 405B, QwQ,Mistral, and Whisper. Service was restored and the root cause is known and will be corrected.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-a14130f131
Is SambaNova Cloud still down?
No, this incident was resolved 2025-04-19 15:30 UTC. For SambaNova Cloud's live state, see https://down.guide/providers/sambanova.
How long did it last?
0m, from 2025-04-19 17:50 UTC to 2025-04-19 15:30 UTC, by the times SambaNova Cloud posted.
What caused it?
SambaNova Cloud wrote: "Service was restored and the root cause is known and will be corrected." The postmortem: https://stspg.io/rqzy69czlq7g
Where does this come from?
SambaNova Cloud's official status page, https://status.sambanova.ai, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.