FERMORITE

Handle
Cluster stats
Netblocks6
Registered in Bulgaria (2) · Greece (1)
All fragments 19 blocks across 6 clusters
Cluster ID208805032
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution RIR handle
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

3 weekly snapshots · JSON
6 0 netblocks since 2026-07-12
2026-07-12 peak 6 2026-07-19

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
176.126.38.89/32 FERMORITE PEERINGDB ASSIGNED ● high
185.0.28.24/32 FERMORITE PEERINGDB ASSIGNED ● high
185.1.226.86/32 FERMORITE PEERINGDB ASSIGNED ● high
2001:67c:29f0::20:7767:1/128 FERMORITE PEERINGDB ASSIGNED ● high
2001:7f8:6e::89/128 FERMORITE PEERINGDB ASSIGNED ● high
2001:7f8:148::20:7767:1/128 FERMORITE PEERINGDB ASSIGNED ● high

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “FERMORITE” — 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.
  • Services 1 via FERMORITE Systems, Applications and Services on IT and Technology IKE sub-allocation
  • Services 2 via FERMORITE Systems, Applications and Services on IT and Technology IKE sub-allocation
  • Services 3 via FERMORITE Systems, Applications and Services on IT and Technology IKE sub-allocation
  • Services 4 via FERMORITE Systems, Applications and Services on IT and Technology IKE sub-allocation

Network trust

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

NIC Handles

AS207767