Acquire BPO
AS58907 · Acquire BPO
Acquire Asia Pacific Pty Ltd
Tools: Where can I peer with Acquire BPO? · Where should Acquire BPO peer next? · Compare Acquire BPO with another network
This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report
PeeringDB fix list Printable page · CSV
7 things to fix in Acquire BPO's PeeringDB record, from what its exchanges publish: 7 to correct. As of 2026-11-19 12:40 UTC.
Make the changes on Acquire BPO's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Correct these entries (7)
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 IPv6 address missing from PeeringDB none 2001:504:40:108::1:74 - In the entry with IPv4 206.41.108.74: set IPv6 to 2001:504:40:108::1:74 (now empty).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7fa:11:1:0:e61b:0:1 - In the entry with IPv4 218.100.78.145: set IPv6 to 2001:7fa:11:1:0:e61b:0:1 (now empty).
PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7fa:11:4:0:e61b:0:1 - In the entry with IPv4 218.100.53.77: set IPv6 to 2001:7fa:11:4:0:e61b:0:1 (now empty).
PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:dea:0:30::78 - In the entry with IPv4 103.26.71.120: set IPv6 to 2001:dea:0:30::78 (now empty).
PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:ded::2f - In the entry with IPv4 103.41.12.47: set IPv6 to 2001:ded::2f (now empty).
PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:dea:0:10::aa - In the entry with IPv4 103.26.68.170: set IPv6 to 2001:dea:0:10::aa (now empty).
PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:de8:12:100::197 - In the entry with IPv4 103.16.102.197: set IPv6 to 2001:de8:12:100::197 (now empty).
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 15 |
| Nov 18, 2026 | 15 |
| Nov 17, 2026 | 15 |
| Nov 16, 2026 | 15 |
| Nov 15, 2026 | 15 |
| Nov 14, 2026 | 15 |
| Nov 13, 2026 | 15 |
| Nov 12, 2026 | 15 |
| Nov 11, 2026 | 15 |
| Nov 10, 2026 | 15 |
| Nov 9, 2026 | 15 |
| Nov 8, 2026 | 15 |
| Nov 7, 2026 | 15 |
| Nov 6, 2026 | 15 |
| Nov 5, 2026 | 15 |
| Nov 4, 2026 | 15 |
| Nov 3, 2026 | 15 |
| Nov 2, 2026 | 15 |
| Nov 1, 2026 | 15 |
| Oct 31, 2026 | 15 |
| Oct 30, 2026 | 15 |
| Oct 29, 2026 | 15 |
| Oct 28, 2026 | 15 |
| Oct 27, 2026 | 15 |
| Oct 26, 2026 | 15 |
| Oct 25, 2026 | 15 |
| Oct 24, 2026 | 15 |
| Oct 23, 2026 | 15 |
| Oct 22, 2026 | 15 |
| Oct 21, 2026 | 15 |
| Oct 20, 2026 | 15 |
| Oct 19, 2026 | 15 |
| Oct 18, 2026 | 15 |
| Oct 17, 2026 | 15 |
| Oct 16, 2026 | 15 |
| Oct 15, 2026 | 15 |
| Oct 14, 2026 | 15 |
| Oct 13, 2026 | 15 |
| Oct 12, 2026 | 15 |
| Oct 11, 2026 | 15 |
| Oct 10, 2026 | 15 |
| Oct 9, 2026 | 15 |
| Oct 8, 2026 | 15 |
| Oct 7, 2026 | 15 |
| Oct 6, 2026 | 15 |
| Oct 5, 2026 | 15 |
| Oct 4, 2026 | 15 |
| Oct 3, 2026 | 15 |
Map
Where Acquire BPO's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.
| AMS-IX Hong Kong Hong Kong, Hong Kong | 1G | Both | |
| Any2West Los Angeles and Silicon Valley, United States | 1G | PeeringDB | |
| ChIX Chicago, United States | 1G | Both | |
| Equinix Hong Kong Hong Kong, Hong Kong | 10G | PeeringDB | |
| Equinix San Jose San Jose, United States | 1G | PeeringDB | |
| Equinix Singapore Singapore, Singapore | 10G | PeeringDB | |
| FL-IX Miami, United States | 10G | Both IPv6 not in PeeringDB | |
| GetaFIX Manila Manila, Philippines | 10G | PeeringDB | |
| IX Australia Melbourne (VIC-IX) Melbourne, Australia | 10G | Both IPv6 not in PeeringDB | |
| IX Australia Sydney (NSW-IX) Sydney, Australia | 10G | Both IPv6 not in PeeringDB | |
| JPIX TOKYO Tokyo, Japan | 10G | Both | |
| MegaIX Melbourne Melbourne, Australia | 1G | Both IPv6 not in PeeringDB | |
| MegaIX Singapore Singapore, Singapore | 1G | Both IPv6 not in PeeringDB | |
| MegaIX Sydney Sydney, Australia | 1G | Both IPv6 not in PeeringDB | |
| SGIX Singapore, Singapore | 10G | Both IPv6 not in PeeringDB |
These exchanges have a switch in a facility where Acquire BPO lists itself in PeeringDB, but don't have Acquire BPO as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.
| BBIX TokyoTokyo, Japan | 454 | |
| HKIXHong Kong, Hong Kong | 300 | |
| JPNAP TokyoTokyo, Japan | 250 | |
| EdgeIX - SydneySydney, Australia | 230 | |
| NetIXSofia, Bulgaria | 204 | |
| Equinix MiamiMiami, United States | 175 | |
| BBIX SingaporeSingapore, Singapore | 169 | |
| DE-CIX ASEANSingapore, Singapore | 140 | |
| Equinix TokyoTokyo, Japan | 127 | |
| BBIX ManilaManila, Philippines | 101 | |
| SFMIXSan Francisco, United States | 100 | |
| BBIX US-WestWest Coast, United States | 87 | |
| EdgeIX - MelbourneMelbourne, Australia | 73 | |
| Equinix Palo AltoPalo Alto, United States | 69 | |
| Transhybrid IX NetworkJakarta, Indonesia | 63 | |
| Maharlika IXManila, Philippines | 57 | |
| Hong Kong Global Internet ExchangeHong Kong, Hong Kong | 33 | |
| JumboIX PeruLima, Peru | 27 | |
| MegaIX Los AngelesLos Angeles, United States | 27 | |
| MegaIX Bay AreaSan Francisco, United States | 21 | |
| NYIIX Los AngelesLos Angeles, United States | 21 | |
| Vitro Internet ExchangePasig, Philippines | 19 | |
| GNM-IX SGSingapore, Singapore | 15 | |
| Zero Internet eXchange San JoseSan Jose, United States | 15 | |
| AMS-IX SingaporeSingapore, Singapore | 14 | |
| PCTA-IX LuzonPasig City, Philippines | 14 | |
| PhIXManila, Philippines | 12 | |
| AKIXZurich, Switzerland | 11 | |
| MegaIX MiamiMiami, United States | 10 | |
| Impart IXSingapore, Singapore | 7 | |
| Konek Internet Exchangegeneral santos city, Philippines | 7 | |
| Global Peer ExchangeWashington, United States | 6 | |
| PIT - LATAM InterconnectMiami, United States | 5 | |
| Ciallo~(∠·ω< )⌒ IX - HKHong Kong, Hong Kong | 4 | |
| GNM-IX USNew York, United States | 4 | |
| Any2FloridaMiami/Orlando, United States | 2 | |
| ixFabricGlobal, Australia | 2 |
Facilities (10)
The buildings Acquire BPO lists in PeeringDB, and how many of the exchanges in each it's on.
| Equinix SG1 - SingaporeSingapore | 3 of 11 | |
| Equinix MI1 - Miami, NOTAMiami | 1 of 9 | |
| Equinix HK2 - Hong KongKwai Chung | 1 of 8 | |
| Equinix SV1/SV5/SV10 - Silicon Valley, San JoseSan Jose | 1 of 8 | |
| VITRO Makati 2Makati | 1 of 8 | |
| Equinix TY2 - TokyoTokyo | 1 of 6 | |
| CoreSite - Los Angeles (LA1) One WilshireLos Angeles | 1 of 5 | |
| DigiCo Sydney SYD1 (formerly Global Switch Australia)Sydney | 2 of 4 | |
| NEXTDC M1Melbourne | 2 of 3 | |
| NEXTDC M2Tullamarine | 1 of 2 |