Genesys Cloud - Main

 View Only

Sign Up

Expand all | Collapse all

Genesys Cloud - Notice Regarding Expanded IP Address Range and Firewall Requirements

  • 1.  Genesys Cloud - Notice Regarding Expanded IP Address Range and Firewall Requirements

    Posted 05-18-2026 02:59
    Edited by Yusuke Ouno 05-18-2026 03:00

    I would like to confirm the following points regarding the recent notification about the IP address range updates.

    ■ Necessity of This Action
    My understanding is that the following actions are required based on the notification. Could you please confirm whether these actions are mandatory?

    Excerpt from the notification:

    Update the firewall allowlist to include the new IP address ranges.
    Retrieve the latest IP ranges using the GET /api/v2/ipranges endpoint or the Resource Center.
    Complete these updates within six months of the announcement.

    ■ Specific Procedure for the Required Actions
    If these actions are indeed required, could you also provide detailed instructions on the necessary configuration changes and the recommended verification steps?

    ■ Impact if No Action Is Taken
    The notification states the following:
    "If the new IP address ranges are not included in your firewall allowlist, access to the platform or certain services may be interrupted."

    Could you please clarify which specific services or functionalities may be affected if no action is taken?

    Thank you for your time and assistance. I appreciate your support and look forward to your clarification.

    https://help.genesys.cloud/ja/announcements/genesys-cloud/ip-address-range-expansion-and-firewall-requirements-notification/


    #GenesysAnnouncements

    ------------------------------
    Yusuke Ouno
    ------------------------------



  • 2.  RE: Genesys Cloud - Notice Regarding Expanded IP Address Range and Firewall Requirements

    Posted 05-18-2026 03:42

    From my understanding, these updates mainly apply to customers/environments that use firewall or proxy allowlists for Genesys services.

    The action itself appears to mainly involve:

    • retrieving the updated IP ranges (via GET /api/v2/ipranges or the Resource Center)
    • updating the customer-managed firewall/proxy allowlists with the new ranges
    • and validating connectivity afterward.

    I could not find detailed Genesys-side configuration steps beyond updating the relevant network/security allowlists, since the actual changes would typically be handled by the customer network/security team.

    The announcement also mentions that the IP range expansion is intended to help Genesys Cloud continue scaling reliably as platform demand grows and reduce the risk of service limitations caused by exhausted address capacity.



    ------------------------------
    Phaneendra
    Technical Solutions Consultant
    ------------------------------



  • 3.  RE: Genesys Cloud - Notice Regarding Expanded IP Address Range and Firewall Requirements

    Posted 05-18-2026 04:15

    Thank you for your reply. I'll keep it in mind.



    ------------------------------
    Yusuke Ouno
    ------------------------------



  • 4.  RE: Genesys Cloud - Notice Regarding Expanded IP Address Range and Firewall Requirements
    Best Answer

    Posted 05-18-2026 03:48

    Hi Yusuke

    If you are currently allowing any of the existing IP ranges, you will need to allow the new ranges as well - https://help.genesys.cloud/articles/ip-addresses-for-the-firewall-allowlist/

    You can retrieve the latest IP ranges using the following API - https://developer.genesys.cloud/organization/utilities-apis#get-api-v2-ipranges.

    Genesys Cloud is introducing additional public IP address ranges used by platform services. These new IP ranges complement existing ranges and support current and future capacity needs.

    Genesys Cloud has published the updated list of IP address ranges through the public API and the Resource Center.

    Genesys Cloud will start using the updated IP address ranges on the effective date.

    Reason - https://help.genesys.cloud/faqs/why-does-genesys-cloud-require-that-i-have-so-many-open-ports-on-my-firewall/

    All client connections (including BYOC Premises Edges, WebRTC Clients, and hard phones for BYOC Cloud and Genesys Cloud Voice customers) to Genesys Cloud are started as outbound connections to Genesys Cloud cloud services

    Hope this helps.

    Regards



    ------------------------------
    Stephan Taljaard
    EMBEDIT s.r.o
    ------------------------------



  • 5.  RE: Genesys Cloud - Notice Regarding Expanded IP Address Range and Firewall Requirements

    Posted 05-18-2026 04:16

    Thank you for your reply. I'll keep it in mind.



    ------------------------------
    Yusuke Ouno
    ------------------------------



  • 6.  RE: Genesys Cloud - Notice Regarding Expanded IP Address Range and Firewall Requirements

    Posted 05-20-2026 22:08

    Could you please let us know which IP addresses were newly added or updated in the latest release?

    [IP address list]

    108.138.0.0/15
    108.156.0.0/14
    111.13.171.128/26
    111.13.171.192/26
    111.13.185.32/27
    111.13.185.64/27
    116.129.226.0/25
    116.129.226.128/26
    118.193.97.128/25
    118.193.97.64/26
    119.147.182.0/25
    119.147.182.128/26
    120.232.236.0/25
    120.232.236.128/26
    120.253.240.192/26
    120.253.241.160/27
    120.253.245.128/26
    120.253.245.192/27
    120.52.12.64/26
    120.52.153.192/26
    120.52.22.96/27
    120.52.39.128/27
    13.224.0.0/14
    13.249.0.0/16
    13.32.0.0/15
    13.35.0.0/16
    130.176.0.0/17
    130.176.128.0/18
    130.176.192.0/19
    130.176.224.0/20
    143.204.0.0/16
    144.220.0.0/16
    15.158.0.0/16
    175.41.236.77/32
    175.41.236.77/32
    175.41.236.77/32
    175.41.236.77/32
    175.41.236.77/32
    175.41.236.77/32
    175.41.236.77/32
    175.41.236.77/32
    175.41.236.77/32
    175.41.236.77/32
    18.154.0.0/15
    18.160.0.0/15
    18.164.0.0/15
    18.172.0.0/15
    18.238.0.0/15
    18.244.0.0/15
    18.64.0.0/14
    18.68.0.0/16
    180.163.57.0/25
    180.163.57.128/26
    204.246.164.0/22
    204.246.168.0/22
    204.246.172.0/24
    204.246.173.0/24
    204.246.174.0/23
    204.246.176.0/20
    205.251.202.0/23
    205.251.204.0/23
    205.251.206.0/23
    205.251.208.0/20
    205.251.249.0/24
    205.251.250.0/23
    205.251.252.0/23
    205.251.254.0/24
    216.137.32.0/19
    23.228.212.0/24
    23.228.213.0/24
    23.228.214.0/24
    23.228.220.0/24
    23.228.221.0/24
    23.228.222.0/24
    23.228.223.0/24
    23.228.244.0/24
    23.234.192.0/18
    23.91.0.0/19
    24.110.32.0/19
    3.160.0.0/14
    3.164.0.0/18
    3.164.128.0/17
    3.164.64.0/18
    3.165.0.0/16
    3.166.0.0/15
    3.168.0.0/14
    3.172.0.0/18
    3.172.64.0/18
    3.173.0.0/17
    3.173.128.0/18
    3.173.192.0/18
    3.174.0.0/15
    35.73.246.146/32
    35.73.246.146/32
    35.73.246.146/32
    35.73.246.146/32
    35.73.246.146/32
    35.73.246.146/32
    35.73.246.146/32
    35.73.246.146/32
    35.73.246.146/32
    35.73.246.146/32
    36.103.232.0/25
    36.103.232.128/26
    51.74.192.0/18
    52.124.128.0/17
    52.193.189.115/32
    52.193.189.115/32
    52.193.189.115/32
    52.193.189.115/32
    52.193.189.115/32
    52.193.189.115/32
    52.193.189.115/32
    52.193.189.115/32
    52.193.189.115/32
    52.193.189.115/32
    52.193.88.27/32
    52.193.88.27/32
    52.196.104.192/32
    52.196.104.192/32
    52.196.104.192/32
    52.196.104.192/32
    52.196.104.192/32
    52.196.104.192/32
    52.196.104.192/32
    52.196.104.192/32
    52.196.104.192/32
    52.196.104.192/32
    52.196.95.160/32
    52.196.95.160/32
    52.222.128.0/17
    52.46.0.0/18
    52.82.128.0/19
    52.84.0.0/15
    54.168.134.195/32
    54.168.134.195/32
    54.182.0.0/16
    54.192.0.0/16
    54.230.0.0/17
    54.230.128.0/18
    54.230.200.0/21
    54.230.208.0/20
    54.230.224.0/19
    54.238.35.109/32
    54.238.35.109/32
    54.238.35.109/32
    54.238.35.109/32
    54.238.35.109/32
    54.238.35.109/32
    54.238.35.109/32
    54.238.35.109/32
    54.238.35.109/32
    54.238.35.109/32
    54.239.128.0/18
    54.239.192.0/19
    54.240.128.0/18
    54.65.93.141/32
    54.65.93.141/32
    54.65.93.141/32
    54.65.93.141/32
    54.65.93.141/32
    54.65.93.141/32
    54.65.93.141/32
    54.65.93.141/32
    54.65.93.141/32
    54.65.93.141/32
    58.254.138.0/25
    58.254.138.128/26
    64.252.128.0/18
    64.252.64.0/18
    65.8.0.0/16
    65.9.0.0/17
    65.9.128.0/18
    70.132.0.0/18
    71.152.0.0/17
    99.84.0.0/16
    99.86.0.0/16


    ------------------------------
    Yusuke Ouno
    ------------------------------



  • 7.  RE: Genesys Cloud - Notice Regarding Expanded IP Address Range and Firewall Requirements

    Posted 26 days ago

    I am also looking for a list of just the new IP addresses added. Also I noticed the below notification link is not working any more. Does that mean this is no longer a requirement? Can someone confirm this? 

    https://help.genesys.cloud/announcements/genesys-cloud/ip-address-range-expansion-and-firewall-requirements-notification/



    ------------------------------
    Philip Varghese
    Lead Programmer Analyst
    ------------------------------



  • 8.  RE: Genesys Cloud - Notice Regarding Expanded IP Address Range and Firewall Requirements

    Posted 26 days ago

    Hello Philip,

    I believe that page was an announcement about the CIDR changes that we made in the past. If you would like to see the which IP addresses that we require, I would recommend checking out this article in the Resource Center. For Amazon specific IP addresses, see the .



    ------------------------------
    Jason Kleitz
    Online Community Manager/Moderator
    ------------------------------



  • 9.  RE: Genesys Cloud - Notice Regarding Expanded IP Address Range and Firewall Requirements

    Posted 26 days ago

    @Jason Kleitz I have similar confusion about the announcement. If the announcement removed was for a previous expansion of IP address, does that mean there is no expansion of IP addresses planned for later this year and no action is needed for me to account for additional IP addresses, assuming I have accounted for all IP addresses as of the beginning of May 2026?

    Thanks.



    ------------------------------
    Corey Blosser
    Wolters Kluwer
    ------------------------------



  • 10.  RE: Genesys Cloud - Notice Regarding Expanded IP Address Range and Firewall Requirements

    Posted 26 days ago

    Hello Corey,

    I am not seeing any change on our Announcements page. We strive to provide everyone with info on upcoming changes such as feature and platform updates and feature deprecations. The best way to make sure that your organization is configured properly is to retrieve the latest IP ranges using the following API calls that Phaneendra and Stephan list above.



    ------------------------------
    Jason Kleitz
    Online Community Manager/Moderator
    ------------------------------



  • 11.  RE: Genesys Cloud - Notice Regarding Expanded IP Address Range and Firewall Requirements

    Posted 26 days ago

    Thank you.



    ------------------------------
    Corey Blosser
    Wolters Kluwer
    ------------------------------



  • 12.  RE: Genesys Cloud - Notice Regarding Expanded IP Address Range and Firewall Requirements

    Posted 26 days ago

    Our TAM advised this change had been pulled and the team was rethinking the approach.



    ------------------------------
    Savino Ricci
    Senior Technical Consultant
    ------------------------------



  • 13.  RE: Genesys Cloud - Notice Regarding Expanded IP Address Range and Firewall Requirements

    Posted 26 days ago

    Hi.

    Regarding the release below, does anyone have information on whether it has been postponed or canceled?


    If it has been postponed, is there any information available on the expected timeline or revised release date?


    Genesys Cloud – IP Address Range Expansion and Firewall Requirements Notification (Announced: May 11, 2026)
    https://help.genesys.cloud/announcements/genesys-cloud/ip-address-range-expansion-and-firewall-requirements-notification/


    Thank you in advance for your assistance.



    ------------------------------
    Yusuke Ouno
    ------------------------------



  • 14.  RE: Genesys Cloud - Notice Regarding Expanded IP Address Range and Firewall Requirements

    Posted 26 days ago

    We have updated our firewall back in October, 2024 so I am sure more IP addresses were added and need to be allowed in our firewall. The API /api/v2/ipranges gives us a list of all IPs that need to be allowed so we had to do a manual compare of the output of the API against what is already allowed in the firewall to come up with the additional IP's to be allowed which is a laborious task. 



    ------------------------------
    Philip Varghese
    Lead Programmer Analyst
    ------------------------------



  • 15.  RE: Genesys Cloud - Notice Regarding Expanded IP Address Range and Firewall Requirements

    Posted 7 days ago

    Hi.

    The page below is currently no longer available; however, does anyone have any information regarding whether this notification has been postponed or canceled?

    If it has been postponed, we would appreciate it if you could share any available information regarding the expected timeline or revised release date.

    Genesys Cloud – IP Address Range Expansion and Firewall Requirements Notification (Announced: May 11, 2026)
    https://help.genesys.cloud/announcements/genesys-cloud/ip-address-range-expansion-and-firewall-requirements-notification/

    Thank you in advance for your assistance.



    ------------------------------
    Yusuke Ouno
    ------------------------------



  • 16.  RE: Genesys Cloud - Notice Regarding Expanded IP Address Range and Firewall Requirements

    Posted 7 days ago

    Yes, the announcement is pulled for further changes, and a revised list of IP ranges will be published some time in August and you will have 6 months to make changes to your firewall from the new announcement date, per our TAM



    ------------------------------
    Philip Varghese
    Lead Programmer Analyst
    ------------------------------