IBM Cloud Docs
Endpoints

Endpoints

Review the connectivity options for interacting with IBM® Log Analysis.

As of 28 March 2024 the IBM Log Analysis and IBM Cloud Activity Tracker services are deprecated and will no longer be supported as of 30 March 2025. Customers will need to migrate to IBM Cloud Logs, which replaces these two services, prior to 30 March 2025.

Due to maintenance, IBM® Log Analysis makes changes periodically to IPs in some regions. You might need to take action to continue using the service. This topic lists the currently supported, or planned to be supported, endpoints. For a history and current status of endpoint changes, see Service IP changes.

Connectivity options

IBM Log Analysis offers two connectivity options:

Public endpoints
By default, you can connect to resources in your account over the IBM Cloud public network.
Private endpoints
For added benefits, you can also enable virtual routing and forwarding (VRF) and service endpoints for your infrastructure account. When you enable VRF for your account, you can connect to IBM Log Analysis by using a private IP that is accessible only through the IBM Cloud private network. To learn more about VRF, see Virtual routing and forwarding on IBM Cloud. To learn how to connect to IBM Log Analysis by using a private endpoint, Securing your connection.

Opening required ports and IP addresses in your firewall

If you have firewalls set up on the public or private network in your IBM Cloud infrastructure account, you need to allow traffic to and from the IBM Log Analysis service. You must allow traffic on TCP port 443 and TCP port 80 in your firewall for the API endpoints and the ingestion endpoints.

The ingestion endpoints are required to send logs into a logging instance. To see the list of endpoints, see Ingestion endpoints.

The API endpoint is required for:

  • The authentication of the logging agent.
  • Exporting logs.
  • Configuring resources by using the Config API.

API endpoints

Public API endpoints

The following table shows the public API endpoints:

Table 1. Lists of public API endpoints for interacting with IBM Log Analysis
Region Public API endpoint Public IP addresses Ports
Chennai (in-che) api.in-che.logging.cloud.ibm.com 169.38.94.141 TCP 443
TCP 80
Dallas (us-south) api.us-south.logging.cloud.ibm.com 52.117.134.204
50.22.151.6
67.228.208.253 		TCP 443
TCP 80
Frankfurt (eu-de) api.eu-de.logging.cloud.ibm.com 158.177.133.235
161.156.28.220
149.81.169.206 		TCP 443
TCP 80
London (eu-gb) api.eu-gb.logging.cloud.ibm.com 158.175.91.91
141.125.86.131
158.176.142.2 		TCP 443
TCP 80
Madrid (eu-es) api.eu-es.logging.cloud.ibm.com 13.120.68.42 (*)
13.121.67.53 (*)
13.122.67.90 (*)		 TCP 443
TCP 80
Osaka (jp-osa) api.jp-osa.logging.cloud.ibm.com 163.68.75.68
163.69.70.155
163.73.70.118 		TCP 443
TCP 80
Sao Paulo (br-sao) api.br-sao.logging.cloud.ibm.com 163.107.67.3
163.107.68.196
163.109.68.98 		TCP 443
TCP 80
Sydney (au-syd) api.au-syd.logging.cloud.ibm.com 135.90.92.246
130.198.1.212
135.90.89.221 		TCP 443
TCP 80
Tokyo (jp-tok) api.jp-tok.logging.cloud.ibm.com 161.202.231.186
128.168.96.179
165.192.111.36 		TCP 443
TCP 80
Toronto (ca-tor) api.ca-tor.logging.cloud.ibm.com 169.53.161.75
163.74.65.133
163.75.73.42 		TCP 443
TCP 80
Washington (us-east) api.us-east.logging.cloud.ibm.com 169.47.134.86
169.60.72.62
169.61.107.10 		TCP 443
TCP 80

(*) Indicates endpoints that are in plan to be supported. See Service IP changes for planned changes. These endpoints should be added to an allowlist in advance to avoid service interruptions.

Private API endpoints

The following table shows the private API endpoints:

Table 2. Lists of private API endpoints for interacting with IBM Log Analysis
Region Private API endpoint Private IP addresses Ports
Chennai (in-che) api.private.in-che.logging.cloud.ibm.com 166.9.60.6

166.9.60.11 (*)

166.9.249.113 (*)
166.9.249.142 (*)
166.9.249.178 (*)

 TCP 443
TCP 80
Dallas (us-south) api.private.us-south.logging.cloud.ibm.com 166.9.16.11
166.9.12.12
166.9.14.2

166.9.90.41 (*)
166.9.85.89 (*)
166.9.61.79 (*)

166.9.228.39 (*)
166.9.229.39 (*)
166.9.230.39 (*)

 TCP 443
TCP 80
Frankfurt (eu-de) api.private.eu-de.logging.cloud.ibm.com 166.9.32.7
166.9.28.2
166.9.30.231

166.9.30.45 (*)
166.9.28.159 (*)
166.9.32.117 (*)

166.9.248.116 (*)
166.9.248.149 (*)
166.9.248.85 (*)

 TCP 443
TCP 80
London (eu-gb) api.private.eu-gb.logging.cloud.ibm.com 166.9.36.2
166.9.38.4
166.9.34.2

166.9.36.105 (*)
166.9.34.79 (*)
166.9.38.84 (*)

166.9.244.22 (*)
166.9.244.53 (*)
166.9.244.85 (*)

 TCP 443
TCP 80
Madrid (eu-es) api.private.eu-es.logging.cloud.ibm.com 166.9.94.33
166.9.95.35
166.9.96.34

166.9.225.13 (*)
166.9.226.14 (*)
166.9.227.13 (*)

 TCP 443
TCP 80
Osaka (jp-osa) api.private.jp-osa.logging.cloud.ibm.com 166.9.71.21
166.9.72.19
166.9.70.19

166.9.71.14 (*)
166.9.72.13 (*)
166.9.70.13 (*)

166.9.247.106 (*)
166.9.247.37 (*)
166.9.247.72 (*)

 TCP 443
TCP 80
Sao Paulo (br-sao) api.private.br-sao.logging.cloud.ibm.com 166.9.83.24
166.9.82.23
166.9.84.25

166.9.83.12 (*)
166.9.82.12 (*)
166.9.84.12 (*)

166.9.246.105 (*)
166.9.246.156 (*)
166.9.246.75 (*)

 TCP 443
TCP 80
Sydney (au-syd) api.private.au-syd.logging.cloud.ibm.com 166.9.56.3
166.9.52.2
166.9.54.128

166.9.56.79 (*)
166.9.52.82 (*)
166.9.54.129 (*)

166.9.244.111 (*)
166.9.244.141 (*)
166.9.244.175 (*)

 TCP 443
TCP 80
Tokyo (jp-tok) api.private.jp-tok.logging.cloud.ibm.com 166.9.40.2
166.9.42.3
166.9.44.13

166.9.40.13 (*)
166.9.42.72 (*)
166.9.44.76 (*)

166.9.249.108 (*)
166.9.249.137 (*)
166.9.249.173 (*)

 TCP 443
TCP 80
Toronto (ca-tor) api.private.ca-tor.logging.cloud.ibm.com 166.9.77.23
166.9.76.26
166.9.78.24

166.9.78.10 (*)
166.9.76.10 (*)
166.9.77.10 (*)

166.9.247.151 (*)
166.9.247.182 (*)
166.9.247.201 (*)

 TCP 443
TCP 80
Washington (us-east) api.private.us-east.logging.cloud.ibm.com 166.9.22.35
166.9.20.72
166.9.24.247

166.9.24.171 (*)
166.9.22.194 (*)
166.9.68.157 (*)

166.9.231.235 (*)
166.9.232.23 (*)
166.9.233.10 (*)

 TCP 443
TCP 80

(*) Indicates endpoints that are in plan to be supported. See Service IP changes for planned changes. These endpoints should be added to an allowlist in advance to avoid service interruptions.

Ingestion endpoints

Public ingestion endpoints

The following table shows the ingestion endpoints:

Table 3. Lists of public ingestion endpoints for interacting with IBM Log Analysis
Region Public Ingestion endpoint Public IP addresses Ports
Chennai (in-che) logs.in-che.logging.cloud.ibm.com 169.38.75.46

169.38.94.141 (*)

 TCP 443
TCP 80
Dallas (us-south) logs.us-south.logging.cloud.ibm.com 169.61.197.84
50.22.153.155
67.228.211.6

52.117.134.204 (*)
50.22.151.6 (*)
67.228.208.253 (*)

 TCP 443
TCP 80
Frankfurt (eu-de) logs.eu-de.logging.cloud.ibm.com 149.81.108.173
158.177.157.66
161.156.78.142

158.177.133.235 (*)
161.156.28.220 (*)
149.81.169.206 (*)

 TCP 443
TCP 80
London (eu-gb) logs.eu-gb.logging.cloud.ibm.com 158.176.163.117
158.175.113.18
141.125.102.149

158.175.91.91 (*)
141.125.86.131 (*)
158.176.142.2 (*)

 TCP 443
TCP 80
Madrid (eu-es) logs.eu-es.logging.cloud.ibm.com 13.120.68.42 (*)
13.121.67.53 (*)
13.122.67.90 (*)		 TCP 443
TCP 80
Osaka (jp-osa) logs.jp-osa.logging.cloud.ibm.com 163.73.68.44
163.69.67.212
163.68.73.62

163.68.75.68 (*)
163.69.70.155 (*)
163.73.70.118 (*)

 TCP 443
TCP 80
Sao Paulo (br-sao) logs.br-sao.logging.cloud.ibm.com 163.109.68.108
163.107.69.13
169.57.152.195

163.107.67.3 (*)
163.107.68.196 (*)
163.109.68.98 (*)

 TCP 443
TCP 80
Sydney (au-syd) logs.au-syd.logging.cloud.ibm.com 168.1.27.60
130.198.1.213
135.90.67.172

135.90.92.246 (*)
130.198.1.212 (*)
135.90.89.221 (*)

 TCP 443
TCP 80
Tokyo (jp-tok) logs.jp-tok.logging.cloud.ibm.com 128.168.107.243
165.192.100.74
169.56.11.253

161.202.231.186 (*)
128.168.96.179 (*)
165.192.111.36 (*)

 TCP 443
TCP 80
Toronto (ca-tor) logs.ca-tor.logging.cloud.ibm.com 163.74.65.131
169.55.135.27
163.75.66.243

169.53.161.75 (*)
163.74.65.133 (*)
163.75.73.42 (*)

 TCP 443
TCP 80
Washington (us-east) logs.us-east.logging.cloud.ibm.com 169.47.134.84
169.60.98.94
169.61.98.204

169.47.134.86 (*)
169.60.72.62 (*)
169.61.107.10 (*)

 TCP 443
TCP 80

(*) Indicates endpoints that are in plan to be supported. See Service IP changes for planned changes. These endpoints should be added to an allowlist in advance to avoid service interruptions.

Private ingestion endpoints

The following table shows the private ingestion endpoints:

Table 4. Lists of private ingestion endpoints for interacting with IBM Log Analysis
Region Private Ingestion endpoint Private IP addresses Ports
Chennai (in-che) logs.private.in-che.logging.cloud.ibm.com 166.9.60.7

166.9.60.11 (*)

166.9.249.113 (*)
166.9.249.142 (*)
166.9.249.178 (*)

 TCP 443
TCP 80
Dallas (us-south) logs.private.us-south.logging.cloud.ibm.com 166.9.61.86
166.9.90.101
166.9.86.91

166.9.90.41 (*)
166.9.85.89 (*)
166.9.61.79 (*)

166.9.228.39 (*)
166.9.229.39 (*)
166.9.230.39 (*)

 TCP 443
TCP 80
Frankfurt (eu-de) logs.private.eu-de.logging.cloud.ibm.com 166.9.28.3
166.9.32.21
166.9.30.238

166.9.30.45 (*)
166.9.28.159 (*)
166.9.32.117 (*)

166.9.248.116 (*)
166.9.248.149 (*)
166.9.248.85 (*)

 TCP 443
TCP 80
London (eu-gb) logs.private.eu-gb.logging.cloud.ibm.com 166.9.36.3
166.9.34.4
166.9.38.5

166.9.36.105 (*)
166.9.34.79 (*)
166.9.38.84 (*)

166.9.244.22 (*)
166.9.244.53 (*)
166.9.244.85 (*)

 TCP 443
TCP 80
Madrid (eu-es) logs.private.eu-es.logging.cloud.ibm.com 166.9.94.33 (*)
166.9.95.35 (*)
166.9.96.34 (*)

166.9.225.13 (*)
166.9.226.14 (*)
166.9.227.13 (*)

 TCP 443
TCP 80
Osaka (jp-osa) logs.private.jp-osa.logging.cloud.ibm.com 166.9.71.20
166.9.70.21
166.9.72.21

166.9.71.14 (*)
166.9.72.13 (*)
166.9.70.13 (*)

166.9.247.106 (*)
166.9.247.37 (*)
166.9.247.72 (*)

 TCP 443
TCP 80
Sao Paulo (br-sao) logs.private.br-sao.logging.cloud.ibm.com 166.9.83.25
166.9.84.27
166.9.82.25

166.9.83.12 (*)
166.9.82.12 (*)
166.9.84.12 (*)

166.9.246.105 (*)
166.9.246.156 (*)
166.9.246.75 (*)

 TCP 443
TCP 80
Sydney (au-syd) logs.private.au-syd.logging.cloud.ibm.com 166.9.52.5
166.9.56.20
166.9.54.127

166.9.56.79 (*)
166.9.52.82 (*)
166.9.54.129 (*)

166.9.244.111 (*)
166.9.244.141 (*)
166.9.244.175 (*)

 TCP 443
TCP 80
Tokyo (jp-tok) logs.private.jp-tok.logging.cloud.ibm.com 166.9.40.3
166.9.42.4
166.9.44.71

166.9.40.13 (*)
166.9.42.72 (*)
166.9.44.76 (*)

166.9.249.108 (*)
166.9.249.137 (*)
166.9.249.173 (*)

 TCP 443
TCP 80
Toronto (ca-tor) logs.private.ca-tor.logging.cloud.ibm.com 166.9.77.26
166.9.76.29
166.9.78.27

166.9.78.10 (*)
166.9.76.10 (*)
166.9.77.10 (*)

166.9.247.151 (*)
166.9.247.182 (*)
166.9.247.201 (*)

 TCP 443
TCP 80
Washington (us-east) logs.private.us-east.logging.cloud.ibm.com 166.9.22.36
166.9.20.73
166.9.24.245

166.9.24.171 (*)
166.9.22.194 (*)
166.9.68.157 (*)

166.9.231.235 (*)
166.9.232.23 (*)
166.9.233.10 (*)

 TCP 443
TCP 80

(*) Indicates endpoints that are in plan to be supported. See Service IP changes for planned changes. These endpoints should be added to an allowlist in advance to avoid service interruptions.

Web UI endpoints

The following table shows the logging web UI endpoints:

Table 5. Lists of UI endpoints
Location Region Public Endpoint
Asia Pacific Chennai (in-che) https://app.in-che.logging.cloud.ibm.com
Asia Pacific Osaka (jp-osa) https://app.jp-osa.logging.cloud.ibm.com
Asia Pacific Sydney (au-syd) https://app.au-syd.logging.cloud.ibm.com
Asia Pacific Tokyo (jp-tok) https://app.jp-tok.logging.cloud.ibm.com
Europe Frankfurt (eu-de) https://app.eu-de.logging.cloud.ibm.com
Europe London (eu-gb) https://app.eu-gb.logging.cloud.ibm.com
Europe Madrid (eu-es) https://app.eu-es.logging.cloud.ibm.com
North America Dallas (us-south) https://app.us-south.logging.cloud.ibm.com
North America Washington DC (us-east) https://app.us-east.logging.cloud.ibm.com
North America Toronto (ca-tor) https://app.ca-tor.logging.cloud.ibm.com
South America Sao Paulo (br-sao) https://app.br-sao.logging.cloud.ibm.com

Syslog endpoints

Syslog public endpoints

The following tables show the syslog public endpoints:

Table 6. List of syslog-a public endpoints
Region Public Syslog TCP Endpoint IP addresses
Chennai (in-che) syslog://syslog-a.in-che.logging.cloud.ibm.com 169.38.75.43
Dallas (us-south) syslog://syslog-a.us-south.logging.cloud.ibm.com 52.117.134.206
52.116.247.170
67.228.102.117
Frankfurt (eu-de) syslog://syslog-a.eu-de.logging.cloud.ibm.com 149.81.108.28
161.156.78.138
158.177.157.70
London (eu-gb) syslog://syslog-a.eu-gb.logging.cloud.ibm.com 141.125.102.148
158.175.113.22
158.176.163.115
Madrid (eu-es) syslog://syslog-a.eu-es.logging.cloud.ibm.com 13.120.67.126 (*)
13.121.68.83 (*)
13.122.68.133 (*)
Osaka (jp-osa) syslog://syslog-a.jp-osa.logging.cloud.ibm.com 163.73.68.45
163.69.67.210
163.68.72.220
Sao Paulo (br-sao) syslog://syslog-a.br-sao.logging.cloud.ibm.com 169.57.254.118
163.107.68.195
163.109.68.109
Sydney (au-syd) syslog://syslog-a.au-syd.logging.cloud.ibm.com 168.1.202.76
135.90.92.254
130.198.1.210
Tokyo (jp-tok) syslog://syslog-a.jp-tok.logging.cloud.ibm.com 128.168.95.2
161.202.248.162
165.192.100.77
Toronto (ca-tor) syslog://syslog-a.ca-tor.logging.cloud.ibm.com 163.75.66.13
169.53.186.154
163.74.69.234
Washington (us-east) syslog://syslog-a.us-east.logging.cloud.ibm.com 169.61.98.203
169.47.34.203
169.60.121.243

(*) Indicates endpoints that are in plan to be supported. See Service IP changes for planned changes. These endpoints should be added to an allowlist in advance to avoid service interruptions.

Table 7. List of syslog-u public endpoints
Region Public Syslog UDP Endpoint IP addresses
Chennai (in-che) syslog://syslog-u.in-che.logging.cloud.ibm.com 169.38.126.5
Dallas (us-south) syslog://syslog-u.us-south.logging.cloud.ibm.com 52.116.247.173
169.60.203.92
67.228.102.116
Frankfurt (eu-de) syslog://syslog-u.eu-de.logging.cloud.ibm.com 161.156.78.139
149.81.108.30
158.177.143.26
London (eu-gb) syslog://syslog-u.eu-gb.logging.cloud.ibm.com 158.175.66.210
158.176.163.156
141.125.140.98
Madrid (eu-es) syslog://syslog-u.eu-es.logging.cloud.ibm.com 13.120.67.123 (*)
13.121.68.85 (*)
13.122.68.132 (*)
Osaka (jp-osa) syslog://syslog-u.jp-osa.logging.cloud.ibm.com 163.69.68.70
163.73.68.46
163.68.72.219
Sao Paulo (br-sao) syslog://syslog-u.br-sao.logging.cloud.ibm.com 169.57.152.196
163.107.69.14
163.109.68.100
Sydney (au-syd) syslog://syslog-u.au-syd.logging.cloud.ibm.com 135.90.92.253
168.1.27.59
130.198.71.30
Tokyo (jp-tok) syslog://syslog-u.jp-tok.logging.cloud.ibm.com 165.192.100.76
169.56.11.252
128.168.107.244
Toronto (ca-tor) syslog://syslog-u.ca-tor.logging.cloud.ibm.com 163.75.66.11
169.55.135.29
163.74.69.236
Washington (us-east) syslog://syslog-u.us-east.logging.cloud.ibm.com 169.47.34.204
169.61.98.202
169.60.98.91

(*) Indicates endpoints that are in plan to be supported. See Service IP changes for planned changes. These endpoints should be added to an allowlist in advance to avoid service interruptions.

Syslog private endpoints

The following table shows the syslog private endpoints:

Table 8. Lists of syslog private endpoints
Region Private Endpoint IP addresses
Chennai (in-che) syslog-a.private.in-che.logging.cloud.ibm.com 166.9.60.9
Dallas (us-south) syslog-a.private.us-south.logging.cloud.ibm.com 166.9.14.5
166.9.12.15
166.9.16.14
Frankfurt (eu-de) syslog-a.private.eu-de.logging.cloud.ibm.com 166.9.32.23
166.9.28.5
166.9.30.236
London (eu-gb) syslog-a.private.eu-gb.logging.cloud.ibm.com 166.9.38.20
166.9.34.18
166.9.36.5
Madrid (eu-es) syslog-a.private.eu-es.logging.cloud.ibm.com 166.9.94.34 (*)
166.9.95.32 (*)
166.9.96.35 (*)
Osaka (jp-osa) syslog-a.private.jp-osa.logging.cloud.ibm.com 166.9.70.22
166.9.71.22
166.9.72.22
Sao Paulo (br-sao) syslog-a.private.br-sao.logging.cloud.ibm.com 166.9.82.26
166.9.83.22
166.9.84.23
Sydney (au-syd) syslog-a.private.au-syd.logging.cloud.ibm.com 166.9.52.8
166.9.56.22
166.9.54.124
Tokyo (jp-tok) syslog-a.private.jp-tok.logging.cloud.ibm.com 166.9.42.26
166.9.40.23
166.9.44.67
Toronto (ca-tor) syslog-a.private.ca-tor.logging.cloud.ibm.com 166.9.76.31
166.9.77.28
166.9.78.29
Washington (us-east) syslog-a.private.us-east.logging.cloud.ibm.com 166.9.22.38
166.9.20.76
166.9.24.243

(*) Indicates endpoints that are in plan to be supported. See Service IP changes for planned changes. These endpoints should be added to an allowlist in advance to avoid service interruptions.

Table 7. List of syslog-u public endpoints
Region Public Endpoint IP addresses
Chennai (in-che) syslog://syslog-u.private.in-che.logging.cloud.ibm.com 166.9.60.10
Dallas (us-south) syslog://syslog-u.private.us-south.logging.cloud.ibm.com 166.9.14.6
166.9.16.15
166.9.12.16
Frankfurt (eu-de) syslog://syslog-u.private.eu-de.logging.cloud.ibm.com 166.9.28.7
166.9.32.24
166.9.30.239
London (eu-gb) syslog://syslog-u.private.eu-gb.logging.cloud.ibm.com 166.9.36.6
166.9.38.21
166.9.34.19
Madrid (eu-es) syslog://syslog-u.private.eu-es.logging.cloud.ibm.com 166.9.94.35 (*)
166.9.95.33 (*)
166.9.96.32 (*)
Osaka (jp-osa) syslog://syslog-u.private.jp-osa.logging.cloud.ibm.com 166.9.70.23
166.9.72.23
166.9.71.23
Sao Paulo (br-sao) syslog://syslog-u.private.br-sao.logging.cloud.ibm.com 166.9.83.26
166.9.84.26
166.9.82.27
Sydney (au-syd) syslog://syslog-u.private.au-syd.logging.cloud.ibm.com 166.9.56.23
166.9.52.9
166.9.54.115
Tokyo (jp-tok) syslog://syslog-u.private.jp-tok.logging.cloud.ibm.com 166.9.42.27
166.9.40.24
166.9.44.73
Toronto (ca-tor) syslog://syslog-u.private.ca-tor.logging.cloud.ibm.com 166.9.76.32
166.9.78.30
166.9.77.29
Washington (us-east) syslog://syslog-u.private.us-east.logging.cloud.ibm.com 166.9.22.39
166.9.20.77
166.9.24.244

(*) Indicates endpoints that are in plan to be supported. See Service IP changes for planned changes. These endpoints should be added to an allowlist in advance to avoid service interruptions.

Syslog TLS endpoints

The following table shows the syslog TLS endpoints:

Table 9. Lists of Syslog-TLS endpoints
Region Public Endpoint IP addresses
Chennai (in-che) syslog-tls://syslog-a.in-che.logging.cloud.ibm.com 169.38.75.43
Dallas (us-south) syslog-tls://syslog-a.us-south.logging.cloud.ibm.com 52.116.247.170
52.117.134.206
67.228.102.117
Frankfurt (eu-de) syslog-tls://syslog-a.eu-de.logging.cloud.ibm.com 161.156.78.138
158.177.157.70
149.81.108.28
London (eu-gb) syslog-tls://syslog-a.eu-gb.logging.cloud.ibm.com 158.176.163.115
141.125.102.148
158.175.113.22
Madrid (eu-es) syslog-tls://syslog-a.eu-es.logging.cloud.ibm.com 13.120.67.126 (*)
13.121.68.83 (*)
13.122.68.133 (*)
Osaka (jp-osa) syslog-tls://syslog-a.jp-osa.logging.cloud.ibm.com 163.69.67.210
163.68.72.220
163.73.68.45
Sao Paulo (br-sao) syslog-tls://syslog-a.br-sao.logging.cloud.ibm.com 169.57.254.118
163.107.68.195
163.109.68.109
Sydney (au-syd) syslog-tls://syslog-a.au-syd.logging.cloud.ibm.com 135.90.92.254
168.1.202.76
130.198.1.210
Tokyo (jp-tok) syslog-tls://syslog-a.jp-tok.logging.cloud.ibm.com 128.168.95.2
161.202.248.162
165.192.100.77
Toronto (ca-tor) syslog-tls://syslog-a.ca-tor.logging.cloud.ibm.com 163.75.66.13
163.74.69.234
169.53.186.154
Washington (us-east) syslog-tls://syslog-a.us-east.logging.cloud.ibm.com 169.60.121.243
169.61.98.203
169.47.34.203

(*) Indicates endpoints that are in plan to be supported. See Service IP changes for planned changes. These endpoints should be added to an allowlist in advance to avoid service interruptions.

Private syslog TLS endpoints

The following table shows the syslog TLS endpoints:

Table 9. Lists of Syslog-TLS endpoints
Region Public Endpoint IP addresses
Chennai (in-che) syslog-tls://syslog-a.private.in-che.logging.cloud.ibm.com 166.9.60.9
Dallas (us-south) syslog-tls://syslog-a.private.us-south.logging.cloud.ibm.com 166.9.16.14
166.9.12.15
166.9.14.5
Frankfurt (eu-de) syslog-tls://syslog-a.private.eu-de.logging.cloud.ibm.com 166.9.28.5
166.9.32.23
166.9.30.236
London (eu-gb) syslog-tls://syslog-a.private.eu-gb.logging.cloud.ibm.com 166.9.34.18
166.9.36.5
166.9.38.20
Madrid (eu-es) syslog-tls://syslog-a.private.eu-es.logging.cloud.ibm.com 166.9.94.34 (*)
166.9.95.32 (*)
166.9.96.35 (*)
Osaka (jp-osa) syslog-tls://syslog-a.private.jp-osa.logging.cloud.ibm.com 166.9.72.22
166.9.71.22
166.9.70.22
Sao Paulo (br-sao) syslog-tls://syslog-a.private.br-sao.logging.cloud.ibm.com 166.9.82.26
166.9.83.22
166.9.84.23
Sydney (au-syd) syslog-tls://syslog-a.private.au-syd.logging.cloud.ibm.com 166.9.52.8
166.9.56.22
166.9.54.124
Tokyo (jp-tok) syslog-tls://syslog-a.private.jp-tok.logging.cloud.ibm.com 166.9.40.23
166.9.42.26
166.9.44.67
Toronto (ca-tor) syslog-tls://syslog-a.private.ca-tor.logging.cloud.ibm.com 166.9.76.31
166.9.78.29
166.9.77.28
Washington (us-east) syslog-tls://syslog-a.private.us-east.logging.cloud.ibm.com 166.9.22.38
166.9.20.76
166.9.24.243

(*) Indicates endpoints that are in plan to be supported. See Service IP changes for planned changes. These endpoints should be added to an allowlist in advance to avoid service interruptions.