IsDownMonitor
World alerts
ZoomProblems — Service Under MaintenanceClaudeProblems — Claude unable to join meetingsCloudflareProblems — Increased latency on Analytics API (GraphQL) queriesVercelProblems — Delays in observability dataTwilioProblems — Voice Call Silent and One-Way Audio from Colombia to a Subset of Twilio Phone NumbersKrakenProblems — Ink Network Funding DelaysElevenLabsProblems — Increased latency and API errorsInternet outage signal in 🇾🇹 Mayottesince · IODAInternet outage signal in 🇬🇮 Gibraltarsince · IODAInternet outage signal in 🇹🇩 Chadsince · IODAInternet outage signal in 🇸🇨 Seychellessince · IODAInternet outage signal in 🇬🇶 Equatorial Guineasince · IODAInternet outage signal in 🇨🇰 Cook Islandssince · IODAInternet outage signal in 🇫🇮 Finlandsince · IODAInternet outage signal in 🇷🇸 Serbiasince · IODAInternet outage signal in 🇹🇯 Tajikistansince · IODA392/419 services operational

Is Telecentro down in Argentina?

Internet & mobile · www.telecentro.com.ar

WhatsApp X
Unverified
One check failed — not verified

Only one probe failed. We do not declare an outage from a single signal.

Last update: (Nov 18, 2026, 8:54 PM UTC)Since: Nov 18, 2026, 1:13 PM UTC
Uptime 24 h91.56 %
Uptime 7 days91.56 %
Median response191 ms
Slowest 5 %4,542 ms
Checks 24 h1,884

Signals

  • Our check · Santiago, Chile (Oracle Cloud)responds · HTTP 200 · 134 ms
  • Our check · Chile (local network)responds · HTTP 200 · 190 ms
  • Our check · São Paulo, Brazil (AWS)responds · HTTP 200 · 154 ms
  • Our check · Virginia, USA (AWS)responds · HTTP 200 · 3345 ms
  • Our check · Oregon, USA (AWS)responds · HTTP 200 · 4941 ms
  • Our check · Frankfurt, Germany (AWS)responds · HTTP 200 · 3357 ms
  • Our check · Tokyo, Japan (AWS)not responding · timeout · 2 failures in a row
  • Our check · Sydney, Australia (AWS)responds · HTTP 200 · 2983 ms

Response time — last 24 h

Each line is one probe location. Red marks are failed checks.

0 ms5 s10 sSantiago, Chile (Oracle Cloud) · timeoutsin-aws · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutsin-aws · timeoutTokyo, Japan (AWS) · timeoutsin-aws · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · ECONNRESETTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · ECONNRESETTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeoutTokyo, Japan (AWS) · timeout-24h-18h-12h-6hnow
Santiago, Chile (Oracle Cloud)Chile (local network)São Paulo, Brazil (AWS)Virginia, USA (AWS)Oregon, USA (AWS)Frankfurt, Germany (AWS)Tokyo, Japan (AWS)Sydney, Australia (AWS)Failure

Availability — last 90 days

90 days ago91.56 %today

Days before monitoring started appear empty.

Incident history

No incidents recorded since monitoring started.

Frequently asked questions

Is Telecentro down right now?

One check failed — not verified (last update: Nov 18, 2026, 8:54 PM UTC). Only one probe failed. We do not declare an outage from a single signal.

How do you know if Telecentro is down?

We combine our own checks every 3 minutes from 8 locations. We only confirm an outage when the official source reports it or at least 2 probes fail twice in a row.

Telecentro isn't working for me but shows operational — what now?

Check whether the problem happens on another network (mobile data vs Wi-Fi). Update or reinstall the app and restart your device. If the official status page reports an incident, wait: it is being worked on. If everything shows as operational, the problem may be your account, device or local connection.

Can I show Telecentro's status on my site?

Yes. Our widgets and status badge are free for editorial use: https://isdownmonitor.com/widgets