Hostinger International: PeeringDB fix list

AS47583 · peeringdb.com/net/27920

PeeringDB

3 things to fix in Hostinger International's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on Hostinger International's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

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. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 40G2 × 100G
    • In the entry with IPv4 80.81.197.57: set Speed to 100000 (100G) (now 40000).
    • In the entry with IPv4 80.81.197.60: set Speed to 100000 (100G) (now 40000).
  2. India DE-CIX Mumbai Mumbai, India · PeeringDB 832
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 3G2 × 5G
    • In the entry with IPv4 103.27.170.41: set Speed to 5000 (5G) (now 3000).
    • In the entry with IPv4 103.27.170.60: set Speed to 5000 (5G) (now 3000).
  3. Indonesia IIX-Jakarta Jakarta, Indonesia · PeeringDB 210
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 10G100G + 10G
    • In the entry with IPv4 123.108.12.20: set Speed to 100000 (100G) (now 10000).

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

From ixreport.com/net/47583/: 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.