GetaFIX.ph Route Servers
Cluster stats
| Netblocks | 12 |
| All fragments | 22 blocks across 2 clusters |
| Cluster ID | 193385398 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| 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 | |
IP Ranges (12)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 103.104.19.1/32 | GetaFIX.ph Route Servers | PEERINGDB | ASSIGNED | ● high |
| 103.104.19.2/32 | GetaFIX.ph Route Servers | PEERINGDB | ASSIGNED | ● high |
| 103.125.245.1/32 | GetaFIX.ph Route Servers | PEERINGDB | ASSIGNED | ● high |
| 103.125.245.2/32 | GetaFIX.ph Route Servers | PEERINGDB | ASSIGNED | ● high |
| 116.89.244.1/32 | GetaFIX.ph Route Servers | PEERINGDB | ASSIGNED | ● high |
| 116.89.244.2/32 | GetaFIX.ph Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2401:fdc0::2:3942:1/128 | GetaFIX.ph Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2401:fdc0::2:3942:2/128 | GetaFIX.ph Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2401:fdc0:0:1:0:2:3942:1/128 | GetaFIX.ph Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2401:fdc0:0:1:0:2:3942:2/128 | GetaFIX.ph Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2401:fdc0:0:2:0:2:3942:1/128 | GetaFIX.ph Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2401:fdc0:0:2:0:2:3942:2/128 | GetaFIX.ph Route Servers | PEERINGDB | ASSIGNED | ● high |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(12 of 12)
No discrepancies found among checked blocks.
NIC Handles
AS23942