Data as of Nov 14, 2026

86.62.240.0/20

3 residential-proxy exits · 30 days

Ooredoo Q.S.C.

Announcement
RPKI valid
Announced by
Type
Mobile
69% of it

Residential-proxy exits

Proxy exits
3
0.07% of its addresses · 30 days
Spread
2 of 16
/24s with at least one exit
Providers
6
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

50 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
86.62.242.0/2402
86.62.255.0/2401

Proxy providers listing exits

  • AnyIP
  • Byteful
  • IPFly
  • LemonBright
  • PuraRoute
  • VitalExclusive

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
86.62.241.0/24
since Mar 2018
AS8781MobileOoredoo Q.S.C.
86.62.242.0/24
since Feb 2015
AS42298Unknown2Ooredoo Q.S.C.
86.62.245.0/24
since Oct 2014
AS42298UnknownOoredoo Q.S.C.
86.62.246.0/24
since May 2014
AS42298ResidentialOoredoo Q.S.C.
86.62.248.0/24
since Dec 2010
AS42298UnknownOoredoo Q.S.C.
86.62.255.0/24
since Feb 2008
AS42298Unknown1Ooredoo Q.S.C.

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
86.62.192.0/1816,384QA-QTEL-20050616Ooredoo Q.S.C. (ORG-QT1-RIPE) · QAALLOCATED PAJun 16, 2005abuse@qatar.net.qa
└ 86.62.240.0/24256MOBILE-BROADBAND-POOLunknownASSIGNED PAApr 11, 2006abuse@qatar.net.qa
via QA-QTEL-20050616
└ 86.62.241.0/24256MOBILE-BROADBAND-POOLunknownASSIGNED PAApr 11, 2006abuse@qatar.net.qa
via QA-QTEL-20050616
└ 86.62.242.0/24256MOBILE-BROADBAND-POOLunknownASSIGNED PAApr 11, 2006abuse@qatar.net.qa
via QA-QTEL-20050616
└ 86.62.243.0/24256MOBILE-BROADBAND-POOLunknownASSIGNED PAApr 11, 2006abuse@qatar.net.qa
via QA-QTEL-20050616
└ 86.62.244.0/24256MOBILE-BROADBAND-POOLunknownASSIGNED PAApr 11, 2006abuse@qatar.net.qa
via QA-QTEL-20050616
└ 86.62.245.0/24256MOBILE-BROADBAND-POOLunknownASSIGNED PAApr 11, 2006abuse@qatar.net.qa
via QA-QTEL-20050616
└ 86.62.246.0/24256MOBILE-BROADBAND-POOLunknownASSIGNED PAJun 4, 2007abuse@qatar.net.qa
via QA-QTEL-20050616
└ 86.62.247.0/24256MOBILE-BROADBAND-POOLunknownASSIGNED PAJun 4, 2007abuse@qatar.net.qa
via QA-QTEL-20050616
└ 86.62.248.0/24256QATAR-DATA-CENTER-14006unknownASSIGNED PAOct 29, 2018abuse@qatar.net.qa
via QA-QTEL-20050616
└ 86.62.249.0/24256MOBILE-BROADBAND-POOLunknownASSIGNED PAJun 4, 2007abuse@qatar.net.qa
via QA-QTEL-20050616
└ 86.62.250.0/24256MOBILE-BROADBAND-POOLunknownASSIGNED PAJun 4, 2007abuse@qatar.net.qa
via QA-QTEL-20050616
└ 86.62.251.0 - 86.62.254.2551,024MOBILE-BROADBAND-POOLunknownASSIGNED PAMar 20, 2007abuse@qatar.net.qa
via QA-QTEL-20050616
└ 86.62.255.0/24256Mobile-Broadband-Pool-No-5Regnet -Subnet-DohaASSIGNED PAJul 31, 2005abuse@qatar.net.qa
via QA-QTEL-20050616

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

4,096 addresses
TypeAddressesShareRanges
Mobile2,81669%8
Unknown1,02425%4
Residential2566.3%1

Network & registry

Routing timeline

Who has announced 86.62.192.0/18

86.62.192.0/18

Routing history

Pattern
Stable
First seen
Jul 2005
Current origin since
Jul 2005 · 21 yr
Origin networks
1