INTERGAZ

BGP inherited

Cluster stats

Netblocks	7
All fragments	8 blocks across 2 clusters
Cluster ID	210902897
Registry	RIPE
Customers	find 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

7 0 netblocks since 2026-07-05

2026-07-05 peak 7 2026-07-19

IP Ranges (7)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
89.218.141.152/30	INTERGAZ	RIPE	ASSIGNED PA	● low
92.47.110.192/30	INTERGAZ	RIPE	ASSIGNED PA	● low
92.47.110.204/30	INTERGAZ	RIPE	ASSIGNED PA	● low
95.59.7.208/30	INTERGAZ	RIPE	ASSIGNED PA	● low
95.59.71.248/30	INTERGAZ	RIPE	ASSIGNED PA	● low
178.89.104.244/30	INTERGAZ	RIPE	ASSIGNED PA	● low
178.90.39.156/30	INTERGAZ	RIPE	ASSIGNED PA	● low

Possibly related to this organisation

what's this?

Same name family

Separately-registered clusters whose names share “INTERGAZ” — 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.

INTERGAZ_KST 1 blocks

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.

INTERGAZESPOLSRO via O2 Czech Republic, a.s. sub-allocation
INTERGAZSERVIS-MINSK via Republican Unitary Telecommunication Enterprise Beltelecom sub-allocation
APOLLO-INTERGAZ-SIA via SIA Tet sub-allocation
INTERGAZ_KST via JSC Kazakhtelecom sub-allocation

Network trust

what's this?

RPKI hygiene: A how networks compare →

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

No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE KNIC-MNT