Vendor record
Baseten
Checked
Front door check counts and Baseten’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We send a request to a documented Baseten endpoint and count the checks that got the answer it is documented to give.
Front door reachable in 2,878 of 2,878 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.
1 more check gave no clear answer and is not counted.
- Endpoint checked
- api.baseten.co
- Scope
- apiNo vendor region
- First check in this window
- Latest clear answer
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Baseten product, region or your app worked.
How we count front door checksBaseten says
Incident posts from Baseten’s status page, with its titles, impact levels and times. They say what Baseten chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
25
incidents Baseten posted, last 90 days
Median recorded duration: 40m. From 25 incidents with vendor-supplied starts and recorded closure times.
Most recent records · all dates
Elevated errors on new model builds. Existing models are not affected
MinorBaseten’s postStarted, per Baseten
Closed in our record(39m)
Metrics degradation in UI and API. **Inference not affected**
MinorBaseten’s postStarted, per Baseten
Closed in our record(22m)
Intermittent 5xx for a subset of models in 1 US Central cluster
MinorBaseten’s postStarted, per Baseten
Closed in our record(1h 25m)
Elevated inference 500s for a subset of models deployed in 1 US-East cluster
MajorBaseten’s postStarted, per Baseten
Closed in our record(46m)
Metrics degradation in UI and API. **Inference not affected**
MinorStarted, per Baseten
Closed in our record(8m)
15 older records
Kimi K3 Model API outage
MajorBaseten’s postStarted, per Baseten
Closed in our record(1h 1m)
Elevated errors for models in a single India-based cluster
MinorBaseten’s postStarted, per Baseten
Closed in our record(47m)
Partial outage on Kimi K3 model API inference (non-US only)
MinorBaseten’s postStarted, per Baseten
Closed in our record(48m)
Partial outage on Nemotron Ultra Model API. **Dedicated Inference is not affected**
MinorBaseten’s postStarted, per Baseten
Closed in our record(17m)
Elevated inference 500s for models in a single US-based cluster
MajorBaseten’s postStarted, per Baseten
Closed in our record(18m)
Elevated errors for models in a single US cluster due to provider outage
MajorStarted, per Baseten
Closed in our record(11m)
Elevated errors for deepseek-ai/DeepSeek-V4-Flash-0731 on Model APIs. **Dedicated Inference is not affected**
MinorBaseten’s postStarted, per Baseten
Closed in our record(47m)
Elevated inference 500s for models in an EU cluster due to provider outage
MinorBaseten’s postStarted, per Baseten
Closed in our record(45m)
Elevated errors for moonshotai/Kimi-K3 for US-pinned traffic on Model APIs. **Dedicated Inference is not affected**
MinorBaseten’s postStarted, per Baseten
Closed in our record(37m)
Elevated errors for moonshotai/Kimi-K3 for US-pinned traffic on Model APIs. **Dedicated Inference is not affected**
MinorBaseten’s postStarted, per Baseten
Closed in our record(1h 25m)
Elevated errors for moonshotai/Kimi-K3 for US-pinned traffic on Model APIs. **Dedicated Inference is not affected**
MinorBaseten’s postStarted, per Baseten
Closed in our record(21m)
Elevated errors for moonshotai/Kimi-K3 for US-pinned traffic on Model APIs. **Dedicated Inference is not affected**
MinorBaseten’s postStarted, per Baseten
Closed in our record(53m)
Elevated errors for moonshotai/Kimi-K3 for US-pinned traffic
MinorBaseten’s postStarted, per Baseten
Closed in our record(54m)
Metrics degradation in UI and API. **Inference not affected**
MinorBaseten’s postStarted, per Baseten
Closed in our record(29m)
Elevated inference 502s for a subset of models in a single US cluster
MinorBaseten’s postStarted, per Baseten
Closed in our record(1h 3m)
Your code, your dependencies
See which of your code paths call Baseten
Connect GitHub or GitLab to find where your public or private repository uses Baseten. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add Baseten status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is Baseten currently down?
Baseten's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did Baseten last have an outage?
The most recent closed incident record began 6 days ago and spans 39 minutes. The vendor reported degraded performance. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for Baseten?
No. CheckUpstream checks Baseten’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.
How do I monitor Baseten in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track Baseten?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.