ixreport

Lancaster-Lebanon IU13 WAN

AS14773 · IU13

Lancaster-Lebanon Intermediate Unit 13

5Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Educational/ResearchType
OpenPeering policy
4Using the route servers
1To fix in PeeringDB
3Facilities in PeeringDB

Tools: Where can I peer with Lancaster-Lebanon IU13 WAN? · Where should Lancaster-Lebanon IU13 WAN peer next? · Compare Lancaster-Lebanon IU13 WAN with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in Lancaster-Lebanon IU13 WAN's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on Lancaster-Lebanon IU13 WAN'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. United States DE-CIX New York New York, United States · PeeringDB 804
    ProblemPeeringDB hasThe export has
    Port speed differs30G100G
    • In the entry with IPv4 206.82.104.249: set Speed to 100000 (100G) (now 30000).

Exchanges over time

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

Map

Where Lancaster-Lebanon IU13 WAN'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 430G across 5 exchanges.

United States DE-CIX New York New York, United States 206.82.104.249 2001:504:36::39b5:0:1 30G 50 routes Both Speed differs
United States NYIIX New York New York, United States 198.32.161.13 2001:504:1::a501:4773:1 100G Yes PeeringDB
United States NYIIX Philadelphia Philadelphia, United States 206.51.30.13 2001:504:1:9:0:a501:4773:1 100G PeeringDB
United States PhillyIX Philadelphia, United States 206.80.234.35 2001:504:90::35 100G Yes Both
United States PIT-IX Pittsburgh, United States 206.71.141.13 2001:504:77::13 100G 51 routes Both

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

These exchanges have a switch in a facility where Lancaster-Lebanon IU13 WAN lists itself in PeeringDB, but don't have Lancaster-Lebanon IU13 WAN 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 165 Halsey Meet-Me Room; Netrality Philadelphia - 401 N Broad
United States GraniteIXSalt Lake City, UT, United States 23 165 Halsey Meet-Me Room
United States MegaIX New YorkNew York, United States 22 165 Halsey Meet-Me Room
Facilities (3)

The buildings Lancaster-Lebanon IU13 WAN lists in PeeringDB, and how many of the exchanges in each it's on.

United States 165 Halsey Meet-Me RoomNewark 2 of 5
United States Netrality Philadelphia - 401 N BroadPhiladelphia 2 of 3
United States DataBank Pittsburgh (PIT1)Pittsburgh 1 of 1