ixreport

r0cket.cloud

AS214503 · R0cket Cloud, QuxLabs AB

QuxLabs AB

5Exchanges
0On an exchange's list, not in PeeringDB
1In PeeringDB, not on the exchange's list
ContentType
OpenPeering policy
5Using the route servers
1To fix in PeeringDB
2Facilities in PeeringDB

Tools: Where can I peer with r0cket.cloud? · Where should r0cket.cloud peer next? · Compare r0cket.cloud with another network

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

PeeringDB fix list Printable page · CSV

One thing to fix in r0cket.cloud's PeeringDB record, from what its exchanges publish: 1 to check. As of 2026-11-19 12:40 UTC.

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

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If r0cket.cloud has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Sweden SOLIX MTU1500 Stockholm, Sweden · PeeringDB 128Not on its website members list
    IPv4193.110.13.164
    IPv62001:7f8:21:9::164
    Speed10000 Mbps (10G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

Exchanges over time

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

Map

Where r0cket.cloud'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 461G across 5 exchanges.

Sweden KeFF-IX Stockholm, Gothenburg, Malmö, Amsterdam, Sweden 193.243.183.141 2001:7f8:153::21:4503:1 40G Yes PeeringDB
Sweden SOLIX MTU1500 Stockholm, Sweden 193.110.13.164 2001:7f8:21:9::164 10G Yes PeeringDB only
Sweden SOLIX MTU4470 Stockholm, Sweden 193.110.12.164 2001:7f8:21:10::164 10G Yes PeeringDB
Sweden SONIX Stockholm Stockholm, Sweden 185.1.215.38 2001:7f8:117::21:4503:1 400G Yes Both
Sweden STHIX - Stockholm Stockholm, Sweden 192.121.80.88 2001:7f8:3e:0:a500:21:4503:1 1G Yes PeeringDB

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

These exchanges have a switch in a facility where r0cket.cloud lists itself in PeeringDB, but don't have r0cket.cloud 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 (2)

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

Sweden Obenet Kista GateKista 5 of 9
Sweden Obenet RiverlakeÄlvsjö 1 of 1