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

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

Peering Exchanges

Aggregate Controls

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

Peering Exchanges

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

Peering Exchanges

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

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

Megaport IX

EdgeIX (AS24224)

Large community equivalents are also supported.

Equinix IX (AS24115)

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.