GoForceX Network
BGP inherited
Cluster stats
| Netblocks | 7 |
| All fragments | 12 blocks across 6 clusters |
| Cluster ID | 191691568 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
2 weekly snapshots · JSON
7
0 netblocks since 2026-07-05
2026-07-05
peak 7
2026-07-06
IP Ranges (7)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 149.112.50.121/32 | GoForceX Network | PEERINGDB | ASSIGNED | ● high |
| 2001:504:125:e1::179/128 | GoForceX Network | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:ca:1:0:21:3782:1/128 | GoForceX Network | PEERINGDB | ASSIGNED | ● high |
| 2406:840:1f:1000:0:21:3782:1/128 | GoForceX Network | PEERINGDB | ASSIGNED | ● high |
| 2a0e:8f01:1000:9::105/128 | GoForceX Network | PEERINGDB | ASSIGNED | ● high |
| 2a0f:85c1:363:1:21:3782:0:1/128 | GoForceX Network | PEERINGDB | ASSIGNED | ● high |
| 2a14:67c1:71::/48 | GoForceX-USA | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
57.1%
of checked blocks have valid RPKI ROA coverage
(4 of 7)
Possible discrepancies (1)
These blocks are registered to GoForceX Network but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 2a14:67c1:71::/48 /48 | authorized for AS213782 — Chang Xin |
NIC Handles
AS213782
DUMY-RIPE
DUMY-RIPE
GOFORCEX-MNT