Data as of Nov 11, 2026

37.75.48.0/20

25 residential-proxy exits · 30 days

Epic Communications Limited

Announcement
this exact prefix
RPKI valid
Announced by
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

Proxy exits
25
0.61% of its addresses · 30 days
Spread
13 of 16
/24s with at least one exit
Providers
61
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

7.0K observations

Proxy providers listing exits

  • 711Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • DataImpulse
  • Decodo
  • EVOPROXY
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • IPFly
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • NextProxy
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • Shifter
  • StrikeProxy
  • SwiftProxy
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
37.75.32.0/19
since Mar 2012
AS33874Mobile55Epic Communications Limited

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
37.75.32.0/198,192MT-VFM-20120130Epic Communications Limited (ORG-VML1-RIPE) · MTALLOCATED PAJan 30, 2012abuse@epic.com.mt
└ 37.75.48.0/204,096EPIC_MTEpic Communications Ltd internet servicesASSIGNED PANov 20, 2020abuse@epic.com.mt
via MT-VFM-20120130

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Apr 2013
Current origin since
Apr 2013 · 14 yr
Origin networks
1