bgpreport

Network · data from 2026-11-12

AS262620 Pox Network Telecomunicacoes

Registry name: AS262620 - Pox Network Telecomunicacoes Ltda-ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS262620, 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.86.20.0/24 Valid Nonecovered by 177.86.20.0/22 671 100% 67
177.86.22.0/24 Valid Nonecovered by 177.86.20.0/22 671 100% 67
2804:718:8000::/33 Valid Nonecovered by 2804:718::/32 352 55% 65
177.86.16.0/21 Valid Other IRR onlyRADB, TC 671 100% 67
177.86.16.0/22 Valid Other IRR onlyRADB 671 100% 67
177.86.16.0/24 Valid Other IRR onlyRADB 671 100% 67
177.86.17.0/24 Valid Other IRR onlyRADB 671 100% 67
177.86.18.0/24 Valid Other IRR onlyRADB 671 100% 67
177.86.20.0/22 Valid Other IRR onlyRADB 671 100% 67
177.86.23.0/24 Valid Other IRR onlyRADB 671 100% 67
177.86.19.0/24 Valid Other IRR onlyRADB 670 100% 67
177.86.21.0/24 Valid Other IRR onlyRADB 670 100% 67
2804:718::/32 Valid Other IRR onlyRADB, TC 634 100% 67

AS-SET

AS262620'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 13 are in fix.csv.

  • Route object: none3
  • Route object: RIR10
ChangePrefix or setDetailFull-table peers
Route object: none177.86.20.0/24No route object for it. A route object for 177.86.20.0/22 with origin AS262620 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262620 in the RIR database for the space.671 of 673
Route object: none177.86.22.0/24No route object for it. A route object for 177.86.20.0/22 with origin AS262620 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262620 in the RIR database for the space.671 of 673
Route object: none2804:718:8000::/33No route object for it. A route object for 2804:718::/32 with origin AS262620 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262620 in the RIR database for the space.352 of 636
Route object: RIR177.86.16.0/21Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.86.16.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR177.86.16.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR177.86.17.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR177.86.18.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR177.86.20.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR177.86.23.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR177.86.19.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR177.86.21.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:718::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

Every route object with origin AS262620 is announced.

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.