Network · data from 2026-11-12
AS6967 AS6967 - Metronet
Registry name: AS6967 - Metronet, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS6967, 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.
| 192.69.179.48/29 | No ROA | None | 2 0%low visibility |
| 46.110.180.0/24 | Valid | Nonecovered by 46.110.180.0/23 | 672 100% |
| 46.110.181.0/24 | Valid | Nonecovered by 46.110.180.0/23 | 672 100% |
AS-SET
AS6967 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 7 are in fix.csv.
- ROA: none1
- Route object: none3
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 192.69.179.48/29 | No ROA covers it. Add a ROA for AS6967, maxLength 29. |
| Route object: none | 192.69.179.48/29 | No route object for it. Add a route object with origin AS6967 in the RIR database for the space. |
| Route object: none | 46.110.180.0/24 | No route object for it. A route object for 46.110.180.0/23 with origin AS6967 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6967 in the RIR database for the space. |
| Route object: none | 46.110.181.0/24 | No route object for it. A route object for 46.110.180.0/23 with origin AS6967 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6967 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS6967 whose prefix no peer sees AS6967 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 46.110.180.0/23 | ARIN | Valid |
| 2606:9380:8000::/33 | ARIN, RADB | No ROA |
| 2606:9380:8000::/42 | 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.