ixreport

SingularCDN: PeeringDB fix list

AS266390 · peeringdb.com/net/12641

PeeringDB

12 things to fix in SingularCDN's PeeringDB record, from what its exchanges publish: 11 to add, 1 to check. As of 2026-10-08 22:13 UTC.

Make the changes on SingularCDN'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 (11)

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

  1. Brazil IX.br (PTT.br) Belém Belém/PA, Brazil · PeeringDB 711From 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) Cuiabá Cuiabá/MT, Brazil · PeeringDB 859From 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.

  3. Brazil IX.br (PTT.br) Florianópolis Florianópolis/SC, Brazil · PeeringDB 175From 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.

  4. Brazil IX.br (PTT.br) Fortaleza Fortaleza/CE, Brazil · PeeringDB 710From 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. Brazil IX.br (PTT.br) João Pessoa João Pessoa/PB, Brazil · PeeringDB 1983From 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.

  6. Brazil IX.br (PTT.br) Manaus Manaus/AM, Brazil · PeeringDB 707From 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.

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

  8. Brazil IX.br (PTT.br) Recife Recife/PE, Brazil · PeeringDB 705From 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.

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

  10. Brazil IX.br (PTT.br) Salvador Salvador/BA, Brazil · PeeringDB 556From 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.

  11. 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.

Check these entries (1)

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

  1. United States FL-IX Miami, United States · PeeringDB 954Not on its IX-F export or website members list
    IPv4206.41.108.100
    IPv62001:504:40:108::1:100
    Speed10000 Mbps (10G)

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