Is X (Twitter) down?
Operationalchecked moments ago
We reached X (Twitter) from all 10 regions we check.
As of Oct 5, 2026, 9:04 PM UTC, X (Twitter) answered RealUptime's probes in all 10 regions that returned a reading.
Last outage: 11 min on Sep 13, 2026 (web surface, from Europe, South America, US-East, US-Central, US-West and Canada).
Email me the next time we see X (Twitter) go down
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
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 web 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.
- WebprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
- AuthUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
What we measured, and what people reported
- North AmericaOperationalUS-East, US-West, US-Central, Canada
- US-EastOperationallatency: 223msstatus code: 200checked: Oct 5, 2026, 9:02 PM UTC0 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-WestOperationallatency: 634msstatus code: 200checked: Oct 5, 2026, 9:01 PM UTC0 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.
- US-CentralOperationallatency: 543msstatus code: 200checked: Oct 5, 2026, 9:00 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach X (Twitter) normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
- CanadaOperationallatency: 1318msstatus code: 200checked: Oct 5, 2026, 9:02 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach X (Twitter) normally. We do not have enough reports from Canada to say anything about what people there are seeing.
- South AmericaOperationallatency: 950msstatus code: 200checked: Oct 5, 2026, 8:59 PM UTC0 people in the last 5 minutesNot enough reports to sayOur South America probes reach X (Twitter) normally. We do not have enough reports from South America to say anything about what people there are seeing.
- EuropeOperationalEurope, UK
- EuropeOperationallatency: 241msstatus code: 200checked: Oct 5, 2026, 9:03 PM UTC0 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.
- UKOperationallatency: 383msstatus code: 200checked: Oct 5, 2026, 9:03 PM UTC0 people in the last 5 minutesNot enough reports to sayOur UK probes reach X (Twitter) normally. We do not have enough reports from UK to say anything about what people there are seeing.
- Asia PacificOperationalAsia-Pacific, Southeast Asia, Australia
- Asia-PacificOperationallatency: 434msstatus code: 200checked: Oct 5, 2026, 9:04 PM UTC0 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.
- Southeast AsiaOperationallatency: 539msstatus code: 200checked: Oct 5, 2026, 9:03 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach X (Twitter) normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
- AustraliaOperationallatency: 1280msstatus code: 200checked: Oct 5, 2026, 9:01 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach X (Twitter) 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 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
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.
Put this badge in your README
Live, from this page's own readings.[](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 10 minutes of downtime for X (Twitter) over the last 30 days, which is 99.9747% 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.
Separately, we measured 3 minutes where only one of our regions was affected. It is excluded above because most SLAs would not credit it, and it is the kind of outage a single-vantage monitor never sees at all.
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.