Alexander Samoylyk

Data as of 2026-08-16
BGP inherited
Cluster stats
Netblocks5
IPv6 4 prefixes (largest 2001:67c:dac::/48)
Cluster ID222457846
RegistryBGP
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 8 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

Footprint over time

2 weekly snapshots · JSON
6 0 netblocks since 2026-08-09
2026-08-09 peak 6 2026-08-16

IP Ranges (5)

⬇ export CSV
CIDR Org name Registry Status Confidence
185.1.59.183/32 Alexander Samoylyk PEERINGDB ASSIGNED ● high
2001:67c:dac::/48 Alexander Samoylyk BGP ANNOUNCED ● high
2001:7f8:ca:1:0:20:605:1/128 Alexander Samoylyk PEERINGDB ASSIGNED ● high
2001:7f8:cc:333::183/128 Alexander Samoylyk PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:54::10d/128 Alexander Samoylyk PEERINGDB ASSIGNED ● high

IPv6 ranges (4)

CIDR
2001:67c:dac::/48
2001:7f8:ca:1:0:20:605:1/128
2001:7f8:cc:333::183/128
2a0e:8f01:1000:54::10d/128

Network trust

what's this?
RPKI hygiene: B how networks compare →
83.3% of checked blocks have valid RPKI ROA coverage (5 of 6)
No discrepancies found among checked blocks.

NIC Handles

AS200605 AS200605 DUMY-RIPE DUMY-RIPE ORG-AS1020-RIPE RIPE-NCC-END-MNT SAMOYLYK-MNT SAMOYLYK-MNT