Network · data from 2026-11-12
AS394028 DLVR - DLVR, Inc.
Registry name: DLVR - DLVR, Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS394028, 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.
| 172.102.239.0/24 | No ROA | Nonecovered by 172.102.232.0/21 | 2 0%low visibility |
AS-SET
AS394028 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 6 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 172.102.239.0/24 | No ROA covers it. Add a ROA for AS394028, maxLength 24. |
| Route object: none | 172.102.239.0/24 | No route object for it. A route object for 172.102.232.0/21 with origin AS394028 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394028 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS394028 whose prefix no peer sees AS394028 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 172.102.232.0/21 | RIPE-NONAUTH | No ROA |
| 185.161.104.0/22 | RIPE | No ROA |
| 2620:122:9000::/44 | RIPE-NONAUTH | No ROA |
| 2a07:c4c0::/29 | RIPE | 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.