Data as of Nov 18, 2026

185.136.108.0/23

1 residential-proxy exit · 30 days

Pernix systems s.r.o.

Announcement
No RPKI
Announced by
Type
Unknown

Residential-proxy exits

Proxy exits
1
0.20% of its addresses · 30 days
Spread
1 of 2
/24s with at least one exit
Providers
3
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

4 observations

Proxy providers listing exits

  • BottingTools
  • IPFly
  • PuraRoute

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
185.136.108.0/24
since Aug 2018
AS203385UnknownPernix systems s.r.o.
185.136.109.0/24
since Aug 2018
AS203385Unknown1Pernix systems s.r.o.

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
185.136.108.0/221,024CZ-PERNIX-20160129Pernix systems s.r.o. (ORG-PSS41-RIPE) · CZALLOCATED PAJan 29, 2016zburget@burgnet.cz
└ 185.136.108.0/2816pernix-servicePernix systems s.r.o. infrastructureASSIGNED PAFeb 16, 2016zburget@burgnet.cz
via CZ-PERNIX-20160129
└ 185.136.108.32/2732pernix-infrastructurePernix systems s.r.o. infrastructure nemciceASSIGNED PAMar 7, 2016zburget@burgnet.cz
via CZ-PERNIX-20160129
└ 185.136.109.0/24256pernix-customersPernix systems s.r.o. customersASSIGNED PAFeb 16, 2016zburget@burgnet.cz
via CZ-PERNIX-20160129

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 185.136.108.0/22

185.136.108.0/22

Routing history

Pattern
Stable
First seen
Feb 2016
Current origin since
May 2019 · 7.5 yr
Origin networks
1