Network · data from 2026-11-12
AS36062 DoubleVerify
Registry name: DOUBLE-VERIFY - DoubleVerify, Inc., US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS36062, 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.
| 69.67.147.0/24 | No ROA | None | 671 100% |
| 69.67.146.0/24 | No ROA | Other IRR onlyRADB | 2 0%low visibility |
| 74.80.226.0/24 | No ROA | RIR databaseARIN | 672 100% |
| 204.154.110.0/23 | No ROA | RIR databaseALTDB, ARIN, RADB | 671 100% |
| 74.80.206.0/24 | No ROA | RIR databaseARIN | 670 100% |
| 74.80.225.0/24 | No ROA | RIR databaseARIN | 670 100% |
AS-SET
PeeringDB's irr_as_set for AS36062: AS-DV. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS36062 isn't in the set, or no route object for AS36062 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS36062 in it | Not covered |
|---|---|---|---|---|---|
| AS-DV | ARIN | 1 | 1 | Yes | 1 |
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 14 are in fix.csv.
- ROA: none6
- Route object: none1
- Route object: RIR1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 69.67.147.0/24 | No ROA covers it. Add a ROA for AS36062, maxLength 24. |
| Route object: none | 69.67.147.0/24 | No route object for it. Add a route object with origin AS36062 in the RIR database for the space. |
| ROA: none | 69.67.146.0/24 | No ROA covers it. Add a ROA for AS36062, maxLength 24. |
| Route object: RIR | 69.67.146.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 74.80.226.0/24 | No ROA covers it. Add a ROA for AS36062, maxLength 24. |
| ROA: none | 204.154.110.0/23 | No ROA covers it. Add a ROA for AS36062, maxLength 23. |
| ROA: none | 74.80.206.0/24 | No ROA covers it. Add a ROA for AS36062, maxLength 24. |
| ROA: none | 74.80.225.0/24 | No ROA covers it. Add a ROA for AS36062, maxLength 24. |
Route objects not announced
Route objects with origin AS36062 whose prefix no peer sees AS36062 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 58.145.175.0/24 | APNIC | Invalid: origin |
| 65.170.130.0/24 | RADB | No ROA |
| 204.154.110.0/24 | ALTDB, ARIN, BBOI, RADB | No ROA |
| 204.154.111.0/24 | ALTDB, ARIN, BBOI, RADB | No ROA |
| 213.254.244.0/24 | NTTCOM | Valid |
| 2620:49:40c0::/48 | 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.