ixreport

Telecall AS62663

AS62663

Telecall

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

Tools: Where can I peer with Telecall AS62663? · Where should Telecall AS62663 peer next? · Compare Telecall AS62663 with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

4 things to fix in Telecall AS62663's PeeringDB record, from what its exchanges publish: 1 to add, 3 to correct. As of 2026-11-19 12:40 UTC.

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

  1. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18From its IX-F export and website members list
    IPv4195.66.231.91
    IPv62001:7f8:4::f4c7:1
    Speed200 Mbps (200M)
    RS peerYes

Correct these entries (3)

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 AMS-IX Amsterdam, Netherlands · PeeringDB 26
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G500M + 250M
    • In the entry with IPv4 80.249.211.109: set Speed to 250 (250M) (now 100000).
    • In the entry with IPv4 80.249.212.130: set Speed to 500 (500M) (now 100000).

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

  2. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs10G200G
    • In the entry with IPv4 80.81.196.104: set Speed to 200000 (200G) (now 10000).
  3. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    Port speed differs200M10G
    • In the entry with IPv4 178.18.236.22: set Speed to 10000 (10G) (now 200).

    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

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

Map

Where Telecall AS62663'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 220.6G across 6 exchanges.

Netherlands AMS-IX Amsterdam, Netherlands 80.249.211.109
80.249.212.130
2001:7f8:1::a506:2663:1
2001:7f8:1::a506:2663:2
2 × 100G Down Both Speed differs
Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.196.104 2001:7f8::f4c7:0:1 10G Down Both Speed differs
United States Equinix Miami Miami, United States 198.32.243.225 2001:504:0:6:0:6:2663:1 10G Yes PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.236.22 2a03:5f80:4:2::236:22 200M Yes Both Speed differs
United Kingdom LINX LON1 London, United Kingdom 195.66.231.91 2001:7f8:4::f4c7:1 200M Down Not in PeeringDB
United States NYIIX Los Angeles Los Angeles, United States 149.112.104.52 2001:504:a::a506:2663:1 200M PeeringDB

Telecall AS62663 lists no facilities in PeeringDB.