Leo Shum

BGP inherited

Cluster stats

Netblocks	9
Cluster ID	211665057
Registry	BGP
Customers	find customers using this network →

Evidence & provenance ?

Attribution	BGP parent (inherited)
Shared handles	clustered on 8 shared RIR contact/maintainer handles
Registry names	2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON

9 0 netblocks since 2026-07-05

2026-07-05 peak 9 2026-07-19

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
2602:f992:f4::/48	Leo Shum	BGP	ANNOUNCED	● high
2a06:9f81:5506::/47	Leo Shum	BGP	ANNOUNCED	● high
2a0e:97c0:730::/48	Leo Shum	BGP	ANNOUNCED	● high
2a0e:97c0:738::/48	Leo Shum	BGP	ANNOUNCED	● high
2a0e:97c0:738::/45	Leo Shum	BGP	ANNOUNCED	● high
2a0e:97c0:73a::/47	Leo Shum	BGP	ANNOUNCED	● high
2a0e:b107:9fe::/48	Leo Shum	BGP	ANNOUNCED	● high
2a06:9f81:5500::/40	Leo Shum	RIPE	ALLOCATED-BY-LIR	● medium
2a0e:97c0:730::/44	Leo Shum	RIPE	ALLOCATED-BY-LIR	● low

what's this?

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.

Liushuming Corp via CNCGROUP IP network of ShangHai IDC sub-allocation
SHUMEIKO via MTS PJSC sub-allocation
NSUK-FOCUSHUMANITARIAN-AD via Claranet Limited sub-allocation
ORBITEL-SHUMEN-1 via A1 Bulgaria EAD sub-allocation
SHUMEJKO sub-allocation
UNI-SHUMEN-47 via Bulgarian Research and Education Network Association (BREN) sub-allocation
NVU-SHUMEN-51 via Bulgarian Research and Education Network Association (BREN) sub-allocation
POL-SHUMNYI-NET via PJSC Rostelecom sub-allocation

what's this?

RPKI hygiene: B how networks compare →

88.9% of checked blocks have valid RPKI ROA coverage (8 of 9)

No discrepancies found among checked blocks.

AS208699 CLOUDIE-MNT DUMY-RIPE DUMY-RIPE ORG-PN139-RIPE SBMT parsns-mnt parsns-mnt