Data as of Nov 10, 2026

149.233.6.0/24

No anonymizer space · no proxy exits in 30 days

NTT Global Data Centers EMEA GmbH

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium

Announcements

Less specific

Covering announcements

PrefixOriginTypeHolderRPKI
149.233.0.0/19
since Mar 2018
AS203329HostingNTT Global Data Centers EMEA GmbH

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
149.233.0.0/198,192DE-E-SHELTER-19930505NTT Global Data Centers EMEA GmbH (ORG-ECG6-RIPE) · DEALLOCATED PAJan 9, 2018dc.emea.abuse@global.ntt
└ 149.233.6.0/24256BER1unknownLIR-PARTITIONED PADec 16, 2025dc.emea.abuse@global.ntt
via DE-E-SHELTER-19930505
└ 149.233.6.0/298Customer_NetworkunknownASSIGNED PAMar 10, 2025dc.emea.abuse@global.ntt
via BER1
└ 149.233.6.8 - 149.233.6.147Customer-LANunknownASSIGNED PAJul 27, 2018dc.emea.abuse@global.ntt
via BER1
└ 149.233.6.36 - 149.233.6.383TransportnetunknownASSIGNED PAOct 18, 2018dc.emea.abuse@global.ntt
via BER1
└ 149.233.6.40/304Customer_NetworkunknownASSIGNED PAMay 4, 2026dc.emea.abuse@global.ntt
via BER1
└ 149.233.6.44/304arxes-tolinaunknownASSIGNED PADec 4, 2019dc.emea.abuse@global.ntt
via BER1
└ 149.233.6.48 - 149.233.6.547TLG_Customer_NetunknownASSIGNED PASep 17, 2019dc.emea.abuse@global.ntt
via BER1
└ 149.233.6.84/304Customer_NetworkunknownASSIGNED PAJul 22, 2025dc.emea.abuse@global.ntt
via BER1
└ 149.233.6.88/304Customer_NetworkunknownASSIGNED PAJan 5, 2024dc.emea.abuse@global.ntt
via BER1
└ 149.233.6.92/304Customer_NetworkunknownASSIGNED PAAug 1, 2025dc.emea.abuse@global.ntt
via BER1
└ 149.233.6.104/298Customer_NetworkunknownASSIGNED PAApr 25, 2025dc.emea.abuse@global.ntt
via BER1
└ 149.233.6.120/298Customer_NetworkunknownASSIGNED PAApr 25, 2025dc.emea.abuse@global.ntt
via BER1
└ 149.233.6.128/2732arxes_tolina_GmbHunknownASSIGNED PADec 2, 2019jens.becker@arxes-tolina.de
└ 149.233.6.160/2816Customer_NetworkunknownASSIGNED PAApr 25, 2025dc.emea.abuse@global.ntt
via BER1
└ 149.233.6.192/2816arxes_tolina_GmbHunknownASSIGNED PADec 17, 2019dc.emea.abuse@global.ntt
via BER1
└ 149.233.6.224 - 149.233.6.23815TransportnetunknownASSIGNED PANov 18, 2020dc.emea.abuse@global.ntt
via BER1
└ 149.233.6.248/298Customer_NetworkunknownASSIGNED PAFeb 2, 2022dc.emea.abuse@global.ntt
via BER1

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Dec 2025
Current origin since
Dec 2025 · 11 mo
Origin networks
1