Data as of Nov 17, 2026

31.58.68.0/24

1 residential-proxy exit · 30 days

Fivemshield Network · 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
1
0.39% of its addresses · 30 days
Providers
2
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

2 observations

Proxy providers listing exits

  • BlurPath
  • Evomi
IPv4 market

Path

1 · Holder
record created Jul 15, 2024 · reallocated to a party the registry does not name Apr 8, 2026
2 · Leased from
3 · Announced by
AS212348 Fivemshield Network
since May 2025 · 18 mo ago
4 · Use
Hosting

Lineage

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

31.58.68.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. Apr 6, 2025– Jun 4, 2025
    Announced
    AS199707 Hongkong Xing Tong HUI Technology Co., Limited
    Hosting
  3. May 24, 2025– today
    Announced
    AS212348 Fivemshield Network
    Hosting
  4. Jun 3, 2025
    Assigned
    FIVEMSHIELD
    ASSIGNED PA
    31.58.68.0/24
  5. Jun 3, 2025
    Route object
    IPXO
    RIPE route object for AS212348 Fivemshield Network, maintainer NETUTILS-MNT
  6. Jun 3, 2025
    Route object
    IPXO
    RADB route object for AS212348 Fivemshield Network, 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.58.0.0/15131,072RIPE-GOERNET-IDunknownSUB-ALLOCATED PAApr 8, 2026abuse@atharva.co.id
└ 31.58.68.0/24256NET-31-58-68-0-24FIVEMSHIELD (ORG-FA1393-RIPE) · FRASSIGNED PAJun 3, 2025report@abuseradar.com

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Rotating
First seen
Apr 2025
Current origin since
May 2025 · 1.5 yr
Origin networks
2
Last change of origin
May 2025
Recorded history

History

Handoffs
1