Data as of Nov 14, 2026

109.239.202.0/24

No anonymizer space · no proxy exits in 30 days

OMG.de GmbH

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

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.202.0/24256OMG-Customer-AllocationunknownSUB-ALLOCATED PAMay 23, 2016abuse@omg.de
via DE-OMG-INTERNET-20100215
└ 109.239.202.1 - 109.239.202.6363LKAUR-NETLandkreis Aurich (ORG-LA2036-RIPE) · DEASSIGNED PAAug 18, 2025rz@landkreis-aurich.de
└ 109.239.202.64/298MEYER-WERFT-NETMeyer Werft GmbH - Aurich NetASSIGNED PAMay 30, 2011abuse@omg.de
via OMG-Customer-Allocation
└ 109.239.202.72/298OEKORENTA-NETunknownASSIGNED PAApr 22, 2016abuse@omg.de
via OMG-Customer-Allocation
└ 109.239.202.80/298STADT-AURICH-NETunknownASSIGNED PAApr 22, 2016abuse@omg.de
via OMG-Customer-Allocation
└ 109.239.202.96/2816FRISIA-ACCESS-NETunknownASSIGNED PADec 30, 2021abuse@omg.de
via OMG-Customer-Allocation
└ 109.239.202.112/298VANHETTINGA-NETunknownASSIGNED PAApr 3, 2018abuse@omg.de
via OMG-Customer-Allocation
└ 109.239.202.120/298OEKORENTA-SRV-NETunknownASSIGNED PAFeb 28, 2018abuse@omg.de
via OMG-Customer-Allocation
└ 109.239.202.160/298AUTOJANSSEN-NETunknownASSIGNED PAMay 23, 2016it-service@bbk.de
└ 109.239.202.176/2816RADSERV-NETRADSERV GmbHASSIGNED PAJul 23, 2012abuse@omg.de
via OMG-Customer-Allocation
└ 109.239.202.200/298HTM-NETunknownASSIGNED PASep 5, 2017abuse@omg.de
via OMG-Customer-Allocation
└ 109.239.202.216/298ZIELINSKY-NETunknownASSIGNED PAApr 16, 2018abuse@omg.de
via OMG-Customer-Allocation
└ 109.239.202.224/298CIMTEC-NETunknownASSIGNED PAJun 12, 2018abuse@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