MiraLogic Telecommunication Systems: PeeringDB fix list
AS12668 · peeringdb.com/net/9048
4 things to fix in MiraLogic Telecommunication Systems's PeeringDB record, from what its exchanges publish: 1 to add, 3 to check. As of 2026-10-08 20:58 UTC.
Make the changes on MiraLogic Telecommunication Systems'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 MiraLogic Telecommunication Systems's PeeringDB record. Add one entry per connection with these values.
-
2 connections, so 2 entries:
IPv4 178.18.233.16 IPv6 2a03:5f80:4:1::233:16 Speed 30000 Mbps (30G) RS peer Yes IPv4 178.18.225.156 IPv6 2a03:5f80:4::225:156 Speed 30000 Mbps (30G) 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.
Check these entries (3)
In PeeringDB, but on none of the exchange's own lists. If MiraLogic Telecommunication Systems has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 195.208.210.247 IPv6 2001:7f8:20:101::210:247 Speed Not published -
IPv4 193.232.87.247 IPv6 2001:7f8:20:401::87:247 Speed Not published -
IPv4 194.226.100.247 IPv6 2001:7f8:20:201::100:247 Speed Not published IPv4 194.226.102.247 IPv6 2001:7f8:20:202::102:247 Speed Not published
From ixreport.com/net/12668/: 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.