IsDownMonitor
World alerts
WhatsAppProblemsAppleProblems — Stocks: Users are experiencing issues with Stocks.ZoomProblems — Service Under MaintenanceClaudeProblems — Claude unable to join meetingsCloudflareProblems — Degraded connectivity between Europe and Asia PacificTwilioProblems — Voice Call Silent and One-Way Audio from Colombia to a Subset of Twilio Phone NumbersKrakenProblems — Ink Network Funding DelaysEntel BoliviaProblems · 🇧🇴Internet outage signal in 🇬🇮 Gibraltarsince · IODAInternet outage signal in 🇹🇩 Chadsince · IODAInternet outage signal in 🇸🇨 Seychellessince · IODAInternet outage signal in 🇬🇶 Equatorial Guineasince · IODAInternet outage signal in 🇫🇮 Finlandsince · IODAInternet outage signal in 🇨🇰 Cook Islandssince · IODAInternet outage signal in 🇲🇿 Mozambiquesince · IODAInternet outage signal in 🇷🇸 Serbiasince · IODAInternet outage signal in 🇭🇹 Haitisince · IODAInternet outage signal in 🇨🇩 Congo - Kinshasasince · IODAInternet outage signal in 🇹🇯 Tajikistansince · IODA395/419 services operational

Is TIM Brasil down in Brazil?

Internet & mobile · www.tim.com.br

WhatsApp X
Operational
No problems detected

Confirmed by at least 2 of our 3 probes in 2 consecutive cycles.

Last update: (Nov 19, 2026, 12:22 AM UTC)
Uptime 24 h94.70 %
Uptime 7 days94.97 %
Median response2,532 ms
Slowest 5 %10,865 ms
Checks 24 h2,321

Signals

  • Our check · Santiago, Chile (Oracle Cloud)responds · HTTP 200 · 706 ms
  • Our check · Chile (local network)responds · HTTP 200 · 814 ms
  • Our check · São Paulo, Brazil (AWS)responds · HTTP 200 · 661 ms
  • Our check · Virginia, USA (AWS)responds · HTTP 200 · 6378 ms
  • Our check · Oregon, USA (AWS)responds · HTTP 200 · 6503 ms
  • Our check · Frankfurt, Germany (AWS)responds · HTTP 200 · 5019 ms
  • Our check · Tokyo, Japan (AWS)responds · HTTP 200 · 7220 ms
  • Our check · Sydney, Australia (AWS)responds · HTTP 200 · 8799 ms

Response time — last 24 h

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

0 ms5 s10 sSantiago, Chile (Oracle Cloud) · timeoutSantiago, Chile (Oracle Cloud) · ECONNRESETVirginia, USA (AWS) · timeoutTokyo, Japan (AWS) · timeoutSão Paulo, Brazil (AWS) · timeoutTokyo, Japan (AWS) · timeoutChile (local network) · timeoutVirginia, USA (AWS) · timeoutVirginia, USA (AWS) · timeoutSydney, Australia (AWS) · http_503Oregon, USA (AWS) · timeoutSão Paulo, Brazil (AWS) · timeoutSydney, Australia (AWS) · timeoutSantiago, Chile (Oracle Cloud) · http_503Chile (local network) · http_503Oregon, USA (AWS) · timeoutFrankfurt, Germany (AWS) · timeoutOregon, USA (AWS) · timeoutFrankfurt, Germany (AWS) · http_503São Paulo, Brazil (AWS) · timeoutSydney, Australia (AWS) · http_503Chile (local network) · timeoutVirginia, USA (AWS) · http_503Santiago, Chile (Oracle Cloud) · timeoutOregon, USA (AWS) · timeoutSão Paulo, Brazil (AWS) · timeoutSydney, Australia (AWS) · http_503Tokyo, Japan (AWS) · timeoutSão Paulo, Brazil (AWS) · timeoutSantiago, Chile (Oracle Cloud) · timeoutOregon, USA (AWS) · timeoutFrankfurt, Germany (AWS) · timeoutVirginia, USA (AWS) · http_503Sydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutSantiago, Chile (Oracle Cloud) · timeoutOregon, USA (AWS) · timeoutFrankfurt, Germany (AWS) · timeoutTokyo, Japan (AWS) · timeoutVirginia, USA (AWS) · http_503Santiago, Chile (Oracle Cloud) · timeoutChile (local network) · timeoutVirginia, USA (AWS) · timeoutChile (local network) · http_503Tokyo, Japan (AWS) · timeoutOregon, USA (AWS) · http_503Frankfurt, Germany (AWS) · timeoutVirginia, USA (AWS) · timeoutTokyo, Japan (AWS) · timeoutSantiago, Chile (Oracle Cloud) · timeoutSão Paulo, Brazil (AWS) · timeoutOregon, USA (AWS) · http_503Frankfurt, Germany (AWS) · http_503Sydney, Australia (AWS) · http_503Virginia, USA (AWS) · http_503São Paulo, Brazil (AWS) · http_503Santiago, Chile (Oracle Cloud) · http_503Frankfurt, Germany (AWS) · http_503Sydney, Australia (AWS) · timeoutSão Paulo, Brazil (AWS) · timeoutVirginia, USA (AWS) · http_503Santiago, Chile (Oracle Cloud) · http_503Oregon, USA (AWS) · timeoutFrankfurt, Germany (AWS) · timeoutVirginia, USA (AWS) · timeoutOregon, USA (AWS) · timeoutSantiago, Chile (Oracle Cloud) · timeoutChile (local network) · timeoutOregon, USA (AWS) · timeoutSão Paulo, Brazil (AWS) · timeoutVirginia, USA (AWS) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · http_503Oregon, USA (AWS) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutSantiago, Chile (Oracle Cloud) · timeoutChile (local network) · timeoutSantiago, Chile (Oracle Cloud) · timeoutChile (local network) · timeoutOregon, USA (AWS) · timeoutFrankfurt, Germany (AWS) · timeoutVirginia, USA (AWS) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutSantiago, Chile (Oracle Cloud) · timeoutSantiago, Chile (Oracle Cloud) · timeoutSantiago, Chile (Oracle Cloud) · timeoutSantiago, Chile (Oracle Cloud) · timeoutChile (local network) · timeoutChile (local network) · timeoutChile (local network) · timeoutSydney, Australia (AWS) · http_503Virginia, USA (AWS) · http_503Tokyo, Japan (AWS) · http_503São Paulo, Brazil (AWS) · timeoutOregon, USA (AWS) · timeoutFrankfurt, Germany (AWS) · timeoutSantiago, Chile (Oracle Cloud) · timeoutSantiago, Chile (Oracle Cloud) · timeoutVirginia, USA (AWS) · timeoutChile (local network) · http_503Chile (local network) · http_503Chile (local network) · http_503Sydney, Australia (AWS) · timeoutVirginia, USA (AWS) · http_503Tokyo, Japan (AWS) · timeoutFrankfurt, Germany (AWS) · timeoutOregon, USA (AWS) · timeoutSantiago, Chile (Oracle Cloud) · timeoutTokyo, Japan (AWS) · timeoutSydney, Australia (AWS) · timeoutChile (local network) · timeoutSydney, Australia (AWS) · timeoutTokyo, Japan (AWS) · timeoutSydney, Australia (AWS) · timeoutFrankfurt, Germany (AWS) · timeoutOregon, USA (AWS) · timeoutOregon, USA (AWS) · timeoutSydney, Australia (AWS) · timeoutSantiago, Chile (Oracle Cloud) · timeoutSantiago, Chile (Oracle Cloud) · timeoutSantiago, Chile (Oracle Cloud) · 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 ago94.97 %today

Days before monitoring started appear empty.

Incident history

  1. Outage confirmedNov 18, 2026, 11:42 PM UTCDuration: 11 min
    • Outage confirmed Confirmed by at least 2 of our 3 probes in 2 consecutive cycles.
    • Unverified Only one probe failed. We do not declare an outage from a single signal.
    • Operational Confirmed by at least 2 of our 3 probes in 2 consecutive cycles.
  2. ProblemsNov 18, 2026, 7:46 PM UTCDuration: 3 min
    • Problems Most of our probes measure response times far above normal.
    • Operational Confirmed by at least 2 of our 3 probes in 2 consecutive cycles.
  3. ProblemsNov 18, 2026, 5:34 PM UTCDuration: 3 min
    • Problems Most of our probes measure response times far above normal.
    • Operational Confirmed by at least 2 of our 3 probes in 2 consecutive cycles.
  4. Outage confirmedNov 18, 2026, 1:22 PM UTCDuration: 1 h 21 min
    • Problems Most of our probes measure response times far above normal.
    • Unverified Only one probe failed. We do not declare an outage from a single signal.
    • Problems Most of our probes measure response times far above normal.
    • Unverified Only one probe failed. We do not declare an outage from a single signal.
    • Outage confirmed Confirmed by at least 2 of our 3 probes in 2 consecutive cycles.
    • Problems Most of our probes measure response times far above normal.
    • Unverified Only one probe failed. We do not declare an outage from a single signal.
    • Problems Most of our probes measure response times far above normal.
    • Outage confirmed Confirmed by at least 2 of our 3 probes in 2 consecutive cycles.
    • Unverified Only one probe failed. We do not declare an outage from a single signal.
    • Problems Most of our probes measure response times far above normal.
    • Unverified Only one probe failed. We do not declare an outage from a single signal.
    • Problems Most of our probes measure response times far above normal.
    • Unverified Only one probe failed. We do not declare an outage from a single signal.
    • Problems Most of our probes measure response times far above normal.
    • Operational Confirmed by at least 2 of our 3 probes in 2 consecutive cycles.
  5. ProblemsNov 17, 2026, 10:54 PM UTCDuration: 1 min
    • Problems Most of our probes measure response times far above normal.
    • Operational Confirmed by at least 2 of our 3 probes in 2 consecutive cycles.

Frequently asked questions

Is TIM Brasil down right now?

No problems detected (last update: Nov 19, 2026, 12:22 AM UTC). Confirmed by at least 2 of our 3 probes in 2 consecutive cycles.

How do you know if TIM Brasil 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.

TIM Brasil 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 TIM Brasil's status on my site?

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