Network · data from 2026-11-12
AS17161 MMC - Marsh Inc.
Registry name: MMC - Marsh Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS17161, 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.
| 167.245.100.0/23 | No ROA | None | 673 100% |
| 167.245.159.0/24 | Valid | None | 673 100% |
| 205.156.72.0/24 | Valid | Nonecovered by 205.156.64.0/18 | 673 100% |
| 167.245.3.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 167.245.8.0/22 | Valid | RIR databaseARIN, RADB | 673 100% |
| 167.245.12.0/22 | Valid | RIR databaseARIN, RADB | 673 100% |
| 167.245.16.0/22 | Valid | RIR databaseARIN, RADB | 673 100% |
| 167.245.20.0/22 | Valid | RIR databaseARIN, RADB | 673 100% |
| 167.245.24.0/22 | Valid | RIR databaseARIN, RADB | 673 100% |
| 167.245.28.0/22 | Valid | RIR databaseARIN, RADB | 673 100% |
| 167.245.32.0/22 | Valid | RIR databaseARIN, RADB | 673 100% |
| 167.245.36.0/22 | Valid | RIR databaseARIN, RADB | 673 100% |
| 167.245.40.0/22 | Valid | RIR databaseARIN, RADB | 673 100% |
| 167.245.104.0/22 | Valid | RIR databaseARIN, RADB | 673 100% |
| 167.245.108.0/23 | Valid | RIR databaseARIN, RADB | 673 100% |
| 167.245.160.0/19 | Valid | RIR databaseARIN, RADB | 673 100% |
| 205.156.84.0/24 | Valid | RIR databaseARIN | 673 100% |
| 205.156.128.0/22 | Valid | RIR databaseARIN | 673 100% |
| 205.156.132.0/23 | Valid | RIR databaseARIN, RADB | 673 100% |
| 205.156.134.0/24 | Valid | RIR databaseARIN | 673 100% |
| 205.156.135.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 205.156.136.0/21 | Valid | RIR databaseARIN, RADB | 673 100% |
| 205.156.144.0/21 | Valid | RIR databaseARIN, RADB | 673 100% |
| 205.156.152.0/22 | Valid | RIR databaseARIN, RADB | 673 100% |
| 205.156.160.0/23 | Valid | RIR databaseARIN, RADB | 673 100% |
| 205.156.164.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
AS-SET
AS17161 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 17 are in fix.csv.
- ROA: none1
- Route object: none3
- Route object: not announced13
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 167.245.100.0/23 | No ROA covers it. Add a ROA for AS17161, maxLength 23. |
| Route object: none | 167.245.100.0/23 | No route object for it. Add a route object with origin AS17161 in the RIR database for the space. |
| Route object: none | 167.245.159.0/24 | No route object for it. Add a route object with origin AS17161 in the RIR database for the space. |
| Route object: none | 205.156.72.0/24 | No route object for it. A route object for 205.156.64.0/18 with origin AS17161 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17161 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS17161 whose prefix no peer sees AS17161 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 167.245.60.0/24 | RADB | No ROA |
| 168.74.0.0/16 | RADB | No ROA |
| 168.168.150.0/24 | APNIC | Valid |
| 168.168.200.0/24 | APNIC | Valid |
| 168.168.254.0/23 | APNIC, RADB | Valid |
| 203.4.128.0/24 | RADB | No ROA |
| 203.4.129.0/24 | RADB | No ROA |
| 205.156.64.0/18 | RADB | No ROA |
| 205.156.84.0/22 | RADB | No ROA |
| 205.156.116.0/23 | RIPE-NONAUTH | No ROA |
| 205.156.118.0/24 | RIPE-NONAUTH | No ROA |
| 205.156.128.0/18 | RADB | No ROA |
| 205.156.180.0/22 | 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.