ASE IT Networks
AS38583
Tools: Where can I peer with ASE IT Networks? · Where should ASE IT Networks peer next? · Compare ASE IT Networks with another network
This network elsewhere: its routes on BGP Report
PeeringDB fix list Printable page · CSV
4 things to fix in ASE IT Networks's PeeringDB record, from what its exchanges publish: 2 to add, 2 to correct. As of 2026-11-19 12:40 UTC.
Make the changes on ASE IT Networks'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 ASE IT Networks's PeeringDB record. Add one entry per connection with these values.
-
IPv4 218.100.78.24 IPv6 2001:7fa:11:1:0:96b7:0:1 Speed 10000 Mbps (10G) 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.
-
IPv4 103.26.71.98 IPv6 2001:dea:0:30::62 Speed Not published 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.
Correct these entries (2)
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:7fa:11:4:0:96b7:0:1 - In the entry with IPv4 218.100.52.88: set IPv6 to 2001:7fa:11:4:0:96b7:0:1 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 103.26.68.64 103.26.68.37 103.26.68.64 IPv6 address missing from PeeringDB none 2001:dea:0:10::25 2001:dea:0:10::40 - In the entry with IPv4 103.26.68.64: set IPv6 to 2001:dea:0:10::40 (now empty).
- Add an entry: IPv4 103.26.68.37, IPv6 2001:dea:0:10::25, RS peer no.
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 5 |
| Nov 18, 2026 | 5 |
| Nov 17, 2026 | 5 |
| Nov 16, 2026 | 5 |
| Nov 15, 2026 | 5 |
| Nov 14, 2026 | 5 |
| Nov 13, 2026 | 5 |
| Nov 12, 2026 | 5 |
| Nov 11, 2026 | 5 |
| Nov 10, 2026 | 5 |
| Nov 9, 2026 | 5 |
| Nov 8, 2026 | 5 |
| Nov 7, 2026 | 5 |
| Nov 6, 2026 | 5 |
| Nov 5, 2026 | 5 |
| Nov 4, 2026 | 5 |
| Nov 3, 2026 | 5 |
| Nov 2, 2026 | 5 |
| Nov 1, 2026 | 5 |
| Oct 31, 2026 | 5 |
| Oct 30, 2026 | 5 |
| Oct 29, 2026 | 5 |
| Oct 28, 2026 | 5 |
| Oct 27, 2026 | 5 |
| Oct 26, 2026 | 5 |
| Oct 25, 2026 | 5 |
| Oct 24, 2026 | 5 |
| Oct 23, 2026 | 5 |
| Oct 22, 2026 | 5 |
| Oct 21, 2026 | 5 |
| Oct 20, 2026 | 5 |
| Oct 19, 2026 | 5 |
| Oct 18, 2026 | 5 |
| Oct 17, 2026 | 5 |
| Oct 16, 2026 | 5 |
| Oct 15, 2026 | 5 |
| Oct 14, 2026 | 5 |
| Oct 13, 2026 | 5 |
| Oct 12, 2026 | 5 |
| Oct 11, 2026 | 5 |
| Oct 10, 2026 | 5 |
| Oct 9, 2026 | 5 |
| Oct 8, 2026 | 5 |
| Oct 7, 2026 | 5 |
| Oct 6, 2026 | 5 |
| Oct 5, 2026 | 5 |
| Oct 4, 2026 | 5 |
| Oct 3, 2026 | 5 |
Map
Where ASE IT Networks'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.
| Equinix Sydney Sydney, Australia | 1G | PeeringDB | |
| IX Australia Melbourne (VIC-IX) Melbourne, Australia | 10G | Not in PeeringDB | |
| IX Australia Sydney (NSW-IX) Sydney, Australia | 10G | Both IPv6 not in PeeringDB | |
| MegaIX Melbourne Melbourne, Australia | Not in PeeringDB | ||
| MegaIX Sydney Sydney, Australia | 10G | Both IPv4 not in PeeringDBIPv6 not in PeeringDB |
ASE IT Networks lists no facilities in PeeringDB.