Is X (Twitter) down?
No, we are not detecting any problems with X (Twitter) right now.
Server responded with HTTP 200 OK.
Last checked
What problem are you having with X (Twitter)?
What usually breaks on X (Twitter)
X, formerly Twitter, is a real-time public conversation platform — which makes it the place people go to report that other services are down, and conspicuous when it is the one failing. Its API and website fail independently, so third-party tools can break while the site is fine.
Timeline will not load past a point
The timeline service degrades separately from posting and the rest of the site.
Rate limit messages during outages
'Rate limit exceeded' often appears under heavy load or degradation rather than because of anything you did.
Third-party clients break alone
Apps built on the API can stop working while x.com is perfectly healthy.
30-Day X (Twitter) Uptime
Daily probe results for X (Twitter) over the last 30 days.
X (Twitter) Problems — Last 90 Days
No problems reported for X (Twitter) in the last 90 days.
This is a good sign — no outage reports from visitors over the last three months.
Recent X (Twitter) Response Times
| Date & time | Response | Status |
|---|---|---|
| 139 ms | up | |
| 151 ms | up | |
| 148 ms | up | |
| 152 ms | up | |
| 146 ms | up | |
| 146 ms | up | |
| 155 ms | up | |
| 150 ms | up | |
| 141 ms | up | |
| 160 ms | up | |
| 155 ms | up | |
| 152 ms | up |
Troubleshooting tips for X (Twitter)
If our monitor reports X (Twitter) is up but you still can't reach it, try these steps in order:
Hard-refresh your browser
- Press Ctrl + F5 (Windows) or Cmd + Shift + R (Mac) to bypass the cache.
- If that fails, open the page in an incognito / private window.
Clear cookies and cache
- Open your browser settings → Privacy / History.
- Clear cookies and cached files for the last hour, then reload.
Flush your DNS
- Windows: open Command Prompt and run ipconfig /flushdns.
- macOS: open Terminal and run sudo killall -HUP mDNSResponder.
- Linux: run sudo systemd-resolve --flush-caches (or systemctl restart nscd).
Restart your router
- Unplug the router and modem for 30 seconds.
- Plug them back in and wait until all lights are stable, then retry.
Try a different DNS or VPN
- Switch your DNS to 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google).
- Use a reputable VPN to test from a different country — useful when the site may be region-blocked.
Frequently asked questions about X (Twitter)
Comments about X (Twitter)
(0)No comments yet — be the first to share an update.
Similar services to check
(Social)Common Problems at X (Twitter)
No user reports yet. Be the first to report a problem above.