ixreport

Telekomunikasi Indonesia Int (TELIN): PeeringDB fix list

AS7713 · peeringdb.com/net/2803

PeeringDB

7 things to fix in Telekomunikasi Indonesia Int (TELIN)'s PeeringDB record, from what its exchanges publish: 5 to add, 2 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on Telekomunikasi Indonesia Int (TELIN)'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 (5)

On the exchange's own member list, but not in Telekomunikasi Indonesia Int (TELIN)'s PeeringDB record. Add one entry per connection with these values.

  1. France DE-CIX Marseille Marseille, France · PeeringDB 1149From its IX-F export and website members list
    IPv4185.1.47.27
    IPv62001:7f8:36::1e21:0:1
    Speed10000 Mbps (10G)
    RS peerYes
  2. Italy DE-CIX Palermo Palermo, Italy · PeeringDB 1131From its IX-F export and website members list
    IPv4185.1.46.7
    IPv62001:7f8:32::1e21:0:1
    Speed1000 Mbps (1G)
    RS peerYes
  3. United Kingdom IXLeeds Leeds / Western Yorkshire, United Kingdom · PeeringDB 435From its IX-F export and website members list
    IPv491.217.231.44
    IPv62001:7f8:67::1e21:1
    SpeedNot published
    RS peerNot published
  4. Italy MIX-IT Milan, Italy · PeeringDB 35From its IX-F export
    IPv4217.29.66.227
    IPv62001:7f8:b:100:1d1:a5d0:7713:227
    Speed10000 Mbps (10G)
    RS peerYes
  5. Sweden Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden · PeeringDB 2846From its IX-F export
    IPv4194.68.128.123
    IPv62001:7f8:d:fe::123
    Speed2000000 Mbps (2T)
    RS peerYes

Correct these entries (2)

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 IIX-Jakarta Jakarta, Indonesia · PeeringDB 210
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 10G10G

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

  2. ProblemPeeringDB hasThe export has
    Port speed differs1G2T
    • In the entry with IPv4 194.68.123.123: set Speed to 2000000 (2T) (now 1000).

From ixreport.com/net/7713/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.