NET-US-BOEHRINGER-INGELHEIM
BGP inherited
Cluster stats
| Netblocks | 12 |
| All fragments | 16 blocks across 3 clusters |
| Cluster ID | 205778668 |
| 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 | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
4 weekly snapshots · JSON
12
0 netblocks since 2026-07-05
2026-07-05
peak 12
2026-07-13
IP Ranges (12)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 46.248.142.120/29 | NET-US-BOEHRINGER-INGELHEIM | RIPE | ASSIGNED PA | ● low |
| 46.248.142.144/28 | NET-US-BOEHRINGER-INGELHEIM | RIPE | ASSIGNED PA | ● low |
| 46.248.142.208/29 | NET-US-Boehringer-Ingelheim | RIPE | ASSIGNED PA | ● low |
| 46.248.142.232/29 | NET-US-BOEHRINGER-INGELHEIM | RIPE | ASSIGNED PA | ● low |
| 46.248.156.8/29 | NET-US-Boehringer-Ingelheim | RIPE | ASSIGNED PA | ● low |
| 46.248.156.24/29 | NET-US-Boehringer-Ingelheim | RIPE | ASSIGNED PA | ● low |
| 2001:924:1:1200::/56 | NET-US-BOEHRINGER-INGELHEIM | RIPE | ASSIGNED | ● low |
| 2001:924:1:1400::/56 | NET-US-BOEHRINGER-INGELHEIM | RIPE | ASSIGNED | ● low |
| 2001:924:1:1600::/56 | NET-US-Boehringer-Ingelheim | RIPE | ASSIGNED | ● low |
| 2001:924:1:1700::/56 | NET-US-Boehringer-Ingelheim | RIPE | ASSIGNED | ● low |
| 2001:924:1:1800::/56 | NET-US-Boehringer-Ingelheim | RIPE | ASSIGNED | ● low |
| 2001:924:20:900::/56 | NET-US-BOEHRINGER-INGELHEIM | RIPE | ASSIGNED | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “NET US BOEHRINGER INGELHEIM” — 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.
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.
- Boehringer Ingelheim Rcv Gmbh via GTS Telecom SRL sub-allocation
- TNSE-CUST-BOEHRINGER-INGELHEIM-AB via Telenor Norge AS sub-allocation
- Boehringer Ingelheim International Gmbh Norway via GLOBALCONNECT AS sub-allocation
- Boehringer Ingelheim International Gmbh via GLOBALCONNECT AS sub-allocation
- Boehringer Ingelheim Animal Health Italia Spa via COLT Technology Services Group Limited sub-allocation
- BOEHRINGER-INGELHEIM-ANIMAL-HEALTH_J8023-00001-002 via Societe Francaise Du Radiotelephone - SFR SA sub-allocation
- BOEHRINGERINGELHEIMFINLAND-210514 via DNA Oyj sub-allocation
- Boehringer Ingelheim Animal Health via COLT Technology Services Group Limited sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(12 of 12)
Possible discrepancies (6)
These blocks are registered to NET-US-BOEHRINGER-INGELHEIM 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:924:1:1200::/56 /56 | authorized for AS8220 — COLT Technology Services Group Limited |
| 2001:924:1:1400::/56 /56 | authorized for AS8220 — COLT Technology Services Group Limited |
| 2001:924:1:1600::/56 /56 | authorized for AS8220 — COLT Technology Services Group Limited |
| 2001:924:20:900::/56 /56 | authorized for AS8220 — COLT Technology Services Group Limited |
| 2001:924:1:1700::/56 /56 | authorized for AS8220 — COLT Technology Services Group Limited |
| 2001:924:1:1800::/56 /56 | authorized for AS8220 — COLT Technology Services Group Limited |
NIC Handles
COLT-MNT
DUMY-RIPE
DUMY-RIPE