YELLOWPAGES

BGP inherited

Cluster stats

Netblocks	7
All fragments	8 blocks across 2 clusters
Cluster ID	208834596
Registry	RIPE
Customers	find customers using this network →

Evidence & provenance ?

Attribution	BGP parent (inherited)
Shared handles	clustered on 4 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

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
194.90.151.32/27	NV-YELLOWPAGES	RIPE	ASSIGNED PA	● low
212.117.156.32/28	YELLOWPAGES	RIPE	ASSIGNED PA	● low
212.117.156.48/28	YELLOWPAGES	RIPE	ASSIGNED PA	● low
212.117.156.64/28	YELLOWPAGES	RIPE	ASSIGNED PA	● low
212.117.156.80/28	YELLOWPAGES	RIPE	ASSIGNED PA	● low
212.199.96.160/27	YELLOWPAGES	RIPE	ASSIGNED PA	● low
212.235.110.4/30	NV-YELLOWPAGES	RIPE	ASSIGNED PA	● low

Possibly related to this organisation

what's this?

Same name family

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

YELLOWPAGES-LAN 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.

YELLOWPAGES-LAN via PJSC MegaFon sub-allocation
Yellow Pages via Drustvo za telekomunikacije Orion telekom doo Beograd-Zemun sub-allocation
SUZHOU-YELLOWPAGES-INFO-CORP via No.31,Jin-rong Street 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

AS9116-MNT DUMY-RIPE DUMY-RIPE NV-MNT-RIPE