Telecall AS62663
AS62663
Telecall
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.
-
IPv4 195.66.231.91 IPv6 2001:7f8:4::f4c7:1 Speed 200 Mbps (200M) RS peer Yes
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.
-
Problem PeeringDB has The export has Port speed differs 2 × 100G 500M + 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.
-
Problem PeeringDB has The export has Port speed differs 10G 200G - In the entry with IPv4 80.81.196.104: set Speed to 200000 (200G) (now 10000).
-
Problem PeeringDB has The export has Port speed differs 200M 10G - 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
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 6 |
| Nov 18, 2026 | 7 |
| Nov 17, 2026 | 7 |
| Nov 16, 2026 | 7 |
| Nov 15, 2026 | 7 |
| Nov 14, 2026 | 7 |
| Nov 13, 2026 | 7 |
| Nov 12, 2026 | 7 |
| Nov 11, 2026 | 7 |
| Nov 10, 2026 | 7 |
| Nov 9, 2026 | 7 |
| Nov 8, 2026 | 7 |
| Nov 7, 2026 | 7 |
| Nov 6, 2026 | 7 |
| Nov 5, 2026 | 7 |
| Nov 4, 2026 | 7 |
| Nov 3, 2026 | 7 |
| Nov 2, 2026 | 7 |
| Nov 1, 2026 | 7 |
| Oct 31, 2026 | 7 |
| Oct 30, 2026 | 7 |
| Oct 29, 2026 | 7 |
| Oct 28, 2026 | 7 |
| Oct 27, 2026 | 7 |
| Oct 26, 2026 | 7 |
| Oct 25, 2026 | 6 |
| Oct 24, 2026 | 6 |
| Oct 23, 2026 | 6 |
| Oct 22, 2026 | 6 |
| Oct 21, 2026 | 6 |
| Oct 20, 2026 | 7 |
| Oct 19, 2026 | 7 |
| Oct 18, 2026 | 7 |
| Oct 17, 2026 | 7 |
| Oct 16, 2026 | 7 |
| Oct 15, 2026 | 7 |
| Oct 14, 2026 | 7 |
| Oct 13, 2026 | 7 |
| Oct 12, 2026 | 7 |
| Oct 11, 2026 | 7 |
| Oct 10, 2026 | 7 |
| Oct 9, 2026 | 7 |
| Oct 8, 2026 | 7 |
| Oct 7, 2026 | 7 |
| Oct 6, 2026 | 7 |
| Oct 5, 2026 | 7 |
| Oct 4, 2026 | 7 |
| Oct 3, 2026 | 7 |
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.
| AMS-IX Amsterdam, Netherlands | 2 × 100G | Both Speed differs | |
| DE-CIX Frankfurt Frankfurt, Germany | 10G | Both Speed differs | |
| Equinix Miami Miami, United States | 10G | PeeringDB | |
| GNM-IX Amsterdam, Netherlands | 200M | Both Speed differs | |
| LINX LON1 London, United Kingdom | 200M | Not in PeeringDB | |
| NYIIX Los Angeles Los Angeles, United States | 200M | PeeringDB |
Telecall AS62663 lists no facilities in PeeringDB.