bgpreport

Network · data from 2026-11-12

AS393230 DM-TECH-INTERNET - DM-Tech Internet

Registry name: DM-TECH-INTERNET - DM-Tech Internet, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS393230, 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.
38.80.128.0/24 No ROA Other IRR onlyRADB 672 100% 67
38.80.129.0/24 No ROA Other IRR onlyRADB 672 100% 67
38.80.130.0/24 No ROA Other IRR onlyRADB 672 100% 67
38.80.131.0/24 No ROA Other IRR onlyRADB 672 100% 67
38.80.132.0/24 No ROA Other IRR onlyRADB 672 100% 67
38.80.133.0/24 No ROA Other IRR onlyRADB 672 100% 67
38.80.134.0/24 No ROA Other IRR onlyRADB 672 100% 67
38.80.135.0/24 No ROA Other IRR onlyRADB 672 100% 67
38.80.128.0/21 No ROA Other IRR onlyRADB 671 100% 68
38.133.112.0/21 No ROA Other IRR onlyRADB 671 100% 68

AS-SET

AS393230 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 28 are in fix.csv.

  • ROA: none10
  • Route object: RIR10
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none38.80.128.0/24No ROA covers it. Add a ROA for AS393230, maxLength 24.672 of 673
Route object: RIR38.80.128.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.80.129.0/24No ROA covers it. Add a ROA for AS393230, maxLength 24.672 of 673
Route object: RIR38.80.129.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.80.130.0/24No ROA covers it. Add a ROA for AS393230, maxLength 24.672 of 673
Route object: RIR38.80.130.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.80.131.0/24No ROA covers it. Add a ROA for AS393230, maxLength 24.672 of 673
Route object: RIR38.80.131.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.80.132.0/24No ROA covers it. Add a ROA for AS393230, maxLength 24.672 of 673
Route object: RIR38.80.132.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.80.133.0/24No ROA covers it. Add a ROA for AS393230, maxLength 24.672 of 673
Route object: RIR38.80.133.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.80.134.0/24No ROA covers it. Add a ROA for AS393230, maxLength 24.672 of 673
Route object: RIR38.80.134.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.80.135.0/24No ROA covers it. Add a ROA for AS393230, maxLength 24.672 of 673
Route object: RIR38.80.135.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.80.128.0/21No ROA covers it. Add a ROA for AS393230, maxLength 21.671 of 673
Route object: RIR38.80.128.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.133.112.0/21No ROA covers it. Add a ROA for AS393230, maxLength 21.671 of 673
Route object: RIR38.133.112.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

Route objects with origin AS393230 whose prefix no peer sees AS393230 announce. Many are kept on purpose (backup routes, space announced only in some places).

38.133.112.0/24RADBNo ROA
38.133.113.0/24RADBNo ROA
38.133.114.0/24RADBNo ROA
38.133.115.0/24RADBNo ROA
38.133.116.0/24RADBNo ROA
38.133.117.0/24RADBNo ROA
38.133.118.0/24RADBNo ROA
38.133.119.0/24RADBNo 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.