Fiberway

Registry
Cluster stats
Netblocks7
All fragments 22 blocks across 3 clusters
Cluster ID213183192
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-19

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
89.46.144.140/32 Fiberway PEERINGDB ASSIGNED ● high
93.159.151.17/32 Fiberway PEERINGDB ASSIGNED ● high
178.216.40.122/32 Fiberway PEERINGDB ASSIGNED ● high
195.182.218.192/32 Fiberway PEERINGDB ASSIGNED ● high
2001:678:3ac::140/128 Fiberway PEERINGDB ASSIGNED ● high
2001:7f8:42::a505:1399:1/128 Fiberway PEERINGDB ASSIGNED ● high
2001:7f8:5b::122/128 Fiberway PEERINGDB ASSIGNED ● high

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “Fiberway” — 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.
  • Nat4 via Fiberway Sp. z o.o. sub-allocation

Network trust

what's this?
RPKI hygiene: B how networks compare →
85.7% of checked blocks have valid RPKI ROA coverage (6 of 7)
No discrepancies found among checked blocks.

NIC Handles

AS51399