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

208.68.181.0/24

20 residential-proxy exits · 30 days

Axivora Connect Ltd · space held by MoeQing

Announcement
this exact prefix
RPKI valid
Announced by
AS204539
Type
Residential
Risk
0 / 100 · Low
Proxy exits nearby

Residential-proxy exits

Proxy exits
20
7.8% of its addresses · 30 days
Always-on exits
19
95% of its exits
Providers
45
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

192K observations

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • 9Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • Evomi
  • FLAMEPROXIES_PREMIUM
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonode
  • Infatica
  • InfiniteProxies
  • LemonPrime
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYWING_BASIC
  • PacketStream
  • PrivateProxy
  • Proxies.fo
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy4U
  • ProxyGeo
  • ProxyRack
  • Proxyma
  • QUANTICDATA
  • RainProxy
  • Shifter
  • StrikeProxy
  • Thordata
  • VitalExclusive
  • Webshare

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
208.68.180.0/221,024MQNET-01MoeQing (MNL-86) · USDirect AllocationSep 30, 2025hao.yang@moeqing.com
└ 208.68.181.0/24256AXIVORA-CONNECT-LTDAxivora Connect LTD (C11383789) · NLReassignedOct 9, 2025hao.yang@moeqing.com
via MQNET-01

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
Jan 2026
Current origin since
Jan 2026 · 9 mo
Origin networks
1