Metwide Communications: PeeringDB fix list
AS9627
One thing to fix in Metwide Communications's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-10-08 21:56 UTC.
AS9627 has no PeeringDB record. Create one (register, then request the network for your organisation) before adding these exchanges.
Add these exchanges (1)
On the exchange's own member list, but not in Metwide Communications's PeeringDB record. Add one entry per connection with these values.
-
IPv4 103.26.69.81 IPv6 2001:dea:0:10::151 Speed Not published RS peer No PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
From ixreport.com/net/9627/: 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.