Deutsche Telekom GBSN: PeeringDB fix list

AS20936

2 things to fix in Deutsche Telekom GBSN's PeeringDB record, from what its exchanges publish: 2 to add. As of 2026-10-08 20:58 UTC.

AS20936 has no PeeringDB record. Create one (register, then request the network for your organisation) before adding these exchanges.

Add these exchanges (2)

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

  1. Netherlands AMS-IX Amsterdam, Netherlands · PeeringDB 26From 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.

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

  2. Hong Kong AMS-IX Hong Kong Hong Kong, Hong Kong · PeeringDB 577From 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.

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