Stephen Fraser
Data as of 2026-08-16
BGP inherited
Cluster stats
| Netblocks | 15 · 266 IPv4 addresses |
| IPv6 | 11 prefixes (largest 2a14:a901::/40) |
| Registered in | United Kingdom (3) · United States (1) |
| Cluster ID | 222423445 |
| Registry | BGP |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 11 shared RIR contact/maintainer handles |
| Registry names | 6 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
Footprint over time
8 weekly snapshots · JSON
16
0 netblocks since 2026-07-05
2026-07-05
peak 16
2026-08-16
IP Ranges (15)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 44.31.86.0/24 | Stephen Fraser | BGP | ANNOUNCED | ● high |
| 91.198.241.247/32 | Stephen Fraser | PEERINGDB | ASSIGNED | ● high |
| 2001:67c:2f68::/48 | Stephen Fraser | BGP | ANNOUNCED | ● high |
| 2001:7f8:ca:1:0:20:7748:1/128 | Stephen Fraser | PEERINGDB | ASSIGNED | ● high |
| 2a0c:2f07:ffff::25f2/128 | Stephen Fraser | PEERINGDB | ASSIGNED | ● high |
| 2a0e:8f01:1000:10::13d/128 | Stephen Fraser | PEERINGDB | ASSIGNED | ● high |
| 2a14:a901::/40 | Stephen Fraser | BGP | ANNOUNCED | ● high |
| 2a14:a901::/44 | Stephen Fraser | BGP | ANNOUNCED | ● high |
| 2a14:a901::/48 | Stephen Fraser | BGP | ANNOUNCED | ● high |
| 2a14:a901:1::/48 | Stephen Fraser | BGP | ANNOUNCED | ● high |
| 81.187.19.194/32 | STEPHEN-TAN | RIPE | ASSIGNED PA | ● low |
| 194.74.237.16/29 | STEPHEN-A | RIPE | ASSIGNED PA | ● low |
| 2a00:2381:207f::/48 | STEPHEN-HAY | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a00:2381:e258::/48 | STEPHEN-A | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a00:2381:e258::/56 | STEPHEN-A | RIPE | ASSIGNED | ● low |
IPv6 ranges (11)
Network trust
what's this?
RPKI hygiene: B
how networks compare →
87.5%
of checked blocks have valid RPKI ROA coverage
(14 of 16)
Possible discrepancies (3)
These blocks are registered to Stephen Fraser 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.
| 2a00:2381:e258::/48 /48 | authorized for AS2856 — British Telecommunications Limited |
| 2a00:2381:207f::/48 /48 | authorized for AS2856 — British Telecommunications Limited |
| 2a00:2381:e258::/56 /56 | authorized for AS2856 — British Telecommunications Limited |
NIC Handles
AA
AS207748
AS207748
BTNET-MNT
DUMY-RIPE
DUMY-RIPE
ORG-TA1405-RIPE
RIPE-NCC-END-MNT
SF11398-MNT
SF11398-MNT
lir-uk-jim-1-MNT