Skip to content

Outage tracker / X (Twitter)

Is X (Twitter) down?

Short linkrlup.io/down/x-twitter

I'm having a problem

Operationalchecked 21 minutes ago

We reached X (Twitter) from all 4 regions we check.

Functional endpoints verified

No outage recorded in the 14 days we have measured X (Twitter) (since Aug 20, 2026).

our independent probeslive · checked Sep 3, 2026, 1:09 AM UTC
US-East515 msOperational
US-West55 msOperational
Europe201 msOperational
Asia-Pacific385 msOperational
their status pagetheir claim, not our reading

X (Twitter) publishes no status feed we can read, so the only independent reading here is ours on the left.

X (Twitter) response time, by region

US-East
892msp95 · 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-20 UTC: p95 1.0s2026-08-21 UTC: p95 1.0s2026-08-22 UTC: p95 1.0s2026-08-23 UTC: p95 1.2s2026-08-24 UTC: p95 1.2s2026-08-25 UTC: p95 1.1s2026-08-26 UTC: p95 1.2s2026-08-27 UTC: p95 1.1s2026-08-28 UTC: p95 843ms2026-08-29 UTC: p95 836ms2026-08-30 UTC: p95 874ms2026-08-31 UTC: p95 848ms2026-09-01 UTC: p95 930ms2026-09-02 UTC: p95 889ms2026-09-03 UTC: p95 892ms
Aug 5Aug 19Sep 3
US-West
306msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 546ms2026-08-21 UTC: p95 545ms2026-08-22 UTC: p95 328ms2026-08-23 UTC: p95 422ms2026-08-24 UTC: p95 395ms2026-08-25 UTC: p95 455ms2026-08-26 UTC: p95 354ms2026-08-27 UTC: p95 562ms2026-08-28 UTC: p95 547ms2026-08-29 UTC: p95 452ms2026-08-30 UTC: p95 504ms2026-08-31 UTC: p95 435ms2026-09-01 UTC: p95 331ms2026-09-02 UTC: p95 374ms2026-09-03 UTC: p95 306ms
Aug 5Aug 19Sep 3
Europe
251msp95 · latest
500ms250ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 328ms2026-08-21 UTC: p95 324ms2026-08-22 UTC: p95 328ms2026-08-23 UTC: p95 359ms2026-08-24 UTC: p95 440ms2026-08-25 UTC: p95 387ms2026-08-26 UTC: p95 363ms2026-08-27 UTC: p95 343ms2026-08-28 UTC: p95 350ms2026-08-29 UTC: p95 356ms2026-08-30 UTC: p95 350ms2026-08-31 UTC: p95 342ms2026-09-01 UTC: p95 365ms2026-09-02 UTC: p95 426ms2026-09-03 UTC: p95 251ms
Aug 5Aug 19Sep 3
Asia-Pacific
471msp95 · 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-20 UTC: p95 736ms2026-08-21 UTC: p95 585ms2026-08-22 UTC: p95 678ms2026-08-23 UTC: p95 755ms2026-08-24 UTC: p95 699ms2026-08-25 UTC: p95 754ms2026-08-26 UTC: p95 742ms2026-08-27 UTC: p95 787ms2026-08-28 UTC: p95 745ms2026-08-29 UTC: p95 716ms2026-08-30 UTC: p95 668ms2026-08-31 UTC: p95 701ms2026-09-01 UTC: p95 733ms2026-09-02 UTC: p95 921ms2026-09-03 UTC: p95 471ms
Aug 5Aug 19Sep 3

Is it X (Twitter), 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 X (Twitter) -- it cannot diagnose X (Twitter)'s own systems.

What we measured, function by function

X (Twitter) 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 auth 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: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
  • AuthprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
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

  • US-East
    Operationallatency: 515msstatus code: 401checked: Sep 3, 2026, 1:09 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach X (Twitter) normally. We do not have enough reports from US-East to say anything about what people there are seeing.
  • US-West
    Operationallatency: 55msstatus code: 401checked: Sep 3, 2026, 1:09 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach X (Twitter) normally. We do not have enough reports from US-West to say anything about what people there are seeing.
  • Europe
    Operationallatency: 201msstatus code: 401checked: Sep 3, 2026, 1:08 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach X (Twitter) normally. We do not have enough reports from Europe to say anything about what people there are seeing.
  • Asia-Pacific
    Operationallatency: 385msstatus code: 401checked: Sep 3, 2026, 1:06 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach X (Twitter) normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
  • US-Central
    Not monitored from this regionX (Twitter) is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Canada
    Not monitored from this regionX (Twitter) is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • UK
    Not monitored from this regionX (Twitter) is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Southeast Asia
    Not monitored from this regionX (Twitter) is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Australia
    Not monitored from this regionX (Twitter) is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionX (Twitter) is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say

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

These are unverified reports from people using X (Twitter), 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 X (Twitter) yet, which is not evidence that nothing is wrong.

Recent outages

No outages on record yet for X (Twitter).

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

We have been measuring X (Twitter) since August 20, 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 X (Twitter) covering any window you pick, with our measurements and X (Twitter)'s own claim at the time, side by side.

Full availability history for X (Twitter): 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 X (Twitter), and again when they can reach it again. That is our own measurement from ten regions, not X (Twitter)'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

X (Twitter) uptime measured by RealUptimeLive, from this page's own readings.
[![X (Twitter) uptime measured by RealUptime](https://realuptime.io/outages/x-twitter/badge.svg?days=30)](https://realuptime.io/outages/x-twitter)
<a href="https://realuptime.io/outages/x-twitter"><img src="https://realuptime.io/outages/x-twitter/badge.svg?days=30" alt="X (Twitter) 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 X (Twitter)'s SLA implies, from our measurement

At or above your target

We measured none of downtime for X (Twitter) over the 337h 30m since we started watching it on 2026-08-20, 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 X (Twitter)'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: auth surface
https://api.x.com/2/tweets/20
secondary
https://x.com/
RealUptime is not affiliated with X (Twitter); the name identifies what we measured, and nothing here speaks for X (Twitter)'s own team. We send a single web request to X (Twitter) from 4 regions on our own schedule and time the response. We do not see inside X (Twitter)'s systems, do not use an account or real transaction, and are not the same signal X (Twitter)'s own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for X (Twitter) 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. X (Twitter) operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. Read the full methodology.

Related services

BlueskyDiscordFacebookGoogle MeetInstagram