bgpreport

Network · data from 2026-11-12

AS262395 AS262395 - WIFI Plus Provedor Ltda.

Registry name: AS262395 - WIFI Plus Provedor Ltda., BR · not in PeeringDB

5IPv4 routes 100.0% RPKI valid · 100.0% with a route object
3IPv6 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
0Low visibility seen by under 10% of full-table peers
30Route objects not announced registered with origin AS262395, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS262395, 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.129.96.0/22 Valid Other IRR onlyALTDB, RADB 672 100% 67
177.129.96.0/24 Valid Other IRR onlyALTDB, RADB 672 100% 67
177.129.97.0/24 Valid Other IRR onlyALTDB, RADB 672 100% 67
177.129.98.0/24 Valid Other IRR onlyALTDB, RADB 672 100% 67
177.129.99.0/24 Valid Other IRR onlyALTDB, RADB 672 100% 67
2804:8dc::/32 Valid Other IRR onlyALTDB, RADB 636 100% 67
2804:8dc::/33 Valid Other IRR onlyALTDB, RADB 636 100% 67
2804:8dc:8000::/33 Valid Other IRR onlyALTDB, RADB 636 100% 67

AS-SET

AS262395 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 38 are in fix.csv.

  • Route object: RIR8
  • Route object: not announced30
ChangePrefix or setDetailFull-table peers
Route object: RIR177.129.96.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.129.96.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.129.97.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.129.98.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.129.99.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:8dc::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:8dc::/33Route object only in ALTDB, RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:8dc:8000::/33Route object only in ALTDB, RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

177.129.96.0/23ALTDB, RADBValid
177.129.98.0/23ALTDB, RADBValid
2804:8dc::/34ALTDB, RADBValid
2804:8dc::/35RADBValid
2804:8dc::/36RADBValid
2804:8dc:1000::/36RADBValid
2804:8dc:2000::/35RADBValid
2804:8dc:2000::/36RADBValid
2804:8dc:3000::/36RADBValid
2804:8dc:4000::/34ALTDB, RADBValid
2804:8dc:4000::/35RADBValid
2804:8dc:4000::/36RADBValid
2804:8dc:5000::/36RADBValid
2804:8dc:6000::/35RADBValid
2804:8dc:6000::/36RADBValid
2804:8dc:7000::/36RADBValid
2804:8dc:8000::/34ALTDB, RADBValid
2804:8dc:8000::/35RADBValid
2804:8dc:8000::/36RADBValid
2804:8dc:9000::/36RADBValid
2804:8dc:a000::/35RADBValid
2804:8dc:a000::/36RADBValid
2804:8dc:b000::/36RADBValid
2804:8dc:c000::/34ALTDB, RADBValid
2804:8dc:c000::/35RADBValid
2804:8dc:c000::/36RADBValid
2804:8dc:d000::/36RADBValid
2804:8dc:e000::/35RADBValid
2804:8dc:e000::/36RADBValid
2804:8dc:f000::/36RADBValid

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.