Together AI status — and how to poll it yourself

Snapshot: Aug 31, 2026 9:30 AM ET · Statuses shown are build-time snapshots — they refresh on each site rebuild. Live auto-refresh ships post-launch.

At this snapshot, 8 of the 9 providers on our status board reported fully operational. Here is where Together AI stood, and how to get the same answer from its status API without a browser.

Status pagehttps://status.together.ai
Snapshot statusOperational Aggregate state: operational (as of Aug 31, 2026 9:30 AM ET)
Components22/22
Status API formatbetterstack
JSON endpointhttps://status.together.ai/index.json?include=resources
Gotcha/api/v2/status.json redirects to page root; use /index.json (BetterStack). As of 2026-08-06 resources are no longer inlined — append ?include=resources to get per-component state
Verificationverified — live fetch on 2026-08-31

The 22 components Together AI reports status for

When Together AI says "operational", this is the granularity behind the claim — the component list its own status feed publishes, fetched 2026-08-31. All were reported operational at snapshot time. If an incident hits, these are the names its status page will scope it to.

Polling Together AI's status programmatically

BetterStack (Better Uptime). GET /index.json returns the aggregate state and resource list. /api/v2/status.json is NOT a data endpoint on this platform — it redirects to the page root.

curl -s https://status.together.ai/index.json?include=resources

Gotcha (verified 2026-08-31): /api/v2/status.json redirects to page root; use /index.json (BetterStack). As of 2026-08-06 resources are no longer inlined — append ?include=resources to get per-component state

Everything above was verified against the live endpoint on 2026-08-31 — nothing is inferred from platform defaults. If the endpoint moved, tell us.

Model retirements — Together AI

Our 129-row deprecations table tracks the providers that publish dated, citable retirement schedules (OpenAI, Anthropic, Google Vertex AI and Azure OpenAI). Together AI publishes no dated model-retirement schedule we could verify against its own docs — absence here means absence of a published schedule, not a no-deprecation guarantee. Pin model versions and watch the provider's changelog either way.

Other providers