fux eG
fux-viktoria-intern
BGP inherited
Cluster stats
| Netblocks | 1 · 511 IPv4 addresses |
| All fragments | 3 blocks across 3 clusters |
| Cluster ID | 205911138 |
| 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 | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (1)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 185.161.128.0/23 | fux-viktoria-intern | RIPE | ASSIGNED PA | ● medium |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “fux viktoria” — 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.
- fux-viktoria-legacy 1 blocks
- fux-viktoria 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.
- VIKTORIA-BONAREVA via Nova Telecommunications & Media Single Member S.A sub-allocation
- SKVIKTORIA via JSC Kazakhtelecom sub-allocation
- Mistura-Sarah-Viktoria via T-Mobile Austria GmbH sub-allocation
- Alpenresidenz-Viktoria-GmbH via T-Mobile Austria GmbH sub-allocation
- Viktoria Tian via JSC Kazakhtelecom sub-allocation
- FCVIKTORIA-1 sub-allocation
- FVIKTORIA-1 sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(1 of 1)
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
de-fux-1-mnt