Data as of Nov 10, 2026

46.182.80.0/22

9 residential-proxy exits · 30 days

'Gigatrans Ukraine', LLC

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

Residential-proxy exits

Proxy exits
9
0.88% of its addresses · 30 days
Always-on exits
1
11% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
48
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

1.9K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BestProxy
  • BirdProxies
  • BottingTools
  • Byteful
  • CatProxies
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • Geonode
  • HideProxy
  • IPFly
  • IPPeak
  • InfiniteProxies
  • Kookey
  • LemonBright
  • LudaxProxy
  • NSocks
  • NovaProxy
  • Novada
  • PrivateProxy
  • ProxiesVision
  • Proxiware
  • ProxyEmpire
  • ProxyGeo
  • ProxyWing
  • PuraRoute
  • RainProxy
  • RapidProxy
  • RolaProxy
  • SPYDERPROXY_BASIC
  • Shifter
  • Smartproxy
  • StrikeProxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

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.182.80.0/212,048UA-GTU-20101124"Gigatrans Ukraine", LLC (ORG-UL225-RIPE) · UAALLOCATED PADec 14, 2021abuse@gigatrans.ua
└ 46.182.80.0/24256GT-CUSTOMERS-80unknownASSIGNED PAJan 10, 2018abuse@gigatrans.ua
via UA-GTU-20101124
└ 46.182.81.0/24256GT-CUSTOMERS-81unknownASSIGNED PAJan 10, 2018abuse@gigatrans.ua
via UA-GTU-20101124
└ 46.182.82.0/24256GT-CUSTOMERS-82unknownASSIGNED PAJan 10, 2018abuse@gigatrans.ua
via UA-GTU-20101124
└ 46.182.83.0/24256GT-CUSTOMERS-83unknownASSIGNED PAJan 10, 2018abuse@gigatrans.ua
via UA-GTU-20101124

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
Dec 2010
Current origin since
Sep 2016 · 10 yr
Origin networks
1