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

213.22.136.0/24

6 residential-proxy exits · 30 days

NOS Comunicacoes, S.A.

Announcement
213.22.128.0/18
RPKI valid
Announced by
AS2860
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Always-on exits
1
17% of its exits
Providers
29
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

8.6K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CoreProxy
  • Decodo
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • Geonode
  • GonzoProxy
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonBright
  • Oxylabs
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
213.22.0.0/16
since May 2015
AS2860Residential6,261
148 always on
NOS Comunicacoes, S.A.

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
213.22.0.0/1665,536PT-NOS-991028NOS Comunicacoes, S.A. (ORG-TPS1-RIPE) · PTALLOCATED PA—abuse@nos.pt
└ 213.22.128.0/198,192NOSNOS Comunicacoes S.A.ASSIGNED PAJul 24, 2002abuse@nos.pt
via PT-NOS-991028

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

Covering aggregate above, the prefix's own history below

213.22.128.0/18

Routing history

Pattern
Stable
First seen
Aug 2011
Current origin since
May 2015 · 12 yr
Origin networks
2
Last change of origin
May 2015
Recorded history

History

Handoffs
1