← HonkWatch.com

Is X (Twitter) down in Saint Kitts and Nevis?

No problems reported with X (Twitter) right now

People in Saint Kitts and Nevis: 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, 22:31 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 Saint Kitts and Nevis

Last 24 hours · Saint Kitts and Nevis · times in UTC

0 reports

No community reports in the last 24 hours from Saint Kitts and Nevis. 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:25 UTC: 35 of 35 places loaded it, typical 241 to 257 ms21:25-21:30 UTC: 34 of 34 places loaded it, typical 263 ms21:30-21:40 UTC: 35 of 35 places loaded it, typical 251 to 253 ms21:40-21:45 UTC: 34 of 34 places loaded it, typical 271 ms21:45-21:55 UTC: 35 of 35 places loaded it, typical 252 to 254 ms21:55-22:00 UTC: 34 of 34 places loaded it, typical 256 ms22:00-22:10 UTC: 35 of 35 places loaded it, typical 280 to 284 ms22:10-22:15 UTC: 34 of 34 places loaded it, typical 277 ms22:15-22:25 UTC: 35 of 35 places loaded it, typical 247 to 253 ms22:25-22:30 UTC: 34 of 34 places loaded it, typical 250 ms22:30-22:35 UTC: 13 of 13 places loaded it, typical 216 ms Typical response time of the places that loaded it, at most 284 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 Saint Kitts and Nevis only.

Latest checks, 22:30-22:35 UTC: 13 of 13 places loaded it, typical 216 ms.

Report totals as of 7 Nov, 22:31 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 Saint Kitts and Nevis

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 Saint Kitts and Nevis. The report chart above is filtered to Saint Kitts and Nevis.

Our own checks of x.com

Every 5 minutes, from our probes

Our checks from 35 cities: all fine.

Osaka: loaded in 216 ms Madrid: loaded in 216 ms Delhi: loaded in 735 ms Lauterbourg: loaded in 215 ms St. Louis: loaded in 317 ms São Paulo: loaded in 251 ms Dallas: loaded in 177 ms Santiago: loaded in 272 ms Doha: loaded in 584 ms London: loaded in 195 ms Atlanta: loaded in 118 ms Toronto: loaded in 138 ms Warsaw: loaded in 219 ms Johannesburg: loaded in 469 ms Bangalore: loaded in 377 ms Frankfurt: loaded in 200 ms New Jersey: loaded in 177 ms Tel Aviv: loaded in 296 ms Mumbai: loaded in 372 ms Querétaro: loaded in 141 ms Sydney: loaded in 279 ms Seoul: loaded in 246 ms Los Angeles: loaded in 188 ms Port Louis: loaded in 457 ms Tokyo: loaded in 209 ms Cape Town: loaded in 402 ms Hamina: loaded in 254 ms Melbourne: loaded in 934 ms Portsmouth: loaded in 258 ms Seattle: loaded in 107 ms Hong Kong: loaded in 756 ms Amsterdam: loaded in 205 ms Singapore: loaded in 264 ms Jakarta: loaded in 325 ms New York: loaded in 130 ms
  • OsakaReachable216 ms, 1 min ago
  • MadridReachable216 ms, 1 min ago
  • DelhiReachable735 ms, 1 min ago
  • LauterbourgReachable215 ms, 1 min ago
  • St. LouisReachable317 ms, 1 min ago
  • São PauloReachable251 ms, 1 min ago
  • DallasReachable177 ms, 1 min ago
  • SantiagoReachable272 ms, 1 min ago
  • DohaReachable584 ms, 2 min ago
  • LondonReachable195 ms, 2 min ago
  • AtlantaReachable118 ms, 2 min ago
  • TorontoReachable138 ms, 2 min ago
  • WarsawReachable219 ms, 2 min ago
  • JohannesburgReachable469 ms, 2 min ago
  • BangaloreReachable377 ms, 2 min ago
  • FrankfurtReachable200 ms, 2 min ago
  • New JerseyReachable177 ms, 2 min ago
  • Tel AvivReachable296 ms, 2 min ago
  • MumbaiReachable372 ms, 2 min ago
  • QuerétaroReachable141 ms, 2 min ago
  • SydneyReachable279 ms, 2 min ago
  • SeoulReachable246 ms, 2 min ago
  • Los AngelesReachable188 ms, 2 min ago
  • Port LouisReachable457 ms, 2 min ago
  • TokyoReachable209 ms, 3 min ago
  • Cape TownReachable402 ms, 3 min ago
  • HaminaReachable254 ms, 3 min ago
  • MelbourneReachable934 ms, 3 min ago
  • PortsmouthReachable258 ms, 3 min ago
  • SeattleReachable107 ms, 3 min ago
  • Hong KongReachable756 ms, 3 min ago
  • AmsterdamReachable205 ms, 3 min ago
  • SingaporeReachable264 ms, 3 min ago
  • JakartaReachable325 ms, 3 min ago
  • New YorkReachable130 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 Saint Kitts and Nevis 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 Saint Kitts and Nevis · Find another service