Live - 300+ check locations
Is X (Twitter) down right now?
HostTracker's monitoring network reached x.com and completed a full check without errors. It has been up for 27d 11h.
Stop finding out from a search - HostTracker's website monitoring checks the services you depend on from 300+ locations and alerts you the moment one changes.
Up
for 27d 11h
- Last check
- just now
- Next check
- -
- HTTP
- OK
Checking x.com right now
A fresh check, started when you opened this page - each probe runs its own independent DNS, TCP, TLS and HTTP request. Anonymous runs sample the network; a signed-in account checks from more locations.
How X (Twitter) has behaved
Every figure here comes from HostTracker's own checks of x.com, not from the vendor's status page.
Response time
516ms avg · 6911ms peak
What we check
-
HTTP528 ms average, every 10 minutesOK
-
Ping10 ms average, every 10 minutesOK
-
Page Speed4180 ms average, every 15 minutesFailing
90-day uptime
99.991% · 5 incidents · 11.8 min in total · longest 11.7 min
- Operational
- Degraded
- Down
- No data
Incident history
Every outage of X (Twitter)- 11.7 min
-
0 min
-
0 min
-
0 min
-
0.1 min
Is X (Twitter) not working for you?
Tell us what is broken. One click, no account.
One report per visitor per hour. We keep only the country and the problem type, never your IP address.
Problem reports, last 24 hours
Reports come from visitors of this page. A sharp rise above the usual level, together with failed checks in the live check below, means the problem is on X (Twitter)'s side, not yours.
Top reported problems
Share of reports in the last 2 hours.
About X (Twitter) outages
Written by the HostTracker monitoring team · updated from live probe data.
X (formerly Twitter) functions as a real-time public information channel as much as a social network - it's often where people check first during breaking news, and it's also where official status updates from OTHER companies' outages frequently get posted, which creates an odd twist: when X itself is down, it can be harder for the internet to coordinate around unrelated outages too. For businesses running ads, customer support, or automated posting through X's API, an outage can break scheduled content and support workflows even when the public-facing timeline still loads. Checking x.com's own reachability directly is the fastest way to confirm a real platform-wide issue versus a problem specific to one account or app.
Common causes of X (Twitter) downtime
Not sure whether it's X (Twitter) or your own connection? Read the full breakdown in our website down checker guide for a general walkthrough of diagnosing any outage, from DNS failures to expired certificates.
Timeline/feed-loading incidents that leave the app open but unable to load new posts
API-layer incidents that break third-party apps, bots, and automated posting without necessarily affecting the main web app
Media (image/video) delivery issues that leave text posts loading while attachments fail
Regional network or DNS issues making x.com unreachable from specific countries or ISPs
Other services we track
HostTracker has monitored websites and online services since 2004 and is trusted by 500,000+ sites today, covering 14 check types from 300+ global locations. Want the same multi-location confirmation and instant alerts for your own site or any service you depend on? Getting started costs nothing - start a free monitor or compare plans and pricing.
Questions people ask during an outage
The live probe run on this page tests x.com from a broad sample of HostTracker's 300+-location monitoring network - many independent networks at the same moment, rather than just your own connection. If every location fails to reach it, the outage is real and affects everyone; if only a few locations fail while most load normally, the problem is local to those regions or networks rather than X (Twitter) being fully down. A single refresh from your own browser can never make that distinction, because it only ever tests from one vantage point on one network.
Yes. HostTracker lets you add any URL - including third-party services you depend on, not just your own website - as a monitored target, and notifies you automatically the moment it becomes unreachable. Before sending an alert, HostTracker re-verifies a failure from multiple locations in its 300+-location network, so you're notified about real, confirmed outages rather than a single location's momentary blip. The free plan checks two monitors every 30 minutes indefinitely at no cost; paid plans check as often as once a minute, with alerts available through SMS, email, voice call, and several messenger apps.
No - as of the most recent check, x.com is responding normally to HostTracker's monitoring network, and has been up for 27d 11h. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.
No - as of the most recent check, x.com is responding normally to HostTracker's monitoring network, and has been up for 27d 11h. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.
No - as of the most recent check, x.com is responding normally to HostTracker's monitoring network, and has been up for 27d 11h. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.
Posting text and uploading media are handled by somewhat different backend systems, so it's a known pattern for text posts to work normally while image or video uploads fail or hang - this usually points to a media-pipeline-specific incident rather than a full platform outage. If it's consistent across multiple posts and not just one large file, it's more likely server-side than a problem with your specific upload.
Not necessarily. The consumer web/app experience and the developer API run on related but distinct infrastructure, so it's possible for one to have an incident while the other stays healthy - a third-party app or bot using the API can fail while x.com loads fine in a browser, or the reverse. If you depend on the API specifically, checking its status directly is more reliable than inferring API health from whether the website loads.
Monitor your website from 300+ locations
Start a free trial and get instant alerts when your site goes down - verified from multiple locations before you're notified.
- Trusted since 2004
- 500,000+ websites monitored
- 300+ checkpoints worldwide