ixreport

Qlosr

AS51956

Qlosr AB

7Exchanges
4On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
NSPType
OpenPeering policy
7Using the route servers
6To fix in PeeringDB
6Facilities in PeeringDB

Tools: Where can I peer with Qlosr? · Where should Qlosr peer next? · Compare Qlosr with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

6 things to fix in Qlosr's PeeringDB record, from what its exchanges publish: 4 to add, 2 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on Qlosr's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (4)

On the exchange's own member list, but not in Qlosr's PeeringDB record. Add one entry per connection with these values.

  1. Denmark Netnod Copenhagen BLUE -- MTU9K Malmo / Copenhagen, Denmark · PeeringDB 2868From its IX-F export
    IPv4212.237.192.16
    IPv62001:7f8:d:202::16
    SpeedNot published
    RS peerYes
  2. Denmark Netnod Copenhagen GREEN -- MTU9K Malmo / Copenhagen, Denmark · PeeringDB 193From its IX-F export
    IPv4212.237.193.16
    IPv62001:7f8:d:203::16
    SpeedNot published
    RS peerYes
  3. Sweden Netnod Stockholm BLUE -- MTU4470 Stockholm, Sweden · PeeringDB 2847From its IX-F export
    IPv4195.69.119.50
    IPv62001:7f8:d:fb::50
    SpeedNot published
    RS peerYes
  4. Sweden Netnod Stockholm GREEN -- MTU4470 Stockholm, Sweden · PeeringDB 2845From its IX-F export
    IPv4195.245.240.50
    IPv62001:7f8:d:fc::50
    SpeedNot published
    RS peerYes

Correct these entries (2)

Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.

  1. ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:d:fe::50
    • In the entry with IPv4 194.68.128.50: set IPv6 to 2001:7f8:d:fe::50 (now empty).
  2. ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:d:ff::50
    • In the entry with IPv4 194.68.123.50: set IPv6 to 2001:7f8:d:ff::50 (now empty).

Exchanges over time

02468Oct 3, 2026Nov 19, 20267
Show as a table
DateExchanges
Nov 19, 20267
Nov 18, 20267
Nov 17, 20267
Nov 16, 20267
Nov 15, 20267
Nov 14, 20267
Nov 13, 20267
Nov 12, 20267
Nov 11, 20267
Nov 10, 20267
Nov 9, 20267
Nov 8, 20267
Nov 7, 20267
Nov 6, 20267
Nov 5, 20267
Nov 4, 20267
Nov 3, 20267
Nov 2, 20267
Nov 1, 20267
Oct 31, 20267
Oct 30, 20267
Oct 29, 20267
Oct 28, 20267
Oct 27, 20267
Oct 26, 20267
Oct 25, 20267
Oct 24, 20267
Oct 23, 20267
Oct 22, 20267
Oct 21, 20267
Oct 20, 20267
Oct 19, 20267
Oct 18, 20267
Oct 17, 20267
Oct 16, 20267
Oct 15, 20267
Oct 14, 20267
Oct 13, 20267
Oct 12, 20267
Oct 11, 20267
Oct 10, 20267
Oct 9, 20267
Oct 8, 20267
Oct 7, 20267
Oct 6, 20264
Oct 5, 20264
Oct 4, 20264
Oct 3, 20264

Map

Where Qlosr's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 30G, at the 3 of 7 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Denmark Netnod Copenhagen BLUE -- MTU9K Malmo / Copenhagen, Denmark 212.237.192.16 2001:7f8:d:202::16 19 routes Not in PeeringDB
Denmark Netnod Copenhagen GREEN -- MTU9K Malmo / Copenhagen, Denmark 212.237.193.16 2001:7f8:d:203::16 Yes Not in PeeringDB
Sweden Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden 194.68.128.50 10G 19 routes Both IPv6 not in PeeringDB
Sweden Netnod Stockholm BLUE -- MTU4470 Stockholm, Sweden 195.69.119.50 2001:7f8:d:fb::50 Yes Not in PeeringDB
Sweden Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden 194.68.123.50 10G Yes Both IPv6 not in PeeringDB
Sweden Netnod Stockholm GREEN -- MTU4470 Stockholm, Sweden 195.245.240.50 2001:7f8:d:fc::50 Yes Not in PeeringDB
Sweden STHIX - Stockholm Stockholm, Sweden 192.121.80.227 2001:7f8:3e:0:a500:19:8549:1 10G Yes PeeringDB

Exchanges in its buildings that it isn't on (12)

These exchanges have a switch in a facility where Qlosr lists itself in PeeringDB, but don't have Qlosr as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Facilities (6)

The buildings Qlosr lists in PeeringDB, and how many of the exchanges in each it's on.

Sweden Equinix SK2 - Stockholm, SköndalStockholm 5 of 10
Sweden STOKAB KN7, ÖstermalmStockholm 5 of 9
Sweden Glesys Stockholm 1Stockholm 5 of 7
Sweden Gothnet DC MarieholmGothenburg 0 of 5
Sweden Equinix SK3 - Stockholm, SpångaStockholm 0 of 3
Sweden 31173 DC Malmö ScheelegatanMalmö No exchange