Force Telecom

Data as of 2026-09-06
BGP inherited
This organisation
Netblocks8
IPv6 4 prefixes (largest 2001:12f8:0:13::158/128)
Also registered under this name 10 netblocks across 2 separate records
Record ID239851163
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
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 · report an issue

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.184.144.158/32 Force Telecom PEERINGDB ASSIGNED ● high
45.184.146.180/32 Force Telecom PEERINGDB ASSIGNED ● high
187.16.211.159/32 Force Telecom PEERINGDB ASSIGNED ● high
200.219.141.158/32 Force Telecom PEERINGDB ASSIGNED ● high
2001:12f8::211:159/128 Force Telecom PEERINGDB ASSIGNED ● high
2001:12f8:0:4::180/128 Force Telecom PEERINGDB ASSIGNED ● high
2001:12f8:0:5::158/128 Force Telecom PEERINGDB ASSIGNED ● high
2001:12f8:0:13::158/128 Force Telecom PEERINGDB ASSIGNED ● high

IPv6 ranges (4)

Footprint over time

8 weekly snapshots · JSON
8 0 netblocks since 2026-07-13
2026-07-13 peak 8 2026-09-06

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (8 of 8)
No discrepancies found among checked blocks.

NIC Handles

AS262411