outages.live
Live
Weights & BiasesIncident ·

Web Page Unavailability

ResolvedOfficial update
0

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.

State

Resolved

Started

Lasted

13 min

Worst impact

Degraded

Timeline

3 updates
18:4018:4418:4718:5018:53
DegradedUpdate postedTimes in UTC

Investigating

11 min 81%

Monitoring

2 min 19%

Updates

Times in UTC

As posted by Weights & Biases

Resolved

This incident has been resolved.

Monitoring

A fix has been implemented and we are monitoring. Logins should succeed now.

Investigating

We are continuing to investigate this issue.

Affected components

2
Backend APIAuth0 User Authentication

Weights & Biases in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

2

Days with an incident

2

Median duration

1 h 31 min

This incident

86% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

2 h 48 min
median 1 h 31 min
90 days agoToday

Other Weights & Biases incidents

All incidents

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.

Resolved

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.

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 "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.

RSS
https://outages.live/feed.xml?providers=wandb
Slack
/feed subscribe https://outages.live/feed.xml?providers=wandb

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane