ixreport

Creasa

AS210821

Creasa VOF

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

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

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

Correct these entries (1)

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. Germany DE-CIX Dusseldorf Düsseldorf, Germany · PeeringDB 1214
    ProblemPeeringDB hasThe export has
    Port speed differs1G200G
    • In the entry with IPv4 185.1.171.42: set Speed to 200000 (200G) (now 1000).

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, 20263
Oct 26, 20263
Oct 25, 20263
Oct 24, 20263
Oct 23, 20263
Oct 22, 20263
Oct 21, 20263
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 Creasa'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 3G across 3 exchanges.

Belgium BelgiumIX Brussels, Ghent, Leuven, Antwerp, Hasselt, Belgium 185.1.127.45 2001:7f8:d2::45 1G Yes PeeringDB
Germany DE-CIX Dusseldorf Düsseldorf, Germany 185.1.171.42 2001:7f8:9e:0:3:3785:0:1 1G 4 routes Both Speed differs
Netherlands ixFabric - Amsterdam Amsterdam, Netherlands 2a0e:8f01:1000:11::115 1G Yes PeeringDB

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

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

Belgium BNIXBrussels, Belgium 84 Unix-Solutions DC Zaventem
Facilities (1)

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

Belgium Unix-Solutions DC ZaventemZaventem 1 of 2