bgpreport

Network · data from 2026-11-12

AS262452 VCNETWORK SOLUCOES TECNOLOGICA

Registry name: AS262452 - VCNETWORK SOLUCOES TECNOLOGICA, BR · PeeringDB

5IPv4 routes 100.0% RPKI valid · 100.0% with a route object
2IPv6 routes 100.0% RPKI valid · 50.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
3Route objects not announced registered with origin AS262452, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS262452, 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:3f94:8000::/33 Valid Nonecovered by 2804:3f94::/32 630 99% 67
177.52.218.0/24 Valid Other IRR onlyRADB, TC 667 99% 67
177.52.219.0/24 Valid Other IRR onlyRADB 666 99% 67
177.52.216.0/23 Valid Other IRR onlyRADB, TC 665 99% 67
177.52.216.0/24 Valid Other IRR onlyRADB 665 99% 67
177.52.217.0/24 Valid Other IRR onlyRADB 665 99% 67
2804:3f94::/33 Valid Other IRR onlyTC 630 99% 67

AS-SET

AS262452'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 10 are in fix.csv.

  • Route object: none1
  • Route object: RIR6
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: none2804:3f94:8000::/33No route object for it. A route object for 2804:3f94::/32 with origin AS262452 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262452 in the RIR database for the space.630 of 636
Route object: RIR177.52.218.0/24Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR177.52.219.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR177.52.216.0/23Route object only in RADB, TC. Add it in the RIR database for the space.665 of 673
Route object: RIR177.52.216.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR177.52.217.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR2804:3f94::/33Route object only in TC. Add it in the RIR database for the space.630 of 636

Route objects not announced

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

177.52.216.0/22RADB, TCNo ROA
177.52.218.0/23RADBNo ROA
2804:3f94::/32RADB, TCNo 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.