SEEWEB-BACKBONE

Data as of 2026-09-13
BGP inherited
This organisation
Netblocks6 · 704 IPv4 addresses
Record ID242179619
RegistryRIPE
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
85.94.192.0/25 SEEWEB-BACKBONE RIPE ASSIGNED PA ● low
85.94.206.0/25 SEEWEB-BACKBONE RIPE ASSIGNED PA ● low
85.94.223.0/25 SEEWEB-BACKBONE RIPE ASSIGNED PA ● low
95.174.9.64/26 SEEWEB-BACKBONE RIPE ASSIGNED PA ● low
217.168.224.0/25 SEEWEB-BACKBONE RIPE ASSIGNED PA ● low
217.168.226.0/25 SEEWEB-BACKBONE RIPE ASSIGNED PA ● low

Footprint over time

9 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-09-06

Network trust

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

NIC Handles

DUMY-RIPE DUMY-RIPE SEEWEB-MNT