Configure your network for Genesys-defined Autonomous System Numbers (ASNs)

AI-generated summary

to both Direct Connect connections for failover resilience. Regional ASN implementation began in January 2027 on a weekly rollout basis; customers must not apply filters before their region's implementation date, as premature filtering will not match currently received routes. Use of Genesys ASNs is optional and applies only to customers with specific route-path requirements; those without such requirements require no action. Confirmed ASN values by region are published by Genesys before implementation begins.

Feature coming soon

If you use AWS Direct Connect to connect your network to Genesys Cloud and have route-path requirements, such as steering a redundant Direct Connect to accept only a specific region’s routes, then you can use the Genesys ASNs feature to identify, filter, or steer Genesys Cloud routes by region.

For example, a customer with a redundant Direct Connect in one location can filter it to accept only a single region’s Genesys ASN, keeping other regions off that path. Because the match is on the ASN, Genesys can add new address ranges to a region later without requiring a change on your side.

What is an Autonomous System Number (ASN)?

An Autonomous System Number is a globally unique number that identifies a network on the internet. Networks use the Border Gateway Protocol (BGP) to advertise their routes, and every route carries an AS_PATH — the list of ASNs the traffic passes through. Previously, Genesys Cloud traffic reaching you over AWS Direct Connect was advertised under Amazon’s own ASN, so there was no Genesys-specific marker you could match on to tell Genesys routes apart by region.

Genesys now advertises its regional prefixes under Genesys-defined ASNs. A Genesys ASN appears in the AS_PATH of the routes you receive, giving you a stable, Genesys-owned identifier for Genesys Cloud traffic per region, which is something you can reference in your own routing policies.

When can I begin to apply route filtering?

You can begin to apply the Genesys ASN in your route policies after your region has migrated. The region migration will roll-out on a weekly basis throughout the month of January.

Warning: Do not apply a filter before your region’s implementation date. The Genesys ASNs are not used to update customer or carrier networking equipment before they are implemented in a region. Applying a filter early will not match the routes you currently receive.

Configure the route policy

After your region’s ASN implementation date has arrived, you can proceed with this configuration.

Get the Genesys ASN for your region from the table above.
On your Direct Connect router, add an inbound BGP policy that matches the Genesys ASN in the AS_PATH, then apply your accept or filter rule.
Apply the policy to both Direct Connect connections so it holds across path failover.

Frequently asked questions

What is an ASN, in one line?
A globally unique number that identifies a network in BGP routing. After the ASN implementation, a Genesys-owned ASN identifies Genesys Cloud routes per region, which you can optionally reference in your own route policies.

Do I have to use the Genesys ASN?
No. Referencing the Genesys ASN is entirely optional and applies only to customers with route-path requirements. If you have no such requirement, no action is needed.

Where do I get the confirmed ASN values?
Genesys publishes the confirmed table of Genesys ASNs by region before the January 10, 2027 maintenance start. Use the published values rather than any pre-publication draft when configuring your policies.

[NEXT] Was this article helpful?

Get user feedback about articles.