Data as of Nov 11, 2026

5.23.48.0/24

3 residential-proxy exits · 30 days

JSC 'Timeweb'

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

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

901 observations
IPv4 market

Path

1 · Holder
JSC "Timeweb"
record created May 7, 2012
2 · Leased from
its owner, directly
3 · Announced by
AS9123 JSC 'Timeweb'
since Oct 2017 · 9.1 yr ago
4 · Use
Hosting

Lineage

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

5.23.48.0/24

From the registry to its use

  1. May 7, 2012
    Registry record
    JSC "Timeweb"
    ALLOCATED PA
    5.23.48.0/21
  2. May 16, 2013
    Route object
    AS9123 JSC 'Timeweb'
    RIPE route object for AS9123 JSC 'Timeweb', maintainer TIMEWEB-MNT
  3. Jun 1, 2013– Jun 27, 2016
    Announced
    AS9123 JSC 'Timeweb'
    Hosting
  4. Oct 14, 2016– Oct 25, 2016
    Announced
    AS9123 JSC 'Timeweb'
    Hosting
  5. Oct 9, 2017– today
    Announced
    AS9123 JSC 'Timeweb'
    Hosting
  6. 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
5.23.48.0/212,048RU-TIMEWEB2-20120507JSC "Timeweb" (ORG-TL188-RIPE) · RUALLOCATED PAMay 7, 2012abuse@timeweb.ru
└ 5.23.48.0/24256TW-CloudJSC "Timeweb" (ORG-TL188-RIPE) · RUASSIGNED PADec 12, 2017abuse@timeweb.ru

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Jun 2013
Current origin since
Oct 2017 · 9.1 yr
Origin networks
1