Transit and Peering Policy Updates

Scheduled for Mar 24, 22:00 AEDT  -  Mar 25, 02:00 AEDT

Update

We will be undergoing scheduled maintenance during this time.
Posted Mar 16, 2026 - 11:00 AEDT

Scheduled

Summary

RWTS (AS45437) will be performing scheduled maintenance to standardise BGP export policies across our network and migrate our AAPT transit interconnect from AS7545 to AS2764. This maintenance also introduces an expanded set of BGP communities available to customers for traffic engineering.

No customer traffic disruption is expected. All changes have been assessed against current customer configurations and confirmed to have zero impact on existing route advertisement behaviour.

BGP Community Reference

AS45437 supports the following communities for customer use. Customers with BGP transit sessions may send these communities to control how their prefixes are advertised to our upstream transit providers and IX peering partners.

Blackhole and DDoS Mitigation

CommunityEffect
45437:666Blackhole — drop traffic to this prefix at network edge
45437:999Scrubbing — redirect traffic to DDoS scrubbing

Advertisement Control

These communities control which upstreams and peering points receive the prefix. By default, transit customer prefixes are advertised to all transit providers and peering exchanges.

Transit Providers

CommunityEffect
45437:4002Advertise to Vocus (AS4826)
45437:4003Advertise to Telstra (AS1221)
45437:4025Advertise to AAPT (AS2764)
45437:4015Advertise to Superloop (AS38195)

Peering Exchanges

CommunityEffect
45437:4019Advertise to EdgeIX Sydney
45437:4028Advertise to EdgeIX Darwin
45437:4020Advertise to Megaport IX Sydney
45437:4021Advertise to Megaport IX Melbourne
45437:4032Advertise to Megaport IX Brisbane
45437:4024Advertise to IX Australia NSW
45437:4030Advertise to IX Australia VIC
45437:4031Advertise to IX Australia QLD
45437:4026Advertise to IX Australia WA
45437:4027Advertise to IX Australia SA
45437:4029Advertise to Equinix IX Sydney

Aggregate Controls

CommunityEffect
45437:45437Advertise to all transit and peering (default for transit customers)
45437:4005Advertise to all peering exchanges

NO-EXPORT Modifiers

These communities cause the well-known NO_EXPORT community to be attached when advertising to a specific upstream. The upstream receives the route but will not re-advertise it to its own peers.

Transit Providers

CommunityEffect
45437:4200NO-EXPORT toward Vocus
45437:4201NO-EXPORT toward Telstra
45437:4203NO-EXPORT toward AAPT
45437:4205NO-EXPORT toward Superloop

Peering Exchanges

CommunityEffect
45437:4206NO-EXPORT toward EdgeIX Sydney
45437:4212NO-EXPORT toward EdgeIX Darwin
45437:4207NO-EXPORT toward Megaport IX Sydney
45437:4208NO-EXPORT toward Megaport IX Melbourne
45437:4216NO-EXPORT toward Megaport IX Brisbane
45437:4209NO-EXPORT toward IX Australia NSW
45437:4214NO-EXPORT toward IX Australia VIC
45437:4215NO-EXPORT toward IX Australia QLD
45437:4210NO-EXPORT toward IX Australia WA
45437:4211NO-EXPORT toward IX Australia SA
45437:4213NO-EXPORT toward Equinix IX Sydney

AS-Path Prepending

These communities cause AS45437 to be prepended to the AS-path when advertising to a specific upstream, making the path less preferred. The community format is 45437:50[ID][count] where ID identifies the upstream and count is the prepend multiplier (1–5).

Transit Providers

Provider1x2x3x4x5x
Vocus45437:501145437:501245437:501345437:501445437:5015
Telstra45437:502145437:502245437:502345437:502445437:5025
AAPT45437:503145437:503245437:503345437:503445437:5035
Superloop45437:505145437:505245437:505345437:505445437:5055

Peering Exchanges

Exchange1x2x3x4x5x
EdgeIX SYD45437:506145437:506245437:506345437:506445437:5065
Megaport SYD45437:507145437:507245437:507345437:507445437:5075
Megaport MEL45437:508145437:508245437:508345437:508445437:5085
IX Australia NSW45437:509145437:509245437:509345437:509445437:5095
IX Australia WA45437:510145437:510245437:510345437:510445437:5105
IX Australia SA45437:511145437:511245437:511345437:511445437:5115
EdgeIX DRW45437:512145437:512245437:512345437:512445437:5125
Equinix IX SYD45437:513145437:513245437:513345437:513445437:5135
IX Australia VIC45437:514145437:514245437:514345437:514445437:5145
IX Australia QLD45437:515145437:515245437:515345437:515445437:5155
Megaport BNE45437:516145437:516245437:516345437:516445437:5165

IX Route Server Communities

Customers may also send IX route server communities to control per-peer behaviour at exchanges. These communities are passed through to the route servers unmodified.

IX Australia (AS7606) — NSW-IX, VIC-IX, QLD-IX, WA-IX, SA-IX

CommunityEffect
0:<peer-as>Do not advertise to specific peer
7606:<peer-as>Advertise to specific peer
0:7606Do not advertise to any peer
7606:7606Advertise to all peers
1:<peer-as>Prepend 1x toward specific peer
2:<peer-as>Prepend 2x toward specific peer
3:<peer-as>Prepend 3x toward specific peer

Large community equivalents are also supported (7606:0:<peer-as>, etc.).

Megaport IX

CommunityEffect
65000:0Do not announce to any peer
65000:<ASN>Do not announce to specific peer
64960:<ASN>Override: announce to specific peer (when 65000:0 is set)
65001:<ASN>Prepend 1x toward specific peer
65002:<ASN>Prepend 2x toward specific peer
65003:<ASN>Prepend 3x toward specific peer
65070:<METRO_ID>Do not announce to specific metro

EdgeIX (AS24224)

CommunityEffect
0:<peer-as>Do not advertise to specific peer
24224:<peer-as>Advertise to specific peer
0:24224Do not advertise to any peer
24224:24224Advertise to all peers

Large community equivalents are also supported.

Equinix IX (AS24115)

CommunityEffect
0:<ASN>Do not announce to specific peer
24115:<ASN>Announce to specific peer
0:24115Do not announce to any peer
65501:<ASN>Prepend 1x toward specific peer
65502:<ASN>Prepend 2x toward specific peer
65503:<ASN>Prepend 3x toward specific peer
24115:111:<ms>Prepend 1x for peers above latency threshold
24115:112:<ms>Prepend 2x for peers above latency threshold
24115:113:<ms>Prepend 3x for peers above latency threshold

Large community equivalents are also supported (24115:0:<ASN>, 24115:101:<ASN>, etc.).

AAPT Interconnect Migration

What Is Changing

The RWTS transit interconnect currently peering with AS7545 (TPG) is migrating to AS2764 (AAPT). This reflects a change in the upstream carrier's BGP configuration. The physical interconnect and service arrangement are unchanged.

Impact on Customers

  • No action required for most customers. Existing BGP community values for AAPT traffic engineering are unchanged.
  • Customers using communities 45437:4025, 45437:4203, or 45437:5031–5035 will continue to function without modification — these communities now apply to the AS2764 session.
  • Customers receiving a filtered routing table from this transit link will continue to receive equivalent routes from AS2764.

Timeline

Both the BGP policy standardisation and the AAPT interconnect migration will be completed during the scheduled maintenance window. Further details will be communicated separately.

Questions

For questions about these changes or assistance configuring BGP communities, contact RWTS Network Engineering.
Posted Mar 16, 2026 - 10:31 AEDT
This scheduled maintenance affects: Network Services (IP Transit).
← Current Status Powered by Atlassian Statuspage