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

149.249.56.0/21

No anonymizer space · no proxy exits in 30 days

NetCom BW GmbH

Announcement
this exact prefix
RPKI valid
Announced by
AS41998
Type
Residential
96% of it

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.249.56.0/212,048Netcom_BWNetCom BW GmbH (ORG-OTG1-RIPE) · DELEGACYApr 6, 2021abuse@netcom-bw.de
└ 149.249.56.0/2732IPv4_Range_for_e-business_over_NetCom_BWunknownLEGACYApr 9, 2026abuse@netcom-bw.de
via Netcom_BW
└ 149.249.56.32/298IPv4_Range_for_Rotzinger_PharmaPack_over_NetCom_BWunknownLEGACYApr 15, 2026abuse@netcom-bw.de
via Netcom_BW
└ 149.249.56.48/2816IPv4_Range_for_Mann_und_Schroeder_over_NetCom_BWunknownLEGACYApr 22, 2026abuse@netcom-bw.de
via Netcom_BW
└ 149.249.56.64/298IPv4_Range_for_Hannusch_Industrieelektronik_over_NetCom_BWunknownLEGACYMay 6, 2026abuse@netcom-bw.de
via Netcom_BW
└ 149.249.56.72/298IPv4_Range_for_V4Smart_over_NetCom_BWunknownLEGACYMay 7, 2026abuse@netcom-bw.de
via Netcom_BW
└ 149.249.56.80/2816IPv4_Range_for_e-business_over_NetCom_BWunknownLEGACYMay 12, 2026abuse@netcom-bw.de
via Netcom_BW
└ 149.249.56.96/298IPv4_Range_for_Wolff_und_Mueller_Holding_over_NetCom_BWunknownLEGACYJun 2, 2026abuse@netcom-bw.de
via Netcom_BW
└ 149.249.56.104/298IPv4_Range_for_Landkreis_Ravensburg_over_NetCom_BWunknownLEGACYMay 29, 2026abuse@netcom-bw.de
via Netcom_BW
└ 149.249.56.112/2816IPv4_Range_for_Konrad_Hornschuch_over_NetCom_BWunknownLEGACYMay 27, 2026abuse@netcom-bw.de
via Netcom_BW
└ 149.249.56.128/2816IPv4_Range_for_e-business_over_NetCom_BWunknownLEGACYJun 8, 2026abuse@netcom-bw.de
via Netcom_BW
└ 149.249.56.144/2816IPv4_Range_for_Grant_Thornton_AG_over_NetCom_BWunknownLEGACYJun 9, 2026abuse@netcom-bw.de
via Netcom_BW
└ 149.249.56.160/298IPv4_Range_for_Modine_Europe_over_NetCom_BWunknownLEGACYJun 17, 2026abuse@netcom-bw.de
via Netcom_BW
└ 149.249.56.168/298IPv4_Range_for_CARIAD_SE_over_NetCom_BWunknownLEGACYAug 11, 2026abuse@netcom-bw.de
via Netcom_BW
└ 149.249.56.176/2816IPv4_Range_for_Eruid_Otto_Meyer-Technik_over_NetCom_BWunknownLEGACYJun 22, 2026abuse@netcom-bw.de
via Netcom_BW
└ 149.249.56.192/2732IPv4_Range_for_TeGe_Deutschland_over_NetCom_BWunknownLEGACYJun 18, 2026abuse@netcom-bw.de
via Netcom_BW
└ 149.249.56.224/2816IPv4_Range_for_Stadt_Bietigheim-Bissingen_over_NetCom_BWunknownLEGACYJun 22, 2026abuse@netcom-bw.de
via Netcom_BW
└ 149.249.56.240/298IPv4_for_LinTec_Aulendorf_over_NetCom_BWunknownLEGACYJul 10, 2026abuse@netcom-bw.de
via Netcom_BW
└ 149.249.56.248/298IPv4_Range_for_Hensoldt_Optronics_over_NetCom_BWunknownLEGACYJul 1, 2026abuse@netcom-bw.de
via Netcom_BW
└ 149.249.57.0/298IPv4_Range_for_OBRIST_DE_over_NetCom_BWunknownLEGACYJul 29, 2026abuse@netcom-bw.de
via Netcom_BW
└ 149.249.57.8/298IPv4_Range_for_Stadtwerke_Stuttgart_over_NetCom_BWunknownLEGACYAug 21, 2026abuse@netcom-bw.de
via Netcom_BW
└ 149.249.57.16/298IPv4_Range_for_Wiedmann_und_Winz_over_NetCom_BWunknownLEGACYSep 1, 2026abuse@netcom-bw.de
via Netcom_BW
└ 149.249.57.32/2816IPv4_Range_for_Gemeindeverwaltungsverband_Altshausen_over_NetCom_BWunknownLEGACYSep 17, 2026abuse@netcom-bw.de
via Netcom_BW
└ 149.249.57.48/2816IPv4_Range_for_STRABAG_BRVZ_over_NetCom_BWunknownLEGACYOct 12, 2026abuse@netcom-bw.de
via Netcom_BW
└ 149.249.57.64/2816IPv4_Range_for_Haeffner_over_Netcom_BWunknownLEGACYOct 9, 2026abuse@netcom-bw.de
via Netcom_BW
└ 149.249.57.80/298IPv4_Range_for_Liebherr-Werk_Ehingen_over_NetCom_BWunknownLEGACYOct 26, 2026abuse@netcom-bw.de
via Netcom_BW
└ 149.249.57.88/298IPv4_Range_for_NetCom_BW_over_NetCom_BWunknownLEGACYNov 3, 2026abuse@netcom-bw.de
via Netcom_BW
└ 149.249.57.128/25128IPv4_Range_for_Stadtverwaltung_Aalen_over_NetCom_BWunknownLEGACYNov 11, 2026abuse@netcom-bw.de
via Netcom_BW
└ 149.249.58.0/298IPv4_Range_for_Netze_BW_NOC_over_NetCom_BWunknownLEGACYNov 13, 2026abuse@netcom-bw.de
via Netcom_BW
└ 149.249.58.16/2816IPv4_Range_for_e-business_over_NetCom_BWunknownLEGACYNov 13, 2026abuse@netcom-bw.de
via Netcom_BW

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

2,048 addresses
TypeAddressesShareRanges
Residential1,96896%4
Business803.9%4

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Jul 2024
Current origin since
Jul 2024 · 2.3 yr
Origin networks
1