IBM Cloud Docs
Service IP changes

Service IP changes

Due to maintenance, IBM® Log Analysis makes changes periodically to service IPs in some regions. You might need to take action to continue using the service.

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.

For the current list of endpoints that should be allowlisted in your environment, see endpoints.

Endpoints and regions that are not listed are unchanged.

After 17 November 2023

The IP addresses of the following endpoints will be changing after 17 November 2023. The new IPs are listed in endpoints. The new IPs can be allowlisted in advance to avoid impacts when the change is made.

Chennai (in-che)

  • api.private.in-che.logging.cloud.ibm.com
  • logs.private.in-che.logging.cloud.ibm.com

After 30 October 2023

The IP addresses of the following endpoints will be changing after 30 October 2023. The new IPs are listed in endpoints. The new IPs can be allowlisted in advance to avoid impacts when the change is made.

Dallas (us-south)

  • api.private.us-south.logging.cloud.ibm.com
  • logs.private.us-south.logging.cloud.ibm.com

Frankfurt (eu-de)

  • api.private.eu-de.logging.cloud.ibm.com
  • logs.private.eu-de.logging.cloud.ibm.com

London (eu-gb)

  • api.private.eu-gb.logging.cloud.ibm.com
  • logs.private.eu-gb.logging.cloud.ibm.com

Madrid (eu-es)

  • api.private.eu-es.logging.cloud.ibm.com
  • logs.private.eu-es.logging.cloud.ibm.com

Osaka (jp-osa)

  • api.private.jp-osa.logging.cloud.ibm.com
  • logs.private.jp-osa.logging.cloud.ibm.com

Sao Paulo (br-sao)

  • api.private.br-sao.logging.cloud.ibm.com
  • logs.private.br-sao.logging.cloud.ibm.com

Sydney (au-syd)

  • api.private.au-syd.logging.cloud.ibm.com
  • logs.private.au-syd.logging.cloud.ibm.com

Tokyo (jp-tok)

  • api.private.jp-tok.logging.cloud.ibm.com
  • logs.private.jp-tok.logging.cloud.ibm.com

Toronto (ca-tor)

  • api.private.ca-tor.logging.cloud.ibm.com
  • logs.private.ca-tor.logging.cloud.ibm.com

Washington (us-east)

  • api.private.us-east.logging.cloud.ibm.com
  • logs.private.us-east.logging.cloud.ibm.com

After 26 September 2023

The following endpoints will be changing after 26 September 2023. The new IPs are listed in endpoints. The new IPs can be allowlisted in advance to avoid impacts when the change is made.

Madrid (eu-es)

This is a newly opened region.

  • api.eu-es.logging.cloud.ibm.com
  • api.private.eu-es.logging.cloud.ibm.com
  • logs.eu-es.logging.cloud.ibm.com
  • logs.private.eu-es.logging.cloud.ibm.com
  • app.eu-es.logging.cloud.ibm.com
  • syslog-a.eu-es.logging.cloud.ibm.com
  • syslog-a.private.eu-es.logging.cloud.ibm.com
  • syslog-u.eu-es.logging.cloud.ibm.com
  • syslog-u.private.eu-es.logging.cloud.ibm.com

After 24 January 2023

The following endpoints will be changing after 24 January 2023. The new IPs are listed in endpoints. The new IPs can be allowlisted in advance to avoid impacts when the change is made.

Chennai (in-che)

  • api.private.in-che.logging.cloud.ibm.com
  • logs.in-che.logging.cloud.ibm.com
  • logs.private.in-che.logging.cloud.ibm.com

Dallas (us-south)

  • api.private.us-south.logging.cloud.ibm.com
  • logs.us-south.logging.cloud.ibm.com
  • logs.private.us-south.logging.cloud.ibm.com

Frankfurt (eu-de)

  • api.private.eu-de.logging.cloud.ibm.com
  • logs.eu-de.logging.cloud.ibm.com
  • logs.private.eu-de.logging.cloud.ibm.com

London (eu-gb)

  • api.private.eu-gb.logging.cloud.ibm.com
  • logs.eu-gb.logging.cloud.ibm.com
  • logs.private.eu-gb.logging.cloud.ibm.com

Osaka (jp-osa)

  • api.private.jp-osa.logging.cloud.ibm.com
  • logs.jp-osa.logging.cloud.ibm.com
  • logs.private.jp-osa.logging.cloud.ibm.com

Sao Paulo (br-sao)

  • api.private.br-sao.logging.cloud.ibm.com
  • logs.br-sao.logging.cloud.ibm.com
  • logs.private.br-sao.logging.cloud.ibm.com

Sydney (au-syd)

  • api.private.au-syd.logging.cloud.ibm.com
  • logs.au-syd.logging.cloud.ibm.com
  • logs.private.au-syd.logging.cloud.ibm.com

Tokyo (jp-tok)

  • api.private.jp-tok.logging.cloud.ibm.com
  • logs.jp-tok.logging.cloud.ibm.com
  • logs.private.jp-tok.logging.cloud.ibm.com

Toronto (ca-tor)

  • api.private.ca-tor.logging.cloud.ibm.com
  • logs.ca-tor.logging.cloud.ibm.com
  • logs.private.ca-tor.logging.cloud.ibm.com

Washington (us-east)

  • api.private.us-east.logging.cloud.ibm.com
  • logs.us-east.logging.cloud.ibm.com
  • logs.private.us-east.logging.cloud.ibm.com

8 December 2022

The following endpoints have changes effective 8 December 2022.

Dallas (us-south)

  • logs.private.us-south.logging.cloud.ibm.com
  • syslog-tls://syslog-a.us-south.logging.cloud.ibm.com

Frankfurt (eu-de)

  • api.private.eu-de.logging.cloud.ibm.com
  • logs.private.eu-de.logging.cloud.ibm.com
  • syslog-a.private.eu-de.logging.cloud.ibm.com
  • syslog://syslog-u.private.eu-de.logging.cloud.ibm.com
  • syslog-tls://syslog-a.private.eu-de.logging.cloud.ibm.com

Sao Paulo (br-sao)

  • api.private.br-sao.logging.cloud.ibm.com

Seoul (kr-seo)

All Seoul (kr-seo) endpoints are deprecated.

  • api.kr-seo.logging.cloud.ibm.com
  • api.private.kr-seo.logging.cloud.ibm.com
  • logs.kr-seo.logging.cloud.ibm.com
  • logs.private.kr-seo.logging.cloud.ibm.com
  • syslog://syslog-a.kr-seo.logging.cloud.ibm.com
  • syslog-a.private.kr-seo.logging.cloud.ibm.com
  • syslog://syslog-u.kr-seo.logging.cloud.ibm.com
  • syslog://syslog-u.private.kr-seo.logging.cloud.ibm.com
  • syslog-tls://syslog-a.kr-seo.logging.cloud.ibm.com
  • syslog-tls://syslog-a.private.kr-seo.logging.cloud.ibm.com

Sydney (au-syd)

  • api.private.au-syd.logging.cloud.ibm.com
  • logs.private.au-syd.logging.cloud.ibm.com
  • syslog-a.private.au-syd.logging.cloud.ibm.com
  • syslog://syslog-u.private.au-syd.logging.cloud.ibm.com
  • syslog-tls://syslog-a.private.au-syd.logging.cloud.ibm.com

Tokyo (jp-tok)

  • api.private.jp-tok.logging.cloud.ibm.com
  • logs.private.jp-tok.logging.cloud.ibm.com
  • syslog://syslog-a.jp-tok.logging.cloud.ibm.com
  • syslog-a.private.jp-tok.logging.cloud.ibm.com
  • syslog://syslog-u.private.jp-tok.logging.cloud.ibm.com
  • syslog-tls://syslog-a.jp-tok.logging.cloud.ibm.com
  • syslog-tls://syslog-a.private.jp-tok.logging.cloud.ibm.com

Toronto (ca-tor)

  • api.private.ca-tor.logging.cloud.ibm.com
  • logs.private.ca-tor.logging.cloud.ibm.com

Washington (us-east)

  • api.private.us-east.logging.cloud.ibm.com
  • logs.private.us-east.logging.cloud.ibm.com
  • syslog-a.private.us-east.logging.cloud.ibm.com
  • syslog://syslog-u.private.us-east.logging.cloud.ibm.com
  • syslog-tls://syslog-a.private.us-east.logging.cloud.ibm.com

9 May 2022

The following endpoints have changes effective 9 May 2022.

Chenai (in-che)

  • api.in-che.logging.cloud.ibm.com
  • syslog-a.private.in-che.logging.cloud.ibm.com

Dallas (us-south)

  • api.us-south.logging.cloud.ibm.com
  • syslog-a.private.us-south.logging.cloud.ibm.com

Frankfurt (eu-de)

  • api.eu-de.logging.cloud.ibm.com
  • syslog-a.private.eu-de.logging.cloud.ibm.com

London (eu-gb)

  • api.eu-gb.logging.cloud.ibm.com
  • syslog-a.private.eu-gb.logging.cloud.ibm.com

Osaka (jp-osa)

  • api.jp-osa.logging.cloud.ibm.com
  • syslog-a.private.jp-osa.logging.cloud.ibm.com

Sao Paulo (br-sao)

  • api.br-sao.logging.cloud.ibm.com
  • api.private.br-sao.logging.cloud.ibm.com
  • syslog-a.private.br-sao.logging.cloud.ibm.com

Seoul (kr-seo)

  • api.kr-seo.logging.cloud.ibm.com
  • syslog-a.private.kr-seo.logging.cloud.ibm.com

Sydney (au-syd)

  • api.au-syd.logging.cloud.ibm.com
  • syslog-a.private.au-syd.logging.cloud.ibm.com

Tokyo (jp-tok)

  • api.jp-tok.logging.cloud.ibm.com
  • api.private.jp-tok.logging.cloud.ibm.com
  • syslog://syslog-a.jp-tok.logging.cloud.ibm.com
  • syslog-a.private.jp-tok.logging.cloud.ibm.com

Toronto (ca-tor)

  • api.ca-tor.logging.cloud.ibm.com
  • api.private.ca-tor.logging.cloud.ibm.com
  • syslog-a.private.ca-tor.logging.cloud.ibm.com

Washington (us-east)

  • api.us-east.logging.cloud.ibm.com
  • api.private.us-east.logging.cloud.ibm.com
  • syslog-a.private.us-east.logging.cloud.ibm.com

3 February 2022

The following endpoint had changes effective 3 February 2022.

Tokyo (jp-tok)

  • syslog://syslog-a.jp-tok.logging.cloud.ibm.com

28 May 2021

The following endpoints have changes effective 28 May 2021.

London (eu-gb)

  • logs.eu-gb.logging.cloud.ibm.com
  • logs.private.eu-gb.logging.cloud.ibm.com
  • syslog-a.eu-gb.logging.cloud.ibm.com
  • api.eu-gb.logging.cloud.ibm.com
  • api.private.eu-gb.logging.cloud.ibm.com

Dallas (us-south)

  • logs.us-south.logging.cloud.ibm.com
  • logs.private.us-south.logging.cloud.ibm.com
  • syslog-a.us-south.logging.cloud.ibm.com
  • api.us-south.logging.cloud.ibm.com
  • api.private.us-south.logging.cloud.ibm.com

Frankfurt (eu-de)

  • logs.eu-de.logging.cloud.ibm.com
  • logs.private.eu-de.logging.cloud.ibm.com
  • syslog-a.eu-de.logging.cloud.ibm.com
  • api.eu-de.logging.cloud.ibm.com
  • api.private.eu-de.logging.cloud.ibm.com

User-required tasks

If you are using public endpoints, you must complete the following tasks:

Reconfigure your firewalls to the new IPs

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. Check that valid IPs are configured per region where you operate. For a list of valid IPs, see IP changes by region.

Reconfigure applications and services

If you have applications and services that restrict connectivity to specific IPs and communicate with the Log Analysis service, make sure the new IPs are configured to avoid interruption of the logging service.