ixreport

MYCorous360

AS58578 · Corous360 SDN BHD

0Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
ContentType
OpenPeering policy
0Using the route servers
1Facility in PeeringDB

Tools: Where can I peer with MYCorous360? · Where should MYCorous360 peer next? · Compare MYCorous360 with another network

This network elsewhere: its registry history on RIR Tracker

PeeringDB fix list

Nothing to compare: MYCorous360 isn't on any exchange.

Exchanges over time

This chart fills in as daily counts build up.

Map

Where MYCorous360's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Not on any exchange right now.

Exchanges in its buildings that it isn't on (6)

These exchanges have a switch in a facility where MYCorous360 lists itself in PeeringDB, but don't have MYCorous360 as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Bulgaria NetIXSofia, Bulgaria 204 AIMS Kuala Lumpur
Singapore DE-CIX ASEANSingapore, Singapore 140 AIMS Kuala Lumpur
Malaysia MyIXKuala Lumpur, Malaysia 120 AIMS Kuala Lumpur
Malaysia DE-CIX Kuala LumpurKuala Lumpur, Malaysia 45 AIMS Kuala Lumpur
Malaysia DE-CIX MalaysiaKuala Lumpur, Cyberjaya, Johor Bahru, Malaysia 15 AIMS Kuala Lumpur
Thailand CSL Thai-IX MalaysiaBangkok, Thailand 13 AIMS Kuala Lumpur
Facilities (1)

The buildings MYCorous360 lists in PeeringDB, and how many of the exchanges in each it's on.

Malaysia AIMS Kuala LumpurKuala Lumpur 0 of 6