Network · data from 2026-11-12
AS394353 USC/ISI B-ROOT
Registry name: BROOT-AS - B.Root-Server-OPS, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS394353, 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.
| 190.103.186.240/28 | Invalid: origin | None | 1 0%low visibility |
| 170.247.171.0/24 | Valid | Nonecovered by 170.247.170.0/23 | 666 99% |
| 170.247.170.0/24 | Valid | Nonecovered by 170.247.170.0/23 | 664 99% |
| 2001:500:207::/48 | Valid | Nonecovered by 2001:500:200::/44 | 635 100% |
| 2001:500:208::/48 | Valid | Nonecovered by 2001:500:200::/44 | 635 100% |
| 2001:500:20a::/48 | Valid | Nonecovered by 2001:500:200::/44 | 634 100% |
| 2801:1b8:11::/48 | Valid | Nonecovered by 2801:1b8:10::/44 | 630 99% |
| 2801:1b8:10::/48 | Valid | Nonecovered by 2801:1b8:10::/44 | 629 99% |
| 2001:500:206::/48 | Valid | Nonecovered by 2001:500:200::/44 | 2 0%low visibility |
| 170.247.170.0/23 | Valid | RIR databaseLACNIC | 670 100% |
| 199.9.14.0/23 | Valid | RIR databaseARIN, NTTCOM, RADB | 669 99% |
| 199.9.15.0/24 | Valid | RIR databaseARIN, NTTCOM | 669 99% |
| 192.228.79.0/24 | Valid | RIR databaseARIN, RADB | 662 98% |
| 199.9.14.0/24 | Valid | RIR databaseARIN, NTTCOM | 662 98% |
| 2001:500:204::/48 | Valid | RIR databaseARIN | 635 100% |
| 2001:500:209::/48 | Valid | RIR databaseARIN | 635 100% |
| 2001:500:200::/44 | Valid | RIR databaseARIN | 634 100% |
| 2801:1b8:10::/44 | Valid | RIR databaseLACNIC | 634 100% |
| 2001:500:205::/48 | Valid | RIR databaseARIN | 631 99% |
| 2001:500:84::/48 | Valid | RIR databaseARIN, RADB | 630 99% |
| 2001:500:201::/48 | Valid | RIR databaseARIN, RADB | 630 99% |
| 2001:500:200::/48 | Valid | RIR databaseARIN, RADB | 627 99% |
AS-SET
PeeringDB's irr_as_set for AS394353: AS-BROOT. 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 (AS394353 isn't in the set, or no route object for AS394353 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 | AS394353 in it | Not covered |
|---|---|---|---|---|---|
| AS-BROOT | ARIN | 1 | 1 | 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 12 are in fix.csv.
- ROA: origin1
- Route object: none9
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 190.103.186.240/28 | ROAs covering it name AS20080, not AS394353. If AS394353 should announce it, add a ROA for AS394353. |
| Route object: none | 190.103.186.240/28 | No route object for it. Add a route object with origin AS394353 in the RIR database for the space. |
| Route object: none | 170.247.171.0/24 | No route object for it. A route object for 170.247.170.0/23 with origin AS394353 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394353 in the RIR database for the space. |
| Route object: none | 170.247.170.0/24 | No route object for it. A route object for 170.247.170.0/23 with origin AS394353 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394353 in the RIR database for the space. |
| Route object: none | 2001:500:207::/48 | No route object for it. A route object for 2001:500:200::/44 with origin AS394353 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394353 in the RIR database for the space. |
| Route object: none | 2001:500:208::/48 | No route object for it. A route object for 2001:500:200::/44 with origin AS394353 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394353 in the RIR database for the space. |
| Route object: none | 2001:500:20a::/48 | No route object for it. A route object for 2001:500:200::/44 with origin AS394353 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394353 in the RIR database for the space. |
| Route object: none | 2801:1b8:11::/48 | No route object for it. A route object for 2801:1b8:10::/44 with origin AS394353 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394353 in the RIR database for the space. |
| Route object: none | 2801:1b8:10::/48 | No route object for it. A route object for 2801:1b8:10::/44 with origin AS394353 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394353 in the RIR database for the space. |
| Route object: none | 2001:500:206::/48 | No route object for it. A route object for 2001:500:200::/44 with origin AS394353 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394353 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS394353 whose prefix no peer sees AS394353 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2001:500:84:200::/56 | ARIN | Valid |
| 2001:13c7:702f::/48 | LACNIC | 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.