X (Twitter) is up.
It answers from all 10 monitoring groups, in a median of 548 ms.
We keep your country, an area of about 25 km and your network's name, never your address.
Is it just you?
Asking X (Twitter) from your connection…
Place by place
Where each check runs, what it saw last and how it did over the day.
| Place | Now | Answer | 24 h |
|---|---|---|---|
| Los AngelesLAX · group: Western North America | answers | 475 ms | 100% |
| MiamiMIA · group: Eastern North America | answers | 615 ms | 99.4% |
| AtlantaATL · group: South America | answers | 411 ms | 99.6% |
| LondonLHR · group: Western Europe | answers | 502 ms | 99.2% |
| WarsawWAW · group: Eastern Europe | answers | 625 ms | 99% |
| FrankfurtFRA · group: the Middle East | answers | 548 ms | 99.8% |
| LondonLHR · group: Africa | answers | 367 ms | 99.8% |
| OsakaKIX · group: Asia-Pacific | answers | 615 ms | 100% |
| SydneySYD · group: Oceania | answers | 860 ms | 99.8% |
| Amsterdamour server | answers | 304 ms | 99.9% |
The last 24 hours
Every quarter hour from each place: the darker the red, the more checks failed.
LAX
MIA
ATL
LHR
WAW
FRA
LHR
KIX
SYD
AMS
02:1508:1514:1520:1502:00
Every minute from Amsterdam
Green when it answered, red when it did not; the line is how long the answer took.
02:1002:05
24 h uptime: 99.9%Answer: 282 ms
Reports
People who told us it is down for them, per 15 minutes.
02:1502:00
Reports in the last hour: 0
Status page
No status page we can read.
What it depends on
Found in its DNS and addresses. When these fail, it usually fails with them.
- CDN in front of itCloudflare
- DNStwtrdns.net
Its outages
No repeated check failures recorded in the last 90 days.