Data as of Nov 19, 2026

81.29.112.0/20

3 residential-proxy exits · 30 days

TelecomService Ltd.

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
3
0.07% of its addresses · 30 days
Spread
3 of 16
/24s with at least one exit
Providers
3
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

61 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
81.29.114.0/2401
81.29.115.0/2401
81.29.119.0/2401

Proxy providers listing exits

  • BottingTools
  • 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
81.29.112.0/204,096RU-NVRTELCOM-20060327TelecomService Ltd. (ORG-TL57-RIPE) · RUALLOCATED PAMar 27, 2006telekom@nvrsk.ru
└ 81.29.112.0/221,024TSERV-01Equipment, ServicesASSIGNED PAMar 28, 2006telekom@nvrsk.ru
via RU-NVRTELCOM-20060327
└ 81.29.116.0/221,024TSERV-02Equipment, ServicesASSIGNED PAApr 10, 2008telekom@nvrsk.ru
via RU-NVRTELCOM-20060327
└ 81.29.120.0/221,024TSERV-03Customers - PPPoEASSIGNED PAOct 8, 2014telekom@nvrsk.ru
via RU-NVRTELCOM-20060327
└ 81.29.124.0/221,024TSERV-04Customers VoIPASSIGNED PAApr 8, 2022telekom@nvrsk.ru
via RU-NVRTELCOM-20060327

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
Feb 2016
Current origin since
Feb 2016 · 11 yr
Origin networks
1