Data as of Nov 16, 2026

209.248.58.0/23

7 residential-proxy exits · 30 days

Sakura Link Limited · space held by Heptasky Hong Kong Limited

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting

Residential-proxy exits

Proxy exits
7
1.4% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
23
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

93 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
209.248.58.0/2405
209.248.59.0/2402

Proxy providers listing exits

  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • Infatica
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
209.248.56.0/22
since Apr 2026
AS49304Hosting20Heptasky Hong Kong Limited
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
209.248.58.0/24
since Jun 2026
AS49304Hosting5Heptasky Hong Kong Limited
209.248.59.0/24
since May 2026
AS49304Hosting2Heptasky Hong Kong Limited

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
209.248.0.0/1816,384HK-HEPTA-19990519Heptasky Hong Kong Limited (ORG-HHKL1-RIPE) · HKALLOCATED PAFeb 24, 2026abuse@heptasky.com
└ 209.248.32.0/198,192SKR-1-20260315Sakura Communications Limited (ORG-SIIL1-RIPE) · HKSUB-ALLOCATED PAMar 15, 2026abuse@sakura.as
└ 209.248.56.0/221,024SKR-Hepta-US-1unknownSUB-ALLOCATED PAMar 18, 2026abuse@sakura.as
via SKR-1-20260315

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
May 2026
Current origin since
May 2026 · 6 mo
Origin networks
1