Vivo outages and problems
User reports, last 24 hours
3,683 reports in total, counted in 15-minute windows
In the last hour, 90 problem reports came in for Vivo, against about 54 at this time on a usual day. Over the last 24 hours there were 3,683 reports. Most recent reports were about mobile internet (42%) and broadband internet (36%). The last spike in reports was just now and lasted 15 min. These are user reports from Brazil, where most people report Vivo problems.
- NormalClose to the usual level15 h 15 min · 1,011 reports
- ElevatedMore than 1.5 times the usual level7 h · 1,096 reports
- OutageMore than twice the usual level and far above the day's average1 h 45 min · 1,576 reports
- Usual levelWhat a usual day sees at that timeAbout 54 an hour now
In the past 24 hours, 3,683 user reports came in for Vivo. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 92.71% uptime for the day.
The most recent spike big enough to count as an outage was 8 hours ago. The busiest 15-minute window of the day had 349 reports, about 8 hours ago.
-
Elevated reports
Ended 45 min agoLasted 30 min27peak reports
-
Elevated reports
Ended 3 h agoLasted 2 h 45 min60peak reports
-
Outage
Ended 6 h agoLasted 3 h349peak reports
-
Elevated reports
Ended 10 h agoLasted 45 min40peak reports
-
Elevated reports
Ended 12 h agoLasted 15 min39peak reports
Vivo in November 2026
- Problem reports in November (since 3 November)
- 3,939
Monthly report for November 2026
What went wrong
What people said was wrong in recent problem reports for Vivo.
Share of 910 recent reports that said what was wrong.
Where Vivo problem reports come from
The map shows where recent problem reports for Vivo came from in Brazil. Big cities always send the most, so dots in many places point to a widespread problem, and one area far ahead of the rest can mean a regional one.
- Outage now
- Problems now
- Normal
Map outlines: Natural Earth.
Vivo problem spikes, last 30 days
Since 3 November, Vivo had 1 outage spike and 14 periods of elevated reports. The longest lasted 3 h, on 4 November.
-
Elevated reports
Thu 5 Nov, 02:42–02:57Lasted 15 min24peak reports
-
Elevated reports
Thu 5 Nov, 01:48–02:18Lasted 30 min33peak reports
-
Elevated reports
Wed 4 Nov, 21:33–00:18Lasted 2 h 45 min73peak reports
-
Outage
Lasted 3 h361peak reports
-
Elevated reports
Wed 4 Nov, 16:18–17:03Lasted 45 min46peak reports
-
Elevated reports
Wed 4 Nov, 15:18–15:33Lasted 15 min44peak reports
-
Elevated reports
Wed 4 Nov, 14:33–14:48Lasted 15 min41peak reports
-
Elevated reports
Wed 4 Nov, 13:03–14:03Lasted 1 h57peak reports
7 earlier spikes in this period.
A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 3 November 2026. Monthly reports for all services
How to fix Vivo not working
Vivo is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:
Your browser tries to reach vivo.com.br over your own connection, right now. Nothing is sent to us or stored.
Reload and restart
Reload the page (Ctrl+F5, or Cmd+Shift+R on a Mac), or fully close the app and open it again.
Try another connection
Switch between Wi-Fi and mobile data. If it works on one and not the other, the problem is your network, not Vivo.
Update the app
Install the latest version from the App Store or Google Play. Old versions can stop connecting after a server-side change.
While Vivo is down: what to use instead
- Meu Vivo app Use the app if the website stalls, since account login, bill viewing, and plan details may still work there.
- Vivo website Try the website from a browser if the app freezes or will not open past the sign-in screen.
- Bank app payment Pay an existing bill or barcode through your bank app if the account area will not load at payment time.
- Another connection Use Wi-Fi from another provider or a second SIM from Claro or TIM if mobile data or calls on the service are failing.
Problems at the same time as Vivo
Since 3 November, all 15 of Vivo's spikes in problem reports overlapped a spike at another service.
When several services get problem reports at once, something they share, such as a cloud host or a network, can be the real cause. Matching times alone do not prove it.
Most often at the same time
- USPS15 times
- Pix14 times
- Capital One13 times
- Archive of Our Own13 times
- GOV.BR12 times
- Freenet12 times
How many of Vivo's spikes overlapped one of theirs.
During the latest spike
Vivo: Thu 5 Nov, 02:42 to 02:57
- Facebook, outage,4 Nov 13:47 to 03:02
- Capital One, outage,4 Nov 16:48 to 03:03
- Bell Canada, outage,4 Nov 20:03 to 03:03
- Reddit, outage,4 Nov 21:17 to 03:02
- Blizzard Battle.net, outage,4 Nov 21:47 to 03:02
- Plex, outage,4 Nov 22:17 to 03:02
- World of Warcraft, outage,4 Nov 22:18 to 03:03
- eSocial, outage,4 Nov 23:48 to 02:48
31 more services. Red dot: outage. Amber dot: elevated reports.
A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.
When people report Vivo problems
The busiest hour for reports about Vivo is 00:00 to 01:00 Central European time, and the busiest day is Wednesday.
By hour of the day
- 00:00 to 01:00: 5 reports on an average day
- 01:00 to 02:00: 4.2 reports on an average day
- 02:00 to 03:00: 2.3 reports on an average day
- 03:00 to 04:00: 1.5 reports on an average day
- 04:00 to 05:00: 1.4 reports on an average day
- 05:00 to 06:00: 0.45 reports on an average day
- 06:00 to 07:00: 0.42 reports on an average day
- 07:00 to 08:00: 0.29 reports on an average day
- 08:00 to 09:00: 0.37 reports on an average day
- 09:00 to 10:00: 0.79 reports on an average day
- 10:00 to 11:00: 1.1 reports on an average day
- 11:00 to 12:00: 1.6 reports on an average day
- 12:00 to 13:00: 3.3 reports on an average day
- 13:00 to 14:00: 1.2 reports on an average day
- 14:00 to 15:00: 2.2 reports on an average day
- 15:00 to 16:00: 3.3 reports on an average day
- 16:00 to 17:00: 2.2 reports on an average day
- 17:00 to 18:00: 4.8 reports on an average day
- 18:00 to 19:00: 0 reports on an average day
- 19:00 to 20:00: 0 reports on an average day
- 20:00 to 21:00: 0 reports on an average day
- 21:00 to 22:00: 3.1 reports on an average day
- 22:00 to 23:00: 0 reports on an average day
- 23:00 to 00:00: 1 report on an average day
By day of the week
- Monday: 0 reports on an average Monday
- Tuesday: 5.8 reports on an average Tuesday
- Wednesday: 267 reports on an average Wednesday
- Thursday: 54 reports on an average Thursday
- Friday: 0 reports on an average Friday
- Saturday: 0 reports on an average Saturday
- Sunday: 0 reports on an average Sunday
Each bar is the average number of user reports in that hour, or on that day of the week, from 28 days of reports since 5 October 2026. The busiest bar is highlighted. Spikes in reports are left out, so one outage does not set the pattern.
Vivo IP address, servers and network
- IPv4 addresses
- 162.159.135.63
Show all 2
- 162.159.136.63
- IPv6
- Not offered
- Network
- AS13335 · Cloudflare, Inc., registered in the United States
- Served through
- Cloudflare · our check was answered by its Frankfurt (FRA) data centre
- DNS hosted by
- its own name servers (com.br)
- HTTPS certificate
- Issued by Valid Certificadora Digital LTDA, valid until 19 Apr 2027 (164 days)
- HTTP/3
- Not advertised
- Our check
- Answered in 36 ms (it turned away our automated check, which is common)
Checked from our server in Frankfurt, Germany, 1 h ago, for vivo.com.br. A service behind a CDN answers from many data centres, usually the one nearest to you, so these addresses are where its traffic enters, not where its own servers stand. Visitors elsewhere may see different addresses.
Checked from 12 places around the world
All 12 locations got an answer from vivo.com.br. Fastest from Milan (12 ms), slowest from Vienna (488 ms). Every location connected through Cloudflare, Inc. (AS13335), using 2 different addresses.
| Location | Result | Time | Address reached |
|---|---|---|---|
| FrankfurtGermany | Up · HTTP 308 | 218 ms | 162.159.136.63 |
| ViennaAustria | Up · HTTP 308 | 488 ms | 162.159.135.63 |
| MilanItaly | Up · HTTP 308 | 12 ms | 162.159.135.63 |
| ParisFrance | Up · HTTP 308 | 211 ms | 162.159.136.63 |
| AmsterdamNetherlands | Up · HTTP 308 | 18 ms | 162.159.135.63 |
| MadridSpain | Up · HTTP 308 | 224 ms | 162.159.136.63 |
| WarsawPoland | Up · HTTP 308 | 283 ms | 162.159.136.63 |
| DallasUSA | Up · HTTP 308 | 426 ms | 162.159.135.63 |
| Los AngelesUSA | Up · HTTP 308 | 34 ms | 162.159.136.63 |
| São PauloBrazil | Up · HTTP 308 | 19 ms | 162.159.136.63 |
| SingaporeSingapore | Up · HTTP 308 | 33 ms | 162.159.135.63 |
| TokyoJapan | Up · HTTP 308 | 300 ms | 162.159.135.63 |
Checked with check-host.net from its servers in these cities 1 h ago, for vivo.com.br. Time is how long each server took to load the page.
Service updates from @vivobr
No posts about problems from @vivobr in the last 14 days. The latest is from .
Contact Vivo support
- Help centrevivo.com.br/portalweb/appmanager/env/web?_nfpb=true&_nfls=false&_pageLabel=vcAtendFCEscrevTelefCOLPage
- Websitevivo.com.br
- X (Twitter)x.com/vivobr
- Facebookfacebook.com/193824160646270
Tip: Vivo doesn't list a public status page that we know of, so its help centre and the report chart on this page are the best places to check.
How we track Vivo
The status on this page comes from user-submitted problem reports for Vivo, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for Vivo, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.
When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. Vivo doesn't publish a public status page that we know of, so user reports are often the quickest sign that something is wrong on their side.