bgpreport

Network · data from 2026-11-12

AS52962 Vipnet Baixada Telecomunicacoes e Informatica LTDA

Registry name: AS52962 - Vipnet Baixada Telecom. e Informatica Ltda, BR · PeeringDB

7IPv4 routes 100.0% RPKI valid · 71.4% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
23Route objects not announced registered with origin AS52962, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS52962, 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.

177.11.0.0/22 Valid Nonecovered by 177.11.0.0/21 670 100% 66
179.97.48.0/22 Valid Nonecovered by 179.97.48.0/21 670 100% 66
177.11.0.0/24 Valid Other IRR onlyRADB 670 100% 66
177.11.1.0/24 Valid Other IRR onlyRADB 670 100% 66
177.11.2.0/24 Valid Other IRR onlyRADB 670 100% 66
177.11.3.0/24 Valid Other IRR onlyRADB 670 100% 66
179.97.48.0/20 Valid Other IRR onlyRADB, TC 670 100% 66

AS-SET

AS52962'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 30 are in fix.csv.

  • Route object: none2
  • Route object: RIR5
  • Route object: not announced23
ChangePrefix or setDetailFull-table peers
Route object: none177.11.0.0/22No route object for it. A route object for 177.11.0.0/21 with origin AS52962 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52962 in the RIR database for the space.670 of 673
Route object: none179.97.48.0/22No route object for it. A route object for 179.97.48.0/21 with origin AS52962 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52962 in the RIR database for the space.670 of 673
Route object: RIR177.11.0.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR177.11.1.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR177.11.2.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR177.11.3.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR179.97.48.0/20Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

177.11.0.0/21RADB, TCNo ROA
179.97.48.0/21RADBValid
179.97.48.0/24RADBValid
179.97.49.0/24RADBValid
179.97.50.0/24RADBValid
179.97.51.0/24RADBValid
179.97.52.0/24RADBValid
179.97.53.0/24RADBValid
179.97.54.0/24RADBValid
179.97.55.0/24RADBValid
179.97.56.0/21RADBValid
179.97.56.0/22RADBValid
179.97.56.0/24RADBValid
179.97.57.0/24RADBValid
179.97.58.0/24RADBValid
179.97.60.0/23RADBValid
179.97.60.0/24RADBValid
179.97.61.0/24RADBValid
179.97.63.0/24RADBValid
2804:31c::/32RADB, TCValid
2804:31c:2c00::/40RADBValid
2804:31c:6500::/40RADBValid
2804:449c::/32RADBNo ROA

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.