Skip to content

Outage tracker / Together AI

Is Together AI down?

I'm having a problem

Operationalchecked 2 minutes ago

We reached Together AI from all 10 regions we check.

Functional endpoints verified

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

our independent probeslive · checked Sep 5, 2026, 2:06 AM UTC
US-East388 msOperational
US-West140 msOperational
Europe372 msOperational
Asia-Pacific259 msOperational
US-Central584 msOperational
Canada586 msOperational
UK327 msOperational
Southeast Asia657 msOperational
Australia232 msOperational
South America282 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
371msp95 · 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-08-22 UTC: p95 1.1s2026-08-23 UTC: p95 1.3s2026-08-24 UTC: p95 1.2s2026-08-25 UTC: p95 1.1s2026-08-26 UTC: p95 1.0s2026-08-27 UTC: p95 974ms2026-08-28 UTC: p95 1.2s2026-08-29 UTC: p95 1.0s2026-08-30 UTC: p95 1.1s2026-08-31 UTC: p95 1.2s2026-09-01 UTC: p95 1.4s2026-09-02 UTC: p95 949ms2026-09-03 UTC: p95 1s2026-09-04 UTC: p95 759ms2026-09-05 UTC: p95 371ms
Aug 7Aug 21Sep 5
US-West
139msp95 · 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-08-22 UTC: p95 262ms2026-08-23 UTC: p95 282ms2026-08-24 UTC: p95 506ms2026-08-25 UTC: p95 723ms2026-08-26 UTC: p95 849ms2026-08-27 UTC: p95 1.1s2026-08-28 UTC: p95 555ms2026-08-29 UTC: p95 564ms2026-08-30 UTC: p95 684ms2026-08-31 UTC: p95 546ms2026-09-01 UTC: p95 325ms2026-09-02 UTC: p95 363ms2026-09-03 UTC: p95 402ms2026-09-04 UTC: p95 229ms2026-09-05 UTC: p95 139ms
Aug 7Aug 21Sep 5
Europe
370msp95 · 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-08-22 UTC: p95 312ms2026-08-23 UTC: p95 781ms2026-08-24 UTC: p95 827ms2026-08-25 UTC: p95 828ms2026-08-26 UTC: p95 710ms2026-08-27 UTC: p95 621ms2026-08-28 UTC: p95 589ms2026-08-29 UTC: p95 427ms2026-08-30 UTC: p95 580ms2026-08-31 UTC: p95 471ms2026-09-01 UTC: p95 560ms2026-09-02 UTC: p95 650ms2026-09-03 UTC: p95 392ms2026-09-04 UTC: p95 567ms2026-09-05 UTC: p95 370ms
Aug 7Aug 21Sep 5
Asia-Pacific
402msp95 · 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-08-22 UTC: p95 427ms2026-08-23 UTC: p95 458ms2026-08-24 UTC: p95 578ms2026-08-25 UTC: p95 645ms2026-08-26 UTC: p95 831ms2026-08-27 UTC: p95 649ms2026-08-28 UTC: p95 773ms2026-08-29 UTC: p95 801ms2026-08-30 UTC: p95 416ms2026-08-31 UTC: p95 724ms2026-09-01 UTC: p95 766ms2026-09-02 UTC: p95 380ms2026-09-03 UTC: p95 891ms2026-09-04 UTC: p95 716ms2026-09-05 UTC: p95 402ms
Aug 7Aug 21Sep 5
US-Central
576msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 560ms2026-09-04 UTC: p95 603ms2026-09-05 UTC: p95 576ms
Aug 7Aug 21Sep 5
Canada
583msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 593ms2026-09-04 UTC: p95 676ms2026-09-05 UTC: p95 583ms
Aug 7Aug 21Sep 5
UK
325msp95 · latest
500ms250ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 328ms2026-09-04 UTC: p95 398ms2026-09-05 UTC: p95 325ms
Aug 7Aug 21Sep 5
Southeast Asia
807msp95 · latest
1s500ms0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 904ms2026-09-04 UTC: p95 1s2026-09-05 UTC: p95 807ms
Aug 7Aug 21Sep 5
Australia
357msp95 · 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-03 UTC: p95 759ms2026-09-04 UTC: p95 399ms2026-09-05 UTC: p95 357ms
Aug 7Aug 21Sep 5
South America
574msp95 · latest
1s500ms0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 910ms2026-09-04 UTC: p95 985ms2026-09-05 UTC: p95 574ms
Aug 7Aug 21Sep 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
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: 388msstatus code: 401checked: Sep 5, 2026, 2:04 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
      Operationallatency: 140msstatus code: 401checked: Sep 5, 2026, 2:03 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
      Operationallatency: 584msstatus code: 401checked: Sep 5, 2026, 2:03 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
      Operationallatency: 586msstatus code: 401checked: Sep 5, 2026, 2:06 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
    Operationallatency: 282msstatus code: 401checked: Sep 5, 2026, 1:38 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 372msstatus code: 401checked: Sep 5, 2026, 1:42 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
      Operationallatency: 327msstatus code: 401checked: Sep 5, 2026, 1:42 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 259msstatus code: 401checked: Sep 5, 2026, 1:54 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
      Operationallatency: 657msstatus code: 401checked: Sep 5, 2026, 1:14 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
      Operationallatency: 232msstatus code: 401checked: Sep 5, 2026, 2:06 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 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

Tell me when this goes down

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.

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 338h 8m since we started watching it on 2026-08-22, which is 100% uptime by our reading. A 99.9% target allows 20 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.