bgpreport

Network · data from 2026-11-12

AS271868 GPON NETWORKS

Registry name: AS271868 - GPON NETWORKS S.A.C., PE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271868, 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.
204.199.171.0/24 No ROA None 673 100% 67
200.215.228.0/24 Valid Nonecovered by 200.215.228.0/22 672 100% 67
200.215.231.0/24 Valid Nonecovered by 200.215.228.0/22 672 100% 67
200.215.230.0/24 Valid Nonecovered by 200.215.228.0/22 671 100% 67
200.215.229.0/24 Valid Other IRR onlyRADB 671 100% 67
209.61.13.0/24 Valid RIR databaseARIN 672 100% 67
2803:8c10:40::/42 Valid RIR databaseLACNIC, RADB 636 100% 67
2803:8c10:80::/42 Valid RIR databaseLACNIC, RADB 636 100% 67

AS-SET

AS271868'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 9 are in fix.csv.

  • ROA: none1
  • Route object: none4
  • Route object: RIR1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none204.199.171.0/24No ROA covers it. Add a ROA for AS271868, maxLength 24.673 of 673
Route object: none204.199.171.0/24No route object for it. Add a route object with origin AS271868 in the RIR database for the space.673 of 673
Route object: none200.215.228.0/24No route object for it. A route object for 200.215.228.0/22 with origin AS271868 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271868 in the RIR database for the space.672 of 673
Route object: none200.215.231.0/24No route object for it. A route object for 200.215.228.0/22 with origin AS271868 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271868 in the RIR database for the space.672 of 673
Route object: none200.215.230.0/24No route object for it. A route object for 200.215.228.0/22 with origin AS271868 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271868 in the RIR database for the space.671 of 673
Route object: RIR200.215.229.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

190.108.91.0/24RADBValid
200.215.228.0/22LACNICValid
2803:8c10::/42RADBNo 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.