Data as of Nov 14, 2026

46.166.191.0/24

No anonymizer space · no proxy exits in 30 days

NForce Entertainment B.V.

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

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
46.166.176.0/204,096NL-NFORCE-20101216NForce Entertainment B.V. (ORG-NE3-RIPE) · NLALLOCATED PAOct 2, 2013abuse@nforce.com
└ 46.166.191.0/25128NETCRAWLED_LLCCustomer 1052ASSIGNED PANov 5, 2014abuse@nforce.com
via NL-NFORCE-20101216
└ 46.166.191.160/2816NFORCE_ENTERTAINMENTCustomer 3834ASSIGNED PAMar 2, 2020abuse@nforce.com
via NL-NFORCE-20101216
└ 46.166.191.192/2732NFORCE_ENTERTAINMENTCustomer 2398ASSIGNED PAFeb 21, 2017abuse@nforce.com
via NL-NFORCE-20101216
└ 46.166.191.224/2816NFORCE_ENTERTAINMENTCustomer 319ASSIGNED PAFeb 24, 2016abuse@nforce.com
via NL-NFORCE-20101216
└ 46.166.191.240/298NFORCE_ENTERTAINMENTCustomer colocation blockASSIGNED PANov 5, 2015abuse@nforce.com
via NL-NFORCE-20101216
└ 46.166.191.248/298NFORCE_ENTERTAINMENTCustomer 1324ASSIGNED PAJan 15, 2016abuse@nforce.com
via NL-NFORCE-20101216

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