bgpreport

Network · data from 2026-11-12

AS262182 AS262182 - TELEFONICA GLOBAL SOLUTIONS PERU S.A.C.

Registry name: AS262182 - TELEFONICA GLOBAL SOLUTIONS PERU S.A.C., PE · not in PeeringDB

27IPv4 routes 77.8% RPKI valid · 51.9% with a route object
24IPv6 routes 58.3% RPKI valid · 58.3% with a route object
0RPKI invalid 0 origin · 0 maxLength
16No ROA 23 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
7Route objects not announced registered with origin AS262182, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS262182, 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.

138.94.18.0/24 No ROA None 671 100% 67
138.219.126.0/23 No ROA None 671 100% 67
138.219.126.0/24 No ROA None 671 100% 67
138.219.127.0/24 No ROA None 671 100% 67
200.108.70.0/23 No ROA None 670 100% 67
2800:4d0:2485::/48 No ROA None 636 100% 67
2800:4d0:2486::/48 No ROA None 636 100% 67
2800:4d0:2487::/48 No ROA None 636 100% 67
2800:4d0:2488::/48 No ROA None 636 100% 67
2804:22cc:400::/38 No ROA None 636 100% 67
2804:27f0:10::/44 No ROA None 636 100% 67
2805:f10:f12::/48 No ROA None 636 100% 67
2805:f10:f13::/48 No ROA None 636 100% 67
2805:f10:f14::/48 No ROA None 636 100% 67
2800:4d0:2489::/48 No ROA None 635 100% 67
187.92.209.0/24 No ROA None 2 0%low visibility 2
89.32.178.0/24 Valid None 671 100% 67
179.56.194.0/24 Valid None 671 100% 67
186.118.186.0/24 Valid Nonecovered by 186.118.186.0/23 671 100% 67
186.118.187.0/24 Valid Nonecovered by 186.118.186.0/23 671 100% 67
190.52.114.0/24 Valid Nonecovered by 190.52.112.0/22 670 100% 67
190.98.168.0/24 Valid Nonecovered by 190.98.168.0/23 670 100% 67
190.98.169.0/24 Valid Nonecovered by 190.98.168.0/23 670 100% 67
131.161.100.0/24 Valid RIR databaseLACNIC 671 100% 67
131.161.101.0/24 Valid RIR databaseLACNIC 671 100% 67
190.52.112.0/22 Valid RIR databaseLACNIC 670 100% 67
190.52.116.0/24 Valid RIR databaseLACNIC 670 100% 67
190.52.117.0/24 Valid RIR databaseLACNIC 670 100% 67
190.52.119.0/24 Valid RIR databaseLACNIC 670 100% 67
190.52.121.0/24 Valid RIR databaseLACNIC 670 100% 67
190.52.123.0/24 Valid RIR databaseLACNIC 670 100% 67
190.52.125.0/24 Valid RIR databaseLACNIC 670 100% 67
190.52.126.0/24 Valid RIR databaseLACNIC 670 100% 67
190.52.127.0/24 Valid RIR databaseLACNIC 670 100% 67
190.52.118.0/24 Valid RIR databaseLACNIC 660 98% 67
190.52.120.0/24 Valid RIR databaseLACNIC 660 98% 67
190.52.122.0/24 Valid RIR databaseLACNIC 660 98% 67
2803:f00::/48 Valid RIR databaseLACNIC 636 100% 67
2803:f00:1::/48 Valid RIR databaseLACNIC 636 100% 67
2803:f00:3::/48 Valid RIR databaseLACNIC 636 100% 67
2803:f00:4::/48 Valid RIR databaseLACNIC 636 100% 67
2803:f00:5::/48 Valid RIR databaseLACNIC 636 100% 67
2803:f00:440::/42 Valid RIR databaseLACNIC 636 100% 67
2803:f00:480::/42 Valid RIR databaseLACNIC 636 100% 67
2803:f00:49b::/48 Valid RIR databaseLACNIC 636 100% 67
2803:f00:4c0::/48 Valid RIR databaseLACNIC 636 100% 67
2803:f00:4c3::/48 Valid RIR databaseLACNIC 636 100% 67
2803:f00:4c9::/48 Valid RIR databaseLACNIC 636 100% 67
2803:f00:64b::/48 Valid RIR databaseLACNIC 636 100% 67
2803:f00:680::/42 Valid RIR databaseLACNIC 636 100% 67
2803:f00:700::/42 Valid RIR databaseLACNIC 636 100% 67

AS-SET

AS262182 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 46 are in fix.csv.

  • ROA: none16
  • Route object: none23
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none138.94.18.0/24No ROA covers it. Add a ROA for AS262182, maxLength 24.671 of 673
Route object: none138.94.18.0/24No route object for it. Add a route object with origin AS262182 in the RIR database for the space.671 of 673
ROA: none138.219.126.0/23No ROA covers it. Add a ROA for AS262182, maxLength 23.671 of 673
Route object: none138.219.126.0/23No route object for it. Add a route object with origin AS262182 in the RIR database for the space.671 of 673
ROA: none138.219.126.0/24No ROA covers it. Add a ROA for AS262182, maxLength 24.671 of 673
Route object: none138.219.126.0/24No route object for it. Add a route object with origin AS262182 in the RIR database for the space.671 of 673
ROA: none138.219.127.0/24No ROA covers it. Add a ROA for AS262182, maxLength 24.671 of 673
Route object: none138.219.127.0/24No route object for it. Add a route object with origin AS262182 in the RIR database for the space.671 of 673
ROA: none200.108.70.0/23No ROA covers it. Add a ROA for AS262182, maxLength 23.670 of 673
Route object: none200.108.70.0/23No route object for it. Add a route object with origin AS262182 in the RIR database for the space.670 of 673
ROA: none2800:4d0:2485::/48No ROA covers it. Add a ROA for AS262182, maxLength 48.636 of 636
Route object: none2800:4d0:2485::/48No route object for it. Add a route object with origin AS262182 in the RIR database for the space.636 of 636
ROA: none2800:4d0:2486::/48No ROA covers it. Add a ROA for AS262182, maxLength 48.636 of 636
Route object: none2800:4d0:2486::/48No route object for it. Add a route object with origin AS262182 in the RIR database for the space.636 of 636
ROA: none2800:4d0:2487::/48No ROA covers it. Add a ROA for AS262182, maxLength 48.636 of 636
Route object: none2800:4d0:2487::/48No route object for it. Add a route object with origin AS262182 in the RIR database for the space.636 of 636
ROA: none2800:4d0:2488::/48No ROA covers it. Add a ROA for AS262182, maxLength 48.636 of 636
Route object: none2800:4d0:2488::/48No route object for it. Add a route object with origin AS262182 in the RIR database for the space.636 of 636
ROA: none2804:22cc:400::/38No ROA covers it. Add a ROA for AS262182, maxLength 38.636 of 636
Route object: none2804:22cc:400::/38No route object for it. Add a route object with origin AS262182 in the RIR database for the space.636 of 636
ROA: none2804:27f0:10::/44No ROA covers it. Add a ROA for AS262182, maxLength 44.636 of 636
Route object: none2804:27f0:10::/44No route object for it. Add a route object with origin AS262182 in the RIR database for the space.636 of 636
ROA: none2805:f10:f12::/48No ROA covers it. Add a ROA for AS262182, maxLength 48.636 of 636
Route object: none2805:f10:f12::/48No route object for it. Add a route object with origin AS262182 in the RIR database for the space.636 of 636
ROA: none2805:f10:f13::/48No ROA covers it. Add a ROA for AS262182, maxLength 48.636 of 636
Route object: none2805:f10:f13::/48No route object for it. Add a route object with origin AS262182 in the RIR database for the space.636 of 636
ROA: none2805:f10:f14::/48No ROA covers it. Add a ROA for AS262182, maxLength 48.636 of 636
Route object: none2805:f10:f14::/48No route object for it. Add a route object with origin AS262182 in the RIR database for the space.636 of 636
ROA: none2800:4d0:2489::/48No ROA covers it. Add a ROA for AS262182, maxLength 48.635 of 636
Route object: none2800:4d0:2489::/48No route object for it. Add a route object with origin AS262182 in the RIR database for the space.635 of 636
ROA: none187.92.209.0/24No ROA covers it. Add a ROA for AS262182, maxLength 24.2 of 673
Route object: none187.92.209.0/24No route object for it. Add a route object with origin AS262182 in the RIR database for the space.2 of 673
Route object: none89.32.178.0/24No route object for it. Add a route object with origin AS262182 in the RIR database for the space.671 of 673
Route object: none179.56.194.0/24No route object for it. Add a route object with origin AS262182 in the RIR database for the space.671 of 673
Route object: none186.118.186.0/24No route object for it. A route object for 186.118.186.0/23 with origin AS262182 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262182 in the RIR database for the space.671 of 673
Route object: none186.118.187.0/24No route object for it. A route object for 186.118.186.0/23 with origin AS262182 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262182 in the RIR database for the space.671 of 673
Route object: none190.52.114.0/24No route object for it. A route object for 190.52.112.0/22 with origin AS262182 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262182 in the RIR database for the space.670 of 673
Route object: none190.98.168.0/24No route object for it. A route object for 190.98.168.0/23 with origin AS262182 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262182 in the RIR database for the space.670 of 673
Route object: none190.98.169.0/24No route object for it. A route object for 190.98.168.0/23 with origin AS262182 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262182 in the RIR database for the space.670 of 673

Route objects not announced

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

186.118.186.0/23LACNICValid
190.52.124.0/24LACNICValid
190.98.168.0/23LACNICValid
200.5.215.0/27LACNICValid
200.5.215.32/29LACNICValid
200.5.215.64/29LACNICValid
200.5.215.248/29LACNICValid

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.