Vocus Communications: PeeringDB fix list
AS4826 · peeringdb.com/net/1703
3 things to fix in Vocus Communications's PeeringDB record, from what its exchanges publish: 2 to add, 1 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on Vocus Communications'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 Vocus Communications's PeeringDB record. Add one entry per connection with these values.
-
IPv4 103.247.139.27 IPv6 2001:df0:296::a500:4826:1 Speed 1000 Mbps (1G) RS peer Yes PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
Correct these entries (1)
Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.
-
Problem PeeringDB has The export has Port speed differs 40G 100G - In the entry with IPv4 27.106.192.55: set Speed to 100000 (100G) (now 40000).
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/4826/: 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.