ixreport

Twitter, Inc.: PeeringDB fix list

AS13414 · peeringdb.com/net/3308

PeeringDB

5 things to fix in Twitter, Inc.'s PeeringDB record, from what its exchanges publish: 5 to add. As of 2026-10-08 18:53 UTC.

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

  1. Japan BBIX Tokyo Tokyo, Japan · PeeringDB 126From 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.

  2. Singapore DE-CIX ASEAN Singapore, Singapore · PeeringDB 3472From its IX-F export and website members list
    IPv4103.162.254.86
    IPv62001:df6:480::3466:0:1
    Speed10000 Mbps (10G)
    RS peerYes
  3. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31From its IX-F export and website members list

    2 connections, so 2 entries:

    IPv480.81.192.10
    IPv62001:7f8::3466:0:1
    Speed100000 Mbps (100G)
    RS peerYes
    IPv480.81.194.21
    IPv62001:7f8::3466:0:2
    Speed100000 Mbps (100G)
    RS peerYes
  4. Brazil IX.br (PTT.br) São Paulo São Paulo/SP, Brazil · PeeringDB 171From 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.

  5. Japan JPNAP Tokyo Tokyo, Japan · PeeringDB 95From 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.

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