LAYER3 INTEL
Get started
Sign in
Data as of Nov 10, 2026

83.68.48.0/22

3 residential-proxy exits · 30 days

SeaExpress Ltd.

Announcement
this exact prefix
No RPKI
Announced by
AS31444
Type
Internet provider
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
3
0.29% of its addresses · 30 days
Spread
3 of 4
/24s with at least one exit
Providers
2
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

5 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
83.68.49.0/2401
83.68.50.0/2401
83.68.51.0/2401

Proxy providers listing exits

  • IPFly
  • PuraRoute

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
83.68.32.0/198,192RU-SEANET-20040506SeaExpress Ltd. (ORG-SL17-RIPE) · RUALLOCATED PAMay 6, 2004net@seaexpress.ru
└ 83.68.48.0/24256RU-SEANET-SMALLNET-48unknownASSIGNED PAJan 15, 2018net@seaexpress.ru
via RU-SEANET-20040506
└ 83.68.49.0/24256RU-SEANET-SMALLNET-49unknownASSIGNED PAJan 16, 2018net@seaexpress.ru
via RU-SEANET-20040506
└ 83.68.50.0/24256RU-SEANET-SMALLNET-50unknownASSIGNED PAJan 16, 2018net@seaexpress.ru
via RU-SEANET-20040506
└ 83.68.51.0/24256RU-SEANET-SMALLNET-51unknownASSIGNED PAJan 16, 2018net@seaexpress.ru
via RU-SEANET-20040506

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Jul 2016
Current origin since
Jul 2016 · 10 yr
Origin networks
1