Data as of Nov 18, 2026

130.49.162.0/24

4 residential-proxy exits · 30 days

eServer s.r.o. · space held by Digital City FZE

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium
Recent change
New origin May 2026
its first announcement on record

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Providers
16
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

89 observations

Proxy providers listing exits

  • Byteful
  • DataImpulse
  • FastProxy
  • GSocks
  • GloryCloud
  • IPFly
  • Infatica
  • KindProxy
  • LudaxProxy
  • NovaProxy
  • PYPROXY
  • Proxiware
  • Q2IP
  • RainProxy
  • RapidProxy
  • ZENPROXY_LITE
IPv4 market

Path

Announced by AS61424 since May 2026 · 6 mo ago
1 · Holder
record created Oct 30, 2025
2 · Leased from
its owner, directly
3 · Announced by
AS61424 eServer s.r.o.
since May 2026 · 6 mo ago
4 · Use
Hosting

Lineage

How this block came to its use, oldest first. The whole IPv4 market →

130.49.162.0/24

From the registry to its use

  1. Oct 29, 2025
    Route object
    AS214798 Digital City FZE
    RIPE route object for AS214798 Digital City FZE, maintainer LIR-AE-DIGITALCITY-1-MNT
  2. Oct 30, 2025
    Registry record
    Digital City FZE
    ALLOCATED PA
    130.49.160.0/22
  3. May 31, 2026– today
    Announced
    AS61424 eServer s.r.o.
    Hosting
  4. Jun 3, 2026
    Route object
    AS61424 eServer s.r.o.
    RIPE route object for AS61424 eServer s.r.o., maintainer LIR-AE-DIGITALCITY-1-MNT
  5. today
    Leased from
    InterLIR
    Lessor

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
130.49.160.0/221,024AE-DIGITALCITY-19880518Digital City FZE (ORG-DCF5-RIPE) · AEALLOCATED PAOct 30, 2025abuse@vps1.net
└ 130.49.162.0/24256VPS1-NET-SKunknownASSIGNED PAJun 3, 2026abuse@vps1.net
via AE-DIGITALCITY-19880518

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
May 2026
Current origin since
May 2026 · 6 mo
Origin networks
1