Network · data from 2026-11-12
AS7423 PUTNAMFT - Putnam Fiduciary Trust
Registry name: PUTNAMFT - Putnam Fiduciary Trust, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS7423, 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.
| 155.39.77.0/24 | No ROA | Nonecovered by 155.39.64.0/20 | 671 100% |
| 155.39.88.0/24 | Valid | RIR databaseARIN | 671 100% |
AS-SET
AS7423 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 11 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 155.39.77.0/24 | No ROA covers it. Add a ROA for AS7423, maxLength 24. |
| Route object: none | 155.39.77.0/24 | No route object for it. A route object for 155.39.64.0/20 with origin AS7423 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7423 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS7423 whose prefix no peer sees AS7423 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 155.39.36.0/23 | RADB | No ROA |
| 155.39.64.0/20 | RADB | No ROA |
| 155.39.64.0/22 | RADB | No ROA |
| 155.39.68.0/22 | RADB | No ROA |
| 155.39.72.0/22 | RADB | No ROA |
| 155.39.164.0/22 | RADB | No ROA |
| 155.39.167.0/24 | RADB | No ROA |
| 155.39.181.0/24 | RADB | No ROA |
| 208.204.155.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.