MEEZA-18883
Data as of 2026-07-26
BGP inherited
Limited data: only 2 ranges found registered
under this exact name. This may not reflect the organisation's full internet footprint — many companies'
web and cloud infrastructure is hosted under a third-party provider's own registration rather than their own.
Cluster stats
| Netblocks | 2 |
| IPv6 | 1 prefix (largest 2001:1a11:12::/48) |
| Cluster ID | 213492167 |
| 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 | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 78.100.37.104/29 | MEEZA-18883 | RIPE | ASSIGNED PA | ● low |
| 2001:1a11:12::/48 | MEEZA-18883 | RIPE | ASSIGNED | ● low |
IPv6 ranges (1)
| CIDR |
|---|
| 2001:1a11:12::/48 |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(2 of 2)
Possible discrepancies (1)
These blocks are registered to MEEZA-18883 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.
| 2001:1a11:12::/48 /48 | authorized for AS42298 — Ooredoo Q.S.C. |
NIC Handles
DUMY-RIPE
DUMY-RIPE
QTEL-NOC
Qtel-NOC