fOxO Internet Service Provider

Data as of 2026-07-26
BGP inherited
Cluster stats
Netblocks8
IPv6 6 prefixes (largest 2a0e:b107:1a30::/48)
Cluster ID214591732
RegistryPEERINGDB
Customersfind 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 · report an issue

Footprint over time

6 weekly snapshots · JSON
8 -21 netblocks since 2026-07-05
2026-07-05 peak 29 2026-07-26

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
103.158.187.119/32 fOxO Internet Service Provider PEERINGDB ASSIGNED ● high
203.163.223.73/32 fOxO Internet Service Provider PEERINGDB ASSIGNED ● high
2404:f4c0:f70e:1980::208:223/128 fOxO Internet Service Provider PEERINGDB ASSIGNED ● high
2406:d400:1:133:203:163:223:73/128 fOxO Internet Service Provider PEERINGDB ASSIGNED ● high
2602:f92a:1315:2::10/128 fOxO Internet Service Provider PEERINGDB ASSIGNED ● high
2a0f:5707:ffe3::119/128 fOxO Internet Service Provider PEERINGDB ASSIGNED ● high
2a0f:7803:fc60:aaaa::2082:23/128 fOxO Internet Service Provider PEERINGDB ASSIGNED ● high
2a0e:b107:1a30::/48 fOxO-internet-ipv6 RIPE ASSIGNED ● low

IPv6 ranges (6)

Network trust

what's this?
RPKI hygiene: C how networks compare →
75.0% of checked blocks have valid RPKI ROA coverage (6 of 8)
Possible discrepancies (1)

These blocks are registered to fOxO Internet Service Provider 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.

2a0e:b107:1a30::/48 /48 authorized for AS208223 — SHU-HAO TUNG

NIC Handles

AS208223 DUMY-RIPE DUMY-RIPE o123ojp-MNT