TDC-SVERIGE-OVERVAKNING-NET

Data as of 2026-09-20
BGP inherited
This organisation
Netblocks7
IPv6 1 prefix (largest 2001:6f0:3c04::/48)
Also registered under this name 83 netblocks across 12 separate records
Record ID240890256
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 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
31.15.32.128/27 TDC-SVERIGE-AB-OVERVAKNING-NET RIPE ASSIGNED PA ● low
31.15.38.48/28 TDC-SVERIGE-OVERVAKNING-NET RIPE ASSIGNED PA ● low
31.15.38.128/28 TDC-SVERIGE-OVERVAKNING-NET RIPE ASSIGNED PA ● low
31.15.55.176/28 TDC-SVERIGE-OVERVAKNING-NET RIPE ASSIGNED PA ● low
62.95.2.208/28 TDC-SVERIGE-OVERVAKNING-NET RIPE ASSIGNED PA ● low
212.214.152.24/29 TDC-SVERIGE-OVERVAKNING-NET RIPE ASSIGNED PA ● low
2001:6f0:3c04::/48 TDC-SVERIGE-OVERVAKNING-NET RIPE ASSIGNED ● low

IPv6 ranges (1)

Footprint over time

13 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-09-20

Network trust

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

NIC Handles

DUMY-RIPE DUMY-RIPE TDC-SE-MNT