Locations and Outgoing POD IPs for each B2C Commerce POD [EMEA/APAC PODs]

The table below provides a description of B2C Commerce PODs that customers can use for allowlisting, maintenance events, and other processes. Please note that more detail beyond this cannot be provided for security purposes.

Additional Information

• POD: A physical collection of servers (blades), where your instances, sites, and data reside.
• Region: The continental region where this POD resides
• Location: The country or region where this POD resides
• GMT: This column provides the timezone where this POD is situated
• DST: Daylight Savings Time. The asterisk “*” indicates that, during Daylight Savings Time (March-November), an hour (+1) is to be added to the timezone (the "GMT” column).
• Outgoing IP: Customers will need to know this address for their POD for integration with back-end data processes on non-B2C Commerce servers — for example, firewall configurations. Customers are strongly encouraged to add their Outgoing POD IP to their firewall rules. This IP can be determined via the following command, found on most operating systems: nslookup outgoing.pod<POD#>.demandware.net
• Disaster Recovery (DR): this is the POD that will take over in case of a Disaster Recovery Situation. Customers are strongly encouraged to add their DR POD IP to their firewall rules; otherwise, recovery time will be impacted, as connections to back-end systems will fail.