Network · data from 2026-11-12
AS29708 FINANCIAL-SECURITY-ASSURANCE - Assured Guaranty Corp
Registry name: FINANCIAL-SECURITY-ASSURANCE - Assured Guaranty Corp, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS29708, 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.39.143.0/24 | No ROA | RIR databaseARIN, RADB | 673 100% |
| 170.76.150.0/24 | No ROA | RIR databaseARIN, RADB | 673 100% |
AS-SET
AS29708 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 4 are in fix.csv.
- ROA: none2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 170.39.143.0/24 | No ROA covers it. Add a ROA for AS29708, maxLength 24. |
| ROA: none | 170.76.150.0/24 | No ROA covers it. Add a ROA for AS29708, maxLength 24. |
Route objects not announced
Route objects with origin AS29708 whose prefix no peer sees AS29708 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 12.173.245.0/24 | RADB | No ROA |
| 208.99.174.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.