Moldtelecom: PeeringDB fix list
AS8926 · peeringdb.com/net/3149
3 things to fix in Moldtelecom's PeeringDB record, from what its exchanges publish: 2 to add, 1 to correct. As of 2026-10-08 21:56 UTC.
Make the changes on Moldtelecom'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 (2)
On the exchange's own member list, but not in Moldtelecom's PeeringDB record. Add one entry per connection with these values.
-
IPv4 178.18.237.91 IPv6 2a03:5f80:4:2::237:91 Speed 100000 Mbps (100G) 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.
-
IPv4 185.1.227.60 IPv6 2001:67c:29f0::8926:1 Speed Not published 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 Port speed differs 2 × 40G 2 × 20G - In the entry with IPv4 80.81.194.94: set Speed to 20000 (20G) (now 40000).
- In the entry with IPv4 80.81.195.94: set Speed to 20000 (20G) (now 40000).
From ixreport.com/net/8926/: 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.