CHG-MERIDIAN AG
Data as of 2026-07-26
GLEIF verified
LEI
529900MC9FIFMI13BR64
Registered name
CHG-MERIDIAN AG
Jurisdiction
Ultimate parent
No parent on file in GLEIF
Cluster stats
| Netblocks | 14 · 320 IPv4 addresses |
| IPv6 | 6 prefixes (largest 2003:69:a017::/48) |
| Cluster ID | 213374913 |
| Registry | BGP |
| Owner jurisdiction | DE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | GLEIF legal-entity match |
| Legal identity | LEI 529900MC9FIFMI13BR64 |
| Shared handles | clustered on 8 shared RIR contact/maintainer handles |
| Registry names | 8 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
Footprint over time
6 weekly snapshots · JSON
15
-1 netblocks since 2026-07-05
2026-07-05
peak 16
2026-07-26
IP Ranges (14)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 185.107.239.0/24 | CHG-MERIDIAN AG | BGP | ANNOUNCED | ● high |
| 62.157.143.176/28 | CHG-MERIDIAN-WEINGARTEN-NET | RIPE | ASSIGNED PA | ● low |
| 80.155.60.128/29 | CHG-MERIDIAN-HAMBURG-NET | RIPE | ASSIGNED PA | ● low |
| 80.155.189.0/29 | CHG-MERIDIAN-BIELEFELD-NET | RIPE | ASSIGNED PA | ● low |
| 87.130.82.24/29 | CHG-MERIDIAN-STUTTGART-NET | RIPE | ASSIGNED PA | ● low |
| 93.241.10.168/29 | CHG-MERIDIAN-BERLIN-NET | RIPE | ASSIGNED PA | ● low |
| 93.241.18.232/29 | CHG-MERIDIAN-MUENCHEN-NET | RIPE | ASSIGNED PA | ● low |
| 217.5.155.160/29 | CHG-MERIDIAN-WEINGARTEN-NET | RIPE | ASSIGNED PA | ● low |
| 2003:69:a017::/48 | CHG-MERIDIAN-WEINGARTEN-NET | RIPE | ASSIGNED | ● low |
| 2003:c9:403c::/48 | CHG-MERIDIAN-HAMBURG-NET | RIPE | ASSIGNED | ● low |
| 2003:ec:a01e::/48 | CHG-MERIDIAN-STUTTGART-NET | RIPE | ASSIGNED | ● low |
| 2003:ee:5019::/48 | CHG-MERIDIAN-BERLIN-NET | RIPE | ASSIGNED | ● low |
| 2003:ee:a821::/48 | CHG-MERIDIAN-MUENCHEN-NET | RIPE | ASSIGNED | ● low |
| 2003:f2:9843::/48 | CHG-MERIDIAN-BIELEFELD-NET | RIPE | ASSIGNED | ● low |
IPv6 ranges (6)
Network trust
what's this?
RPKI hygiene: B
how networks compare →
86.7%
of checked blocks have valid RPKI ROA coverage
(13 of 15)
Possible discrepancies (6)
These blocks are registered to CHG-MERIDIAN AG 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.
| 2003:69:a017::/48 /48 | authorized for AS3320 — Deutsche Telekom AG |
| 2003:c9:403c::/48 /48 | authorized for AS3320 — Deutsche Telekom AG |
| 2003:ee:5019::/48 /48 | authorized for AS3320 — Deutsche Telekom AG |
| 2003:ee:a821::/48 /48 | authorized for AS3320 — Deutsche Telekom AG |
| 2003:ec:a01e::/48 /48 | authorized for AS3320 — Deutsche Telekom AG |
| 2003:f2:9843::/48 /48 | authorized for AS3320 — Deutsche Telekom AG |
NIC Handles
AS211897
DTAG-NIC
DUMY-RIPE
DUMY-RIPE
ORG-CA2113-RIPE
RIPE-NCC-HM-MNT
mnt-de-chg-meridian-1
mnt-de-chg-meridian-1