ixreport

PLANET1

AS63343 · P1N

Planet One Networks

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

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

Make the changes on PLANET1'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 PLANET1's PeeringDB record. Add one entry per connection with these values.

  1. United States Ohio IX Columbus, United States · PeeringDB 869From its IX-F export and website members list
    IPv4206.53.204.107
    IPv6–
    Speed10000 Mbps (10G)
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

Exchanges over time

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

Map

Where PLANET1'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 20G across 2 exchanges.

United States CMH-IX Columbus, United States 206.82.108.11 2001:504:94::11 10G PeeringDB
United States Ohio IX Columbus, United States 206.53.204.107 10G Yes Not in PeeringDB

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

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

United States FD-IX - OhioCleveland, Ohio, United States 5 WOW! Business (Columbus Datacenter); Cologix COL1; Cologix COL2 and 1 more
Facilities (4)

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

United States WOW! Business (Columbus Datacenter)Columbus 2 of 3
United States Cologix COL1Columbus 1 of 2
United States Cologix COL2Columbus 1 of 2
United States Cologix COL3Columbus 1 of 2