Skip to content

Outage tracker / Together AI

Is Together AI down?

I'm having a problem

Operationalchecked 3 minutes ago

We reached Together AI from all 10 regions we check.

As of Oct 5, 2026, 9:01 PM UTC, Together AI answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 44 days we have measured Together AI (since Aug 22, 2026).

our independent probeslive · checked Oct 5, 2026, 9:01 PM UTC
US-East525 msOperational
US-West260 msOperational
Europe225 msOperational
Asia-Pacific249 msOperational
US-Central512 msOperational
Canada445 msOperational
UK214 msOperational
Southeast Asia378 msOperational
Australia688 msOperational
South America1412 msOperational
their status pagetheir claim, not our reading

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

Together AI response time, by region

US-East
644msp95 · 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-06 UTC: p95 638ms2026-09-07 UTC: p95 626ms2026-09-08 UTC: p95 756ms2026-09-09 UTC: p95 650ms2026-09-10 UTC: p95 704ms2026-09-11 UTC: p95 716ms2026-09-12 UTC: p95 656ms2026-09-13 UTC: p95 697ms2026-09-14 UTC: p95 638ms2026-09-15 UTC: p95 916ms2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 1.3s2026-09-18 UTC: p95 1.2s2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 1.2s2026-09-21 UTC: p95 1.2s2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 829ms2026-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 644ms
Sep 6Sep 20Oct 5
US-West
333msp95 · latest
500ms250ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 377ms2026-09-07 UTC: p95 484ms2026-09-08 UTC: p95 430ms2026-09-09 UTC: p95 409ms2026-09-10 UTC: p95 424ms2026-09-11 UTC: p95 327ms2026-09-12 UTC: p95 416ms2026-09-13 UTC: p95 343ms2026-09-14 UTC: p95 292ms2026-09-15 UTC: p95 255ms2026-09-16 UTC: p95 229ms2026-09-17 UTC: p95 211ms2026-09-18 UTC: p95 224ms2026-09-19 UTC: p95 281ms2026-09-20 UTC: p95 228ms2026-09-21 UTC: p95 306ms2026-09-22 UTC: p95 337ms2026-09-23 UTC: p95 251ms2026-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 333ms
Sep 6Sep 20Oct 5
Europe
326msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 466ms2026-09-07 UTC: p95 404ms2026-09-08 UTC: p95 459ms2026-09-09 UTC: p95 549ms2026-09-10 UTC: p95 432ms2026-09-11 UTC: p95 400ms2026-09-12 UTC: p95 583ms2026-09-13 UTC: p95 367ms2026-09-14 UTC: p95 549ms2026-09-15 UTC: p95 510ms2026-09-16 UTC: p95 444ms2026-09-17 UTC: p95 474ms2026-09-18 UTC: p95 380ms2026-09-19 UTC: p95 370ms2026-09-20 UTC: p95 406ms2026-09-21 UTC: p95 384ms2026-09-22 UTC: p95 413ms2026-09-23 UTC: p95 472ms2026-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 326ms
Sep 6Sep 20Oct 5
Asia-Pacific
434msp95 · latest
1s500ms0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 313ms2026-09-07 UTC: p95 428ms2026-09-08 UTC: p95 388ms2026-09-09 UTC: p95 471ms2026-09-10 UTC: p95 497ms2026-09-11 UTC: p95 508ms2026-09-12 UTC: p95 390ms2026-09-13 UTC: p95 442ms2026-09-14 UTC: p95 484ms2026-09-15 UTC: p95 467ms2026-09-16 UTC: p95 451ms2026-09-17 UTC: p95 520ms2026-09-18 UTC: p95 527ms2026-09-19 UTC: p95 529ms2026-09-20 UTC: p95 457ms2026-09-21 UTC: p95 585ms2026-09-22 UTC: p95 401ms2026-09-23 UTC: p95 522ms2026-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 434ms
Sep 6Sep 20Oct 5
US-Central
755msp95 · 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-06 UTC: p95 724ms2026-09-07 UTC: p95 790ms2026-09-08 UTC: p95 817ms2026-09-09 UTC: p95 680ms2026-09-10 UTC: p95 678ms2026-09-11 UTC: p95 818ms2026-09-12 UTC: p95 671ms2026-09-13 UTC: p95 812ms2026-09-14 UTC: p95 738ms2026-09-15 UTC: p95 874ms2026-09-16 UTC: p95 1.2s2026-09-17 UTC: p95 1.2s2026-09-18 UTC: p95 1.2s2026-09-19 UTC: p95 1.2s2026-09-20 UTC: p95 901ms2026-09-21 UTC: p95 978ms2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 1.1s2026-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 755ms
Sep 6Sep 20Oct 5
Canada
957msp95 · 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-06 UTC: p95 757ms2026-09-07 UTC: p95 668ms2026-09-08 UTC: p95 845ms2026-09-09 UTC: p95 711ms2026-09-10 UTC: p95 733ms2026-09-11 UTC: p95 767ms2026-09-12 UTC: p95 573ms2026-09-13 UTC: p95 720ms2026-09-14 UTC: p95 867ms2026-09-15 UTC: p95 1.0s2026-09-16 UTC: p95 1.3s2026-09-17 UTC: p95 996ms2026-09-18 UTC: p95 1.2s2026-09-19 UTC: p95 918ms2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.3s2026-09-22 UTC: p95 1.3s2026-09-23 UTC: p95 1.0s2026-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 957ms
Sep 6Sep 20Oct 5
UK
235msp95 · 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-06 UTC: p95 363ms2026-09-07 UTC: p95 351ms2026-09-08 UTC: p95 349ms2026-09-09 UTC: p95 336ms2026-09-10 UTC: p95 368ms2026-09-11 UTC: p95 381ms2026-09-12 UTC: p95 420ms2026-09-13 UTC: p95 559ms2026-09-14 UTC: p95 395ms2026-09-15 UTC: p95 335ms2026-09-16 UTC: p95 337ms2026-09-17 UTC: p95 343ms2026-09-18 UTC: p95 271ms2026-09-19 UTC: p95 241ms2026-09-20 UTC: p95 241ms2026-09-21 UTC: p95 279ms2026-09-22 UTC: p95 272ms2026-09-23 UTC: p95 242ms2026-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 235ms
Sep 6Sep 20Oct 5
Southeast Asia
517msp95 · 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-06 UTC: p95 868ms2026-09-07 UTC: p95 912ms2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 905ms2026-09-10 UTC: p95 1.0s2026-09-11 UTC: p95 1.0s2026-09-12 UTC: p95 936ms2026-09-13 UTC: p95 917ms2026-09-14 UTC: p95 839ms2026-09-15 UTC: p95 1.1s2026-09-16 UTC: p95 871ms2026-09-17 UTC: p95 655ms2026-09-18 UTC: p95 743ms2026-09-19 UTC: p95 923ms2026-09-20 UTC: p95 909ms2026-09-21 UTC: p95 925ms2026-09-22 UTC: p95 1.0s2026-09-23 UTC: p95 1.7s2026-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 517ms
Sep 6Sep 20Oct 5
Australia
776msp95 · latest
1s500ms0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 579ms2026-09-07 UTC: p95 594ms2026-09-08 UTC: p95 786ms2026-09-09 UTC: p95 694ms2026-09-10 UTC: p95 654ms2026-09-11 UTC: p95 607ms2026-09-12 UTC: p95 519ms2026-09-13 UTC: p95 555ms2026-09-14 UTC: p95 583ms2026-09-15 UTC: p95 601ms2026-09-16 UTC: p95 665ms2026-09-17 UTC: p95 658ms2026-09-18 UTC: p95 656ms2026-09-19 UTC: p95 639ms2026-09-20 UTC: p95 729ms2026-09-21 UTC: p95 609ms2026-09-22 UTC: p95 518ms2026-09-23 UTC: p95 678ms2026-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 776ms
Sep 6Sep 20Oct 5
South America
1.9sp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.4s2026-09-07 UTC: p95 1.4s2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 1.2s2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 690ms2026-09-12 UTC: p95 764ms2026-09-13 UTC: p95 787ms2026-09-14 UTC: p95 1.0s2026-09-15 UTC: p95 832ms2026-09-16 UTC: p95 1.7s2026-09-17 UTC: p95 1.3s2026-09-18 UTC: p95 1.2s2026-09-19 UTC: p95 1.4s2026-09-20 UTC: p95 1.3s2026-09-21 UTC: p95 1.2s2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 1.6s2026-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.9s
Sep 6Sep 20Oct 5

Is it Together AI, or is it you?

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: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational

Get an email when we see Together AI go down, and when it is back

Get told when we measure this

We will tell you when our probes stop reaching Together AI, and again when they can reach it again. That is our own measurement from ten regions, not Together AI's status page. No account, no card.

Delivery channel

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

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 we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 525msstatus code: 401checked: Oct 5, 2026, 8:50 PM 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
      Operationallatency: 260msstatus code: 401checked: Oct 5, 2026, 8:37 PM 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
      Operationallatency: 512msstatus code: 401checked: Oct 5, 2026, 8:20 PM 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
      Operationallatency: 445msstatus code: 401checked: Oct 5, 2026, 8:32 PM 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
    Operationallatency: 1412msstatus code: 401checked: Oct 5, 2026, 9:00 PM 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 225msstatus code: 401checked: Oct 5, 2026, 8:51 PM 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
      Operationallatency: 214msstatus code: 401checked: Oct 5, 2026, 9:01 PM 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 249msstatus code: 401checked: Oct 5, 2026, 8:36 PM 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
      Operationallatency: 378msstatus code: 401checked: Oct 5, 2026, 8:47 PM 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
      Operationallatency: 688msstatus code: 401checked: Oct 5, 2026, 8:54 PM 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 outages

No outages on record yet for Together AI.

measured 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 measurements and Together AI's own claim at the time, side by side.

Full availability history for Together AI: 90-day availability by region, month-by-month uptime, and every incident 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 measured by RealUptimeLive, from this page's own readings.
[![Together AI uptime measured by RealUptime](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 measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and 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: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Together AI's SLA implies, from our measurement

At or above your target

We measured none of downtime for Together AI over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Together AI's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: live API
https://api.together.xyz/v1/models
secondary
https://www.together.ai/
secondary
https://status.together.ai/
RealUptime is not affiliated with Together AI; the name identifies what we measured, 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 clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.