WOIPPY
BGP inherited
Cluster stats
| Netblocks | 6 · 1,530 IPv4 addresses |
| All fragments | 8 blocks across 2 clusters |
| Cluster ID | 210186356 |
| 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 | |
Footprint over time
5 weekly snapshots · JSON
6
0 netblocks since 2026-07-05
2026-07-05
peak 6
2026-07-19
IP Ranges (6)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 185.55.245.0/24 | WOIPPY | RIPE | ASSIGNED PA | ● low |
| 185.55.246.0/24 | WOIPPY | RIPE | ASSIGNED PA | ● low |
| 185.55.247.0/24 | WOIPPY | RIPE | ASSIGNED PA | ● low |
| 185.173.201.0/24 | WOIPPY | RIPE | ASSIGNED PA | ● low |
| 185.173.202.0/24 | WOIPPY | RIPE | ASSIGNED PA | ● low |
| 185.173.203.0/24 | WOIPPY | RIPE | ASSIGNED PA | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “WOIPPY” — 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.
- WOIPPY-CPE 2 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.
- JORDAN-FRANCE-WOIPPY via Societe Francaise Du Radiotelephone - SFR SA sub-allocation
- TUBEST-BATIMENT-WOIPPY via Societe Francaise Du Radiotelephone - SFR SA sub-allocation
- COMMUNE-DE-WOIPPY_I1515-00002-002 via Societe Francaise Du Radiotelephone - SFR SA sub-allocation
- COMMUNE_DE_WOIPPY_I1515-00004-002 via Societe Francaise Du Radiotelephone - SFR SA sub-allocation
- Jean Charles Woippy via Societe Francaise Du Radiotelephone - SFR SA sub-allocation
- Woippy via INGECAP SARL sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(6 of 6)
RPKI-inferred operator
Vialis SEM
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
HOMBOURG-MNT
VIALIS-MNT