bgpreport

Network · data from 2026-11-12

AS11317 Great Plains Network

Registry name: GPN - Great Plains Network, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS11317, 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.
164.113.254.0/23 Valid RIR databaseARIN 20 3%low visibility 18
2001:49d0:3c0::/42 Valid RIR databaseARIN 17 3%low visibility 18
164.113.255.128/27 Valid RIR databaseARIN 8 1%low visibility 10

AS-SET

PeeringDB's irr_as_set for AS11317: RADB::AS-GPN-MEMBERS. 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 (AS11317 isn't in the set, or no route object for AS11317 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 objectsAS11317 in itNot covered
RADB::AS-GPN-MEMBERS RADB3 member sets in no database: AS-IAST-CONE, AS-REED-MEMBERS-I2, AS2495:AS-MEMBERS 489861 No 3

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

  • AS-SET: own ASN1
  • AS-SET: missing member3
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
AS-SET: own ASNRADB::AS-GPN-MEMBERSAS11317 isn't in AS-GPN-MEMBERS (RADB) once expanded. Add AS11317 to it.
AS-SET: missing memberRADB::AS-GPN-MEMBERSAS-GPN-MEMBERS (RADB) lists AS-IAST-CONE; no IRR database read has it.
AS-SET: missing memberRADB::AS-GPN-MEMBERSAS-GPN-MEMBERS (RADB) lists AS-REED-MEMBERS-I2; no IRR database read has it.
AS-SET: missing memberRADB::AS-GPN-MEMBERSAS-GPN-MEMBERS (RADB) lists AS2495:AS-MEMBERS; no IRR database read has it.

Route objects not announced

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

164.113.254.0/26ARINValid
2001:468:100::/40RADBNo 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.