SambaCloud Outage History
9 incidents recorded over the last 365 days, 5 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded SambaCloud Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jun 25, 2026 | SambaNova Cloud login authentication is not functionalThis incident has been resolved. | 8 min | Resolved |
| May 8, 2026 | DeepSeek-V3.2 is under maintenanceThe scheduled maintenance has been completed. | 166h 0m | Scheduled |
| Feb 21, 2026 | Whisper-Large-v3 Model maintenanceThe scheduled maintenance has been completed. | 120h 0m | Scheduled |
| Jan 17, 2026 | E5-Mistral-7B-Instruct downE5-Mistral-7B-Instruct IS back in service | 2h 7m | Resolved |
| Jan 9, 2026 | SambaNova Cloud DownThe issue has been resolved. | 12 min | Resolved |
| Dec 13, 2025 | SambaCloud - Japan Routine Maintenance[Statuspage]scheduled - SambaCloud - Japan Routine Maintenance | 1h 30m | Scheduled |
| Dec 5, 2025 | All Cloud services intermittently unavailableThe issue is now resolved. We will continue to monitor for re-occurances. | 2h 37m | Resolved |
| Dec 4, 2025 | All Cloud services intermittently unavailableThe issue has been resolved . | 45 min | Resolved |
| Nov 9, 2025 | DNS maintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next SambaCloud incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This SambaCloud Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before SambaCloud acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single SambaCloud outage in this window ran 6d 22h, against a mean recovery of 1d 8h. If you depend on SambaCloud in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.