Lumen AS3356: PeeringDB fix list

AS3356 · peeringdb.com/net/504

PeeringDB

11 things to fix in Lumen AS3356's PeeringDB record, from what its exchanges publish: 9 to add, 2 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on Lumen AS3356'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 (9)

On the exchange's own member list, but not in Lumen AS3356's PeeringDB record. Add one entry per connection with these values.

  1. Brazil IX.br (PTT.br) Belo Horizonte Belo Horizonte/MG, Brazil · PeeringDB 176From its IX-F export

    The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

  2. Brazil IX.br (PTT.br) Curitiba Curitiba, Brazil · PeeringDB 174From its IX-F export and website members list

    The exchange's IX-F export and website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

  3. Brazil IX.br (PTT.br) Fortaleza Fortaleza/CE, Brazil · PeeringDB 710From 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.

  4. Brazil IX.br (PTT.br) Porto Alegre Porto Alegre/RS, Brazil · PeeringDB 173From 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.

  5. Brazil IX.br (PTT.br) Rio de Janeiro Rio de Janeiro/RJ, Brazil · PeeringDB 177From 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.

  6. Brazil IX.br (PTT.br) São Paulo São Paulo/SP, Brazil · PeeringDB 171From its IX-F export and website members list

    The exchange's IX-F export and website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

  7. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18From its IX-F export and website members list
    IPv4195.66.224.77
    IPv62001:7f8:4::ddd:1
    Speed10000 Mbps (10G)
    RS peerNo
  8. Ecuador NAP.EC - GYE Guayaquil/GYE, Ecuador · PeeringDB 1042From its IX-F export
    IPv4200.110.120.6
    IPv62001:13c7:6f80::3356:1
    Speed100000 Mbps (100G)
    RS peerYes

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

  9. Ecuador NAP.EC - UIO Quito/UIO, Ecuador · PeeringDB 253From its IX-F export

    2 connections, so 2 entries:

    IPv4200.1.6.6
    IPv62001:13c7:6006::3356:1
    Speed100000 Mbps (100G)
    RS peerYes
    IPv4200.1.6.11
    IPv62001:13c7:6006::3356:2
    Speed100000 Mbps (100G)
    RS peerYes

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

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. South Africa NAPAfrica IX Cape Town Cape Town, South Africa · PeeringDB 597
    ProblemPeeringDB hasThe export has
    Port speed differs70G20G
    • In the entry with IPv4 196.60.70.40: set Speed to 20000 (20G) (now 70000).

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

  2. South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592
    ProblemPeeringDB hasThe export has
    Port speed differs70G20G
    • In the entry with IPv4 196.60.8.213: set Speed to 20000 (20G) (now 70000).

    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/3356/: 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.