Network · data from 2026-11-12
AS17044 IPGAGENCY - THE INTERPUBLIC GROUP OF COMPANIES, INC.
Registry name: IPGAGENCY - THE INTERPUBLIC GROUP OF COMPANIES, INC., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS17044, 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.
| 170.200.80.0/24 | No ROA | None | 673 100% |
| 205.153.104.0/24 | No ROA | None | 673 100% |
| 170.200.76.0/24 | No ROA | Other IRR onlyALTDB | 673 100% |
| 170.200.92.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 199.4.18.0/24 | No ROA | Other IRR onlyALTDB | 347 52% |
| 170.200.49.0/24 | No ROA | RIR databaseARIN, RADB | 673 100% |
| 170.200.55.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 170.200.84.0/24 | No ROA | RIR databaseARIN, RADB | 671 100% |
| 170.200.48.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
AS-SET
AS17044 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 19 are in fix.csv.
- ROA: none8
- Route object: none2
- Route object: RIR3
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 170.200.80.0/24 | No ROA covers it. Add a ROA for AS17044, maxLength 24. |
| Route object: none | 170.200.80.0/24 | No route object for it. Add a route object with origin AS17044 in the RIR database for the space. |
| ROA: none | 205.153.104.0/24 | No ROA covers it. Add a ROA for AS17044, maxLength 24. |
| Route object: none | 205.153.104.0/24 | No route object for it. Add a route object with origin AS17044 in the RIR database for the space. |
| ROA: none | 170.200.76.0/24 | No ROA covers it. Add a ROA for AS17044, maxLength 24. |
| Route object: RIR | 170.200.76.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 170.200.92.0/24 | No ROA covers it. Add a ROA for AS17044, maxLength 24. |
| Route object: RIR | 170.200.92.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 199.4.18.0/24 | No ROA covers it. Add a ROA for AS17044, maxLength 24. |
| Route object: RIR | 199.4.18.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 170.200.49.0/24 | No ROA covers it. Add a ROA for AS17044, maxLength 24. |
| ROA: none | 170.200.55.0/24 | No ROA covers it. Add a ROA for AS17044, maxLength 24. |
| ROA: none | 170.200.84.0/24 | No ROA covers it. Add a ROA for AS17044, maxLength 24. |
Route objects not announced
Route objects with origin AS17044 whose prefix no peer sees AS17044 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 170.200.47.0/24 | ARIN | No ROA |
| 170.200.74.0/24 | RADB | No ROA |
| 170.200.75.0/24 | RADB | No ROA |
| 170.200.78.0/24 | ALTDB, ARIN | No ROA |
| 170.200.86.0/24 | RADB | No ROA |
| 170.200.128.0/21 | 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.