Datagram
AS26163 · dgram
Tools: Where can I peer with Datagram? · Where should Datagram peer next? · Compare Datagram with another network
This network elsewhere: its registry history on RIR Tracker
PeeringDB fix list Printable page · CSV
One thing to fix in Datagram's PeeringDB record, from what its exchanges publish: 1 to check. As of 2026-11-19 12:40 UTC.
Make the changes on Datagram's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Datagram has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 – IPv6 – Speed 10000 Mbps (10G)
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 2 |
| Nov 18, 2026 | 2 |
| Nov 17, 2026 | 2 |
| Nov 16, 2026 | 2 |
| Nov 15, 2026 | 2 |
| Nov 14, 2026 | 2 |
| Nov 13, 2026 | 2 |
| Nov 12, 2026 | 2 |
| Nov 11, 2026 | 2 |
| Nov 10, 2026 | 2 |
| Nov 9, 2026 | 2 |
| Nov 8, 2026 | 2 |
| Nov 7, 2026 | 2 |
| Nov 6, 2026 | 2 |
| Nov 5, 2026 | 2 |
| Nov 4, 2026 | 2 |
| Nov 3, 2026 | 2 |
| Nov 2, 2026 | 2 |
| Nov 1, 2026 | 2 |
| Oct 31, 2026 | 2 |
| Oct 30, 2026 | 2 |
| Oct 29, 2026 | 2 |
| Oct 28, 2026 | 2 |
| Oct 27, 2026 | 2 |
| Oct 26, 2026 | 2 |
| Oct 25, 2026 | 2 |
| Oct 24, 2026 | 2 |
| Oct 23, 2026 | 2 |
| Oct 22, 2026 | 2 |
| Oct 21, 2026 | 2 |
| Oct 20, 2026 | 2 |
| Oct 19, 2026 | 2 |
| Oct 18, 2026 | 2 |
| Oct 17, 2026 | 2 |
| Oct 16, 2026 | 2 |
| Oct 15, 2026 | 2 |
| Oct 14, 2026 | 2 |
| Oct 13, 2026 | 2 |
| Oct 12, 2026 | 2 |
| Oct 11, 2026 | 2 |
| Oct 10, 2026 | 2 |
| Oct 9, 2026 | 2 |
| Oct 8, 2026 | 2 |
| Oct 7, 2026 | 2 |
| Oct 6, 2026 | 2 |
| Oct 5, 2026 | 2 |
| Oct 4, 2026 | 2 |
| Oct 3, 2026 | 2 |
Map
Where Datagram'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.
These exchanges have a switch in a facility where Datagram lists itself in PeeringDB, but don't have Datagram 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.
| Any2WestLos Angeles and Silicon Valley, United States | 284 | |
| DE-CIX New YorkNew York, United States | 281 | |
| NetIXSofia, Bulgaria | 204 | |
| NYIIX New YorkNew York, United States | 186 | |
| BBIX US-WestWest Coast, United States | 87 | |
| Digital Realty New YorkNew York/New Jersey, United States | 53 | |
| JumboIX PeruLima, Peru | 27 | |
| MegaIX Los AngelesLos Angeles, United States | 27 | |
| GraniteIXSalt Lake City, UT, United States | 23 | |
| MegaIX New YorkNew York, United States | 22 | |
| NYIIX Los AngelesLos Angeles, United States | 21 | |
| Global Peer ExchangeWashington, United States | 6 | |
| GNM-IX USNew York, United States | 4 |
Facilities (7)
The buildings Datagram lists in PeeringDB, and how many of the exchanges in each it's on.
| Digital Realty NYC (60 Hudson)New York | 0 of 7 | |
| Digital Realty NYC (111 8th Ave)New York | 0 of 6 | |
| 165 Halsey Meet-Me RoomNewark | 0 of 5 | |
| CoreSite - Los Angeles (LA1) One WilshireLos Angeles | 0 of 5 | |
| 60 HudsonNew York | 0 of 2 | |
| 375 Pearl, Intergate.ManhattanNew York | 0 of 1 | |
| Newport Financial CenterJersey City | No exchange |