Data as of Nov 14, 2026

80.85.105.0/24

1 residential-proxy exit · 30 days

Epic Communications Limited

Announcement
this exact prefix
RPKI valid
Announced by
Type
Business

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Providers
1
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

1 observation

Proxy providers listing exits

  • PuraRoute

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
80.85.96.0/20
since Dec 2008
AS33874Mobile16Epic 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
80.85.96.0/204,096MT-VFM-20010815Epic Communications Limited (ORG-VML1-RIPE) · MTALLOCATED PA—abuse@epic.com.mt
└ 80.85.105.0/2664DAKARunknownASSIGNED PAMar 10, 2021abuse@epic.com.mt
via MT-VFM-20010815
└ 80.85.105.64/2664NebryAddress block assigned to NebryASSIGNED PAJul 23, 2024abuse@epic.com.mt
via MT-VFM-20010815
└ 80.85.105.200/298trelleborgunknownASSIGNED PAAug 13, 2025abuse@epic.com.mt
via MT-VFM-20010815
└ 80.85.105.208/298MMH_EventsSubnet assigned for MMH EventsASSIGNED PAAug 25, 2025abuse@epic.com.mt
via MT-VFM-20010815
└ 80.85.105.240/2816EPIC_MTEpic Communications Ltd internet servicesASSIGNED PAJul 23, 2024abuse@epic.com.mt
via MT-VFM-20010815

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
Jun 2018
Current origin since
Mar 2021 · 5.7 yr
Origin networks
1