Outage on app.baseten.co. Inference is not affected
Baseten reports a partial outage on app.baseten.co. The Model Management API and the Web Application do not work. Inference is not affected. Baseten says the incident is resolved and it lasted about 11 minutes.
State
Resolved
Started
Lasted
11 min
Worst impact
Partial outage
Timeline
3 updatesInvestigating
10 min 90%
Monitoring
1 min 10%
Updates
Times in UTCAs posted by Baseten
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are currently investigating this issue.
Affected components
2Baseten in the last 90 days
Full historyIncidents in 90 days
28
Days with an incident
21
Median duration
32 min
This incident
66% shorter than the median
Other Baseten incidents
All incidentsBaseten·Elevated errors on GLM-5.3-Flash on Model APIs
GLM-5.3-Flash on Model APIs had elevated errors. Baseten reports that the incident is resolved. The outage lasted about 27 minutes.
Baseten·Elevated TTFT on Kimi K3 on MAPIs
Baseten reported elevated time to first token on Kimi K3 on the Model APIs. Baseten implemented a fix and monitored the results. The incident is resolved and lasted about 38 minutes.
Baseten·Elevated errors for multiple models on Model APIs
Baseten reported elevated errors for GLM 5.3 and DeepSeek V4.1 Flash on Model APIs. Baseten later confirmed that both models recovered. Baseten resolved the incident after 36 minutes.
Baseten·Degraded Performance on DSV 4.1 Flash 1017-Fast on Model APIs
This incident has been resolved.
Baseten·Model APIs are down for all models
Baseten Model APIs were down for all models. Baseten reports that the incident is resolved. The outage lasted 21 minutes.
Follow Baseten
Your coding agent knows when Baseten is down, and tells you when a failure is theirs, not yours. You can also get Baseten 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 "baseten" and tell me if Baseten 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=baseten/feed subscribe https://outages.live/feed.xml?providers=basetenFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane