Data as of Nov 15, 2026

178.135.0.0/21

6 residential-proxy exits · 30 days

OGERO

Announcement
this exact prefix
No RPKI
Announced by
Type
Business

Residential-proxy exits

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

Exits seen per day

18 observations

/24s with the most always-on exits

Proxy providers listing exits

  • Decodo
  • IPFly
  • NodeProxy
  • Novada
  • Oxylabs
  • RainProxy
  • VantageProxies

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
178.135.0.0/24
since Sep 2020
AS42003Business3OGERO
178.135.1.0/24
since Sep 2020
AS42003Business1OGERO
178.135.2.0/24
since Sep 2020
AS42003Business1OGERO
178.135.3.0/24
since Sep 2020
AS42003Business1OGERO
178.135.6.0/24
since Sep 2020
AS42003BusinessOGERO
178.135.7.0/24
since May 2021
AS42003BusinessOGERO

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
178.135.0.0/1665,536LB-LIBANTELECOM-20100324OGERO (ORG-LA84-RIPE) · LBALLOCATED PAMar 24, 2010chebaro@ogero.gov.lb
└ 178.135.0.0/212,048JDEIDEHMainunknownLIR-PARTITIONED PASep 27, 2020chebaro@ogero.gov.lb
via LB-LIBANTELECOM-20100324
└ 178.135.0.0/24256VIPRIONJD1unknownLIR-PARTITIONED PASep 23, 2020chebaro@ogero.gov.lb
via JDEIDEHMain
└ 178.135.1.0/24256VIPRIONJD2unknownLIR-PARTITIONED PASep 23, 2020chebaro@ogero.gov.lb
via JDEIDEHMain
└ 178.135.2.0/24256VIPRIONJD3unknownLIR-PARTITIONED PASep 23, 2020chebaro@ogero.gov.lb
via JDEIDEHMain
└ 178.135.3.0/24256VIPRIONJD4unknownLIR-PARTITIONED PASep 23, 2020chebaro@ogero.gov.lb
via JDEIDEHMain
└ 178.135.6.0/24256GGCJD1unknownLIR-PARTITIONED PASep 23, 2020chebaro@ogero.gov.lb
via JDEIDEHMain
└ 178.135.7.0/24256NETFLIXJD1unknownLIR-PARTITIONED PASep 23, 2020chebaro@ogero.gov.lb
via JDEIDEHMain

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
Apr 2010
Current origin since
Jan 2025 · 1.8 yr
Origin networks
1