Serverless Training and Model Distillation Restored
Serverless Training and Model Distillation do not work. The Backend API is affected. Weights & Biases reports that these services are restored and operate normally. Weights & Biases continues to monitor. Resubmit a job if it failed during the unavailability.
State
Investigating
Started
Ongoing for
36 min
Worst impact
Notice
Timeline
1 updateInvestigating
36 min 100%
Updates
Times in UTCAs posted by Weights & Biases
Serverless Training and Model Distillation have been restored and are operating normally. We are continuing to monitor. If a job failed during the unavailability, please resubmit it
Affected components
1Weights & Biases in the last 90 days
Full historyIncidents in 90 days
5
Days with an incident
4
Median duration
1 h 43 min
This incident
65% shorter than the median
Other Weights & Biases incidents
All incidentsWeights & Biases·Serverless Training and Model Distillation Unavailable
Weights & Biases Serverless Training and Model Distillation are unavailable on the Backend API. Weights & Biases reports that the incident is resolved. It lasted about 26 hours, from 12 November 2026 to 13 November 2026.
Weights & Biases·Serverless Training
Weights & Biases reported that Serverless Training and Model Distillation APIs did not work. The Backend API had a partial outage. The incident is resolved. It lasted 37 minutes.
Weights & Biases·Web Page Unavailability
Weights & Biases reports that some web pages were unavailable. The affected components were the Backend API and Auth0 User Authentication. The incident is resolved and lasted 13 minutes.
Weights & Biases·Forge Intermittent Web Page Unavailability
Weights & Biases reports that Forge web pages and the inference API were intermittently unavailable. The Frontend and Inference Endpoint components were affected. Weights & Biases resolved the incident after 2 hours and 48 minutes.
Follow Weights & Biases
Your coding agent knows when Weights & Biases is down, and tells you when a failure is theirs, not yours. You can also get Weights & Biases incidents in a feed reader or in Slack.
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 "wandb" and tell me if Weights & Biases 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.
https://outages.live/feed.xml?providers=wandb/feed subscribe https://outages.live/feed.xml?providers=wandbFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane