ixreport

AMS-IX Singapore: operator report

Singapore, Singapore · PeeringDB 3800 · ixreport.com/ix/3800/report/

Download CSV

Members of AMS-IX Singapore that PeeringDB has wrong, from its IX-F export (14 networks, read 2026-10-08 18:46 UTC), against PeeringDB as of 2026-10-08 18:53 UTC. 3 networks to follow up.

Contacts are the networks' public PeeringDB contacts: the peering (policy) contact where there is one, else technical, then NOC. Networks keep these themselves on PeeringDB.

On your lists, missing from PeeringDB (1)

These networks could add AMS-IX Singapore to their PeeringDB record. Networks with no PeeringDB record would need to create one first.

NetworkOn yourAddressesContact
AS16509 Amazon.com PeeringDBIX-F 112.137.24.160
112.137.24.238
2A00:8422:AE5::A501:6509:1
2A00:8422:AE5::A501:6509:2
2 × 10G
No public contact

Addresses or port speeds that differ (2)

PeeringDB against your IX-F export, for the 13 networks in both. Either the network's PeeringDB record or the export is out of date.

NetworkProblemPeeringDB hasYour export hasContact
AS4775 Globe Telecom PeeringDB Port speed differs10G100G No public contact
AS133160 AMS-IX Singapore Route Servers PeeringDB Port speed differs2 × 1G2 × 10G No public contact

In PeeringDB, not on your lists (0)

Either your lists are missing these networks, or they've left and their PeeringDB record is out of date.

None.