MegaIX Singapore: operator report

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

Download CSV

Members of MegaIX Singapore that PeeringDB has wrong, from its IX-F export (45 networks, read 2026-10-08 20:54 UTC), against PeeringDB as of 2026-10-08 20:58 UTC. 12 networks to follow up; 2 with a public PeeringDB contact.

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 (5)

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

NetworkOn yourAddressesContact
AS4913 Speedcast Australia Pty LtdIX-F 103.41.12.7
2001:ded::7
No PeeringDB record
AS11158 NTT Global Networks Inc. PeeringDBIX-F 103.41.12.20
2001:ded::14
No public contact
AS134363 EZIT Solutions Pte Ltd PeeringDBIX-F 103.41.12.28
2001:ded::1c
No public contact
AS136168 Campana MYTHIC PeeringDBIX-F 103.41.12.21
2001:ded::15
Policy: email address (needs JavaScript)
AS395717 Wasabi Technologies PeeringDBIX-F 103.41.12.38
2001:ded::26
No public contact

Addresses or port speeds that differ (5)

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

NetworkProblemPeeringDB hasYour export hasContact
AS72 Schlumberger Limited PeeringDB IPv6 address missing from PeeringDBnone2001:ded::2e No public contact
AS58580 Fastrack Technology PeeringDB IPv6 address missing from PeeringDBnone2001:ded::1b No public contact
AS58907 Acquire BPO PeeringDB IPv6 address missing from PeeringDBnone2001:ded::2f No public contact
AS133422 Aviva Asia PeeringDB IPv4 address missing from PeeringDB103.41.12.36103.41.12.36 103.41.12.42 No public contact
IPv6 address missing from PeeringDB2001:ded::242001:ded::24 2001:ded::2a
AS207543 DUG-APIC-AUS PeeringDB IPv6 address missing from PeeringDBnone2001:ded::d Policy: email address (needs JavaScript)

In PeeringDB, not on your lists (2)

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

NetworkIn PeeringDBContact
AS3856 PCH AS3856 PeeringDB 103.41.12.49
2001:ded::31
No public contact
AS30081 CacheFly PeeringDB 103.41.12.57
2001:ded::39
No public contact