Baseten Outage History
73 incidents recorded over the last 365 days, 70 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Baseten Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 19, 2026 | Elevated errors for moonshotai/Kimi-K3 for US-pinned traffic on Model APIs. **Dedicated Inference is not affected**This incident has been resolved. | 36 min | Resolved |
| Aug 18, 2026 | Elevated errors for moonshotai/Kimi-K3 for US-pinned traffic on Model APIs. **Dedicated Inference is not affected**This incident has been resolved. | 1h 17m | Resolved |
| Aug 18, 2026 | Elevated errors for moonshotai/Kimi-K3 for US-pinned traffic on Model APIs. **Dedicated Inference is not affected**This incident has been resolved. | 11 min | Resolved |
| Aug 18, 2026 | Elevated errors for moonshotai/Kimi-K3 for US-pinned traffic on Model APIs. **Dedicated Inference is not affected**This incident has been resolved. | 47 min | Resolved |
| Aug 17, 2026 | Elevated errors for moonshotai/Kimi-K3 for US-pinned trafficThis incident has been resolved. | 45 min | Resolved |
| Aug 17, 2026 | Metrics degradation in UI and API. **Inference not affected**This incident has been resolved. | 24 min | Resolved |
| Aug 6, 2026 | Database Upgrade. Inference will not be affectedThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Aug 4, 2026 | Database Upgrade. Inference will not be affectedThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Aug 1, 2026 | Elevated inference 502s for a subset of models in a single US clusterThis incident has been resolved. | 43 min | Resolved |
| Jul 31, 2026 | Elevated inference 502s for a subset of models in a single US clusterThis incident has been resolved. | 28 min | Resolved |
| Jul 31, 2026 | Slower than usual scale-ups for B200sThis incident has been resolved. | 11 min | Resolved |
| Jul 22, 2026 | Elevated inference failures for models in an EU clusterThis incident has been resolved. | 32 min | Resolved |
| Jul 22, 2026 | Slower than usual scale-ups in 1 us-central clusterThis incident has been resolved. | 19 min | Resolved |
| Jul 18, 2026 | GLM 5.2 Model API partial outage due to provider network failureThis incident has been resolved. | 32 min | Resolved |
| Jul 18, 2026 | Elevated inference errors in 1 Canada cluster due to provider network outageThis incident has been resolved. | 5 min | Resolved |
| Jul 16, 2026 | Elevated errors in accessing the Baseten UI. **Inference is not affected**This incident has been resolved. | 1h 18m | Resolved |
| Jul 13, 2026 | Partial Outage on Model APIsKimi-K2.6 recovered. | 2h 6m | Resolved |
| Jul 9, 2026 | Elevated inference 500s for models deployed in 1 US-east clusterThis incident has been resolved. | 20 min | Resolved |
| Jul 8, 2026 | Metrics degradation in UI and API. **Inference not affected**This incident has been resolved. | 1h 55m | Resolved |
| Jul 6, 2026 | Elevated inference 500s — network outage in our cloud provider in DelawareThis incident has been resolved. | 13 min | Resolved |
| Jul 3, 2026 | Elevated errors for GLM 5.2 on Model APIs. **Dedicated Inference is not affected**This incident has been resolved. | 1h 25m | Resolved |
| Jul 3, 2026 | Elevated inference 500s for a subset of models deployed in 1 clusterThis incident has been resolved. | 15 min | Resolved |
| Jul 2, 2026 | Degraded metrics performance in dashboard and API. **Inference is not affected**This incident has been resolved. | 1h 13m | Resolved |
| Jul 1, 2026 | Elevated errors in a single EU clusterThis incident has been resolved. | 59 min | Resolved |
| Jun 29, 2026 | Elevated error rates on GLM 5.2 Model APIs. **Dedicated Inference is not affected**This incident has been resolved. | 35 min | Resolved |
| Jun 27, 2026 | Elevated inference 500s for models in 1 cluster due to cloud provider outageThis incident has been resolved. | 15 min | Resolved |
| Jun 26, 2026 | Elevated model deployment failures. **Inference is not affected**The incident has resolved. New model deployments are successfully coming up. | 1h 14m | Resolved |
| Jun 26, 2026 | Elevated errors for dedicated inference in a subset of clustersThis incident has been resolved. | 14 min | Resolved |
| Jun 23, 2026 | Slower than usual scale-ups. High failure rate for new model deploys. Existing replicas aren't impacted.This incident has been resolved. | 44 min | Resolved |
| Jun 18, 2026 | Elevated errors for models in 1 Austin-based cluster affecting some models on B200sThis incident has been resolved. | 1h 43m | Resolved |
| Jun 17, 2026 | Elevated errors for models in 1 Sweden-based clusterThis incident has been resolved. | 1h 23m | Resolved |
| Jun 15, 2026 | Elevated errors for models in a single EU cloud providerThis incident has been resolved. | 44 min | Resolved |
| Jun 13, 2026 | Elevated errors for models in a single cloud providerThis incident has been resolved. | 44 min | Resolved |
| Jun 5, 2026 | Elevated errors in a single US-East clusterThis incident has been resolved. | 19 min | Resolved |
| Jun 4, 2026 | Elevated latencies for a subset of models in a US-East clusterThis incident has been resolved. | 1h 6m | Resolved |
| Jun 3, 2026 | Slower than usual scale-ups for some models using H100sThis incident has been resolved. | 2h 14m | Resolved |
| May 29, 2026 | Elevated async inference errors in a single clusterThis incident has been resolved. | 32 min | Resolved |
| May 26, 2026 | Slower than usual scale-ups in 1 India clusterThis incident has been resolved. | 13 min | Resolved |
| May 20, 2026 | Elevated errors for models in single regionThis incident has been resolved. | 13 min | Resolved |
| May 18, 2026 | Slower than usual scale-ups for L4s in US-EastThis incident has been resolved. | 38 min | Resolved |
| May 16, 2026 | Slower than usual scale-ups in EU due to a provider failureThis incident has been resolved. | 1h 32m | Resolved |
| May 16, 2026 | Higher latencies for a subset of models in one cluster. Root caused and a fix is in progressThe incident is resolved. | 36 min | Resolved |
| May 15, 2026 | Elevated errors in a single clusterThis incident has been resolved. | 2h 0m | Resolved |
| May 10, 2026 | Training cluster is down due to a provider failureThe issue has been resolved. | 15 min | Resolved |
| May 8, 2026 | Intermittent failure in loading the webapp — inference is *not* affectedThe issue is resolved. | 41 min | Resolved |
| May 7, 2026 | Elevated errors for models in single regionThis incident has been resolved. | 47 min | Resolved |
| Apr 30, 2026 | Planned Maintenance on our Training Cluster. Inference will not be affected.The scheduled maintenance has been completed. | 3h 0m | Scheduled |
| Apr 13, 2026 | Slower than usual scale-ups for a small subset of modelsThis incident has been resolved. | 49 min | Resolved |
| Apr 4, 2026 | Slower than usual scale-ups for a small subset of modelsThis incident has been resolved. | 4h 45m | Resolved |
| Apr 3, 2026 | Builds of new models are currently failing. **Inference is not affected**This incident has been resolved. | 55 min | Resolved |
| Apr 2, 2026 | Elevated deploy failures. Inference is **not** affected.There was a backup in the deploy queue, resulting in some deploy failures. Please retry any deploys from this period. | -67 min | Resolved |
| Mar 12, 2026 | gpt-oss model API service degradationFix is in place and the issue has been resolved. | 17 min | Resolved |
| Feb 28, 2026 | Elevated 500s on Model APIs. **Dedicated Inference is not affected**This incident has been resolved. | 42 min | Resolved |
| Feb 27, 2026 | Partial inference outage in AWS us-east-1This incident has been resolved. | 54 min | Resolved |
| Feb 13, 2026 | Network Errors in single EU ClusterThis incident has been resolved. | 3h 25m | Resolved |
| Feb 9, 2026 | Elevated inference latencies in AWS us-west-2This incident has been resolved. | 2h 13m | Resolved |
| Jan 22, 2026 | Baseten web app is down. **Inference is unaffected**This incident has been resolved. | 23 min | Resolved |
| Jan 21, 2026 | Elevated latency for inference requests in single region in Baseten Cloud WestThis incident has been resolved. | 1h 3m | Resolved |
| Dec 21, 2025 | GPT-OSS on Model APIs is degraded. **Dedicated inference is not affected**.This incident has been resolved. | 21 min | Resolved |
| Dec 21, 2025 | Slower than usual scale-ups and new deploys for all models in GCPThis incident has been resolved. | 54 min | Resolved |
| Dec 6, 2025 | Deepseek V3-0324 on Model APIs is down. **Dedicated inference is not affected**.The incident is resolved. | 20 min | Resolved |
| Nov 17, 2025 | Elevated error rates for inference requests for a subset of models in GCP us-central1This incident has been resolved. | 19 min | Resolved |
| Nov 3, 2025 | New builds are failing to push. Inference is *not* affectedThis incident has been resolved. | 15 min | Resolved |
| Nov 1, 2025 | Elevated errors and delays in new model deploys in 1 cluster. Inference is *not* affected.This incident has been resolved. | 38 min | Resolved |
| Oct 30, 2025 | Elevated errors in model deploys and promotions in 2 clusters. Inference is *not* affected.This incident has been resolved. | 8 min | Resolved |
| Oct 25, 2025 | Slower than usual scale-ups in 1 regionThis incident has been resolved. | 3h 42m | Resolved |
| Oct 24, 2025 | Slower than usual scale-ups in 2 regionsThis incident has been resolved. | 4h 13m | Resolved |
| Oct 23, 2025 | Model logs are slow to load in a single cluster. Inference is not affected.This incident has been resolved. | 15 min | Resolved |
| Oct 20, 2025 | Login timing out on webappThe issue with our auth provider has been fixed, and logins work again. | 6h 37m | Resolved |
| Oct 20, 2025 | Baseten Web Application is down due to AWS outage. Inference is unaffected.Upstream provider has recovered, and the Baseten web app is available. | 2h 15m | Resolved |
| Oct 13, 2025 | High latency on Baseten Web Application and Model Management APIs. Inference is unaffected.The issue is resolved. | 14 min | Resolved |
| Sep 25, 2025 | Build Infrastructure degraded due to Dockerhub outageThis incident has been resolved. | 57 min | Resolved |
| Sep 22, 2025 | L4 capacity in single us-east region having issuesThis incident has been resolved. | 12 min | Resolved |
How to Read This Baseten Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Baseten acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Baseten outage in this window ran 6h 37m, against a mean recovery of 1h 4m. If you depend on Baseten in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.