SPB-BELFAST

Data as of 2026-10-04
BGP inherited
This organisation
Netblocks6
IPv6 1 prefix (largest 2a00:2381:108e::/48)
Record ID245646961
RegistryRIPE
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.252.176.144/29 SPB-BELFAST RIPE ASSIGNED PA ● low
194.168.226.0/26 SPB-BELFAST-LIMITED RIPE ASSIGNED PA ● low
194.168.243.236/30 SPB-BELFAST-LIMITED RIPE ASSIGNED PA ● low
212.250.191.64/26 SPB-BELFAST RIPE ASSIGNED PA ● low
213.81.84.80/29 SPB-BELFAST-LTD RIPE ASSIGNED PA ● low
2a00:2381:108e::/48 SPB-BELFAST RIPE AGGREGATED-BY-LIR ● low

IPv6 ranges (1)

Footprint over time

15 weekly snapshots · JSON
6 -1 netblocks since 2026-07-05
2026-07-05 peak 7 2026-10-04

Network trust

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

These blocks are registered to SPB-BELFAST 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:108e::/48 /48 authorized for AS2856 — British Telecommunications Limited

NIC Handles

AS5089-MNT BTNET-MNT DUMY-RIPE DUMY-RIPE