Is X (Twitter) down right now?
Checking…Verifying live status…
Our latest checks found X (Twitter) responding normally. Live verification is running now.
Your report feeds the live outage-velocity detector. One click per 30 s.
Live latency (probe round-trip, ms)
User reports, last 24 hours
Outage history
last 30 days
Recent outages and issues we recorded for X (Twitter), based on our own checks. An episode opens on the second check that finds a problem, since a single adverse reading is not reported, and closes when a check finds the service normal again.
No problemsProblemsOutageNot monitored
What X (Twitter) reported
last 30 days
Taken from X (Twitter)'s own published incident feed. These are their words about their own service, shown here so you can compare them with what we measured. Scheduled maintenance and test posts are filtered out.
Comments
Comments are hosted and moderated via Disqus. Spam is filtered automatically, readers can flag anything, and the thread loads only when you scroll to it so the rest of the page stays fast.
Comments are loading in our built-in box because Disqus was blocked or unavailable. Spam and abuse are filtered automatically, and comments are hidden once 3 readers flag them.
How we check X (Twitter)
No evidence of problems with X (Twitter). Our last recorded check found it behaving normally. That does not rule out a fault affecting only some users or regions.
Every check runs a four-tier cascade and stops at the first tier that gives a clear answer: X (Twitter)'s official status feed, then a direct HTTP probe, then an ICMP network ping, and finally reports from visitors. The Verification tier box above tells you which one produced the verdict you are looking at. When enough separate people report a problem for it to be well outside what X (Twitter) normally sees, that counts as evidence too, which is how a partial fault can show here before an operator's own status page catches up.
X (Twitter) (x.com) is re-checked continuously, and this page picks up any change on its own, with no refresh needed.
Common X (Twitter) problems users report
- Timeline failing to load or showing nothing new
- Posts failing to send or vanishing after posting
- Rate limit messages while browsing normally
- Login loops and two-factor verification failures
What to do when X (Twitter) is not working
First check the banner above. If it shows evidence of problems, the fault is most likely on X (Twitter)'s side and waiting is usually the only option. If it shows nothing wrong, wait out a rate limit rather than reloading, because reloading counts against the same limit and extends it. Then try the web version in a private window, which separates the app's cached session from an actual outage.
About X (Twitter)
X, formerly Twitter, is a real-time public conversation platform and often the first place people go to check whether something else is down. When X itself breaks, timelines fail to load and posting returns rate-limit errors.
Official X (Twitter) resources
Cross-check an incident with the company's own channels:
- X (Twitter) help centerSupport articles and contact options
- @Support on XOften the fastest official acknowledgement
Frequently asked questions
Is X (Twitter) down right now?
No. Our checks are finding no problems with X (Twitter) right now. That verdict is live, and the banner at the top of this page carries it too. We re-check X (Twitter) continuously using its official status feed, direct network probes and reports from visitors, stopping at the first check that gives a clear answer, and the page updates itself as soon as anything changes. A green verdict does not rule out a fault affecting only some users or regions.
What usually goes wrong with X (Twitter)?
The problems visitors report most often on this page are website / app down, can't log in, feed won't load, no notifications, can't post or comment, images not loading and messages not sending. Those are the options the report button offers for X (Twitter), chosen for how this service actually fails rather than a generic list, and the "user reports" chart above breaks down which ones people are picking right now.
Why is X (Twitter) not loading for me when this page says it is fine?
Our checks run from one place on the internet, so a fault limited to your region or network can be real while our probes succeed. With X (Twitter) specifically, the timeline, posting, direct messages, media and login are separate systems, and X applies per-account rate limits that return errors indistinguishable from an outage. Your account can be limited while everyone around you browses normally. That is why this page reports what it observed rather than declaring the service healthy, and why reports from other visitors count toward the verdict.
How do I tell whether it is X (Twitter) or my own connection?
For X (Twitter), open x.com in a private window while signed out. Public content loading while your signed-in timeline does not points at your account or a rate limit rather than X being down. A problem that follows you across networks and devices is very unlikely to be yours.
What should I do while X (Twitter) is down?
If this page shows evidence of problems, the fault is most likely on X (Twitter)'s side. Specifically: do not repost something that appeared to fail. Posts during an incident are often accepted without a confirmation and show up later, so reposting duplicates them. Avoid logging out, since sign-in is frequently the part that is broken. Reporting it here helps other people see they are not alone.
How does status.buzz check X (Twitter)?
Continuously, around the clock. X (Twitter) does not publish a machine-readable status feed, so we cannot read a verdict from them. We probe x.com directly over HTTP, fall back to an ICMP ping if that is inconclusive, and weigh reports from visitors. That means we can tell you the service is unreachable, but not what X (Twitter) says about it. The verification tier box on this page names whichever check produced the verdict you are reading, so you can see how direct the evidence is.
Is status.buzz affiliated with X (Twitter)?
No. status.buzz is an independent monitoring site operated by LuzLab LLC, with no connection to X (Twitter) or x.com. It reads publicly available endpoints and status feeds, and publishes what it observed. For account or billing problems you need X (Twitter)'s own support, not us.
No comments yet. Be the first to describe what you're seeing.