ABQIX: operator report
Albuquerque, United States · PeeringDB 3322 · ixreport.com/ix/3322/report/
Members of ABQIX that PeeringDB has wrong, from its IX-F export (16 networks, read 2026-10-08 20:54 UTC), against PeeringDB as of 2026-10-08 20:58 UTC. 11 networks to follow up; 1 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 (6)
These networks could add ABQIX to their PeeringDB record. Networks with no PeeringDB record would need to create one first.
| Network | On your | Addresses | Contact |
|---|---|---|---|
| AS10381 Southwest Cyberport | IX-F | 206.83.42.4 2001:504:9a::4 1G |
No public contact |
| AS14818 Cyber Mesa Computer Systems | IX-F | 206.83.42.5 2001:504:9a::5 1G |
No public contact |
| AS16545 OSSDS | IX-F | 206.83.42.3 2001:504:9a::3 10G |
No public contact |
| AS21782 Plateau Telecommunications | IX-F | 206.83.42.13 2001:504:9a::13 10G |
No public contact |
| AS33201 Tilver Enterprises | IX-F | 206.83.42.1 2001:504:9a::1 1G |
No public contact |
| AS394991 SWC TELESOLUTIONS | IX-F | 206.83.42.8 2001:504:9a::8 10G |
No public contact |
Addresses or port speeds that differ (3)
PeeringDB against your IX-F export, for the 10 networks in both. Either the network's PeeringDB record or the export is out of date.
| Network | Problem | PeeringDB has | Your export has | Contact |
|---|---|---|---|---|
| AS13335 Cloudflare | IPv6 address missing from PeeringDB | none | 2001:504:9a::11 | Policy: email address (needs JavaScript) +16503198930email address (needs JavaScript) |
| AS26974 bigbyte.cc Corp | IPv4 address differs | 206.83.42.1 | 206.83.42.14 | No public contact |
| IPv6 address missing from PeeringDB | none | 2001:504:9a::14 | ||
| AS33201 Tilver Enterprises | Address belongs to another network in PeeringDB | 206.83.42.1 is AS26974 bigbyte.cc Corp | 206.83.42.1 | 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.