bgpreport

Network · data from 2026-11-12

AS215710 hdmdigital HDM Dijital Hizmetleri Ticaret Limited Sirketi

Registry name: hdmdigital HDM Dijital Hizmetleri Ticaret Limited Sirketi, TR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS215710, 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.
185.103.202.0/24 No ROA RIR databaseRIPE 672 100% 67
45.95.65.0/24 Valid RIR databaseRADB, RIPE 671 100% 67

AS-SET

AS215710 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 23 are in fix.csv.

  • ROA: none1
  • Route object: not announced22
ChangePrefix or setDetailFull-table peers
ROA: none185.103.202.0/24No ROA covers it. Add a ROA for AS215710, maxLength 24.672 of 673

Route objects not announced

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

62.220.125.0/24RIPEInvalid: origin
81.168.119.0/24RADBValid
181.41.216.0/24RIPEValid
181.214.115.0/24RIPEValid
185.135.156.0/24RIPEValid
194.110.242.0/24RIPEValid
2a05:1e40::/29RIPEValid
2a06:4380::/29RIPEValid
2a09:a800::/29RIPEValid
2a09:bc00::/29RIPEValid
2a09:c700::/29RIPEValid
2a09:cf00::/29RIPEValid
2a09:e700::/29RIPEValid
2a0a:c0c0::/29RIPEValid
2a0c:72c0::/29RIPEValid
2a0c:9480::/29RIPEValid
2a0d:f840::/29RIPEValid
2a0e:5880::/29RIPEValid
2a0e:b200::/29RIPEValid
2a0e:c4c0::/29RIPEValid
2a11:6d00::/29RIPEValid
2a14:180::/48RIPENo 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.