Jet Telecom: PeeringDB fix list
AS263558 · peeringdb.com/net/6599
5 things to fix in Jet Telecom's PeeringDB record, from what its exchanges publish: 2 to add, 3 to check. As of 2026-10-08 21:35 UTC.
Make the changes on Jet Telecom'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 (2)
On the exchange's own member list, but not in Jet Telecom's PeeringDB record. Add one entry per connection with these values.
-
The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
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 (3)
In PeeringDB, but on none of the exchange's own lists. If Jet Telecom has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 80.81.195.128 IPv6 2001:7f8::4:58:0:1 Speed 50000 Mbps (50G) -
IPv4 185.1.131.100 IPv6 2001:7f8:d5:0:4:58:0:1 Speed 50000 Mbps (50G) -
DE-CIX New York New York, United States · PeeringDB 804Not on its IX-F export or website members list
IPv4 206.82.104.212 IPv6 2001:504:36:0:4:58:0:1 Speed 50000 Mbps (50G)
From ixreport.com/net/263558/: 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.