Data as of Nov 14, 2026

178.16.208.0/20

20 residential-proxy exits · 30 days

Bredband2 Stockholms Stadsnaet AB

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
20
0.49% of its addresses · 30 days
Spread
11 of 16
/24s with at least one exit
Providers
15
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

334 observations

Proxy providers listing exits

  • AnyIP
  • BlurPath
  • CliProxy
  • FastProxy
  • IPFly
  • IPPeak
  • LemonBright
  • NovProxy
  • Proxiware
  • Proxy302
  • RainProxy
  • Shifter
  • ThunderProxy
  • VitalExclusive
  • ZENPROXY_PREMIUM

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
178.16.208.0/204,096SE-HPDC-20100309Bredband2 Stockholms Stadsnaet AB (ORG-HPDC1-RIPE) · SEALLOCATED PAMar 9, 2010abuse@bredband2.se
└ 178.16.208.0/24256SE-HPDC-FTTH-178-16-208Stockholm Stadsnat FTTHASSIGNED PAJan 16, 2020abuse@bredband2.se
via SE-HPDC-20100309
└ 178.16.209.0/24256SE-HPDC-FTTH-178-16-209Stockholm Stadsnat FTTHASSIGNED PAJan 16, 2020abuse@bredband2.se
via SE-HPDC-20100309
└ 178.16.210.0/24256SE-HPDC-FTTH-178-16-210Stockholm Stadsnat FTTHASSIGNED PAJan 16, 2020abuse@bredband2.se
via SE-HPDC-20100309
└ 178.16.211.0/24256SE-HPDC-FTTH-178-16-211Stockholm Stadsnat FTTHASSIGNED PAJan 16, 2020abuse@bredband2.se
via SE-HPDC-20100309
└ 178.16.212.0/24256SE-HPDC-FTTH-178-16-212Stockholm Stadsnat FTTHASSIGNED PAJan 16, 2020abuse@bredband2.se
via SE-HPDC-20100309
└ 178.16.213.0/24256SE-HPDC-FTTH-178-16-213Stockholm Stadsnat FTTHASSIGNED PAJan 16, 2020abuse@bredband2.se
via SE-HPDC-20100309
└ 178.16.214.0/24256SE-HPDC-FTTH-178-16-214Stockholm Stadsnat FTTHASSIGNED PAJan 16, 2020abuse@bredband2.se
via SE-HPDC-20100309
└ 178.16.215.0/24256SE-HPDC-FTTH-178-16-215Stockholm Stadsnat FTTHASSIGNED PAJan 16, 2020abuse@bredband2.se
via SE-HPDC-20100309
└ 178.16.216.0/24256SE-HPDC-FTTH-178-16-216Stockholm Stadsnat FTTHASSIGNED PAJan 16, 2020abuse@bredband2.se
via SE-HPDC-20100309
└ 178.16.217.0/24256SE-HPDC-FTTH-178-16-217Stockholm Stadsnat FTTHASSIGNED PAJan 16, 2020abuse@bredband2.se
via SE-HPDC-20100309
└ 178.16.218.0/24256SE-HPDC-FTTH-178-16-218Stockholm Stadsnat FTTHASSIGNED PAJan 16, 2020abuse@bredband2.se
via SE-HPDC-20100309
└ 178.16.219.0/24256SE-HPDC-FTTH-178-16-219Stockholm Stadsnat FTTHASSIGNED PAJan 16, 2020abuse@bredband2.se
via SE-HPDC-20100309
└ 178.16.220.0/24256SE-HPDC-FTTH-178-16-220Stockholm Stadsnat FTTHASSIGNED PAJan 16, 2020abuse@bredband2.se
via SE-HPDC-20100309
└ 178.16.221.0/24256SE-HPDC-FTTH-178-16-221Stockholm Stadsnat FTTHASSIGNED PAJan 16, 2020abuse@bredband2.se
via SE-HPDC-20100309
└ 178.16.222.0/24256SE-HPDC-FTTH-178-16-222Stockholm Stadsnat FTTHASSIGNED PAJan 16, 2020abuse@bredband2.se
via SE-HPDC-20100309
└ 178.16.223.0/24256SE-HPDC-FTTH-178-16-223Stockholm Stadsnat FTTHASSIGNED PAJan 16, 2020abuse@bredband2.se
via SE-HPDC-20100309

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Mar 2010
Current origin since
Oct 2018 · 8.1 yr
Origin networks
3
Last change of origin
Oct 2018
Recorded history

History

Handoffs
2