ixreport

Zextel

AS49954

Progress Technology LLC

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

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

Make the changes on Zextel'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 GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2a03:5f80:4::226:72
    • In the entry with IPv4 178.18.226.72: set IPv6 to 2a03:5f80:4::226:72 (now empty).

    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

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

Map

Where Zextel'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 60G across 6 exchanges.

Netherlands Global-IX Amsterdam, Netherlands 109.239.136.223 10G Yes PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.226.72 10G Yes Both IPv6 not in PeeringDB
Germany PITER-IX Frankfurt Frankfurt, Germany 31.44.187.6 10G Yes PeeringDB
Finland PITER-IX Helsinki Helsinki, Finland 193.27.37.64 10G Yes PeeringDB
Russia PITER-IX Moscow Moscow, Russia 185.0.13.90 10G Yes PeeringDB
Russia PITER-IX Saint-Petersburg Saint-Petersburg, Russia 185.1.152.86 10G Yes PeeringDB

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

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

Russia MSK-IX Saint-PetersburgSt.Petersburg, Russia 71 Raduga-2
Russia CLOUD-IX MSKMoscow, Russia 52 Raduga-2
Russia CLOUD-IX SPBSt. Petersburg, Russia 25 Raduga-2
Russia PIRIXSt.Petersburg, Russia 6 Raduga-2
Facilities (1)

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

Russia Raduga-2St. Petersburg 4 of 8