bgpreport

Network · data from 2026-11-12

AS135217 Peak Air

Registry name: PEAKAIR-AS - Peak Air Pvt Ltd, IN · PeeringDB

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

Announced routes

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

2403:4940:0:400::/54 No ROA Nonecovered by 2403:4940::/32 2 0%low visibility 2
2403:4940:0:800::/54 No ROA Nonecovered by 2403:4940::/32 2 0%low visibility 2
2403:4940:0:1800::/54 No ROA Nonecovered by 2403:4940::/32 2 0%low visibility 2
2403:4940::/32 No ROA RIR databaseAPNIC 636 100% 70
103.138.236.0/24 Valid RIR databaseAPNIC 673 100% 66
103.138.237.0/24 Valid RIR databaseAPNIC 673 100% 66
103.141.56.0/24 Valid RIR databaseAPNIC 673 100% 66
103.141.57.0/24 Valid RIR databaseAPNIC 673 100% 66
103.214.232.0/24 Valid RIR databaseAPNIC 673 100% 67
103.214.233.0/24 Valid RIR databaseAPNIC 673 100% 66
103.214.234.0/24 Valid RIR databaseAPNIC 673 100% 66
103.214.235.0/24 Valid RIR databaseAPNIC 673 100% 66

AS-SET

PeeringDB's irr_as_set for AS135217: AS135217:RS-PEAKAIR. 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 (AS135217 isn't in the set, or no route object for AS135217 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 objectsAS135217 in itNot covered
AS135217:RS-PEAKAIR A route-set, not an AS-SET; route-sets aren't expanded.

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

  • ROA: none4
  • Route object: none3
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none2403:4940:0:400::/54No ROA covers it. Add a ROA for AS135217, maxLength 54.2 of 636
Route object: none2403:4940:0:400::/54No route object for it. A route object for 2403:4940::/32 with origin AS135217 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS135217 in the RIR database for the space.2 of 636
ROA: none2403:4940:0:800::/54No ROA covers it. Add a ROA for AS135217, maxLength 54.2 of 636
Route object: none2403:4940:0:800::/54No route object for it. A route object for 2403:4940::/32 with origin AS135217 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS135217 in the RIR database for the space.2 of 636
ROA: none2403:4940:0:1800::/54No ROA covers it. Add a ROA for AS135217, maxLength 54.2 of 636
Route object: none2403:4940:0:1800::/54No route object for it. A route object for 2403:4940::/32 with origin AS135217 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS135217 in the RIR database for the space.2 of 636
ROA: none2403:4940::/32No ROA covers it. Add a ROA for AS135217, maxLength 32.636 of 636

Route objects not announced

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

103.141.56.0/23APNICValid
103.214.232.0/22APNICValid
103.214.232.0/23APNICValid
103.214.234.0/23APNICValid

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.