ixreport

MENGMENG-AS

AS218643

MENGMENG NETWORK LLC

PeeringDB Follow changes
1Exchange
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
–Type
–Peering policy
1Using the route servers
1To fix in PeeringDB
0Facilities in PeeringDB

Tools: Where can I peer with MENGMENG-AS? · Where should MENGMENG-AS peer next?

PeeringDB fix list Printable page

One thing to fix in MENGMENG-AS's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-10-11 06:39 UTC.

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

  1. United Kingdom Kent Internet Exchange Point Kent, United Kingdom · PeeringDB 4316From its IX-F export
    IPv4185.0.24.164
    IPv62001:7f8:aa::164
    Speed10000 Mbps (10G)
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

Exchanges over time

This chart fills in as daily counts build up; the first was Oct 11, 2026.

Exchanges
United Kingdom Kent Internet Exchange Point Kent, United Kingdom 185.0.24.164 2001:7f8:aa::164 10G Yes Not in PeeringDB

MENGMENG-AS lists no facilities in PeeringDB.

Recent changes Search them

  • Oct 11, 2026 [IXF] AS218643 MENGMENG-AS added to Kent Internet Exchange Point