ixreport

Workonline Communications: PeeringDB fix list

AS37271 · peeringdb.com/net/3539

PeeringDB

5 things to fix in Workonline Communications's PeeringDB record, from what its exchanges publish: 1 to add, 4 to correct. As of 2026-10-08 21:56 UTC.

Make the changes on Workonline Communications'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 Workonline Communications'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.

Correct these entries (4)

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 CINX Cape Town, South Africa · PeeringDB 344
    ProblemPeeringDB hasThe export has
    Port speed differs10G20G
    • In the entry with IPv4 196.223.22.62: set Speed to 20000 (20G) (now 10000).

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

  2. Nigeria IXPN Lagos Lagos, Nigeria · PeeringDB 488
    ProblemPeeringDB hasThe export has
    IPv6 address in PeeringDB, not in the export2001:43f8:bb1::137none
    Port speed differs10G30G
    • In the entry with IPv4 196.216.148.137: set IPv6 to (empty) (now 2001:43f8:bb1::137); set Speed to 30000 (30G) (now 10000).
  3. South Africa NAPAfrica IX Durban Durban, South Africa · PeeringDB 969
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 10G2 × 20G
    • In the entry with IPv4 196.10.141.45: set Speed to 20000 (20G) (now 10000).
    • In the entry with IPv4 196.10.141.76: set Speed to 20000 (20G) (now 10000).

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

  4. South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G3 × 100G + 2 × 10G

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