ixreport

Orakom

AS199181 · Orakom

Orakom S.r.l.

4Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
4Using the route servers
1To fix in PeeringDB
4Facilities in PeeringDB

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

Make the changes on Orakom'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. Netherlands AMS-IX Amsterdam, Netherlands · PeeringDB 26
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:1:0:a500:19:9181:1
    • In the entry with IPv4 80.249.214.179: set IPv6 to 2001:7f8:1:0:a500:19:9181:1 (now empty).

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

Exchanges over time

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

Map

Where Orakom'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 31G across 4 exchanges.

Netherlands AMS-IX Amsterdam, Netherlands 80.249.214.179 1G 4 routes Both IPv6 not in PeeringDB
Italy MINAP Milan Milan, Italy 185.1.114.78 10G 4 routes Both
Italy MIX-IT Milan, Italy 217.29.67.24 10G Yes Both
Italy Namex Rome Rome, Italy 193.201.28.49 10G Yes Both

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

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

Bulgaria NetIXSofia, Bulgaria 204 MIX DC CALDERA; Namex Datacenter Rome; Seeweb Milano Caldera
France nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France 160 MIX DC CALDERA; Seeweb Milano Caldera
Italy Equinix MilanMilan, Italy 35 MIX DC CALDERA
Türkiye EURASIA-IX.NETIstanbul, Türkiye 6 MIX DC CALDERA
United States Global Peer ExchangeWashington, United States 6 MIX DC CALDERA; Seeweb Milano Caldera
Facilities (4)

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

Italy MIX DC CALDERAMilan 1 of 6
Italy Seeweb Milano CalderaMilan 1 of 4
Italy Namex Datacenter RomeRome 1 of 2
Italy Panservice DCLatina No exchange