Skip to main content
Together AI logo

Is Together AI Down?

No — Together AI is up
Together AI's status page
Not available · we could not read it
FlareWarden checks
Website reachable · 8 of 8 regions · 272 ms

Right now

We could not read Together AI's status page, so the verdict rests on our checks. Check it yourself How we decide

FlareWarden checks

api.together.xyz from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable
Regions up
8 of 8
Response
272 ms
Checked

By region

  • Ashburn reachable, 159 ms
  • Dallas reachable, 296 ms
  • Frankfurt reachable, 386 ms
  • Johannesburg reachable, 543 ms
  • London reachable, 287 ms
  • Los Angeles reachable, 96 ms
  • Newark reachable, 164 ms
  • São Paulo reachable, 251 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Ashburn23 ms1 ms4 ms159 ms
Dallas210 ms2 ms9 ms296 ms
Frankfurt203 ms2 ms6 ms386 ms
Johannesburg190 ms1 ms8 ms543 ms
London63 ms3 ms10 ms287 ms
Los Angeles15 ms2 ms11 ms96 ms
Newark46 ms3 ms10 ms163 ms
São Paulo15 ms2 ms9 ms251 ms
We check that api.together.xyz loads, not every feature behind it. Test it yourself

History

Together AI website availability

Measured by FlareWarden · api.together.xyz

Last 7 days
100%
Last 30 days
100%
Last 90 days
100%
Avg response, 30 days
234ms

Last 30 days

71-day clean streak
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Oct 14: 100.00% uptime, 32 checks
Oct 15: 100.00% uptime, 32 checks
Oct 16: 100.00% uptime, 31 checks
Oct 17: 100.00% uptime, 32 checks
Oct 18: 100.00% uptime, 32 checks
Oct 19: 100.00% uptime, 32 checks
Oct 20: 100.00% uptime, 32 checks
Oct 21: 100.00% uptime, 32 checks
Oct 22: 100.00% uptime, 32 checks
Oct 23: 100.00% uptime, 32 checks
Oct 24: 100.00% uptime, 32 checks
Oct 25: 100.00% uptime, 32 checks
Oct 26: 100.00% uptime, 32 checks
Oct 27: 100.00% uptime, 32 checks
Oct 28: 100.00% uptime, 32 checks
Oct 29: 100.00% uptime, 32 checks
Oct 30: 100.00% uptime, 32 checks
Oct 31: 100.00% uptime, 32 checks
Nov 1: 100.00% uptime, 32 checks
Nov 2: 100.00% uptime, 32 checks
Nov 3: 100.00% uptime, 32 checks
Nov 4: 100.00% uptime, 32 checks
Nov 5: 100.00% uptime, 32 checks
Oct 7 Today
No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of api.together.xyz from multiple regions every 6 hours. Together AI's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 71 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What Together AI does

Together AI runs open source and open weight models as a hosted API. Developers send chat, vision, image, embedding and speech requests to endpoints that are OpenAI-compatible and pay per token instead of running GPUs themselves. It also offers fine-tuning and dedicated endpoints, which makes it a direct dependency for applications that route their model calls through it.

What an outage looks like

Calls to api.together.xyz return 5xx errors or time out, and applications waiting on a model response stall rather than failing cleanly. More often the failure is narrower than that: one model returns errors or answers far more slowly than usual while every other model on the platform is fine. The Playground and marketing site may be unaffected throughout.

What to do about it

Check status.together.ai, which reports individual models as their own components under Inference groups for Chat, Vision, Images, Embeddings and Voice. Find your specific model rather than reading the overall banner. If your model is the affected one, switching to another of similar capability is usually faster than waiting, which is the practical benefit of an OpenAI-compatible API.

Is it down for everyone, or just you?

If this page says Together AI is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Replicate
Replicate
Groq
Groq
O
OpenRouter
H
Hugging Face

Together AI outage FAQ

Is Together AI down, or is it just my model?
Usually just the model. Together AI's status page breaks out individual models as separate components, with Chat, Vision, Images, Embeddings and Voice each listing the specific models underneath. One model degrading while the platform stays healthy is the common case, and it is the distinction crowd-report aggregators cannot make.
Will my in-flight requests complete?
Requests already accepted may still return, but one that times out has no queue behind it on a synchronous inference call. It is simply gone, and retrying is your job. Use backoff rather than a tight retry loop, since retrying hard against a degraded endpoint adds to the load that caused the problem in the first place.
Does an incident affect fine-tuning jobs as well as inference?
The status page will not tell you directly. It tracks Website, Playground and the inference model groups, and does not break fine-tuning out as its own component. Check a running job through the API rather than assuming an inference incident stopped it, and rather than assuming it did not.
Should I fail over to another provider?
If your application tolerates a different model's output, yes. The API is OpenAI-compatible, so routing to another provider or another Together model is mostly a base URL and model name change. Applications with prompts tuned to one specific model get less benefit from this, which is a good argument for testing a fallback model before you actually need it.

How we measure this

  • We request Together AI's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Together AI publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Together AI itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. A reading counts for 45 minutes; we read the feed again within minutes of any change to its incidents. The availability figures above are our measurement alone.

Get alerted when Together AI goes down

We check Together AI every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required