Asteroid Amsterdam: operator report
Amsterdam, Netherlands · PeeringDB 1812 · ixreport.com/ix/1812/report/
Members of Asteroid Amsterdam that PeeringDB has wrong, from its IX-F export (27 networks, read 2026-10-08 18:46 UTC), against PeeringDB as of 2026-10-08 18:53 UTC. 12 networks to follow up; 4 with a public PeeringDB contact.
Contacts are the networks' public PeeringDB contacts: the peering (policy) contact where there is one, else technical, then NOC. Networks keep these themselves on PeeringDB.
On your lists, missing from PeeringDB (9)
These networks could add Asteroid Amsterdam to their PeeringDB record. Networks with no PeeringDB record would need to create one first.
| Network | On your | Addresses | Contact |
|---|---|---|---|
| AS1103 SURF | IX-F | 185.1.94.21 2001:7f8:b6::44f:1 10G |
Policy: email address (needs JavaScript) |
| AS3303 Swisscom | IX-F | 185.1.94.19 2001:7f8:b6::ce7:1 10G |
No public contact |
| AS8455 atom86 | IX-F | 185.1.94.31 2001:7f8:b6::2107:1 10G |
Technical: email address (needs JavaScript) +3197010256194 |
| AS20940 Akamai Technologies | IX-F | 185.1.94.11 2001:7f8:b6::51cc:1 100G |
No public contact |
| AS22822 Edgio - AS22822 | IX-F | 185.1.94.38 185.1.94.42 2001:7f8:b6::5926:1 2001:7f8:b6::5926:2 2 × 20G |
No public contact |
| AS24875 NovoServe B.V. | IX-F | 185.1.94.13 2001:7f8:b6::612b:1 100G |
No public contact |
| AS30781 Free Pro | IX-F | 185.1.94.23 2001:7f8:b6::783d:1 10G |
Technical: email address (needs JavaScript) +33488006510 |
| AS49981 Worldstream BV | IX-F | 185.1.94.33 2001:7f8:b6::c33d:1 10G |
No public contact |
| AS51088 A2B Internet | IX-F | 185.1.94.17 2001:7f8:b6::c790:1 10G |
Policy: email address (needs JavaScript) |
Addresses or port speeds that differ (1)
PeeringDB against your IX-F export, for the 18 networks in both. Either the network's PeeringDB record or the export is out of date.
| Network | Problem | PeeringDB has | Your export has | Contact |
|---|---|---|---|---|
| AS30132 ISC F-ROOT AMS1 | Port speed differs | 1G | 10G | No public contact |
In PeeringDB, not on your lists (2)
Either your lists are missing these networks, or they've left and their PeeringDB record is out of date.