ixreport

InterServer

AS19318 · NJIIX

InterServer, Inc

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

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

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

  1. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31From its IX-F export and website members list
    IPv480.81.193.232
    IPv62001:7f8::4b76:0:1
    Speed100000 Mbps (100G)
    RS peerYes

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 InterServer'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 300G across 3 exchanges.

Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.193.232 2001:7f8::4b76:0:1 100G Down Not in PeeringDB
United States DE-CIX New York New York, United States 206.82.104.228 2001:504:36::4b76:0:1 100G Up, 0 routes Both
United States NYIIX New York New York, United States 198.32.160.131 2001:504:1::a501:9318:1 100G Yes PeeringDB

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

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

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

United States Equinix NY2/NY4/NY5/NY6 - New York, SecaucusSecaucus 2 of 9
United States 165 Halsey Meet-Me RoomNewark 2 of 5
United States CoreSite - Secaucus (NY2)Secaucus 1 of 3
United States Equinix LA3/LA4 - Los Angeles, El SegundoEl Segundo 0 of 3
United States Centersquare New Jersey (EWR5)Secaucus 0 of 2
United States 365 Data Centers New Jersey (NJ1)Bridgewater Township No exchange
United States 365 Data Centers Richardson (TX1)Richardson No exchange
United States Dataverge Jersey CityJersey City No exchange
United States H5 Data Centers Secaucus (NJ01)Secaucus No exchange
United States InterServer Teb2Secaucus No exchange