Network · data from 2026-11-12
AS400463 DYNANODE-ASN-01 - DynaNode LLC
Registry name: DYNANODE-ASN-01 - DynaNode LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS400463, 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.
| 196.51.0.0/17 | Valid | Nonecovered by 196.51.0.0/16 | 673 100% |
| 196.51.128.0/17 | Valid | Nonecovered by 196.51.0.0/16 | 673 100% |
| 156.230.192.0/18 | Valid | RIR databaseAFRINIC, RADB | 672 100% |
| 156.241.192.0/18 | Valid | RIR databaseAFRINIC, RADB | 672 100% |
| 199.16.236.0/22 | Valid | RIR databaseARIN | 671 100% |
AS-SET
AS400463 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 8 are in fix.csv.
- Route object: none2
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 196.51.0.0/17 | No route object for it. A route object for 196.51.0.0/16 with origin AS400463 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400463 in the RIR database for the space. |
| Route object: none | 196.51.128.0/17 | No route object for it. A route object for 196.51.0.0/16 with origin AS400463 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400463 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS400463 whose prefix no peer sees AS400463 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 156.241.200.0/22 | RADB | Valid |
| 156.241.204.0/22 | RADB | Valid |
| 156.241.208.0/22 | RADB | Valid |
| 156.241.212.0/22 | RADB | Valid |
| 156.241.255.0/24 | RADB | Valid |
| 196.51.0.0/16 | AFRINIC | 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.