bgpreport

Network · data from 2026-11-12

AS262608 AS262608 - Vapt Solucoes Tecnologicas Ltda

Registry name: AS262608 - Vapt Solucoes Tecnologicas Ltda, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS262608, 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.85.128.0/24 Valid Other IRR onlyRADB 672 100% 67
177.85.130.0/24 Valid Other IRR onlyRADB 672 100% 67
177.85.131.0/24 Valid Other IRR onlyRADB 672 100% 67
177.85.129.0/24 Valid Other IRR onlyRADB 670 100% 67
177.85.132.0/24 Valid Other IRR onlyRADB 669 99% 67
177.85.135.0/24 Valid Other IRR onlyRADB, TC 669 99% 67
177.85.134.0/24 Valid Other IRR onlyTC 667 99% 67
177.85.133.0/24 Valid Other IRR onlyTC 666 99% 67
2804:6d0::/32 Valid Other IRR onlyRADB, TC 635 100% 70
2804:6d0:fd00::/40 Valid Other IRR onlyRADB 632 99% 69
2804:6d0:fc00::/40 Valid Other IRR onlyRADB 630 99% 67
2804:6d0:fe00::/40 Valid Other IRR onlyRADB 630 99% 67
2804:6d0:fdff::/48 Valid Other IRR onlyRADB 2 0%low visibility 2

AS-SET

AS262608 isn't in PeeringDB, where networks name their 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 15 are in fix.csv.

  • Route object: RIR13
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: RIR177.85.128.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.85.130.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.85.131.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.85.129.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR177.85.132.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR177.85.135.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR177.85.134.0/24Route object only in TC. Add it in the RIR database for the space.667 of 673
Route object: RIR177.85.133.0/24Route object only in TC. Add it in the RIR database for the space.666 of 673
Route object: RIR2804:6d0::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:6d0:fd00::/40Route object only in RADB. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:6d0:fc00::/40Route object only in RADB. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:6d0:fe00::/40Route object only in RADB. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:6d0:fdff::/48Route object only in RADB. Add it in the RIR database for the space.2 of 636

Route objects not announced

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

177.85.128.0/21RADB, TCNo ROA
177.85.128.0/22RADBNo 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.