Network · data from 2026-11-12
AS399240 Blue Ridge Internet
Registry name: BLUE-RIDGE-INTERNET - BLUE RIDGE INTERNET, L.L.C, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS399240, 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.
| 38.17.44.0/23 | No ROA | RIR databaseARIN, RADB | 670 100% |
| 205.164.242.0/24 | No ROA | RIR databaseARIN, RADB | 670 100% |
| 38.17.44.0/24 | No ROA | RIR databaseARIN, RADB | 669 99% |
| 38.17.45.0/24 | No ROA | RIR databaseARIN, RADB | 669 99% |
| 38.86.212.0/24 | No ROA | RIR databaseARIN | 119 18% |
| 206.168.160.0/22 | Valid | RIR databaseARIN | 671 100% |
| 206.168.160.0/24 | Valid | RIR databaseARIN | 671 100% |
| 206.168.161.0/24 | Valid | RIR databaseARIN | 671 100% |
| 206.168.162.0/23 | Valid | RIR databaseARIN | 671 100% |
| 206.168.162.0/24 | Valid | RIR databaseARIN | 671 100% |
| 206.168.163.0/24 | Valid | RIR databaseARIN | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS399240: AS-BRI. 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 (AS399240 isn't in the set, or no route object for AS399240 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 | AS399240 in it | Not covered |
|---|---|---|---|---|---|
| AS-BRI | ARINlists itself further down | 2 | 7 | 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 7 are in fix.csv.
- ROA: none5
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.17.44.0/23 | No ROA covers it. Add a ROA for AS399240, maxLength 23. |
| ROA: none | 205.164.242.0/24 | No ROA covers it. Add a ROA for AS399240, maxLength 24. |
| ROA: none | 38.17.44.0/24 | No ROA covers it. Add a ROA for AS399240, maxLength 24. |
| ROA: none | 38.17.45.0/24 | No ROA covers it. Add a ROA for AS399240, maxLength 24. |
| ROA: none | 38.86.212.0/24 | No ROA covers it. Add a ROA for AS399240, maxLength 24. |
Route objects not announced
Route objects with origin AS399240 whose prefix no peer sees AS399240 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 206.168.160.0/23 | ARIN | Valid |
| 2607:30c0::/32 | 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.