Network · data from 2026-11-12
AS40468 MONTGOMERYCOUNTYMDGOV - Montgomery County Government, Maryland
Registry name: MONTGOMERYCOUNTYMDGOV - Montgomery County Government, Maryland, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS40468, 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.
| 205.222.252.0/22 | No ROA | RIR databaseARIN | 671 100% |
| 208.76.112.0/21 | No ROA | RIR databaseARIN, RADB | 671 100% |
AS-SET
AS40468 isn't in PeeringDB, where networks name their AS-SET.
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 9 are in fix.csv.
- ROA: none2
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 205.222.252.0/22 | No ROA covers it. Add a ROA for AS40468, maxLength 22. |
| ROA: none | 208.76.112.0/21 | No ROA covers it. Add a ROA for AS40468, maxLength 21. |
Route objects not announced
Route objects with origin AS40468 whose prefix no peer sees AS40468 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 208.76.112.0/24 | RADB | No ROA |
| 208.76.113.0/24 | RADB | No ROA |
| 208.76.115.0/24 | RADB | No ROA |
| 208.76.116.0/22 | RADB | No ROA |
| 208.76.116.0/24 | RADB | No ROA |
| 208.76.117.0/24 | RADB | No ROA |
| 209.190.194.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.