Data as of Nov 15, 2026

31.56.240.0/24

2 residential-proxy exits · 30 days

Megahost Kazakhstan TOO · space held by Gold IP L.L.C-FZ

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Providers
11
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

6 observations

Proxy providers listing exits

  • Byteful
  • EnigmaProxy
  • GSocks
  • Geonix
  • Geonode
  • Infatica
  • NodeProxy
  • Proxy-Seller
  • ProxyGeo
  • RainProxy
  • VantageProxies
IPv4 market

Path

1 · Holder
record created Jul 15, 2024
2 · Leased from
3 · Announced by
AS208450 Megahost Kazakhstan TOO
since Sep 2024 · 2.2 yr ago
4 · Use
Hosting

Lineage

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

31.56.240.0/24

From the registry to its use

  1. Jul 15, 2024
    Registry record
    Gold IP L.L.C-FZ
    ALLOCATED PA
    31.56.0.0/14
  2. Aug 14, 2024
    Reallocated
    Gold IP L.L.C-FZ
    SUB-ALLOCATED PA
    31.56.128.0/17
  3. Sep 2, 2024– today
    Announced
    AS208450 Megahost Kazakhstan TOO
    Hosting
  4. Sep 6, 2024
    Assigned
    Megahost Kazakhstan TOO
    ASSIGNED PA
    31.56.240.0/24
  5. Sep 6, 2024
    Route object
    IPXO
    RIPE route object for AS208450 Megahost Kazakhstan TOO, maintainer NETUTILS-MNT
  6. today
    Route object
    IPXO
    RADB route object for AS208450 Megahost Kazakhstan TOO, maintainer MAINT-AS834
  7. today
    Leased from
    IPXO
    IP broker

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
31.56.0.0/14262,144AE-GOLDIP-20110128Gold IP L.L.C-FZ (ORG-GIL34-RIPE) · AEALLOCATED PAJul 15, 2024abuse@goldipv4.com
└ 31.56.128.0/1732,768AE-GOLDIPGold IP L.L.C-FZ (ORG-GIL34-RIPE) · AESUB-ALLOCATED PAAug 14, 2024abuse@goldipv4.com
└ 31.56.240.0/24256NET-31-56-240-0-24Megahost Kazakhstan TOO (ORG-MKT4-RIPE) · KZASSIGNED PASep 6, 2024report@abuseradar.com

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Sep 2024
Current origin since
Sep 2024 · 2.2 yr
Origin networks
1