← HonkWatch.com

Is X (Twitter) down in Mexico?

No problems reported with X (Twitter) right now

People in Mexico: 0 reports in the last hour Official page: No connected feed Our checks: loads from 35 of 35 places
Our checks can reach the X (Twitter) website. Updated 7 Nov, 21:21 UTC, just now · Website checks: these do not test every feature Website reachability does not confirm that sign-in, payments, messaging or the app is working.
Report a problem
Change country

No connected status feed

We don't read an official status source for X (Twitter), so no provider incidents or maintenance are shown here.

Our checks show whether x.com loads. Website checks: these do not test every feature.

Reports from people in Mexico

Last 24 hours · Mexico · times in UTC

0 reports

No community reports in the last 24 hours from Mexico. Having trouble? Add your report.

024 00:0006:0012:0018:00 19:10-19:25 UTC: 35 of 35 places loaded it, typical 252 to 274 ms19:25-19:30 UTC: 34 of 34 places loaded it, typical 243 ms19:30-19:40 UTC: 35 of 35 places loaded it, typical 251 to 258 ms19:40-19:45 UTC: 34 of 34 places loaded it, typical 268 ms19:45-19:55 UTC: 35 of 35 places loaded it, typical 255 to 260 ms19:55-20:00 UTC: 33 of 33 places loaded it, typical 240 ms20:00-20:10 UTC: 35 of 35 places loaded it, typical 251 to 275 ms20:10-20:15 UTC: 34 of 34 places loaded it, typical 254 ms20:15-20:25 UTC: 35 of 35 places loaded it, typical 246 to 274 ms20:25-20:30 UTC: 34 of 34 places loaded it, typical 258 ms20:30-20:40 UTC: 35 of 35 places loaded it, typical 246 to 252 ms20:40-20:45 UTC: 34 of 34 places loaded it, typical 251 ms20:45-20:55 UTC: 35 of 35 places loaded it, typical 244 to 253 ms20:55-21:00 UTC: 34 of 34 places loaded it, typical 267 ms21:00-21:10 UTC: 35 of 35 places loaded it, typical 269 to 270 ms21:10-21:15 UTC: 34 of 34 places loaded it, typical 258 ms21:15-21:20 UTC: 35 of 35 places loaded it, typical 241 ms21:20-21:25 UTC: 12 of 12 places loaded it, typical 239 ms Typical response time of the places that loaded it, at most 275 ms

Bars: reports every 15 minutes. Reports alone do not confirm an outage; a flat chart does not prove everything works.

Strip under the bars: how many places loaded x.com in each 5 minutes, of those that checked, and the line under it their typical response time. Any answer from the website counts as loaded, even an error page. Website checks don't test sign-in, payments or every feature. Our checks are worldwide; the bars count reports from Mexico only.

Latest checks, 21:20-21:25 UTC: 12 of 12 places loaded it, typical 239 ms.

Report totals as of 7 Nov, 21:21 UTC

Report a problem with X (Twitter)

Choose where you are, then tap what isn't working. Tapping a problem sends your report; no account needed.

What isn't working? Tap one to send

Anonymous · one report per service per hour. This adds your experience to the chart; the provider is not contacted.

Compare worldwide reports · Other services in Mexico

Where this status comes from

Website checks — Worldwide

The evidence below covers the provider and our available checks. It is not a separate verdict for Mexico. The report chart above is filtered to Mexico.

Our own checks of x.com

Every 5 minutes, from our probes

Our checks from 35 cities: all fine.

Osaka: loaded in 235 ms Madrid: loaded in 208 ms São Paulo: loaded in 242 ms St. Louis: loaded in 273 ms Santiago: loaded in 320 ms Dallas: loaded in 158 ms Delhi: loaded in 342 ms Atlanta: loaded in 103 ms London: loaded in 257 ms Doha: loaded in 571 ms Toronto: loaded in 176 ms Warsaw: loaded in 230 ms Johannesburg: loaded in 380 ms Frankfurt: loaded in 241 ms Bangalore: loaded in 346 ms New Jersey: loaded in 314 ms Mumbai: loaded in 361 ms Sydney: loaded in 574 ms Tel Aviv: loaded in 283 ms Querétaro: loaded in 156 ms Lauterbourg: loaded in 246 ms Seoul: loaded in 241 ms Los Angeles: loaded in 186 ms Port Louis: loaded in 419 ms Tokyo: loaded in 210 ms Melbourne: loaded in 340 ms Hamina: loaded in 263 ms Cape Town: loaded in 390 ms Portsmouth: loaded in 236 ms Seattle: loaded in 108 ms Amsterdam: loaded in 220 ms Hong Kong: loaded in 260 ms Singapore: loaded in 272 ms Jakarta: loaded in 292 ms New York: loaded in 154 ms
  • OsakaReachable235 ms, 1 min ago
  • MadridReachable208 ms, 1 min ago
  • São PauloReachable242 ms, 1 min ago
  • St. LouisReachable273 ms, 1 min ago
  • SantiagoReachable320 ms, 1 min ago
  • DallasReachable158 ms, 1 min ago
  • DelhiReachable342 ms, 1 min ago
  • AtlantaReachable103 ms, 1 min ago
  • LondonReachable257 ms, 1 min ago
  • DohaReachable571 ms, 1 min ago
  • TorontoReachable176 ms, 2 min ago
  • WarsawReachable230 ms, 2 min ago
  • JohannesburgReachable380 ms, 2 min ago
  • FrankfurtReachable241 ms, 2 min ago
  • BangaloreReachable346 ms, 2 min ago
  • New JerseyReachable314 ms, 2 min ago
  • MumbaiReachable361 ms, 2 min ago
  • SydneyReachable574 ms, 2 min ago
  • Tel AvivReachable283 ms, 2 min ago
  • QuerétaroReachable156 ms, 2 min ago
  • LauterbourgReachable246 ms, 2 min ago
  • SeoulReachable241 ms, 2 min ago
  • Los AngelesReachable186 ms, 2 min ago
  • Port LouisReachable419 ms, 2 min ago
  • TokyoReachable210 ms, 2 min ago
  • MelbourneReachable340 ms, 2 min ago
  • HaminaReachable263 ms, 3 min ago
  • Cape TownReachable390 ms, 3 min ago
  • PortsmouthReachable236 ms, 3 min ago
  • SeattleReachable108 ms, 3 min ago
  • AmsterdamReachable220 ms, 3 min ago
  • Hong KongReachable260 ms, 3 min ago
  • SingaporeReachable272 ms, 3 min ago
  • JakartaReachable292 ms, 3 min ago
  • New YorkReachable154 ms, 3 min ago

We request x.com and note whether it answers. These automated checks do not sign in or use the app's features.

Available evidence

We check whether its website loads every 5 minutes. This does not test sign-in, payments, calls or every feature of its app or network. We show a website problem when a quarter of the eligible places cannot load it, and an outage when half cannot. Places that normally cannot reach it are excluded. With too few results, we say we cannot tell.

Outage history

No problems recorded since 7 Nov 2026.

Last 9030 days

100.00% of the time without a reported outage, since 7 Nov

Of the last 90 days, 0 had a partial or major outage, 0 had maintenance only and 89 have no data. Recent problems are listed in a table further down.

90 days ago30 days agoToday

No problems Partial outage Major outage Maintenance No data yet

Recent problems

No problems recorded since 7 Nov 2026.

What can I try?

Having trouble with X (Twitter)?

  1. Compare reports from Mexico and check the latest update above. A quiet chart does not rule out a new or local problem.
  2. Try the service on another device or switch between WiFi and mobile data, if available. If other sites also fail, check your internet provider.
  3. Report a problem with the feature that is failing and the country where you are affected. Submit once; your report appears in the chart.

Reports describe people's experiences. One report alone does not confirm an outage.

Questions about these results

Questions

Is X (Twitter) down, or is it just me?

Our checks reach X (Twitter)'s website from most of our cities. This does not rule out problems with sign-in, payments, an app or a local network. Check the community reports above and report your experience.

How do we know?

No official status feed is connected for X (Twitter). We load x.com from our probes and note whether it answers. People can report problems here. Their reports appear separately and may reveal issues before a provider update.

How often do we check?

The website every 5 minutes, day and night. We keep 90 days of available check history: a day we have no reading for shows as "no data yet", never as working.

Other services in Social media

Each card shows that service's own status, not X (Twitter)'s. A problem listed here does not mean X (Twitter) has one.

See the live outage feed for Mexico · Find another service