Is X (Twitter) down?
Partially degradedchecked moments ago
X (Twitter) is answering our probes, but its web surface is running at least 6x its 7-day median from US-West and its sign-in surface is running at least 0.5x its 7-day median from US-West. Everything else we check answered at its usual speed.
As of Oct 19, 2026, 8:55 PM UTC, RealUptime's checks of X (Twitter) passed in all 10 regions that returned a reading.
Last time our checks failed from two or more distant regions: 11 min on Sep 13, 2026 (web surface, from Europe, South America, US-East, US-Central, US-West and Canada).
Email me when our checks of X (Twitter) fail from two or more distant regions
X (Twitter) publishes no status feed we can read, so the only reading here is our check reading on the left.
X (Twitter) response time, by region
Check your own site while you wait on X (Twitter)
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: Checks passingUS-West: Degraded Answering, but 6x slower than its 7-day median.Europe: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
- AuthUS-East: Checks passingUS-West: Degraded Answering, but 0.5x slower than its 7-day median.Europe: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
What our checks show, and what people reported
- North AmericaDegradedUS-East, US-West, US-Central, Canada
- US-EastChecks passinglatency: 539msstatus code: 200checked: Oct 19, 2026, 8:55 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-WestDegradedlatency: 2196msstatus code: 200checked: Oct 19, 2026, 8:55 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-CentralChecks passinglatency: 308msstatus code: 200checked: Oct 19, 2026, 8:53 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.
- CanadaChecks passinglatency: 1401msstatus code: 200checked: Oct 19, 2026, 8:55 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 AmericaChecks passinglatency: 1215msstatus code: 200checked: Oct 19, 2026, 8:53 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.
- EuropeChecks passingEurope, UK
- EuropeChecks passinglatency: 2028msstatus code: 200checked: Oct 19, 2026, 8:55 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.
- UKChecks passinglatency: 367msstatus code: 200checked: Oct 19, 2026, 8:53 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 PacificChecks passingAsia-Pacific, Southeast Asia, Australia
- Asia-PacificChecks passinglatency: 1086msstatus code: 200checked: Oct 19, 2026, 8:54 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 AsiaChecks passinglatency: 915msstatus code: 200checked: Oct 19, 2026, 8:53 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.
- AustraliaChecks passinglatency: 1419msstatus code: 200checked: Oct 19, 2026, 8:54 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 probe events
check 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 check readings and X (Twitter)'s own claim at the time, side by side.
Full check history for X (Twitter): 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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 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 X (Twitter) down?", https://realuptime.io/outages/x-twitter. 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.
How our checks compare with X (Twitter)'s stated SLA
At or above your target
Our checks of X (Twitter) failed for none over the last 30 days, which is 100% uptime by our checks. A 99.9% target allows 43 minutes over that period.
Our checks show no gap in this period. That does not rule out one you saw.
These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, 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
What our check can and cannot see
A pass means the service's public web page loaded and answered normally. It does not show that the product, the API or sign-in behind it works; a page can load from a cache while the product is down.
Host checked: x.com