ixreport

Medialink Global Mandiri

AS64297 · Globallink

PT Medialink Global Mandiri

5Exchanges
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
–Type
SelectivePeering policy
4Using the route servers
4To fix in PeeringDB
0Facilities in PeeringDB

Tools: Where can I peer with Medialink Global Mandiri? · Where should Medialink Global Mandiri peer next? · Compare Medialink Global Mandiri with another network

This network elsewhere: the registry history of AS64297-AS64316, the block AS64297 is in, on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

4 things to fix in Medialink Global Mandiri's PeeringDB record, from what its exchanges publish: 1 to add, 3 to correct. As of 2026-11-19 12:40 UTC.

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

  1. Indonesia CXC Jakarta Jakarta, Indonesia · PeeringDB 2737From 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 (3)

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. Indonesia AIX Tapos, Depok, Indonesia · PeeringDB 4449
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2401:91e0:31::642:97:1
    • In the entry with IPv4 43.254.82.85: set IPv6 to 2401:91e0:31::642:97:1 (now empty).

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

  2. Indonesia IIX-Jakarta Jakarta, Indonesia · PeeringDB 210
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7fa:2:5::24c
    • In the entry with IPv4 123.108.10.60: set IPv6 to 2001:7fa:2:5::24c (now empty).

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

  3. Indonesia JKT-IX Jakarta, Indonesia · PeeringDB 2476
    ProblemPeeringDB hasThe export has
    Port speed differs10G1G
    • In the entry with IPv4 119.11.185.181: set Speed to 1000 (1G) (now 10000).

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, 20265
Nov 7, 20265
Nov 6, 20265
Nov 5, 20265
Nov 4, 20265
Nov 3, 20265
Nov 2, 20265
Nov 1, 20265
Oct 31, 20265
Oct 30, 20265
Oct 29, 20265
Oct 28, 20265
Oct 27, 20265
Oct 26, 20265
Oct 25, 20265
Oct 24, 20265
Oct 23, 20265
Oct 22, 20265
Oct 21, 20265
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, 20264
Oct 10, 20264
Oct 9, 20264
Oct 8, 20264
Oct 7, 20264
Oct 6, 20264
Oct 5, 20264
Oct 4, 20264
Oct 3, 20264

Map

Where Medialink Global Mandiri'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 31G, at the 4 of 5 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Indonesia AIX Tapos, Depok, Indonesia 43.254.82.85 10G Yes Both IPv6 not in PeeringDB
Indonesia BIX Jakarta Jakarta, Indonesia 218.100.41.165 1G Yes PeeringDB
Indonesia CXC Jakarta Jakarta, Indonesia Not in PeeringDB
Indonesia IIX-Jakarta Jakarta, Indonesia 123.108.10.60 10G Yes Both IPv6 not in PeeringDB
Indonesia JKT-IX Jakarta, Indonesia 119.11.185.181 10G Yes Both Speed differs

Medialink Global Mandiri lists no facilities in PeeringDB.