Network · data from 2026-11-12
AS40220 MARIA
Registry name: MARIA - Virginia Polytechnic Institute and State Univ., US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS40220, 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.68.251.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 38.68.253.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 38.68.255.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 2607:b400::/32 | No ROA | Other IRR onlyRADB | 636 100% |
| 2001:468:cfe::/48 | No ROA | Other IRR onlyRADB | 415 65% |
| 2001:468:c80::/41 | No ROA | Other IRR onlyRADB | 414 65% |
| 2607:b400::/36 | No ROA | Other IRR onlyRADB | 414 65% |
| 192.122.175.0/24 | No ROA | Other IRR onlyRADB | 89 13% |
AS-SET
PeeringDB's irr_as_set for AS40220: AS40220: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 (AS40220 isn't in the set, or no route object for AS40220 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 | AS40220 in it | Not covered |
|---|---|---|---|---|---|
| AS40220:AS-ALL | RADB | 19 | 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 23 are in fix.csv.
- ROA: none8
- Route object: RIR8
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.68.251.0/24 | No ROA covers it. Add a ROA for AS40220, maxLength 24. |
| Route object: RIR | 38.68.251.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 38.68.253.0/24 | No ROA covers it. Add a ROA for AS40220, maxLength 24. |
| Route object: RIR | 38.68.253.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 38.68.255.0/24 | No ROA covers it. Add a ROA for AS40220, maxLength 24. |
| Route object: RIR | 38.68.255.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2607:b400::/32 | No ROA covers it. Add a ROA for AS40220, maxLength 32. |
| Route object: RIR | 2607:b400::/32 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2001:468:cfe::/48 | No ROA covers it. Add a ROA for AS40220, maxLength 48. |
| Route object: RIR | 2001:468:cfe::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2001:468:c80::/41 | No ROA covers it. Add a ROA for AS40220, maxLength 41. |
| Route object: RIR | 2001:468:c80::/41 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2607:b400::/36 | No ROA covers it. Add a ROA for AS40220, maxLength 36. |
| Route object: RIR | 2607:b400::/36 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 192.122.175.0/24 | No ROA covers it. Add a ROA for AS40220, maxLength 24. |
| Route object: RIR | 192.122.175.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS40220 whose prefix no peer sees AS40220 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.68.198.0/24 | RADB | No ROA |
| 38.68.224.0/19 | RADB | No ROA |
| 38.68.240.0/22 | RADB | No ROA |
| 38.68.250.0/24 | RADB | No ROA |
| 38.68.254.0/24 | RADB | No ROA |
| 164.106.127.0/24 | RADB | No ROA |
| 192.88.107.0/24 | RADB | No 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.