ixreport

M1 Limited

AS4773 · M1

5Exchanges
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
SelectivePeering policy
1Using the route servers
2To fix in PeeringDB
3Facilities in PeeringDB

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

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

2 things to fix in M1 Limited's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on M1 Limited'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 M1 Limited's PeeringDB record. Add one entry per connection with these values.

  1. Japan BBIX Tokyo Tokyo, Japan · PeeringDB 126From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

Correct these entries (1)

Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.

  1. Singapore SGIX Singapore, Singapore · PeeringDB 429
    ProblemPeeringDB hasThe export has
    Port speed differs50G100G
    • In the entry with IPv4 103.16.102.27: set Speed to 100000 (100G) (now 50000).

Exchanges over time

0246Oct 3, 2026Nov 19, 20265
Show as a table
DateExchanges
Nov 19, 20265
Nov 18, 20265
Nov 17, 20265
Nov 16, 20265
Nov 15, 20265
Nov 14, 20265
Nov 13, 20265
Nov 12, 20265
Nov 11, 20265
Nov 10, 20265
Nov 9, 20265
Nov 8, 20264
Nov 7, 20264
Nov 6, 20264
Nov 5, 20264
Nov 4, 20264
Nov 3, 20264
Nov 2, 20264
Nov 1, 20264
Oct 31, 20264
Oct 30, 20264
Oct 29, 20264
Oct 28, 20264
Oct 27, 20264
Oct 26, 20264
Oct 25, 20264
Oct 24, 20264
Oct 23, 20264
Oct 22, 20264
Oct 21, 20264
Oct 20, 20265
Oct 19, 20265
Oct 18, 20265
Oct 17, 20265
Oct 16, 20265
Oct 15, 20265
Oct 14, 20265
Oct 13, 20265
Oct 12, 20265
Oct 11, 20265
Oct 10, 20265
Oct 9, 20265
Oct 8, 20265
Oct 7, 20265
Oct 6, 20265
Oct 5, 20265
Oct 4, 20265
Oct 3, 20265

Map

Where M1 Limited'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

Total port capacity 460G, at the 4 of 5 exchanges with a speed in PeeringDB or the exchange's IX-F export.

United States Any2West Los Angeles and Silicon Valley, United States 206.72.210.60 2001:504:13::210:60 10G PeeringDB
Singapore BBIX Singapore Singapore, Singapore 103.231.152.128
103.231.152.151
2001:df5:b800:bb00::4773:1
2001:df5:b800:bb00::4773:2
2 × 100G PeeringDB
Japan BBIX Tokyo Tokyo, Japan Not in PeeringDB
Singapore Equinix Singapore Singapore, Singapore 27.111.228.58 2001:de8:4::4773:1 200G PeeringDB
Singapore SGIX Singapore, Singapore 103.16.102.27 2001:de8:12:100::27 50G Yes Both Speed differs

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

These exchanges have a switch in a facility where M1 Limited lists itself in PeeringDB, but don't have M1 Limited 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.

Facilities (3)

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

Singapore Equinix SG1 - SingaporeSingapore 3 of 11
Singapore Global Switch SingaporeSingapore 2 of 7
United States CoreSite - Los Angeles (LA1) One WilshireLos Angeles 1 of 5