isitdownrightnow.app
  1. Home
  2. Services
  3. X (Twitter)
X (Twitter) x.com

Is X (Twitter) down right now? Live status and outage tracker

No, X (Twitter) is up.

No widespread outage detected. 44 user reports in the last hour is within the normal range.

Live Last spike Data refreshes every 5 minutes
Not working for you? Help centre
User reports, last 24 hours, 15 minutes a segment: 95 flowing, 0 slow (elevated), 1 jammed (outage)

User reports, last 24 hours

1,086 reports in total, counted in 15-minute windows

In the last hour, 44 problem reports came in for X (Twitter), against about 82 at this time on a usual day. Over the last 24 hours there were 1,086 reports. Worldwide, most recent reports were about feed / timeline (27%) and app (26%). The last spike in reports was 14 h ago and lasted 16 min. These are user reports from the US, where most people report X (Twitter) problems.

Around the world right now: normal in 71 other countries. Most reports in the last hour: Brazil 9 · France 6 · Indonesia 6. By country

In the past 24 hours, 1,086 user reports came in for X (Twitter). Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 98.96% uptime for the day. The most recent spike big enough to count as an outage was 23 hours ago. The busiest 15-minute window of the day had 71 reports, about 23 hours ago.
Reports, last hour
44
15% on the hour before
Uptime, 24 h
98.96%
15 min of outage
Last outage
23 h ago
Lasted 15 min
Busiest 15 minutes
71
71 reports, 23 h ago
Last 24 hours

X (Twitter) outages and problems

In the past 24 hours, 1,086 user reports came in for X (Twitter). Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 98.96% uptime for the day.

The most recent spike big enough to count as an outage was 23 hours ago. The busiest 15-minute window of the day had 71 reports, about 23 hours ago.

  • Outage
    Ended 23 h ago
    Lasted 15 min
    71peak reports
Report categories

What people can report about X (Twitter)

What went wrong

What people said was wrong in recent problem reports for X (Twitter) worldwide.

  1. Feed / Timeline27%
  2. App26%
  3. Website23%
  4. Server Connection10%
  5. Login10%
  6. Posting / Publishing4%

Share of 573 recent reports that said what was wrong, from every country listed below.

World map

X (Twitter) reports around the world

In the last 24 hours, 3,850 problem reports about X (Twitter) came in from 69 countries. Right now reports are at the usual level in every country.

  • Outage now
  • Problems now
  • Normal
Each dot is a group of recent reports, coloured by how its country is doing now; bigger dots, more reports.
CountryNowLast hour24 hours
The US numbers above Normal 471,087
Brazil Normal 9152
France Normal 681
Indonesia Normal 652
The UK Normal 4139
Spain Normal 430
Japan Normal 3430
Canada Normal 373
Mexico Normal 360
Turkey Normal 263
Argentina Normal 230
India Normal 1887

Each country's status compares its reports with the usual level there. 60 more countries had 766 reports in the last 24 hours. Map outlines: Natural Earth.

Last 30 days

X (Twitter) problem spikes, last 30 days

Since 5 October, X (Twitter) had 6 outage spikes and 2 periods of elevated reports. The longest lasted 2 h 47 min, on 29 October.

  • Sat 3 Oct: no data
  • Sun 4 Oct: no data
  • Mon 5 Oct: 37 reports (outage spike that day)
  • Tue 6 Oct: 9 reports
  • Wed 7 Oct: 7 reports
  • Thu 8 Oct: 6 reports
  • Fri 9 Oct: 6 reports
  • Sat 10 Oct: 8 reports
  • Sun 11 Oct: 13 reports
  • Mon 12 Oct: 15 reports
  • Tue 13 Oct: 7 reports
  • Wed 14 Oct: 16 reports
  • Thu 15 Oct: 19 reports
  • Fri 16 Oct: 16 reports
  • Sat 17 Oct: 12 reports
  • Sun 18 Oct: 12 reports
  • Mon 19 Oct: 9 reports
  • Tue 20 Oct: 20 reports
  • Wed 21 Oct: no data
  • Thu 22 Oct: 2 reports
  • Fri 23 Oct: 281 reports (outage spike that day)
  • Sat 24 Oct: 15 reports
  • Sun 25 Oct: 15 reports
  • Mon 26 Oct: 14 reports
  • Tue 27 Oct: 14 reports (outage spike that day)
  • Wed 28 Oct: 326 reports (elevated reports that day)
  • Thu 29 Oct: 1,597 reports (outage spike that day)
  • Fri 30 Oct: 1,117 reports (outage spike that day)
  • Sat 31 Oct: 1,085 reports (outage spike that day)
  • Sun 1 Nov: no data
  • Elevated reports
    Sat 31 Oct, 09:57–10:14
    Lasted 16 min
    20peak reports
  • Outage
    Sat 31 Oct, 01:04–01:19
    Lasted 15 min
    73peak reports
  • Outage
    Fri 30 Oct, 05:19–05:45
    Lasted 26 min
    57peak reports
  • Outage
    Thu 29 Oct, 18:52–21:39
    Lasted 2 h 47 min
    93peak reports
  • Elevated reports
    Wed 28 Oct, 07:21–07:48
    Lasted 27 min
    30peak reports
  • Outage
    Tue 27 Oct, 19:16–19:31
    Lasted 15 min
    145peak reports
  • Outage
    Fri 23 Oct, 17:29–18:27
    Lasted 59 min
    128peak reports
  • Outage
    Mon 5 Oct, 22:51–23:21
    Lasted 30 min
    15peak reports

By country

Each square is one day in the countries with the most reports: red when reports stayed at outage level for half an hour or more, amber when they stayed above the usual level for an hour or more, grey otherwise.

  • The US4,367
  • India2,493
  • Mexico1,958
  • Brazil1,258
  • Japan1,211
  • Canada889
  • The UK696
  • France307

Country history starts on 28 October 2026. Days run from midnight to midnight, Central European time.

A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 5 October 2026. Monthly reports for all services

Troubleshooting

How to fix X (Twitter) not working

X (Twitter) is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:

  1. Check the X report level

    Look at the report level at the top of this page before you change any settings. A jump in reports, counted in 15-minute windows over the last 24 hours, points to a service-side problem; a normal level points to your device or connection.

  2. Force close the X app

    On iPhone, swipe up from the bottom and hold to open the app switcher, then swipe the app away; on Android, open Recents and swipe its card away. Open it again and repeat the action that failed.

  3. Sign out and back in

    Open the side menu, then go to Settings and Support > Settings and privacy > Your account > Account information > Sign out. Sign back in with your password and complete two-factor authentication if you use it; a fresh sign-in often clears a stuck session.

  4. Reinstall the app

    Delete the app from your phone. Open the App Store or Google Play, find the app, and tap Get or Install; your account stays on the service's servers.

While X (Twitter) is down: what to use instead

  • x.com in a browser If the app shows a blank timeline or keeps telling you something went wrong, open the site in a desktop or mobile browser, because the app and the website sometimes break separately.
  • Bluesky Plenty of journalists and public accounts post there as well, so you can keep up with breaking news while your usual feed won't load.
  • Threads You sign in with your Instagram account, so setup takes a minute.
  • Mastodon Join any server and look up the people you follow; many news outlets and developers keep accounts there.
Your device

Fix X (Twitter) on Windows, Mac, Android and iPhone

X (Twitter) on Windows

Fix
To fix X (Twitter) on Windows, clear your browser's cache and cookies, or try accessing the site in an Incognito window. Ensure your browser is updated to the latest version and temporarily disable conflicting extensions like ad blockers.
Check
Check if X (Twitter) is down on Windows by trying to load the official website in an alternative browser or a private browsing window. If you receive a connection timeout or server error across multiple browsers, the issue is likely on their end.
Command Prompt
ping x.comTest whether X (Twitter)'s servers reply
nslookup x.comCheck that X (Twitter)'s DNS resolves
tracert x.comTrace where the connection drops
ipconfig /flushdnsClear the DNS cache, then reload

X (Twitter) on Mac

Fix
Fix X (Twitter) on macOS by clearing Safari or Chrome browsing history and disabling extensions that may interfere with page scripts. You can also restart your Mac and router to resolve local network routing issues.
Check
To tell if X (Twitter) is down on a Mac, check if the website fails to load in Safari and other installed browsers. If the page displays a server error or fails to resolve, try loading a different website to verify your internet connection.
Terminal
ping -c 4 x.comTest whether X (Twitter)'s servers reply
nslookup x.comCheck that X (Twitter)'s DNS resolves
traceroute x.comTrace where the connection drops
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderFlush the macOS DNS cache, then reload

X (Twitter) on Android

Fix
Fix X (Twitter) on Android by clearing the app's cache and data in your device settings, or updating the app to the latest version via the Google Play Store. Reinstalling the app can also resolve persistent loading issues.
Check
Determine if X (Twitter) is down on Android by checking if the app fails to load feeds while you are connected to both Wi-Fi and mobile data. If you see a 'Cannot retrieve posts' error, try accessing the service via a mobile web browser.

X (Twitter) on iPhone and iPad

Fix
Fix X (Twitter) on iPhone or iPad by force closing and restarting the app, or checking the App Store for any pending updates. If the problem persists, uninstalling and reinstalling the app will clear corrupted temporary files.
Check
Check if X (Twitter) is down on iOS by attempting to refresh your timeline or posting an update. If you receive persistent connection errors on both Wi-Fi and cellular data, check if the mobile website works in Safari.
Same time

Problems at the same time as X (Twitter)

Since 5 October, 7 of X (Twitter)'s 8 spikes in problem reports overlapped a spike at another service.

When several services get problem reports at once, something they share, such as a cloud host or a network, can be the real cause. Matching times alone do not prove it.

Most often at the same time

How many of X (Twitter)'s spikes overlapped one of theirs.

During the latest spike

X (Twitter): Sat 31 Oct, 09:57 to 10:14

Red dot: outage. Amber dot: elevated reports.

A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.

Busiest times

When people report X (Twitter) problems

The busiest hour for reports about X (Twitter) is 22:00 to 23:00 Central European time, and the busiest day is Thursday.

By hour of the day

  • 00:00 to 01:00: 7.1 reports on an average day
  • 01:00 to 02:00: 8.5 reports on an average day
  • 02:00 to 03:00: 8.1 reports on an average day
  • 03:00 to 04:00: 7.3 reports on an average day
  • 04:00 to 05:00: 8.8 reports on an average day
  • 05:00 to 06:00: 5.9 reports on an average day
  • 06:00 to 07:00: 6.2 reports on an average day
  • 07:00 to 08:00: 3.9 reports on an average day
  • 08:00 to 09:00: 4.5 reports on an average day
  • 09:00 to 10:00: 4.2 reports on an average day
  • 10:00 to 11:00: 3.2 reports on an average day
  • 11:00 to 12:00: 3.9 reports on an average day
  • 12:00 to 13:00: 4.2 reports on an average day
  • 13:00 to 14:00: 5.1 reports on an average day
  • 14:00 to 15:00: 5.3 reports on an average day
  • 15:00 to 16:00: 5.1 reports on an average day
  • 16:00 to 17:00: 6.7 reports on an average day
  • 17:00 to 18:00: 6.2 reports on an average day
  • 18:00 to 19:00: 6 reports on an average day
  • 19:00 to 20:00: 8.1 reports on an average day
  • 20:00 to 21:00: 7.9 reports on an average day
  • 21:00 to 22:00: 8.3 reports on an average day
  • 22:00 to 23:00: 9.7 reports on an average day
  • 23:00 to 00:00: 8.6 reports on an average day

By day of the week

  • Monday: 18 reports on an average Monday
  • Tuesday: 13 reports on an average Tuesday
  • Wednesday: 117 reports on an average Wednesday
  • Thursday: 352 reports on an average Thursday
  • Friday: 279 reports on an average Friday
  • Saturday: 268 reports on an average Saturday
  • Sunday: 13 reports on an average Sunday

Each bar is the average number of user reports in that hour, or on that day of the week, from 24 days of reports since 5 October 2026. The busiest bar is highlighted. Spikes in reports are left out, so one outage does not set the pattern.

About

What happens when X (Twitter) goes down

X (Twitter) is a social network built around posts, replies, direct messages and live updates, and journalists, brands, sports fans and public agencies rely on it to reach people fast. An outage interrupts reading the timeline, posting updates and getting alerts or messages through.

Timeline refresh and posting usually fail first: new posts may not load, and a post can stall or return a generic 'Something went wrong. Try reloading' message. Replies and direct messages can hang next, while media uploads, search, notifications and profile pages may lag or come back empty. The trouble is often partial: the mobile app can fail while the web session still works, or one region can see errors while another does not. A working login screen proves little, since the feed and posting path can break after you are signed in.

Servers and network

X (Twitter) IP address, servers and network

IPv4 address
162.159.140.229
IPv6
Not offered
Network
AS13335 · Cloudflare, Inc., registered in the United States
Served through
Cloudflare · our check was answered by its Frankfurt (FRA) data centre
DNS hosted by
its own name servers (twtrdns.net)
HTTPS certificate
Issued by Let's Encrypt, valid until 27 Dec 2026 (56 days)
HTTP/3
Not advertised
Our check
Answered in 177 ms

Checked from our server in Frankfurt, Germany, 13 h ago, for x.com. A service behind a CDN answers from many data centres, usually the one nearest to you, so these addresses are where its traffic enters, not where its own servers stand. Visitors elsewhere may see different addresses.

Checked from 11 places around the world

All 11 locations got an answer from x.com. Fastest from Los Angeles (107 ms), slowest from Singapore (676 ms). The answers came through 2 networks: Cloudflare, Inc. (AS13335) and Fastly, Inc. (AS54113).

LocationResultTimeAddress reached
FrankfurtGermanyUp190 ms162.159.140.229Cloudflare, Inc.
ViennaAustriaUp224 ms162.159.140.229Cloudflare, Inc.
MilanItalyUp196 ms162.159.140.229Cloudflare, Inc.
ParisFranceUp205 ms162.159.140.229Cloudflare, Inc.
AmsterdamNetherlandsUp189 ms172.66.0.227Cloudflare, Inc.
MadridSpainUp192 ms172.66.0.227Cloudflare, Inc.
WarsawPolandUp235 ms172.66.0.227Cloudflare, Inc.
Los AngelesUSAUp107 ms151.101.2.146Fastly, Inc.
São PauloBrazilUp210 ms172.66.0.227Cloudflare, Inc.
SingaporeSingaporeUp676 ms162.159.140.229Cloudflare, Inc.
TokyoJapanUp164 ms162.159.140.229Cloudflare, Inc.

Checked with check-host.net from its servers in these cities 4 h ago, for x.com. Time is how long each server took to load the page.

Questions

X (Twitter) FAQ

Is X (Twitter) down right now?
The status at the top of this page shows whether user problem reports for the service are above their usual level, counted in 15-minute windows over the last 24 hours. That reading comes from what people report; the site does not ping or probe anything itself. To rule out your own connection, load another site, switch to mobile data, and sign out and back in. If the app misbehaves on one network but behaves on another, the fault is local.

Why does my timeline stay empty while search still works?
A stale cache or an old app build often breaks the timeline feed while search, which pulls fresh from the server, keeps working. Force close the app and clear its cache on Android, or delete and reinstall it on iOS. Test that first. If the feed returns on mobile data but stalls on Wi-Fi, your network is the problem.

My post fails with "Something went wrong. Try reloading." What should I do?
That message usually means the request never reached the server or came back rejected, so your draft stays in the compose box. Copy the text out, reload the page or restart the app, then post again. Media uploads trip this more often than plain text, so try posting without the image or video to see which part fails.

Why is my login code from X not arriving?
Short-code SMS messages get filtered by some carriers, so the code can lag or never land. Check that your phone clock is set to automatic before you request another code, because a wrong time breaks codes from an authenticator app. If you still have access to the account, add a second sign-in method while you can.

Why do direct messages fail to send when my timeline loads fine?
A recipient who only accepts messages from people they follow will not get yours, and the app can show a plain failure instead of explaining why. Check whether the person follows you back, and drop any links if the message keeps bouncing. When the timeline loads and only DMs fail, look at account limits before blaming an outage.
For your site

Put the X (Twitter) status badge on your site

Paste one of these into a web page, a blog post or a README. The badge shows the same status as this page, based on user problem reports. Browsers can keep a copy for up to 4 hours. It links back here.

X (Twitter) status badge, as it looks now

HTML
<a href="https://isitdownrightnow.app/services/twitter/"><img src="https://isitdownrightnow.app/badge/twitter.svg" alt="X (Twitter) status" height="20"></a>
Markdown, for README files
[![X (Twitter) status](https://isitdownrightnow.app/badge/twitter.svg)](https://isitdownrightnow.app/services/twitter/)

The badge is a plain image: no scripts, no cookies. People who see it on your page load it from our server.

How we track X (Twitter)

The status on this page comes from user-submitted problem reports for X (Twitter), counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for X (Twitter), so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.

When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. X (Twitter) doesn't publish a public status page that we know of, so user reports are often the quickest sign that something is wrong on their side.

Elsewhere

Check other services

See all 500+ services

Problems elsewhere right now

Strips: user reports, last 6 hours, 15 minutes a segment.