bgpreport

Network · data from 2026-11-12

AS53194 VIA NOVA TELECOMUNICACOES LTDA

Registry name: AS53194 - VIP NETWORK TELECOMUNICACOES LTDA, BR · PeeringDB

18IPv4 routes 100.0% RPKI valid · 100.0% with a route object
4IPv6 routes 100.0% RPKI valid · 75.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
19Route objects not announced registered with origin AS53194, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS53194, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

2804:4a28::/33 Valid Nonecovered by 2804:4a28::/32 635 100% 67
186.232.165.0/24 Valid Other IRR onlyRADB 672 100% 67
186.232.169.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
186.232.160.0/20 Valid Other IRR onlyRADB, TC 670 100% 67
186.232.160.0/21 Valid Other IRR onlyRADB, TC 670 100% 67
186.232.162.0/24 Valid Other IRR onlyRADB, TC 670 100% 67
186.232.163.0/24 Valid Other IRR onlyRADB, TC 670 100% 67
186.232.167.0/24 Valid Other IRR onlyRADB, TC 670 100% 67
186.232.168.0/24 Valid Other IRR onlyRADB, TC 670 100% 67
186.232.170.0/24 Valid Other IRR onlyRADB, TC 670 100% 67
186.232.172.0/24 Valid Other IRR onlyRADB, TC 670 100% 67
186.232.173.0/24 Valid Other IRR onlyRADB, TC 670 100% 67
186.232.175.0/24 Valid Other IRR onlyRADB, TC 670 100% 67
186.232.160.0/24 Valid Other IRR onlyRADB, TC 669 99% 67
186.232.161.0/24 Valid Other IRR onlyRADB, TC 669 99% 67
186.232.164.0/24 Valid Other IRR onlyRADB, TC 669 99% 67
186.232.168.0/21 Valid Other IRR onlyRADB, TC 669 99% 67
186.232.171.0/24 Valid Other IRR onlyRADB, TC 669 99% 67
186.232.174.0/24 Valid Other IRR onlyRADB, TC 669 99% 67
2804:4a28:820::/44 Valid Other IRR onlyTC 635 100% 67
2804:4a28:830::/44 Valid Other IRR onlyTC 635 100% 67
2804:4a28::/32 Valid Other IRR onlyRADB, TC 633 100% 67

AS-SET

AS53194's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 41 are in fix.csv.

  • Route object: none1
  • Route object: RIR21
  • Route object: not announced19
ChangePrefix or setDetailFull-table peers
Route object: none2804:4a28::/33No route object for it. A route object for 2804:4a28::/32 with origin AS53194 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53194 in the RIR database for the space.635 of 636
Route object: RIR186.232.165.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.232.169.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR186.232.160.0/20Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR186.232.160.0/21Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR186.232.162.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR186.232.163.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR186.232.167.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR186.232.168.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR186.232.170.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR186.232.172.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR186.232.173.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR186.232.175.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR186.232.160.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR186.232.161.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR186.232.164.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR186.232.168.0/21Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR186.232.171.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR186.232.174.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:4a28:820::/44Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:4a28:830::/44Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:4a28::/32Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636

Route objects not announced

Route objects with origin AS53194 whose prefix no peer sees AS53194 announce. Many are kept on purpose (backup routes, space announced only in some places).

186.232.160.0/22TCValid
186.232.160.0/23TCValid
186.232.162.0/23TCValid
186.232.164.0/22TCValid
186.232.164.0/23TCValid
186.232.166.0/24RADBValid
186.232.168.0/22TCValid
186.232.168.0/23TCValid
186.232.170.0/23TCValid
186.232.172.0/23TCValid
186.232.174.0/23TCValid
2804:4a28:1f28::/45RADBValid
2804:4a28:1f30::/45RADBValid
2804:4a28:1f38::/45RADBValid
2804:4a28:1f38::/46RADBValid
2804:4a28:1f3c::/46RADBValid
2804:4a28:1f40::/45RADBValid
2804:4a28:1f40::/46RADBValid
2804:4a28:1f44::/46RADBValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.