CHYP.ai · ORBIT // Cloudy_Day Security Suite

Outages · AI services

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

100

Clear skies: official status: Operational

At a glance

28official incidents, 90 d
100%of our checks clean (9)
37 minmedian time to resolve
0visitor reports, 24 h
0reports, last 15 min
0status changes recorded

90-day timeline (1 day tracked)

2026-08-24: no data yet2026-08-25: no data yet2026-08-26: no data yet2026-08-27: no data yet2026-08-28: no data yet2026-08-29: no data yet2026-08-30: no data yet2026-08-31: no data yet2026-09-01: no data yet2026-09-02: no data yet2026-09-03: no data yet2026-09-04: no data yet2026-09-05: no data yet2026-09-06: no data yet2026-09-07: no data yet2026-09-08: no data yet2026-09-09: no data yet2026-09-10: no data yet2026-09-11: no data yet2026-09-12: no data yet2026-09-13: no data yet2026-09-14: no data yet2026-09-15: no data yet2026-09-16: no data yet2026-09-17: no data yet2026-09-18: no data yet2026-09-19: no data yet2026-09-20: no data yet2026-09-21: no data yet2026-09-22: no data yet2026-09-23: no data yet2026-09-24: no data yet2026-09-25: no data yet2026-09-26: no data yet2026-09-27: no data yet2026-09-28: no data yet2026-09-29: no data yet2026-09-30: no data yet2026-10-01: no data yet2026-10-02: no data yet2026-10-03: no data yet2026-10-04: no data yet2026-10-05: no data yet2026-10-06: no data yet2026-10-07: no data yet2026-10-08: no data yet2026-10-09: no data yet2026-10-10: no data yet2026-10-11: no data yet2026-10-12: no data yet2026-10-13: no data yet2026-10-14: no data yet2026-10-15: no data yet2026-10-16: no data yet2026-10-17: no data yet2026-10-18: no data yet2026-10-19: no data yet2026-10-20: no data yet2026-10-21: no data yet2026-10-22: no data yet2026-10-23: no data yet2026-10-24: no data yet2026-10-25: no data yet2026-10-26: no data yet2026-10-27: no data yet2026-10-28: no data yet2026-10-29: no data yet2026-10-30: no data yet2026-10-31: no data yet2026-11-01: no data yet2026-11-02: no data yet2026-11-03: no data yet2026-11-04: no data yet2026-11-05: no data yet2026-11-06: no data yet2026-11-07: no data yet2026-11-08: no data yet2026-11-09: no data yet2026-11-10: no data yet2026-11-11: no data yet2026-11-12: no data yet2026-11-13: no data yet2026-11-14: no data yet2026-11-15: no data yet2026-11-16: no data yet2026-11-17: no data yet2026-11-18: no data yet2026-11-19: no data yet2026-11-20: no data yet2026-11-21: 9 checks, 0 with an official incident (worst: none)90 days agotoday

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

3 incident(s), week ending 2026-08-2931 incident(s), week ending 2026-09-0511 incident(s), week ending 2026-09-1212 incident(s), week ending 2026-09-1925 incident(s), week ending 2026-09-2652 incident(s), week ending 2026-10-0322 incident(s), week ending 2026-10-1020 incident(s), week ending 2026-10-175 incident(s), week ending 2026-10-2450 incident(s), week ending 2026-10-311 incident(s), week ending 2026-11-0713 incident(s), week ending 2026-11-1433 incident(s), week ending 2026-11-21313 weeks agothis weekmax 5/week

Impact mix, 90 d

1 critical8 major19 minor28
  • 8 major
  • 19 minor
  • 1 critical

Visitor reports, last 24 h

24 h agonow · peak 1/15 min

Unverified reports from ORBIT visitors, in 15-minute buckets. Add yours.

Incident history

  1. → resolved · lasted 11 minOutage on app.baseten.co. Inference is not affectedmajor resolved · Model Management API, Web Application · official notice ↗ · replay & discuss
  2. → resolved · lasted 27 minElevated errors on GLM-5.3-Flash on Model APIsminor resolved · Model APIs · official notice ↗ · replay & discuss
  3. → resolved · lasted 38 minElevated TTFT on Kimi K3 on MAPIsminor resolved · Model APIs · official notice ↗ · replay & discuss
  4. → resolved · lasted 1.8 hElevated errors for multiple models on Model APIsminor resolved · Model APIs · official notice ↗ · replay & discuss
  5. → resolved · lasted 47 minDegraded Performance on DSV 4.1 Flash 1017-Fast on Model APIsminor resolved · Model APIs · official notice ↗ · replay & discuss
  6. → resolved · lasted 21 minModel APIs are down for all modelscritical resolved · Model APIs · official notice ↗ · replay & discuss
  7. → 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
  8. → resolved · lasted 56 minElevated errors for US-only GLM 5.3 Flash on Model APIsminor resolved · Model APIs · official notice ↗ · replay & discuss
  9. → resolved · lasted 40 minElevated errors on DeepSeek V4 Flash on Model APIsminor resolved · Model APIs · official notice ↗ · replay & discuss
  10. → resolved · lasted 21 minElevated errors for image requests on multiple Model APIsminor resolved · Model APIs · official notice ↗ · replay & discuss
  11. → resolved · lasted 6 minDeepSeek V4.1 Flash Fast Outage on Model APIsmajor resolved · Model APIs · official notice ↗ · replay & discuss
  12. → resolved · lasted 8 minElevated errors on Model APIsminor resolved · Model APIs · official notice ↗ · replay & discuss
  13. → resolved · lasted 37 minElevated errors on new model builds. Existing models are not affectedminor resolved · Model Management API · official notice ↗ · replay & discuss
  14. → resolved · lasted 13 minDeepSeek v4.1 outage on Model APIs. Dedicated Inference is not affectedmajor resolved · Model APIs · official notice ↗ · replay & discuss
  15. → resolved · lasted 13 minElevated 500s in Single us-central Regionmajor resolved · Dedicated Inference · official notice ↗ · replay & discuss
  16. → resolved · lasted 21 minMetrics degradation in UI and API. **Inference not affected**minor resolved · Model Management API, Web Application · official notice ↗ · replay & discuss
  17. → resolved · lasted 1.4 hIntermittent 5xx for a subset of models in 1 US Central clusterminor resolved · Dedicated Inference · official notice ↗ · replay & discuss
  18. → resolved · lasted 42 minElevated inference 500s for a subset of models deployed in 1 US-East clustermajor resolved · Dedicated Inference · official notice ↗ · replay & discuss
  19. → resolved · lasted 7 minElevated inference 500s for a subset of models deployed in GCP central1major resolved · Dedicated Inference · official notice ↗ · replay & discuss
  20. → resolved · lasted 11 minMetrics degradation in UI and API. **Inference not affected**minor resolved · Model Management API · official notice ↗ · replay & discuss
  21. → resolved · lasted 55 minKimi K3 Model API outagemajor resolved · Model APIs · official notice ↗ · replay & discuss
  22. → resolved · lasted 45 minElevated errors for models in a single India-based clusterminor resolved · Dedicated Inference · official notice ↗ · replay & discuss
  23. → resolved · lasted 42 minPartial outage on Kimi K3 model API inference (non-US only)minor resolved · Model APIs · official notice ↗ · replay & discuss
  24. → resolved · lasted 6 minPartial outage on Nemotron Ultra Model API. **Dedicated Inference is not affected**minor resolved · Model APIs · official notice ↗ · replay & discuss
  25. → resolved · lasted 24 minElevated inference 500s for models in a single US-based clustermajor resolved · Dedicated Inference · official notice ↗ · replay & discuss

All 28 incidents →

Related services

"Runs on" links are inferred from public information and may be outdated.

How we score status

  1. 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.
  2. 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.
  3. 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).
  4. 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.
  5. 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.

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.

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.

Where to next