Data as of Nov 14, 2026

209.248.44.0/23

19 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
Recent change
New origin Jul 2026
its first announcement on record

Residential-proxy exits

Proxy exits
19
3.7% of its addresses · 30 days
Spread
1 of 2
/24s with at least one exit
Providers
27
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

372 observations

Proxy providers listing exits

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

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
209.248.44.0/22
since Apr 2026
AS49304Hosting22Heptasky Hong Kong Limited
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
209.248.44.0/24AS49304HostingHeptasky Hong Kong Limited
209.248.45.0/24AS49304Hosting19Heptasky 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.32.0/204,096SKR-Hepta-HK-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
Jul 2026
Current origin since
Jul 2026 · 4 mo
Origin networks
1