bgpreport

Network · data from 2026-11-12

AS135120 PROJECT ELIV

Registry name: PROJECTELIV-AS-AP - PROJECT ELIV, KR · PeeringDB

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

Announced routes

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

2a0f:6284:3301::/48 Valid Nonecovered by 2a0f:6284:3300::/40 634 100% 68
2a0f:6284:3302::/48 Valid Nonecovered by 2a0f:6284:3300::/40 634 100% 68
2a0f:6284:3303::/48 Valid Nonecovered by 2a0f:6284:3300::/40 634 100% 68
2a0f:6284:3320::/48 Valid Nonecovered by 2a0f:6284:3300::/40 634 100% 68
2a0f:6284:3322::/48 Valid Nonecovered by 2a0f:6284:3300::/40 634 100% 68
2a0f:6284:33fe::/48 Valid Nonecovered by 2a0f:6284:3300::/40 634 100% 68
2a0f:6284:3300::/48 Valid Nonecovered by 2a0f:6284:3300::/40 633 100% 68
2a0f:6284:3321::/48 Valid Nonecovered by 2a0f:6284:3300::/40 633 100% 68
2a0f:6284:3324::/48 Valid Nonecovered by 2a0f:6284:3300::/40 629 99% 67
2a0f:6284:3306::/48 Valid Nonecovered by 2a0f:6284:3300::/40 1 0%low visibility 1
2a0f:6284:3323::/48 Valid Nonecovered by 2a0f:6284:3300::/40 1 0%low visibility 1
89.23.91.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
103.31.181.0/24 Valid RIR databaseAPNIC 672 100% 66
103.31.182.0/24 Valid RIR databaseAPNIC 672 100% 66
103.31.183.0/24 Valid RIR databaseAPNIC 672 100% 66
121.0.127.0/24 Valid RIR databaseAPNIC 672 100% 66
142.249.59.0/24 Valid RIR databaseARIN 672 100% 66
147.90.2.0/23 Valid RIR databaseRADB, RIPE 672 100% 70
167.148.69.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
203.210.16.0/24 Valid RIR databaseAPNIC 672 100% 66
203.210.17.0/24 Valid RIR databaseAPNIC 672 100% 66
203.210.18.0/24 Valid RIR databaseAPNIC 672 100% 66
203.210.19.0/24 Valid RIR databaseAPNIC 672 100% 66
203.210.20.0/24 Valid RIR databaseAPNIC 672 100% 66
203.210.21.0/24 Valid RIR databaseAPNIC 672 100% 66
203.210.22.0/24 Valid RIR databaseAPNIC 672 100% 66
203.210.23.0/24 Valid RIR databaseAPNIC 672 100% 66
203.210.26.0/24 Valid RIR databaseAPNIC 672 100% 66
203.210.27.0/24 Valid RIR databaseAPNIC 672 100% 66
203.210.31.0/24 Valid RIR databaseAPNIC 672 100% 66
45.120.67.0/24 Valid RIR databaseAPNIC 671 100% 66
182.237.54.0/24 Valid RIR databaseAPNIC 671 100% 66
185.227.146.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
210.87.193.0/24 Valid RIR databaseAPNIC 671 100% 66
210.87.195.0/24 Valid RIR databaseAPNIC 671 100% 66
210.87.196.0/24 Valid RIR databaseAPNIC 671 100% 66
210.87.198.0/24 Valid RIR databaseAPNIC 671 100% 66
210.87.199.0/24 Valid RIR databaseAPNIC 671 100% 66
210.87.200.0/24 Valid RIR databaseAPNIC 671 100% 66
210.87.201.0/24 Valid RIR databaseAPNIC 671 100% 66
210.87.202.0/24 Valid RIR databaseAPNIC 671 100% 66
210.87.205.0/24 Valid RIR databaseAPNIC 671 100% 66
210.87.207.0/24 Valid RIR databaseAPNIC 671 100% 66
210.87.208.0/21 Valid RIR databaseAPNIC 671 100% 66
210.87.216.0/24 Valid RIR databaseAPNIC 671 100% 66
210.87.217.0/24 Valid RIR databaseAPNIC 671 100% 66
210.87.218.0/24 Valid RIR databaseAPNIC 671 100% 66
210.87.219.0/24 Valid RIR databaseAPNIC 671 100% 66
210.87.220.0/24 Valid RIR databaseAPNIC 671 100% 66
210.87.221.0/24 Valid RIR databaseAPNIC 671 100% 66
210.87.222.0/24 Valid RIR databaseAPNIC 671 100% 66
103.31.180.0/24 Valid RIR databaseAPNIC 670 100% 66
121.0.111.0/24 Valid RIR databaseAPNIC 670 100% 66
45.120.64.0/24 Valid RIR databaseAPNIC 667 99% 67
210.87.206.0/24 Valid RIR databaseAPNIC 661 98% 66
210.87.197.0/24 Valid RIR databaseAPNIC 647 96% 66
210.87.204.0/24 Valid RIR databaseAPNIC 647 96% 66
31.57.50.0/24 Valid RIR databaseRADB, RIPE 645 96% 67
203.210.18.0/23 Valid RIR databaseAPNIC 2 0%low visibility 2
210.87.216.0/22 Valid RIR databaseAPNIC 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS135120: AS135120:AS-ELIV. 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 (AS135120 isn't in the set, or no route object for AS135120 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 objectsAS135120 in itNot covered
AS135120:AS-ELIV APNIC 131201 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 29 are in fix.csv.

  • Route object: none11
  • Route object: not announced18
ChangePrefix or setDetailFull-table peers
Route object: none2a0f:6284:3301::/48No route object for it. A route object for 2a0f:6284:3300::/40 with origin AS135120 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135120 in the RIR database for the space.634 of 636
Route object: none2a0f:6284:3302::/48No route object for it. A route object for 2a0f:6284:3300::/40 with origin AS135120 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135120 in the RIR database for the space.634 of 636
Route object: none2a0f:6284:3303::/48No route object for it. A route object for 2a0f:6284:3300::/40 with origin AS135120 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135120 in the RIR database for the space.634 of 636
Route object: none2a0f:6284:3320::/48No route object for it. A route object for 2a0f:6284:3300::/40 with origin AS135120 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135120 in the RIR database for the space.634 of 636
Route object: none2a0f:6284:3322::/48No route object for it. A route object for 2a0f:6284:3300::/40 with origin AS135120 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135120 in the RIR database for the space.634 of 636
Route object: none2a0f:6284:33fe::/48No route object for it. A route object for 2a0f:6284:3300::/40 with origin AS135120 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135120 in the RIR database for the space.634 of 636
Route object: none2a0f:6284:3300::/48No route object for it. A route object for 2a0f:6284:3300::/40 with origin AS135120 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135120 in the RIR database for the space.633 of 636
Route object: none2a0f:6284:3321::/48No route object for it. A route object for 2a0f:6284:3300::/40 with origin AS135120 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135120 in the RIR database for the space.633 of 636
Route object: none2a0f:6284:3324::/48No route object for it. A route object for 2a0f:6284:3300::/40 with origin AS135120 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135120 in the RIR database for the space.629 of 636
Route object: none2a0f:6284:3306::/48No route object for it. A route object for 2a0f:6284:3300::/40 with origin AS135120 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135120 in the RIR database for the space.1 of 636
Route object: none2a0f:6284:3323::/48No route object for it. A route object for 2a0f:6284:3300::/40 with origin AS135120 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135120 in the RIR database for the space.1 of 636

Route objects not announced

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

210.87.208.0/22APNICValid
210.87.208.0/23APNICValid
210.87.208.0/24APNICValid
210.87.209.0/24APNICValid
210.87.210.0/23APNICValid
210.87.210.0/24APNICValid
210.87.211.0/24APNICValid
210.87.212.0/22APNICValid
210.87.212.0/23APNICValid
210.87.212.0/24APNICValid
210.87.213.0/24APNICValid
210.87.214.0/23APNICValid
210.87.214.0/24APNICValid
210.87.215.0/24APNICValid
210.87.216.0/23APNICValid
210.87.218.0/23APNICValid
2a0f:6284:e::/48RIPEValid
2a0f:6284:3300::/40RIPENo 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.