Magyar Telekom plc.
AS5483 · Hungarian Telecom
Tools: Where can I peer with Magyar Telekom plc.? · Where should Magyar Telekom plc. peer next? · Compare Magyar Telekom plc. with another network
This network elsewhere: its routes on BGP Report
PeeringDB fix list Printable page · CSV
2 things to fix in Magyar Telekom plc.'s PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-11-19 12:40 UTC.
Make the changes on Magyar Telekom plc.'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 Magyar Telekom plc.'s PeeringDB record. Add one entry per connection with these values.
-
IPv4 86.104.125.136 IPv6 2001:7f8:64:225::5483:1 Speed 10000 Mbps (10G) RS peer Yes PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 193.188.137.139 193.188.137.12 193.188.137.139 IPv6 address missing from PeeringDB none 2001:7f8:35::5483:1 2001:7f8:35::5483:2 Port speed differs 40G 2 × 100G - In the entry with IPv4 193.188.137.139: set IPv6 to 2001:7f8:35::5483:2 (now empty); set Speed to 100000 (100G) (now 40000).
- Add an entry: IPv4 193.188.137.12, IPv6 2001:7f8:35::5483:1, speed 100000 (100G), RS peer yes.
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 Magyar Telekom plc.'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.
| BIX Budapest, Hungary | 40G | Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs | |
| InterLAN-IX Bucharest, Romania | 10G | Not in PeeringDB |
These exchanges have a switch in a facility where Magyar Telekom plc. lists itself in PeeringDB, but don't have Magyar Telekom plc. 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.
Facilities (1)
The buildings Magyar Telekom plc. lists in PeeringDB, and how many of the exchanges in each it's on.
| Dataplex BudapestBudapest | 1 of 3 |