Live check from PingDeck's monitoring servers — not cached search results.
up X (Twitter) appears UP
Last checked: 0 seconds ago (Thu, 24 Sep 2026 05:08:53 GMT).
Our checker probed https://x.com and it responded with HTTP 200 in 299ms. Rechecked at most every 60s.
Observed uptime: 100.00% across 28 checks (up to 90 days).
| Time | Status | Response | Latency |
|---|---|---|---|
| 2026-09-24 05:08:53 UTC | up | HTTP 200 | 299ms |
| 2026-09-22 05:10:06 UTC | up | HTTP 200 | 288ms |
| 2026-09-21 12:50:48 UTC | up | HTTP 200 | 335ms |
| 2026-09-21 11:53:01 UTC | up | HTTP 200 | 2267ms |
| 2026-09-20 12:22:40 UTC | up | HTTP 200 | 276ms |
| 2026-09-20 04:11:30 UTC | up | HTTP 200 | 277ms |
| 2026-09-17 18:14:31 UTC | up | HTTP 200 | 251ms |
| 2026-09-15 05:25:36 UTC | up | HTTP 200 | 279ms |
Response time, last 28 checks (peak 2267ms)
| Started | Duration | Detail |
|---|---|---|
| No incidents observed in our monitoring window — last verified Thu, 24 Sep 2026 05:08:53 GMT | ||
Paste a Discord, Slack, or any webhook URL. One message when X (Twitter) comes back up — no account, no email.
This page checks X (Twitter)'s public web endpoint from our cloud servers. If we show it UP but it fails for you, the problem is usually on your side of the internet: your DNS resolver, ISP routing, a VPN, or a regional outage. Try another network (e.g. switch off Wi-Fi to mobile data) and check your DNS records.
If we show it DOWN, the outage is likely on X (Twitter)'s side — large services usually recover within minutes to hours. Note: for app-based services, the app backend can differ from the website we probe.
Short answer: as of our latest live check, X (Twitter) appears UP — its web endpoint responded normally. This page rechecks at most every 60 seconds.
Short answer: if this page shows X (Twitter) UP but it fails for you, the problem is on your side — DNS resolver, ISP routing, or VPN. Try another network first.
Short answer: most single-user failures are local: stale DNS cache, Wi-Fi issues, VPN endpoints, or an outdated app. Follow the troubleshooting steps above in order.
Short answer: on demand with a 60-second cache — every visit within a minute reuses the freshest result, and history is stored for the uptime statistics on this page.
Short answer: sometimes. We probe the public web endpoint; a mobile app can use different backend services, so the app can fail while the website is fine (and vice versa).
Short answer: the share of our stored checks (up to 90 days) where X (Twitter) responded successfully. It reflects reachability of the public endpoint we probe, not every internal X (Twitter) component.
Short answer: most large-service incidents resolve within minutes to a few hours. Ongoing incidents appear in the incident table above with start time and duration.
Short answer: yes — PingDeck monitors any site 24/7 with alerts to Discord, Slack, or any webhook. The free plan covers 5 monitors at https://getpingdeck.com/app
Is YouTube down? · Is Google down? · Is Facebook down? · Is Instagram down? · Is TikTok down? · Is WhatsApp down?
Or check any site with the website down checker · all service status checks.