Data as of Nov 14, 2026

185.13.124.0/22

5 residential-proxy exits · 30 days

Svorka AS

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

Residential-proxy exits

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

Exits seen per day

403 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
185.13.124.0/2402
185.13.126.0/2402
185.13.125.0/2401

Proxy providers listing exits

  • 2Extract
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • GSocks
  • Geonix
  • GonzoProxy
  • Infatica
  • KocerRoxy
  • LemonBright
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter
  • ThunderProxy
  • VantageProxies
  • VitalExclusive

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
185.13.124.0/221,024NO-SVORKA-20121214Svorka AS (ORG-SAA37-RIPE) · NOALLOCATED PADec 14, 2012abuse@svorka.no
└ 185.13.124.0/23512SUNDBSund BredbandASSIGNED PADec 16, 2012abuse@svorka.no
via NO-SVORKA-20121214
└ 185.13.126.0/23512SUNDB2unknownASSIGNED PAAug 2, 2016abuse@svorka.no
via NO-SVORKA-20121214

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
Rotating
First seen
Dec 2012
Current origin since
Aug 2023 · 3.2 yr
Origin networks
4
Last change of origin
Aug 2023
Recorded history

History

Handoffs
4