bgpreport

Network · data from 2026-11-12

AS27027 AirLink Internet Services

Registry name: AIRLINK-INTERNET - AirLink Internet Services, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS27027, 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.
162.222.232.0/24 Valid Nonecovered by 162.222.232.0/21 673 100% 67
162.222.233.0/24 Valid Other IRR onlyRADB 673 100% 67
162.222.235.0/24 Valid Other IRR onlyRADB 673 100% 67
162.222.236.0/24 Valid Other IRR onlyRADB 673 100% 67
162.222.237.0/24 Valid Other IRR onlyRADB 673 100% 67
162.222.238.0/24 Valid Other IRR onlyRADB 673 100% 67
2607:8280:4::/48 Valid Other IRR onlyRADB 11 2%low visibility 11
162.222.232.0/21 Valid RIR databaseARIN, RADB 673 100% 67
2607:8280::/32 Valid RIR databaseARIN 11 2%low visibility 11

AS-SET

AS27027'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 20 are in fix.csv.

  • Route object: none1
  • Route object: RIR6
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
Route object: none162.222.232.0/24No route object for it. A route object for 162.222.232.0/21 with origin AS27027 covers it (filters allowing more-specifics accept it). Add a route object with origin AS27027 in the RIR database for the space.673 of 673
Route object: RIR162.222.233.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR162.222.235.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR162.222.236.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR162.222.237.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR162.222.238.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR2607:8280:4::/48Route object only in RADB. Add it in the RIR database for the space.11 of 636

Route objects not announced

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

162.222.234.0/24RADBValid
162.222.239.0/24RADBValid
196.32.0.0/21RADBNo ROA
204.10.112.0/21RADB, RIPE-NONAUTHNo ROA
204.10.112.0/24RIPE-NONAUTHNo ROA
204.10.113.0/24RIPE-NONAUTHNo ROA
204.10.114.0/24RIPE-NONAUTHNo ROA
204.10.115.0/24RIPE-NONAUTHNo ROA
208.138.19.0/24RADBNo ROA
208.163.56.0/23RADBNo ROA
208.163.56.0/24RADBNo ROA
208.163.57.0/24RADBNo ROA
2607:8280:1::/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.