When did the maintenance start and end?

It started at 2026-11-09 22:00 UTC and ended at 2026-11-10 01:03 UTC. It lasted 3 h 3 min.

How do I get alerts for SambaNova?

Subscribe to the SambaNova live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of SambaNova. outages.live reads it every few minutes and keeps every update.

Scheduled Maintenance — Monday, November 9, 2026 2:00 PM – 5:00 PM PT (22:00 – 01:00 UTC)

Q: What happened?

SambaNova reported "Scheduled Maintenance — Monday, November 9, 2026 2:00 PM – 5:00 PM PT (22:00 – 01:00 UTC)" on its status page at 2026-11-09 22:00 UTC.

Q: What is affected?

SambaNova lists these components: SambaCloud Playground, MiniMax-M2.7, SambaCloud API Gateway, gpt-oss-120b, gemma-4-31B-it, Meta-Llama-3.3-70B-Instruct, and 13 more.

ResolvedOfficial update

Scheduled maintenance is currently in progress. We will provide updates as necessary.

The latest update from SambaNova.

State

Resolved

Started

Lasted

3 h 3 min

Worst impact

Maintenance

Timeline

4 updates

22:0022:4523:3100:1701:03

MaintenanceUpdate postedTimes in UTC

Scheduled

3 min 2%

In progress

3 h 98%

Updates

Times in UTC

As posted by SambaNova

Resolved

In progress

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Scheduled

Maintenance will begin as scheduled in 60 minutes.

Scheduled

Scheduled Maintenance — Monday, November 9, 2026 2:00 PM – 5:00 PM PT (22:00 – 01:00 UTC) We will be performing scheduled maintenance during the window above. No service outage or disruption is expected — all services will remain fully available throughout the maintenance period. We’re posting this notice for transparency and awareness. No action is required on your part. If you experience any unexpected issues during this window, please contact support and we’ll assist you right away. We’ll update this page when maintenance is complete.

Affected components

SambaCloud PlaygroundMiniMax-M2.7SambaCloud API Gatewaygpt-oss-120bgemma-4-31B-itMeta-Llama-3.3-70B-InstructSambaCloud - JapanDeepSeek-V3.1

SambaNova in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

Not enough data

This incident

Not comparable

Follow SambaNova

Your coding agent knows when SambaNova is down, and tells you when a failure is theirs, not yours. You can also get SambaNova incidents in a feed reader or in Slack.

Prompt

Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "sambanova" and tell me if SambaNova has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS

https://outages.live/feed.xml?providers=sambanova

Slack

/feed subscribe https://outages.live/feed.xml?providers=sambanova

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane