bgpreport

Network · data from 2026-11-12

AS42136 DVTK-AS DVTK LLC

Registry name: DVTK-AS DVTK LLC, RU · not in PeeringDB

5IPv4 routes 0.0% RPKI valid · 100.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
6No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS42136, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS42136, 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.

91.204.232.0/22 No ROA RIR databaseRIPE 672 100% 67
93.114.142.0/24 No ROA RIR databaseRIPE 672 100% 67
185.141.238.0/23 No ROA RIR databaseRIPE 672 100% 67
185.203.144.0/22 No ROA RIR databaseRIPE 672 100% 67
194.247.20.0/23 No ROA RIR databaseRIPE 672 100% 67
2a0c:e140::/29 No ROA RIR databaseRIPE 634 100% 68

AS-SET

AS42136 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: none6
ChangePrefix or setDetailFull-table peers
ROA: none91.204.232.0/22No ROA covers it. Add a ROA for AS42136, maxLength 22.672 of 673
ROA: none93.114.142.0/24No ROA covers it. Add a ROA for AS42136, maxLength 24.672 of 673
ROA: none185.141.238.0/23No ROA covers it. Add a ROA for AS42136, maxLength 23.672 of 673
ROA: none185.203.144.0/22No ROA covers it. Add a ROA for AS42136, maxLength 22.672 of 673
ROA: none194.247.20.0/23No ROA covers it. Add a ROA for AS42136, maxLength 23.672 of 673
ROA: none2a0c:e140::/29No ROA covers it. Add a ROA for AS42136, maxLength 29.634 of 636

Route objects not announced

Every route object with origin AS42136 is announced.

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.