Network · data from 2026-11-12
AS215313 linear.network
Registry name: LINEAR-NETWORK Emily Ingalls, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS215313, 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.
| 2a0f:85c1:b20::/44 | Valid | RIR databaseRIPE | 634 100% |
| 2a0f:85c1:398::/48 | Valid | RIR databaseRADB, RIPE | 625 98% |
AS-SET
PeeringDB's irr_as_set for AS215313: AS215313:AS-LINEAR-NETWORK. 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 (AS215313 isn't in the set, or no route object for AS215313 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 | AS215313 in it | Not covered |
|---|---|---|---|---|---|
| AS215313:AS-LINEAR-NETWORK | RIPE | 1 | 1 | Yes | 0 |
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 1 are in fix.csv.
- Route object: not announced1
Route objects not announced
Route objects with origin AS215313 whose prefix no peer sees AS215313 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a0f:85c1:b21::/48 | RIPE | 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.