GEORG-FISCHER-LEIPZIG-NET
BGP inherited
Cluster stats
| Netblocks | 4 |
| All fragments | 26 blocks across 8 clusters |
| Cluster ID | 205521949 |
| 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 (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 87.129.56.104/29 | GEORG-FISCHER-LEIPZIG-NET | RIPE | ASSIGNED PA | ● low |
| 91.25.165.160/29 | GEORG-FISCHER-LEIPZIG-NET | RIPE | ASSIGNED PA | ● low |
| 2003:c1:6032::/48 | GEORG-FISCHER-LEIPZIG-NET | RIPE | ASSIGNED | ● low |
| 2003:e9:301d::/48 | GEORG-FISCHER-LEIPZIG-NET | RIPE | ASSIGNED | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “GEORG FISCHER” — 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.
- GEORG-FISCHER-ALBERSHAUSEN-NET 6 blocks
- GEORG-FISCHER-NEUBURG-AN-DER-DONAU-NET 4 blocks
- GEORG-FISCHER-ETTENHEIM-NET 4 blocks
- GEORG-FISCHER-NET 2 blocks
- GEORG-FISCHER-HANNOVER-NET 2 blocks
- GEORG-FISCHER-PIPNG-SYSTEMS-ALBERTSHAUSEN_NET 2 blocks
- GEORG-FISCHER-SCHORNDORF-NET 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.
- GEORGFISCHER-RASZYN via Netia SA sub-allocation
- Georg Fischer Sas via COLT Technology Services Group Limited sub-allocation
- GEORGFISCHERSPA via Vianova S.p.A sub-allocation
- GEORGFISCHERTPASRL via Vianova S.p.A sub-allocation
- GEORGEFISCHER via Brightsolid Online Technology Ltd sub-allocation
- FISCHERGEORG-HWY-AT via A1 Telekom Austria AG sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(4 of 4)
No discrepancies found among checked blocks.
NIC Handles
DTAG-NIC
DUMY-RIPE
DUMY-RIPE