Data as of Nov 16, 2026

109.239.203.0/24

1 residential-proxy exit · 30 days

OMG.de GmbH

Announcement
this exact prefix
RPKI valid
Announced by
Type
Business
Risk
0 / 100 · Low

Residential-proxy exits

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

Exits seen per day

1 observation

Proxy providers listing exits

  • AnyIP
  • FloppyData

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
109.239.192.0/204,096DE-OMG-INTERNET-20100215OMG.de GmbH (ORG-OG20-RIPE) · DEALLOCATED PAFeb 15, 2010abuse@omg.de
└ 109.239.203.0/24256OMG-Customer-AllocationunknownSUB-ALLOCATED PAOct 14, 2020abuse@omg.de
via DE-OMG-INTERNET-20100215
└ 109.239.203.0/2816NET-1TOP-SRV1unknownASSIGNED PANov 4, 2026abuse@omg.de
via OMG-Customer-Allocation
└ 109.239.203.32/2732CNMAESTRO-NETunknownASSIGNED PASep 23, 2026abuse@omg.de
via OMG-Customer-Allocation
└ 109.239.203.80/2816OMG-PLESK-NETunknownASSIGNED PAOct 14, 2020abuse@omg.de
via OMG-Customer-Allocation
└ 109.239.203.97 - 109.239.203.11014BUENTING-WEBSRV-NETBuenting Informationstechnologie GmbHASSIGNED PAJul 14, 2015abuse@omg.de
via OMG-Customer-Allocation
└ 109.239.203.120/298NET-1TOP-GW1unknownASSIGNED PANov 4, 2026abuse@omg.de
via OMG-Customer-Allocation
└ 109.239.203.128/298BRANDKASSEAURICH-NETunknownASSIGNED PAJan 14, 2019abuse@omg.de
via OMG-Customer-Allocation
└ 109.239.203.137 - 109.239.203.1437FRISIA-AZURE-NETunknownASSIGNED PAJan 22, 2019abuse@omg.de
via OMG-Customer-Allocation
└ 109.239.203.144/298NV-INFRASTRUCTURE-NETunknownASSIGNED PAJun 7, 2016abuse@omg.de
via OMG-Customer-Allocation
└ 109.239.203.160/304HARTRUMPF-NETunknownASSIGNED PADec 29, 2016abuse@omg.de
via OMG-Customer-Allocation
└ 109.239.203.184/298MULTI-LEER-NETunknownASSIGNED PADec 30, 2021abuse@omg.de
via OMG-Customer-Allocation
└ 109.239.203.192/298HOSPIMOBIL-NETunknownASSIGNED PAMay 22, 2024abuse@omg.de
via OMG-Customer-Allocation
└ 109.239.203.200/298WUB-EXT-NETunknownASSIGNED PAMay 20, 2019abuse@omg.de
via OMG-Customer-Allocation
└ 109.239.203.208/298SWE-NETunknownASSIGNED PADec 30, 2021abuse@omg.de
via OMG-Customer-Allocation
└ 109.239.203.216/298RJANSSEN2-NETunknownASSIGNED PAOct 14, 2020abuse@omg.de
via OMG-Customer-Allocation
└ 109.239.203.224/304LKAUR-GACAUR-NETunknownASSIGNED PAOct 14, 2020abuse@omg.de
via OMG-Customer-Allocation
└ 109.239.203.232/304Andreesen-NetunknownASSIGNED PAOct 27, 2020abuse@omg.de
via OMG-Customer-Allocation
└ 109.239.203.240/2816FRISONAUT-NETunknownASSIGNED PAMay 22, 2024abuse@omg.de
via OMG-Customer-Allocation

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
Mar 2014
Current origin since
Mar 2014 · 13 yr
Origin networks
1