Jeremy Utley

Data as of 2026-08-30
BGP inherited
Cluster stats
Netblocks12 · 281 IPv4 addresses
IPv6 8 prefixes (largest 2a05:dfc1:9800::/40)
Registered in United Kingdom (3) · United States (1)
Cluster ID231505203
RegistryBGP
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 10 shared RIR contact/maintainer handles
Registry names 5 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

Footprint over time

10 weekly snapshots · JSON
12 0 netblocks since 2026-07-05
2026-07-05 peak 12 2026-08-30

IP Ranges (12)

⬇ export CSV
CIDR Org name Registry Status Confidence
44.30.42.0/24 Jeremy Utley BGP ANNOUNCED ● high
2001:7f8:ca:1:0:21:6242:1/128 Jeremy Utley PEERINGDB ASSIGNED ● high
2602:fa3d:f4:1::b/128 Jeremy Utley PEERINGDB ASSIGNED ● high
2a05:dfc1:9800::/40 Jeremy Utley RIPE ALLOCATED-BY-LIR ● high
2a05:dfc1:9800::/42 Jeremy Utley BGP ANNOUNCED ● high
2a05:dfc1:9840::/42 Jeremy Utley BGP ANNOUNCED ● high
2a05:dfc1:9880::/42 Jeremy Utley BGP ANNOUNCED ● high
2a05:dfc1:98c0::/42 Jeremy Utley BGP ANNOUNCED ● high
81.2.69.144/28 JEREMY-GOW RIPE ASSIGNED PA ● low
81.2.81.99/32 JEREMY-GOW RIPE ASSIGNED PA ● low
81.2.108.24/29 JEREMY-GOW RIPE ASSIGNED PA ● low
2a00:2381:c60e::/48 JEREMY-C RIPE AGGREGATED-BY-LIR ● low

IPv6 ranges (8)

Network trust

what's this?
RPKI hygiene: B how networks compare →
83.3% of checked blocks have valid RPKI ROA coverage (10 of 12)
Possible discrepancies (1)

These blocks are registered to Jeremy Utley 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:c60e::/48 /48 authorized for AS2856 — British Telecommunications Limited

NIC Handles

AA AS216242 AS216242 BTNET-MNT CLOUDIE-MNT DUMY-RIPE DUMY-RIPE JUTLEY-MNT JUTLEY-MNT ORG-JU17-RIPE