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

91.90.40.0/21

66 anonymizer addresses · 3.2% · VPN

Blix Solutions AS · space held by Blix Group AS

Announcement
this exact prefix
RPKI valid
Announced by
AS50304
Type
Internet provider
62% of it
IPv4 market

Path

1 · Holder
Blix Group AS
record created Oct 21, 2014
2 · Leased from
not leased
3 · Announced by
AS50304 Blix Solutions AS
since Jul 2014 · 12.3 yr ago
4 · Use
VPN servicesnamed Mullvad VPN
Internet provider

Operators, sellers and brokers

VPN services

NameParentIn 91.90.40.0/21/24s
Mullvad VPNMullvad VPN AB
663.2%
1

Lineage

How this block came to its use, oldest first. The whole IPv4 market →

91.90.40.0/21

From the registry to its use

  1. Nov 15, 2006– Jul 1, 2014
    Announced
    AS41869 Blix Group AS
    Internet provider
  2. Jul 8, 2014– today
    Announced
    AS50304 Blix Solutions AS
    Internet provider
  3. Jul 14, 2014
    Route object
    AS50304 Blix Solutions AS
    RIPE route object for AS50304 Blix Solutions AS, maintainer BLIX-MNT
  4. Oct 21, 2014
    Registry record
    Blix Group AS
    ALLOCATED PA
    91.90.40.0/21
  5. today
    Used
    Mullvad VPN
    VPN

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
91.90.40.0/212,048NO-BLIXGROUP-20061103Blix Group AS (ORG-BGA22-RIPE) · NOALLOCATED PAOct 21, 2014abuse@blixsolutions.no
└ 91.90.40.0/298NO-BLIXCUST10510Customer 10510ASSIGNED PAMar 18, 2019abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.40.128/25128NO-BLIXCUST10412Customer 10412ASSIGNED PAFeb 21, 2024abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.42.32/2732NO-BLIXCUST10477unknownASSIGNED PADec 12, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.42.80/304NO-BLIXCUST10332unknownASSIGNED PADec 12, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.42.84/304NO-BLIXCUST10493unknownASSIGNED PADec 12, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.42.96/321NO-BLIXCUST10256Customer 10256ASSIGNED PAJan 14, 2019abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.42.160/298NO-BLIXCUST10425Customer 10425ASSIGNED PAFeb 28, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.42.168/298NO-BLIXCUST10494Customer 10494ASSIGNED PAFeb 28, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.42.176/298NO-BLIXCUST10491Customer 10491ASSIGNED PAFeb 28, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.42.184/304NO-BLIXCUST10491Customer 10491ASSIGNED PAFeb 28, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.42.188/304NO-BLIXCUST10477Customer 10477ASSIGNED PAFeb 28, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.42.248/298NO-BLIXCUST10503unknownASSIGNED PAFeb 28, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.43.0/2732NO-BLIXCUST10548unknownASSIGNED PADec 12, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.43.32/298NO-BLIXCUST10311unknownASSIGNED PADec 13, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.43.48/304NO-BLIXCUST10132unknownASSIGNED PADec 13, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.43.80/298NO-BLIXCUST10557unknownASSIGNED PADec 12, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.43.96/2816NO-BLIXCUST10218unknownASSIGNED PADec 13, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.43.128/298NO-BLIXCUST10494unknownASSIGNED PAFeb 28, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.43.136/304INFRA-AWunknownASSIGNED PAFeb 28, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.43.140/304INFRA-AWunknownASSIGNED PAFeb 28, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.43.144/298NO-BLIXCUST10511unknownASSIGNED PAFeb 28, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.43.152/304INFRA-AWunknownASSIGNED PAFeb 28, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.43.156/304INFRA-AWunknownASSIGNED PAFeb 28, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.43.160/298INFRA-AWunknownASSIGNED PAFeb 28, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.43.168/304NO-BLIXCUST10436Customer 10436ASSIGNED PAFeb 28, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.43.172/304INFRA-AWunknownASSIGNED PAFeb 28, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.43.192/298NO-BLIXCUST10494unknownASSIGNED PAFeb 28, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.43.200/304NO-BLIXCUST10142Customer 10142ASSIGNED PAFeb 28, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.43.204/304INFRA-AWunknownASSIGNED PAFeb 28, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.43.208/298NO-BLIXCUST10461Customer 10461ASSIGNED PAFeb 28, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.43.216/304NO-BLIXCUST10513Customer 10513ASSIGNED PAFeb 28, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.43.220/304NO-BLIXCUST10512Customer 10512ASSIGNED PAFeb 28, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.43.224/304NO-BLIXCUST10514Customer 10514ASSIGNED PAFeb 28, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.43.228/304NO-BLIXCUST10515Customer 10515ASSIGNED PAFeb 28, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.43.232/304NO-BLIXCUST10521Customer 10521ASSIGNED PAFeb 28, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.43.236/304NO-BLIXCUST10522Customer 10522ASSIGNED PAFeb 28, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.43.240/304NO-BLIXCUST10555unknownASSIGNED PADec 12, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.43.244/304INFRA-AWunknownASSIGNED PAFeb 28, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.43.248/304NO-BLIXCUST10026Customer 10026ASSIGNED PAFeb 28, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.43.252/304NO-BLIXCUST10517unknownASSIGNED PADec 12, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.44.0/2664NO-BLIXCUST10412Customer 10412ASSIGNED PAFeb 28, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.44.64/2816NO-BLIXCUST10514Customer 10514ASSIGNED PAFeb 28, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.44.96/304NO-BLIXCUST10416unknownASSIGNED PADec 12, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.44.100/304NO-BLIXCUST10416unknownASSIGNED PADec 12, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.44.104/298NO-BLIXCUST10344unknownASSIGNED PADec 12, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.44.128/25128NO-BLIX-DHCPCUSTOMERSDHCP customersASSIGNED PAFeb 28, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.45.64/2732NO-BLIXCUST10299Customer 1099ASSIGNED PAFeb 28, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.45.96/298NO-BLIXCUST10520Customer 10520ASSIGNED PAFeb 28, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.45.104/298NO-BLIXCUST10521Customer 10521ASSIGNED PAFeb 28, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.45.112/304US-BLIXCUST10322Customer 10505ASSIGNED PAFeb 28, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.45.144/2816NO-BLIXCUST10546unknownASSIGNED PADec 13, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.45.192/2664NO-BLIXCUST10298Customer 10298ASSIGNED PAJan 17, 2015abuse@blixsolutions.no
via NO-BLIXGROUP-20061103
└ 91.90.46.0/23512NO-BLIXVIRTUALBlix Solutions AS Virtual ClusterASSIGNED PAAug 2, 2018abuse@blixsolutions.no
via NO-BLIXGROUP-20061103

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
Internet provider1,26362%15
Business55927%51
Hosting1607.8%2
VPNanonymizer663.2%28

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Nov 2006
Current origin since
Jul 2014 · 12 yr
Origin networks
2
Last change of origin
Jul 2014
Recorded history

History

Handoffs
1