ixreport

bluvisio

AS206272

Bluvisio GmbH

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

Tools: Where can I peer with bluvisio? · Where should bluvisio peer next? · Compare bluvisio 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 bluvisio's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-11-19 18:41 UTC.

Make the changes on bluvisio'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 (1)

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

  1. Netherlands ERA-IX Amsterdam Amsterdam, Netherlands · PeeringDB 3789From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

Exchanges over time

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

Map

Where bluvisio'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 40G, at the 2 of 3 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Netherlands ERA-IX Amsterdam Amsterdam, Netherlands Website list only
Germany ERA-IX Frankfurt Frankfurt, Germany 185.0.27.70
185.0.27.71
2001:7f8:15e::70
2001:7f8:15e::71
2 × 10G Yes Both
Germany LOCIX FRANKFURT Frankfurt am Main, Germany 185.1.166.41
185.1.167.41
2001:7f8:f2:e1:0:206:272:1
2001:7f8:f2:e1:0:206:272:2
2 × 10G Yes PeeringDB

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

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

Germany DE-CIX FrankfurtFrankfurt, Germany 1,075 NTT Frankfurt 1 Data Center (FRA1)
Switzerland FogIXPAvers, Switzerland 532 NTT Frankfurt 1 Data Center (FRA1)
Germany KleyReXFrankfurt, Germany 471 NTT Frankfurt 1 Data Center (FRA1)
France nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France 160 NTT Frankfurt 1 Data Center (FRA1)
Germany MegaIX FrankfurtFrankfurt, Germany 114 NTT Frankfurt 1 Data Center (FRA1)
Germany FogIXP FrankfurtFrankfurt, Germany 67 NTT Frankfurt 1 Data Center (FRA1)
Facilities (1)

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

Germany NTT Frankfurt 1 Data Center (FRA1)Frankfurt 2 of 8