Skip to content

Outage tracker / Together AI

Is Together AI down?

I'm having a problem

Vendor reports no incidentWhat Together AI reports

Together AI reports no incident on its status page.

As of the last successful poll, 2026-10-23 11:47 UTC.

Together AI's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 2 minutes ago

Our checks of Together AI pass from all 10 regions we check.

As of Oct 23, 2026, 11:55 AM UTC, RealUptime's checks of Together AI passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Oct 23, 2026, 11:55 AM UTC
US-East847 msChecks passing
US-West1257 msChecks passing
Europe536 msChecks passing
Asia-Pacific1196 msChecks passing
US-Central1404 msChecks passing
Canada987 msChecks passing
UK313 msChecks passing
Southeast Asia924 msChecks passing
Australia1833 msChecks passing
South America966 msChecks passing
their status pagetheir claim, not our reading

Together AI publishes no status feed we can read, so the only reading here is our check reading on the left.

Together AI response time, by region

US-East
1.1sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 777ms2026-09-25 UTC: p95 1.0s2026-09-26 UTC: p95 757ms2026-09-27 UTC: p95 984ms2026-09-28 UTC: p95 1.0s2026-09-29 UTC: p95 808ms2026-09-30 UTC: p95 982ms2026-10-01 UTC: p95 748ms2026-10-02 UTC: p95 630ms2026-10-03 UTC: p95 688ms2026-10-04 UTC: p95 730ms2026-10-05 UTC: p95 639ms2026-10-06 UTC: p95 832ms2026-10-07 UTC: p95 750ms2026-10-08 UTC: p95 737ms2026-10-09 UTC: p95 683ms2026-10-10 UTC: p95 674ms2026-10-11 UTC: p95 795ms2026-10-12 UTC: p95 493ms2026-10-13 UTC: p95 723ms2026-10-14 UTC: p95 588ms2026-10-15 UTC: p95 592ms2026-10-16 UTC: p95 678ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 1.1s
Sep 24Oct 8Oct 23
US-West
1.1sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 290ms2026-09-25 UTC: p95 376ms2026-09-26 UTC: p95 357ms2026-09-27 UTC: p95 342ms2026-09-28 UTC: p95 324ms2026-09-29 UTC: p95 351ms2026-09-30 UTC: p95 394ms2026-10-01 UTC: p95 292ms2026-10-02 UTC: p95 360ms2026-10-03 UTC: p95 364ms2026-10-04 UTC: p95 326ms2026-10-05 UTC: p95 393ms2026-10-06 UTC: p95 404ms2026-10-07 UTC: p95 362ms2026-10-08 UTC: p95 313ms2026-10-09 UTC: p95 415ms2026-10-10 UTC: p95 367ms2026-10-11 UTC: p95 357ms2026-10-12 UTC: p95 299ms2026-10-13 UTC: p95 332ms2026-10-14 UTC: p95 384ms2026-10-15 UTC: p95 419ms2026-10-16 UTC: p95 390ms2026-10-17 UTC: p95 863ms2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 1.1s
Sep 24Oct 8Oct 23
Europe
865msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 554ms2026-09-25 UTC: p95 452ms2026-09-26 UTC: p95 587ms2026-09-27 UTC: p95 387ms2026-09-28 UTC: p95 380ms2026-09-29 UTC: p95 587ms2026-09-30 UTC: p95 355ms2026-10-01 UTC: p95 520ms2026-10-02 UTC: p95 335ms2026-10-03 UTC: p95 397ms2026-10-04 UTC: p95 326ms2026-10-05 UTC: p95 322ms2026-10-06 UTC: p95 337ms2026-10-07 UTC: p95 315ms2026-10-08 UTC: p95 300ms2026-10-09 UTC: p95 289ms2026-10-10 UTC: p95 345ms2026-10-11 UTC: p95 315ms2026-10-12 UTC: p95 340ms2026-10-13 UTC: p95 427ms2026-10-14 UTC: p95 384ms2026-10-15 UTC: p95 709ms2026-10-16 UTC: p95 488ms2026-10-17 UTC: p95 904ms2026-10-18 UTC: p95 1.0s2026-10-19 UTC: p95 985ms2026-10-20 UTC: p95 973ms2026-10-21 UTC: p95 971ms2026-10-22 UTC: p95 969ms2026-10-23 UTC: p95 865ms
Sep 24Oct 8Oct 23
Asia-Pacific
1.5sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 461ms2026-09-25 UTC: p95 432ms2026-09-26 UTC: p95 389ms2026-09-27 UTC: p95 506ms2026-09-28 UTC: p95 393ms2026-09-29 UTC: p95 445ms2026-09-30 UTC: p95 462ms2026-10-01 UTC: p95 610ms2026-10-02 UTC: p95 539ms2026-10-03 UTC: p95 411ms2026-10-04 UTC: p95 534ms2026-10-05 UTC: p95 433ms2026-10-06 UTC: p95 545ms2026-10-07 UTC: p95 432ms2026-10-08 UTC: p95 357ms2026-10-09 UTC: p95 386ms2026-10-10 UTC: p95 510ms2026-10-11 UTC: p95 621ms2026-10-12 UTC: p95 457ms2026-10-13 UTC: p95 435ms2026-10-14 UTC: p95 557ms2026-10-15 UTC: p95 483ms2026-10-16 UTC: p95 561ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 1.5s
Sep 24Oct 8Oct 23
US-Central
1.4sp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 946ms2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 988ms2026-09-27 UTC: p95 919ms2026-09-28 UTC: p95 907ms2026-09-29 UTC: p95 1.2s2026-09-30 UTC: p95 985ms2026-10-01 UTC: p95 780ms2026-10-02 UTC: p95 752ms2026-10-03 UTC: p95 862ms2026-10-04 UTC: p95 864ms2026-10-05 UTC: p95 750ms2026-10-06 UTC: p95 588ms2026-10-07 UTC: p95 769ms2026-10-08 UTC: p95 834ms2026-10-09 UTC: p95 827ms2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 799ms2026-10-12 UTC: p95 971ms2026-10-13 UTC: p95 1.0s2026-10-14 UTC: p95 951ms2026-10-15 UTC: p95 921ms2026-10-16 UTC: p95 963ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 1.8s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.5s2026-10-23 UTC: p95 1.4s
Sep 24Oct 8Oct 23
Canada
1.3sp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 1.3s2026-09-25 UTC: p95 1.0s2026-09-26 UTC: p95 1.2s2026-09-27 UTC: p95 1.2s2026-09-28 UTC: p95 1.2s2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 752ms2026-10-02 UTC: p95 762ms2026-10-03 UTC: p95 937ms2026-10-04 UTC: p95 910ms2026-10-05 UTC: p95 937ms2026-10-06 UTC: p95 844ms2026-10-07 UTC: p95 770ms2026-10-08 UTC: p95 795ms2026-10-09 UTC: p95 834ms2026-10-10 UTC: p95 735ms2026-10-11 UTC: p95 859ms2026-10-12 UTC: p95 965ms2026-10-13 UTC: p95 922ms2026-10-14 UTC: p95 933ms2026-10-15 UTC: p95 835ms2026-10-16 UTC: p95 808ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.7s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.5s2026-10-23 UTC: p95 1.3s
Sep 24Oct 8Oct 23
UK
696msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 254ms2026-09-25 UTC: p95 257ms2026-09-26 UTC: p95 289ms2026-09-27 UTC: p95 237ms2026-09-28 UTC: p95 254ms2026-09-29 UTC: p95 260ms2026-09-30 UTC: p95 246ms2026-10-01 UTC: p95 384ms2026-10-02 UTC: p95 266ms2026-10-03 UTC: p95 228ms2026-10-04 UTC: p95 269ms2026-10-05 UTC: p95 235ms2026-10-06 UTC: p95 253ms2026-10-07 UTC: p95 555ms2026-10-08 UTC: p95 292ms2026-10-09 UTC: p95 535ms2026-10-10 UTC: p95 731ms2026-10-11 UTC: p95 264ms2026-10-12 UTC: p95 310ms2026-10-13 UTC: p95 290ms2026-10-14 UTC: p95 310ms2026-10-15 UTC: p95 591ms2026-10-16 UTC: p95 476ms2026-10-17 UTC: p95 235ms2026-10-18 UTC: p95 529ms2026-10-19 UTC: p95 952ms2026-10-20 UTC: p95 829ms2026-10-21 UTC: p95 752ms2026-10-22 UTC: p95 572ms2026-10-23 UTC: p95 696ms
Sep 24Oct 8Oct 23
Southeast Asia
1.1sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 1.0s2026-09-27 UTC: p95 1.3s2026-09-28 UTC: p95 892ms2026-09-29 UTC: p95 921ms2026-09-30 UTC: p95 533ms2026-10-01 UTC: p95 529ms2026-10-02 UTC: p95 887ms2026-10-03 UTC: p95 679ms2026-10-04 UTC: p95 488ms2026-10-05 UTC: p95 516ms2026-10-06 UTC: p95 526ms2026-10-07 UTC: p95 456ms2026-10-08 UTC: p95 572ms2026-10-09 UTC: p95 540ms2026-10-10 UTC: p95 819ms2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.5s2026-10-13 UTC: p95 932ms2026-10-14 UTC: p95 631ms2026-10-15 UTC: p95 523ms2026-10-16 UTC: p95 614ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.5s2026-10-23 UTC: p95 1.1s
Sep 24Oct 8Oct 23
Australia
2.0sp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 497ms2026-09-25 UTC: p95 608ms2026-09-26 UTC: p95 682ms2026-09-27 UTC: p95 735ms2026-09-28 UTC: p95 628ms2026-09-29 UTC: p95 766ms2026-09-30 UTC: p95 794ms2026-10-01 UTC: p95 752ms2026-10-02 UTC: p95 823ms2026-10-03 UTC: p95 594ms2026-10-04 UTC: p95 701ms2026-10-05 UTC: p95 763ms2026-10-06 UTC: p95 570ms2026-10-07 UTC: p95 685ms2026-10-08 UTC: p95 679ms2026-10-09 UTC: p95 571ms2026-10-10 UTC: p95 567ms2026-10-11 UTC: p95 505ms2026-10-12 UTC: p95 418ms2026-10-13 UTC: p95 445ms2026-10-14 UTC: p95 526ms2026-10-15 UTC: p95 346ms2026-10-16 UTC: p95 335ms2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 2.0s2026-10-19 UTC: p95 1.8s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 1.9s2026-10-22 UTC: p95 1.9s2026-10-23 UTC: p95 2.0s
Sep 24Oct 8Oct 23
South America
1.6sp95 · latest
2.5s1.3s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 1.4s2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 1.3s2026-09-27 UTC: p95 1.3s2026-09-28 UTC: p95 1.5s2026-09-29 UTC: p95 1.5s2026-09-30 UTC: p95 1.6s2026-10-01 UTC: p95 1.7s2026-10-02 UTC: p95 1.7s2026-10-03 UTC: p95 1.9s2026-10-04 UTC: p95 1.7s2026-10-05 UTC: p95 1.9s2026-10-06 UTC: p95 1.8s2026-10-07 UTC: p95 1.7s2026-10-08 UTC: p95 1.6s2026-10-09 UTC: p95 1.9s2026-10-10 UTC: p95 2.3s2026-10-11 UTC: p95 2.3s2026-10-12 UTC: p95 1.7s2026-10-13 UTC: p95 1.7s2026-10-14 UTC: p95 1.8s2026-10-15 UTC: p95 1.7s2026-10-16 UTC: p95 1.6s2026-10-17 UTC: p95 1.7s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 1.8s2026-10-21 UTC: p95 1.7s2026-10-22 UTC: p95 1.7s2026-10-23 UTC: p95 1.6s
Sep 24Oct 8Oct 23

Check your own site while you wait on Together AI

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Together AI. It cannot diagnose Together AI's own systems.

What we measured, function by function

Together AI answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when Together AI reports an incident on its status page, and again when it reports it resolved.

Get an email when Together AI reports an incident

Email me when Together AI reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when it reports an incident, one when it reports it resolved, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is Together AI's own statement from its status page, with our regional reading beside it.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 847msstatus code: 401checked: Oct 23, 2026, 11:51 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Together AI normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1257msstatus code: 401checked: Oct 23, 2026, 11:28 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Together AI normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 1404msstatus code: 401checked: Oct 23, 2026, 11:25 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Together AI normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 987msstatus code: 401checked: Oct 23, 2026, 11:39 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Together AI normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 966msstatus code: 401checked: Oct 23, 2026, 11:13 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Together AI normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 536msstatus code: 401checked: Oct 23, 2026, 11:50 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Together AI normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 313msstatus code: 401checked: Oct 23, 2026, 11:21 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Together AI normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1196msstatus code: 401checked: Oct 23, 2026, 11:37 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Together AI normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 924msstatus code: 401checked: Oct 23, 2026, 11:55 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Together AI normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 1833msstatus code: 401checked: Oct 23, 2026, 11:04 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Together AI normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Together AI, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Together AI yet, which is not evidence that nothing is wrong.

Recent probe events

No probe events on record yet for Together AI.

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Together AI since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Together AI covering any window you pick, with our check readings and Together AI's own claim at the time, side by side.

Full check history for Together AI: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Put this badge in your README

Together AI uptime by RealUptime's checksLive, from this page's own readings.
[![Together AI uptime by RealUptime's checks](https://realuptime.io/outages/together-ai/badge.svg?days=30)](https://realuptime.io/outages/together-ai)
<a href="https://realuptime.io/outages/together-ai"><img src="https://realuptime.io/outages/together-ai/badge.svg?days=30" alt="Together AI uptime by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. The window is printed on it, so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Together AI down?", https://realuptime.io/outages/together-ai. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

What we check

primaryfunctional: live API
https://api.together.xyz/v1/models
secondary
https://www.together.ai/
secondary
https://status.together.ai/

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.together.xyz

RealUptime is not affiliated with Together AI; the name identifies what we checked, and nothing here speaks for Together AI's own team. We send a single web request to Together AI from 10 regions on our own schedule and time the response. We do not see inside Together AI's systems, do not use an account or real transaction, and are not the same signal Together AI's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Together AI is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.