Data as of Nov 13, 2026

46.229.208.0/22

6 residential-proxy exits · 30 days

'OBIT' Ltd.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Internet provider

Residential-proxy exits

Proxy exits
6
0.59% of its addresses · 30 days
Spread
3 of 4
/24s with at least one exit
Providers
30
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

299 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
46.229.208.0/2403
46.229.209.0/2403
46.229.211.0/2401

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • FlashProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • Infatica
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • Shifter
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
46.229.208.0/23
since Sep 2016
AS8492Internet provider6"OBIT" Ltd.
46.229.210.0/24
since Sep 2016
AS8492Internet provider"OBIT" Ltd.
via Obit, Ltd.
46.229.211.0/24
since Aug 2019
AS8492Internet provider1"OBIT" Ltd.
via Obit, Ltd.

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
46.229.208.0/221,024RU-OBIT-20110221"OBIT" Ltd. (ORG-OL12-RIPE) · RUALLOCATED PAMay 30, 2011abuse@obit.ru
└ 46.229.208.0/24256OBIT-LANObit, Ltd.LIR-PARTITIONED PAJun 25, 2024abuse@obit.ru
via RU-OBIT-20110221
└ 46.229.209.0/24256OBIT-LANObit, Ltd.LIR-PARTITIONED PAJun 25, 2024abuse@obit.ru
via RU-OBIT-20110221
└ 46.229.210.0/24256OBIT-LANObit, Ltd.LIR-PARTITIONED PAJun 25, 2024abuse@obit.ru
via RU-OBIT-20110221
└ 46.229.211.0/24256OBIT-LANObit, Ltd.LIR-PARTITIONED PAAug 30, 2019abuse@obit.ru
via RU-OBIT-20110221

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
Jun 2011
Current origin since
Sep 2016 · 10 yr
Origin networks
3
Last change of origin
Sep 2016
Recorded history

History

Handoffs
2