bgpreport

Network · data from 2026-11-12

AS12067 ShawneeLink

Registry name: SHAWNEELINK - ShawneeLink Corporation, US · PeeringDB

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

Announced routes

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

216.240.80.0/20 No ROA Nonecovered by 216.240.64.0/19 672 100% 67
64.27.224.0/21 No ROA Other IRR onlyALTDB 669 99% 68
64.27.232.0/21 No ROA Other IRR onlyALTDB 669 99% 68
216.240.64.0/20 No ROA Other IRR onlyRADB 669 99% 68
64.27.224.0/20 No ROA RIR databaseARIN 669 99% 68
216.240.64.0/19 No ROA RIR databaseARIN 669 99% 68
2606:1e00::/32 No ROA RIR databaseARIN 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS12067: RS-SHTC. 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 (AS12067 isn't in the set, or no route object for AS12067 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 objectsAS12067 in itNot covered
RS-SHTC 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: none7
  • Route object: none1
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
ROA: none216.240.80.0/20No ROA covers it. Add a ROA for AS12067, maxLength 20.672 of 673
Route object: none216.240.80.0/20No route object for it. A route object for 216.240.64.0/19 with origin AS12067 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12067 in the RIR database for the space.672 of 673
ROA: none64.27.224.0/21No ROA covers it. Add a ROA for AS12067, maxLength 21.669 of 673
Route object: RIR64.27.224.0/21Route object only in ALTDB. Add it in the RIR database for the space.669 of 673
ROA: none64.27.232.0/21No ROA covers it. Add a ROA for AS12067, maxLength 21.669 of 673
Route object: RIR64.27.232.0/21Route object only in ALTDB. Add it in the RIR database for the space.669 of 673
ROA: none216.240.64.0/20No ROA covers it. Add a ROA for AS12067, maxLength 20.669 of 673
Route object: RIR216.240.64.0/20Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none64.27.224.0/20No ROA covers it. Add a ROA for AS12067, maxLength 20.669 of 673
ROA: none216.240.64.0/19No ROA covers it. Add a ROA for AS12067, maxLength 19.669 of 673
ROA: none2606:1e00::/32No ROA covers it. Add a ROA for AS12067, maxLength 32.635 of 636

Route objects not announced

Every route object with origin AS12067 is announced.

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.