ixreport

Sign In: PeeringDB fix list

AS140607 · peeringdb.com/net/25798

PeeringDB

2 things to fix in Sign In's PeeringDB record, from what its exchanges publish: 1 to add, 1 to check. As of 2026-10-08 18:53 UTC.

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

  1. Pakistan PKIX Lahore Lahore, Pakistan · PeeringDB 3743From its IX-F export

    2 connections, so 2 entries:

    IPv4–
    IPv62001:db8::120
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4–
    IPv62001:db8::121
    Speed10000 Mbps (10G)
    RS peerYes

    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.

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If Sign In has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Pakistan Pakistan Internet Exchange (PIE) Karachi Karachi, Pakistan · PeeringDB 4271Not on its website members list
    IPv458.181.127.5
    IPv62001:df2:b940:0:2:253f:0:1
    Speed10000 Mbps (10G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

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