Operational Baseten outage dossier
baseten.co · Official status page (Statuspage-compatible JSON)
Official status now
Operational Operational
checked 0 min ago How we score status
All Systems Operational
Read just now from: Official status page (Statuspage-compatible JSON) · official page ↗
ORBIT score
Clear skies: official status: Operational
At a glance
90-day timeline (1 day tracked)
Each bar is a day. Green: our checks found no official incident. Amber/red: the provider reported one. Grey: before ORBIT started tracking this service. This is "share of our checks with no official incident", not the provider's SLA.
Official incidents per week
Impact mix, 90 d
- 8 major
- 19 minor
- 1 critical
Visitor reports, last 24 h
Unverified reports from ORBIT visitors, in 15-minute buckets. Add yours.
Incident history
- → resolved · lasted 11 minOutage on app.baseten.co. Inference is not affectedmajor resolved · Model Management API, Web Application · official notice ↗ · replay & discuss
- → resolved · lasted 27 minElevated errors on GLM-5.3-Flash on Model APIsminor resolved · Model APIs · official notice ↗ · replay & discuss
- → resolved · lasted 38 minElevated TTFT on Kimi K3 on MAPIsminor resolved · Model APIs · official notice ↗ · replay & discuss
- → resolved · lasted 1.8 hElevated errors for multiple models on Model APIsminor resolved · Model APIs · official notice ↗ · replay & discuss
- → resolved · lasted 47 minDegraded Performance on DSV 4.1 Flash 1017-Fast on Model APIsminor resolved · Model APIs · official notice ↗ · replay & discuss
- → resolved · lasted 21 minModel APIs are down for all modelscritical resolved · Model APIs · official notice ↗ · replay & discuss
- → resolved · lasted 5.2 hElevated errors for Kimi-K3 on Model APIs. **Dedicated Inference is not affected**minor resolved · Model APIs · official notice ↗ · replay & discuss
- → resolved · lasted 56 minElevated errors for US-only GLM 5.3 Flash on Model APIsminor resolved · Model APIs · official notice ↗ · replay & discuss
- → resolved · lasted 40 minElevated errors on DeepSeek V4 Flash on Model APIsminor resolved · Model APIs · official notice ↗ · replay & discuss
- → resolved · lasted 21 minElevated errors for image requests on multiple Model APIsminor resolved · Model APIs · official notice ↗ · replay & discuss
- → resolved · lasted 6 minDeepSeek V4.1 Flash Fast Outage on Model APIsmajor resolved · Model APIs · official notice ↗ · replay & discuss
- → resolved · lasted 8 minElevated errors on Model APIsminor resolved · Model APIs · official notice ↗ · replay & discuss
- → resolved · lasted 37 minElevated errors on new model builds. Existing models are not affectedminor resolved · Model Management API · official notice ↗ · replay & discuss
- → resolved · lasted 13 minDeepSeek v4.1 outage on Model APIs. Dedicated Inference is not affectedmajor resolved · Model APIs · official notice ↗ · replay & discuss
- → resolved · lasted 13 minElevated 500s in Single us-central Regionmajor resolved · Dedicated Inference · official notice ↗ · replay & discuss
- → resolved · lasted 21 minMetrics degradation in UI and API. **Inference not affected**minor resolved · Model Management API, Web Application · official notice ↗ · replay & discuss
- → resolved · lasted 1.4 hIntermittent 5xx for a subset of models in 1 US Central clusterminor resolved · Dedicated Inference · official notice ↗ · replay & discuss
- → resolved · lasted 42 minElevated inference 500s for a subset of models deployed in 1 US-East clustermajor resolved · Dedicated Inference · official notice ↗ · replay & discuss
- → resolved · lasted 7 minElevated inference 500s for a subset of models deployed in GCP central1major resolved · Dedicated Inference · official notice ↗ · replay & discuss
- → resolved · lasted 11 minMetrics degradation in UI and API. **Inference not affected**minor resolved · Model Management API · official notice ↗ · replay & discuss
- → resolved · lasted 55 minKimi K3 Model API outagemajor resolved · Model APIs · official notice ↗ · replay & discuss
- → resolved · lasted 45 minElevated errors for models in a single India-based clusterminor resolved · Dedicated Inference · official notice ↗ · replay & discuss
- → resolved · lasted 42 minPartial outage on Kimi K3 model API inference (non-US only)minor resolved · Model APIs · official notice ↗ · replay & discuss
- → resolved · lasted 6 minPartial outage on Nemotron Ultra Model API. **Dedicated Inference is not affected**minor resolved · Model APIs · official notice ↗ · replay & discuss
- → resolved · lasted 24 minElevated inference 500s for models in a single US-based clustermajor resolved · Dedicated Inference · official notice ↗ · replay & discuss
Related services
- OperationalOpenAI (ChatGPT & API)Operational→
- OperationalAnthropic (Claude)Operational→
- no official feedGoogle Geminino official feed→
- OperationalGitHub CopilotOperational→
- OperationalMistral AIOperational→
- OperationalCohereOperational→
- OperationalPerplexityOperational→
- OperationalHugging FaceOperational→
"Runs on" links are inferred from public information and may be outdated.
How we score status
- Source. Every reading comes from the provider's own public status page or status API (Statuspage, Instatus, incident.io-style JSON, or the provider's RSS/JSON). ORBIT never pings or scans the service.
- Scope. For each open incident we count the regions or components it names against the total the provider publishes, and label it global, multi-region, 1 region or n of N components.
- Age. Incidents are new (under 1 hour), active, long-running (open more than 48 hours) or stale (no provider update for 24 hours or more).
- Headline. The headline colour comes from current incidents only. A single-region or small-scope incident caps the headline at "Degraded"; a global or widespread one keeps the provider's impact. Long-running or stale issues limited to one region or a few components get a known long-running issue badge and don't set the headline colour.
- Transparency. The provider's own page-level status is always shown next to ORBIT's headline, with a link to the official page. When they differ, the provider's page is the authority on what it says.
Where this data comes from. "Official status" is read from each provider's own public status page or status API (the same JSON or RSS their status page publishes), cached for a minute or more. ORBIT never pings, scans or probes the provider's systems. "Our checks" and history are ORBIT's own record of those readings, kept in our database. Visitor reports are unverified. Headlines are matched by name and shown for context: coincidence, not causation. Cloudy_Day is independent and not an official source for any company listed.
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.