SK-VERIZON-BA

BGP inherited
Cluster stats
Netblocks8
All fragments 24 blocks across 12 clusters
Cluster ID210282000
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
85.248.11.208/28 SK-VERIZON-BA RIPE ASSIGNED PA ● low
85.248.48.16/28 SK-VERIZON-BA RIPE ASSIGNED PA ● low
195.168.39.8/29 SK-VERIZON-BA RIPE ASSIGNED PA ● low
195.168.54.32/29 SK-VERIZON-BA RIPE ASSIGNED PA ● low
195.168.102.56/29 SK-VERIZON-BA RIPE ASSIGNED PA ● low
195.168.126.88/29 SK-VERIZON-BA RIPE ASSIGNED PA ● low
195.168.178.112/29 SK-VERIZON-BA RIPE ASSIGNED PA ● low
2a00:1298:802c::/48 SK-VERIZON-BA RIPE ASSIGNED ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “SK VERIZON” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
Combined view of all 12 name-family clusters →
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (8 of 8)
Possible discrepancies (1)

These blocks are registered to SK-VERIZON-BA but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

2a00:1298:802c::/48 /48 authorized for AS5578 — SWAN, a.s.

NIC Handles

DUMY-RIPE DUMY-RIPE SWAN-MNT