Relevant Products
Y Soft hosted cloud addresses are available in BREEZE PRINT BREEZE MFD PRO PRINT PRO MFD
From time to time customers who are hosted in the Y Soft cloud require the inbound and output IP addresses for example for opening only for specific IP addresses, or creating conditional access policies in Microsoft Entra ID or similar.
Below are the currently used IP addresses inbound and outbound for each Y Soft hosted region.
IP addresses are subject to change! Subscribe to service announcements on status.ysoft.cloud to be notified of changes to IP’s.
To create your own custom domain names, do not use IP addresses, but instead CNAME. Please refer to Use your own custom domain names for more information.
Inbound IP’s are relevant when a client (such as PC, secondary gateway, MFD or similar) connects across the Internet to the hosted SAFEQ Cloud cloud servers.
Outbound IP’s are relevant when SAFEQ Cloud makes requests from the hosted SAFEQ Cloud cloud servers to something across the Internet, such as Microsoft Entra ID.
Cloud Client Auto-update requires an additional address to be allowed, as referenced in its documentation page.
EU region (*.eu.ysoft.cloud)
|
Inbound (from Internet to SAFEQ Cloud cloud) |
Outbound (from SAFEQ Cloud cloud to Internet) |
|---|---|
|
52.50.253.210 |
176.34.88.154 |
|
18.202.147.163 |
54.217.150.104 |
|
52.19.122.66 |
54.155.19.247 |
EU Central region (*.eu-central.ysoft.cloud)
|
Inbound (from Internet to SAFEQ Cloud cloud) |
Outbound (from SAFEQ Cloud cloud to Internet) |
|---|---|
|
18.159.1.221 |
18.184.95.83 |
|
52.57.32.65 |
3.66.14.128 |
|
3.78.120.145 |
18.199.47.109 |
UK region (*.uk.ysoft.cloud)
|
Inbound (from Internet to SAFEQ Cloud cloud) |
Outbound (from SAFEQ Cloud cloud to Internet) |
|---|---|
|
3.8.221.201 |
18.134.42.232 |
|
52.56.154.204 |
3.11.157.65 |
|
18.135.59.42 |
3.10.114.230 |
SE region (*.se.ysoft.cloud)
|
Inbound (from Internet to SAFEQ Cloud cloud) |
Outbound (from SAFEQ Cloud cloud to Internet) |
|---|---|
|
13.53.92.64 |
13.60.134.63 |
|
51.20.47.173 |
51.20.113.52 |
|
13.49.112.57 |
51.21.77.223 |
DE region (*.de.ysoft.cloud)
|
Inbound (from Internet to SAFEQ Cloud cloud) |
Outbound (from SAFEQ Cloud cloud to Internet) |
|---|---|
|
80.158.108.210 |
80.158.110.114 |
US region (*.us.ysoft.cloud)
|
Inbound (from Internet to SAFEQ Cloud cloud) |
Outbound (from SAFEQ Cloud cloud to Internet) |
|---|---|
|
23.21.249.252 |
35.168.89.37 |
|
54.225.106.109 |
35.169.168.199 |
|
54.205.27.251 |
3.225.50.8 |
CA region (*.ca.ysoft.cloud)
|
Inbound (from Internet to SAFEQ Cloud cloud) |
Outbound (from SAFEQ Cloud cloud to Internet) |
|---|---|
|
15.222.76.70 |
15.222.53.82 |
|
15.156.3.124 |
3.98.69.134 |
|
15.156.139.9 |
15.156.114.171 |
AP region (*.ap.ysoft.cloud)
|
Inbound (from Internet to SAFEQ Cloud cloud) |
Outbound (from SAFEQ Cloud cloud to Internet) |
|---|---|
|
18.140.149.203 |
54.179.98.153 |
|
52.220.47.220 |
46.51.216.209 |
|
54.255.127.37 |
18.140.41.81 |
AU region (*.au.ysoft.cloud)
|
Inbound (from Internet to SAFEQ Cloud cloud) |
Outbound (from SAFEQ Cloud cloud to Internet) |
|---|---|
|
54.153.223.24 |
13.236.170.166 |
|
13.237.129.18 |
3.106.171.162 |
|
13.238.29.243 |
13.237.17.215 |
IP Whitelisting Considerations
Whitelisting specific IP addresses for inbound or outbound traffic is generally not recommended when using cloud-based infrastructure such as AWS or T Cloud Public. Due to the dynamic and distributed nature of AWS (TCP) services, the underlying IP ranges may change over time without prior notice. Relying on static IP allowlists can therefore lead to connectivity issues or service disruptions.
If your security requirements necessitate IP-based filtering, you should ensure that your allowlists are regularly reviewed and updated in accordance with the official AWS IP range documentation. Refer to the AWS-maintained resource on IP address ranges (https://docs.aws.amazon.com/vpc/latest/userguide/aws-ip-ranges.html) and implement automated processes where possible to keep your configurations aligned with the latest published data.
In contrast, T-Cloud Public does not provide a centralized, provider-maintained list of service IP ranges. As a result, IP-based filtering must be configured and maintained manually, and customers are responsible for ensuring that any changes to underlying infrastructure are reflected in their whitelisting rules. Failure to keep these rules up to date may result in degraded functionality or loss of access to critical services.
Failure to keep these rules up to date may result in degraded functionality or loss of access to critical services.