Network · data from 2026-11-12
AS16851 Nebraskalink
Registry name: NEBRASKALINK - NebraskaLink, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS16851, 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.
| 104.218.80.0/22 | No ROA | None | 671 100% |
| 104.152.240.0/24 | Valid | Nonecovered by 104.152.240.0/22 | 671 100% |
| 2607:3700:1::/48 | Valid | Nonecovered by 2607:3700::/32 | 634 100% |
| 209.94.54.0/23 | Valid | RIR databaseARIN | 673 100% |
| 104.152.240.0/22 | Valid | RIR databaseARIN | 671 100% |
| 107.167.242.0/23 | Valid | RIR databaseARIN | 671 100% |
| 162.212.16.0/22 | Valid | RIR databaseARIN | 671 100% |
| 199.36.116.0/22 | Valid | RIR databaseARIN | 671 100% |
| 199.58.136.0/24 | Valid | RIR databaseARIN | 671 100% |
| 2607:3700::/32 | Valid | RIR databaseARIN | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS16851: AS16851:AS-ALL. 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 (AS16851 isn't in the set, or no route object for AS16851 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.
| Name | Database | ASNs | Sets | AS16851 in it | Not covered |
|---|---|---|---|---|---|
| AS16851:AS-ALL | ARIN | 48 | 6 | Yes | 1 |
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 8 are in fix.csv.
- ROA: none1
- Route object: none3
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 104.218.80.0/22 | No ROA covers it. Add a ROA for AS16851, maxLength 22. |
| Route object: none | 104.218.80.0/22 | No route object for it. Add a route object with origin AS16851 in the RIR database for the space. |
| Route object: none | 104.152.240.0/24 | No route object for it. A route object for 104.152.240.0/22 with origin AS16851 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16851 in the RIR database for the space. |
| Route object: none | 2607:3700:1::/48 | No route object for it. A route object for 2607:3700::/32 with origin AS16851 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16851 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS16851 whose prefix no peer sees AS16851 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 104.218.81.0/24 | ARIN | Valid |
| 104.218.82.0/24 | ARIN | Valid |
| 216.142.253.0/24 | RADB | No ROA |
| 2001:470:5a4::/48 | ARIN | Valid |
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.