Magyar Telekom plc.: PeeringDB fix list
AS5483 · peeringdb.com/net/5025
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-10-08 18:53 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.
From ixreport.com/net/5483/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.