bgpreport

Network · data from 2026-11-12

AS262621 Pontonet Telecom

Registry name: AS262621 - LIMA & VICENTE Diversoes Eletronicas LTDA, BR · PeeringDB

6IPv4 routes 100.0% RPKI valid · 100.0% with a route object
3IPv6 routes 100.0% RPKI valid · 33.3% with a route object
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
8Route objects not announced registered with origin AS262621, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS262621, 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:720::/33 Valid Nonecovered by 2804:720::/32 112 18% 43
2804:720:8000::/33 Valid Nonecovered by 2804:720::/32 112 18% 43
131.0.44.0/22 Valid Other IRR onlyRADB, TC 670 100% 67
177.86.32.0/22 Valid Other IRR onlyRADB, TC 670 100% 67
2804:720::/32 Valid Other IRR onlyRADB, TC 636 100% 67
131.0.44.0/23 Valid Other IRR onlyTC 123 18% 44
131.0.46.0/23 Valid Other IRR onlyTC 123 18% 44
177.86.34.0/23 Valid Other IRR onlyTC 123 18% 44
177.86.32.0/23 Valid Other IRR onlyTC 122 18% 44

AS-SET

AS262621'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 17 are in fix.csv.

  • Route object: none2
  • Route object: RIR7
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
Route object: none2804:720::/33No route object for it. A route object for 2804:720::/32 with origin AS262621 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262621 in the RIR database for the space.112 of 636
Route object: none2804:720:8000::/33No route object for it. A route object for 2804:720::/32 with origin AS262621 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262621 in the RIR database for the space.112 of 636
Route object: RIR131.0.44.0/22Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR177.86.32.0/22Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:720::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636
Route object: RIR131.0.44.0/23Route object only in TC. Add it in the RIR database for the space.123 of 673
Route object: RIR131.0.46.0/23Route object only in TC. Add it in the RIR database for the space.123 of 673
Route object: RIR177.86.34.0/23Route object only in TC. Add it in the RIR database for the space.123 of 673
Route object: RIR177.86.32.0/23Route object only in TC. Add it in the RIR database for the space.122 of 673

Route objects not announced

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

131.0.44.0/24TCValid
131.0.45.0/24TCValid
131.0.46.0/24TCValid
131.0.47.0/24TCValid
177.86.32.0/24TCValid
177.86.33.0/24TCValid
177.86.34.0/24TCValid
177.86.35.0/24TCValid

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.