T-2 d.o.o.: PeeringDB fix list
AS34779 · peeringdb.com/net/8611
2 things to fix in T-2 d.o.o.'s PeeringDB record, from what its exchanges publish: 1 to correct, 1 to check. As of 2026-10-08 18:53 UTC.
Make the changes on T-2 d.o.o.'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.
-
Problem PeeringDB has The export has Port speed differs 2 × 100G 25G - In the entry with IPv4 185.0.20.34: set Speed to 25000 (25G) (now 100000).
- In the entry with IPv4 185.0.20.75: set Speed to 25000 (25G) (now 100000).
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If T-2 d.o.o. has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 91.220.194.114 IPv6 2001:7f8:46::3:4779 Speed 100000 Mbps (100G) IPv4 91.220.194.14 IPv6 2001:7f8:46:0:1:0:3:4779 Speed 100000 Mbps (100G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
From ixreport.com/net/34779/: 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.