bgpreport

Network · data from 2026-11-12

AS64116 PIT - Peru - IP Services

Registry name: AS64116 - PIT PERU S.A.C, PE · PeeringDB

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

Announced routes

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

38.56.100.0/23 No ROA Other IRR onlyRADB 672 100% 67
38.56.101.0/24 No ROA Other IRR onlyRADB 24 4%low visibility 11
2803:cd60:43::/48 Valid Nonecovered by 2803:cd60::/32 20 3%low visibility 10
2803:cd60:8674::/48 Valid Nonecovered by 2803:cd60::/32 20 3%low visibility 10
45.183.44.0/24 Valid Other IRR onlyRADB 668 99% 67
45.183.45.0/24 Valid Other IRR onlyRADB 668 99% 67
2803:cd60:5112::/48 Valid Other IRR onlyRADB 636 100% 67
2803:cd60:5122::/48 Valid Other IRR onlyRADB 636 100% 67
2803:cd60:5701::/48 Valid Other IRR onlyRADB 636 100% 67
2803:cd60:5006::/48 Valid Other IRR onlyRADB 634 100% 67
2803:cd60:5012::/48 Valid Other IRR onlyRADB 634 100% 67
38.56.99.0/24 Valid RIR databaseARIN, RADB 671 100% 67
38.199.83.0/24 Valid RIR databaseARIN, RADB 671 100% 67
38.56.96.0/24 Valid RIR databaseARIN, RADB 670 100% 67
38.56.123.0/24 Valid RIR databaseARIN 670 100% 67
38.137.193.0/24 Valid RIR databaseARIN 670 100% 67
38.199.82.0/24 Valid RIR databaseARIN, RADB 670 100% 67
138.99.177.0/24 Valid RIR databaseLACNIC, RADB 668 99% 67
38.56.100.0/24 Valid RIR databaseARIN, RADB 667 99% 67
2803:cd60::/32 Valid RIR databaseLACNIC, RADB 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS64116: AS-PERUIX. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS64116 isn't in the set, or no route object for AS64116 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS64116 in itNot covered
AS-PERUIX RADB 106740,039 Yes 0

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

  • ROA: none2
  • Route object: none2
  • Route object: RIR9
  • Route object: not announced17
ChangePrefix or setDetailFull-table peers
ROA: none38.56.100.0/23No ROA covers it. Add a ROA for AS64116, maxLength 23.672 of 673
Route object: RIR38.56.100.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.56.101.0/24No ROA covers it. Add a ROA for AS64116, maxLength 24.24 of 673
Route object: RIR38.56.101.0/24Route object only in RADB. Add it in the RIR database for the space.24 of 673
Route object: none2803:cd60:43::/48No route object for it. A route object for 2803:cd60::/32 with origin AS64116 covers it (filters allowing more-specifics accept it). Add a route object with origin AS64116 in the RIR database for the space.20 of 636
Route object: none2803:cd60:8674::/48No route object for it. A route object for 2803:cd60::/32 with origin AS64116 covers it (filters allowing more-specifics accept it). Add a route object with origin AS64116 in the RIR database for the space.20 of 636
Route object: RIR45.183.44.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR45.183.45.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR2803:cd60:5112::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2803:cd60:5122::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2803:cd60:5701::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2803:cd60:5006::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2803:cd60:5012::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

38.56.106.0/24ARIN, RADBValid
38.56.116.0/24RADBNo ROA
38.56.122.0/24ARIN, RADBValid
38.56.125.0/24RADBNo ROA
38.199.81.0/24ARIN, RADBValid
45.68.39.0/24RADBValid
45.183.44.0/22LACNICValid
45.183.44.0/23RADBValid
138.185.13.0/24RADBValid
2801:155:80::/44RADBValid
2801:155:80::/48RADBValid
2801:1dd:2::/48RADBNo ROA
2803:5200:1000::/48RADBNo ROA
2803:cd60:5032::/48RADBValid
2803:cd60:5106::/48RADBValid
2803:cd60:5201::/48RADBValid
2803:cd60:ffff::/48RADBValid

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.