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

46.166.136.0/24

No anonymizer space · no proxy exits in 30 days

NForce Entertainment B.V.

Announcement
this exact prefix
RPKI valid
Announced by
AS43350
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.128.0/198,192NL-NFORCE-20101216NForce Entertainment B.V. (ORG-NE3-RIPE) · NLALLOCATED PAOct 2, 2013abuse@nforce.com
└ 46.166.136.0/2816NFORCE_ENTERTAINMENTCustomer 319ASSIGNED PAOct 9, 2018abuse@nforce.com
via NL-NFORCE-20101216
└ 46.166.136.16/2816NFORCE_ENTERTAINMENTCustomer 319ASSIGNED PAFeb 20, 2015abuse@nforce.com
via NL-NFORCE-20101216
└ 46.166.136.96/2816NFORCE_ENTERTAINMENTCustomer 1830ASSIGNED PAMar 11, 2015abuse@nforce.com
via NL-NFORCE-20101216
└ 46.166.136.112/2816NFORCE_ENTERTAINMENTCustomer 1523ASSIGNED PAMar 11, 2015abuse@nforce.com
via NL-NFORCE-20101216
└ 46.166.136.160/2816NFORCE_ENTERTAINMENTCustomer 1532ASSIGNED PAMar 19, 2015abuse@nforce.com
via NL-NFORCE-20101216
└ 46.166.136.224/2732NFORCE_ENTERTAINMENTCustomer 1523ASSIGNED PAOct 10, 2015abuse@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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Reactivated
First seen
May 2011
Current origin since
Mar 2023 · 3.7 yr
Origin networks
4
Last change of origin
Mar 2023
Recorded history

History

Handoffs
3