ixreport

ACCESS 4

AS134844

ACCESS 4 PTY LTD

1Exchange
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
–Type
RestrictivePeering policy
1Using the route servers
1To fix in PeeringDB
2Facilities in PeeringDB

Tools: Where can I peer with ACCESS 4? · Where should ACCESS 4 peer next? · Compare ACCESS 4 with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in ACCESS 4's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-11-19 18:41 UTC.

Make the changes on ACCESS 4'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 (1)

On the exchange's own member list, but not in ACCESS 4's PeeringDB record. Add one entry per connection with these values.

  1. Australia MegaIX Melbourne Melbourne, Australia · PeeringDB 779From its IX-F export
    IPv4103.26.71.138
    IPv62001:dea:0:30::8a
    SpeedNot published
    RS peerYes

    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

01Oct 3, 2026Nov 19, 20261
Show as a table
DateExchanges
Nov 19, 20261
Nov 18, 20261
Nov 17, 20261
Nov 16, 20261
Nov 15, 20261
Nov 14, 20261
Nov 13, 20261
Nov 12, 20261
Nov 11, 20261
Nov 10, 20261
Nov 9, 20261
Nov 8, 20261
Nov 7, 20261
Nov 6, 20261
Nov 5, 20261
Nov 4, 20261
Nov 3, 20261
Nov 2, 20261
Nov 1, 20261
Oct 31, 20261
Oct 30, 20261
Oct 29, 20261
Oct 28, 20261
Oct 27, 20261
Oct 26, 20261
Oct 25, 20261
Oct 24, 20261
Oct 23, 20261
Oct 22, 20261
Oct 21, 20261
Oct 20, 20261
Oct 19, 20261
Oct 18, 20261
Oct 17, 20261
Oct 16, 20261
Oct 15, 20261
Oct 14, 20261
Oct 13, 20261
Oct 12, 20261
Oct 11, 20261
Oct 10, 20261
Oct 9, 20261
Oct 8, 20261
Oct 7, 20261
Oct 6, 20261
Oct 5, 20261
Oct 4, 20261
Oct 3, 20261

Map

Where ACCESS 4'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.

Exchanges

Australia MegaIX Melbourne Melbourne, Australia 103.26.71.138 2001:dea:0:30::8a Yes Not in PeeringDB

Exchanges in its buildings that it isn't on (8)

These exchanges have a switch in a facility where ACCESS 4 lists itself in PeeringDB, but don't have ACCESS 4 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.

Australia IX Australia Sydney (NSW-IX)Sydney, Australia 270 Equinix SY3 - Sydney
Australia MegaIX SydneySydney, Australia 267 Equinix SY3 - Sydney
Australia EdgeIX - SydneySydney, Australia 230 Equinix SY3 - Sydney
Australia Equinix SydneySydney, Australia 219 Equinix SY3 - Sydney
Bulgaria NetIXSofia, Bulgaria 204 Equinix SY3 - Sydney
Australia IX Australia Melbourne (VIC-IX)Melbourne, Australia 106 NEXTDC M1
Australia EdgeIX - MelbourneMelbourne, Australia 73 NEXTDC M1
Australia ixFabricGlobal, Australia 2 Equinix SY3 - Sydney
Facilities (2)

The buildings ACCESS 4 lists in PeeringDB, and how many of the exchanges in each it's on.

Australia Equinix SY3 - SydneySydney 0 of 6
Australia NEXTDC M1Melbourne 1 of 3