MVA Connect

BGP inherited

Cluster stats

Netblocks	4
Cluster ID	207730538
Registry	PEERINGDB
Customers	find customers using this network →

Evidence & provenance ?

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

IP Ranges (4)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
193.201.28.196/32	MVA Connect	PEERINGDB	ASSIGNED	● high
217.29.67.229/32	MVA Connect	PEERINGDB	ASSIGNED	● high
2001:7f8:b:100:1d1:a520:2803:229/128	MVA Connect	PEERINGDB	ASSIGNED	● high
2001:7f8:10::20:2803/128	MVA Connect	PEERINGDB	ASSIGNED	● high

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.

WARWICKNET-HRI-MAINTENANCECONNECTION via Glide Student & Residential Limited sub-allocation
CONNECTCOM1-NET via Sunrise GmbH sub-allocation
PROCONNECT via Vancis IP B.V. sub-allocation
World-Connection-Ali-Motaz via T-Mobile Austria GmbH sub-allocation
INTERCONNECT-KOSTROMA via Svyaz-Energo Ltd. sub-allocation
MYSMART-CONNECT-NET2 via MK Netzdienste Verwaltungs GmbH trading as MK Netzdienste GmbH & Co. KG sub-allocation
Connect Nett via T-Mobile Czech Republic a.s. sub-allocation
ADCONNECTION-20101125 via Syntura Group Limited sub-allocation

what's this?

RPKI hygiene: A how networks compare →

100.0% of checked blocks have valid RPKI ROA coverage (4 of 4)

No discrepancies found among checked blocks.

AS202803