Is X down?
X is up.
Our last check reached x.com and got a healthy response.
The numbers
Availability and response time for X over the last 24 hours.
Availability
100%
22 checks, none failed
Avg response
300 ms
Mean of every check
Slowest
665 ms
Worst single check
Incidents
0
Runs of failing checks
Downtime
None
Estimated from samples
Downtime is estimated from 10-minute samples, so figures are accurate to within one check interval.
Over time
Every check we ran, and how long each one took.
Availability
- All checks passed
- Some checks failed
- All checks failed
Response time
Where the time goes
"Is it down?" is usually really "it feels broken — what's wrong with it?" This is the answer: every millisecond of a request to x.com, broken into the four phases it actually spends time in.
- DNS
- 5 ms2%
- TCP + TLS
- 5 ms2%
- Time to first byte
- 197 ms65%
- Download
- 94 ms31%
Resolving the hostname to an IP address.
Opening the connection and completing the TLS handshake.
Waiting for the server to start responding. Usually the server thinking.
Transferring the response body.
Averaged over the last 24 hours. The four phases add up to the total response time of 301 ms.
Incidents
Every time a check against x.com failed in the last 30 days, grouped into incidents.
No incidents recorded for X.
Every check we’ve run against X has passed.
This page is a Checkly monitor.
Not a mockup of one. Everything above is produced by the monitor below, running every 10 minutes from N. Virginia and Frankfurt. It lives in a repo, gets code-reviewed, and deploys from CI — the same way you would monitor your own service.
That’s the whole product. Monitoring you can read, diff, and version.
How we check X
A real request to the endpoint that matters, every 10 minutes — measured, not crowd-sourced.
What we actually do
- We send a real HTTP GET to
https://x.comevery 10 minutes. - We run it from two datacenters: N. Virginia and Frankfurt.
- It passes if the endpoint answers with a status below 400 within 10 seconds. Slower than 3 seconds is “degraded”, not down.
What a green check means
- X answered a real request from both N. Virginia and Frankfurt — an actual measurement, not complaints counted from a crowd.
- We probe the endpoint that fails when X fails, so a green check tracks the part you depend on, not a marketing page that stays up regardless.
- Checks run around the clock, every 10 minutes, on the same infrastructure Checkly customers monitor production with.
Frequently asked
No. Our most recent check reached https://x.com and got a healthy response. We check every 10 minutes from N. Virginia and Frankfurt.
We run a real HTTP request against https://x.com every 10 minutes from N. Virginia and Frankfurt, using Checkly's synthetic monitoring. A check passes when the endpoint returns a status below 400 within 10 seconds. We are not counting user reports — we are measuring the actual response.
We probe https://x.com because it is the endpoint that best reflects whether X is actually usable.
We check X from N. Virginia and Frankfurt. If it answers us but not you, the problem is usually specific to your network, ISP, region, or account rather than X itself.
Downdetector counts user reports — how many people are complaining. We run an actual synthetic check against the service and report what the wire says. Reports lag the outage and can be noisy; a probe either gets a response or it doesn't.