vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Locations 

IBM Cloud® Activity Tracker is available in the following locations:

Zoom

![The image shows the locations where the IBM Cloud Activity Tracker service is available.](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/Activity-Tracker-Search-06-Locations.svg)

Figure 1. Displays the regions where you can create and manage IBM Cloud Activity Tracker resources.

This image is an artistic representation and does not reflect actual political or geographic boundaries.



Table 1. List of locations for Activity Tracker hosted event search offerings

 Geography        Region                        EU-Supported   HA Status 

 Asia Pacific     Chennai (in-che)              N/A            SZR       
 Asia Pacific     Tokyo (jp-tok)                N/A            MZR       
 Asia Pacific     Sydney (au-syd)               N/A            MZR       
 Asia Pacific     Osaka (jp-osa)                N/A            MZR       
 Europe           Frankfurt (eu-de) () ()       YES            MZR       
 Europe           London (eu-gb)                NO             MZR       
 North America    Dallas (us-south)             N/A            MZR       
 North America    Washington (us-east)          N/A            MZR       
 North America    Toronto (ca-tor)              N/A            MZR       
 South America    Sao Paulo (br-sao)            N/A            MZR       



Where



*  A geography is a geographic area or larger political body that contains one or more regions.
*  A region is a defined geographic territory. A region could be a specific postal code area, a town, a city, a state, a group of states, or even a group of countries.
*  N/A means feature that is not applicable to that geography.



() For more information, see [Enabling the EU Supported setting](https://cloud.ibm.com/docs/account?topic=account-eu-hipaa-supportedbill_eusupported).

() Fixes to bugs and new features take a few days more to deploy into Frankfurt than to other regions.
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/b698ea8660e1f51664f7479f870bbf8840335d06/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/b698ea8660e1f51664f7479f870bbf8840335d06/icons/checkmark-icon.svg) 
 Washington DC 4 ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/b698ea8660e1f51664f7479f870bbf8840335d06/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/b698ea8660e1f51664f7479f870bbf8840335d06/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/b698ea8660e1f51664f7479f870bbf8840335d06/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/b698ea8660e1f51664f7479f870bbf8840335d06/icons/checkmark-icon.svg) 
 Washington DC 5 ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/b698ea8660e1f51664f7479f870bbf8840335d06/icons/checkmark-icon.svg) !
[check icon](https://cloud.ibm.com/docs-content/v1/content/d56dbd8ab7d14086029681ee71679e14aea53723/icons/checkmark-icon.svg) ![check icon](https://cloud.ibm.com/docs-content/v1/content/d56dbd8ab7d14086029681ee71679e14aea53723/icons/checkmark-icon.svg) 
 Osaka (jp-osa) ![check icon](https://cloud.ibm.com/docs-content/v1/content/d56dbd8ab7d14086029681ee71679e14aea53723/icons/checkmark-icon.svg) ![check icon](https://cloud.ibm.com/docs-content/v1/content/d56dbd8ab7d14086029681ee71679e14aea53723/icons/checkmark-icon.svg) ![check icon](https://cloud.ibm.com/docs-content/v1/content/d56dbd8ab7d14086029681ee71679e14aea53723/icons/checkmark-icon.svg) 
 Tokyo (jp-tok) ![check icon](https://cloud.ibm.com/docs-content/v1/content/d56dbd8ab7d14086029681ee71679e14aea53723/icons/checkmark-icon.svg) ![check icon](https://cloud.ibm.com/docs-content/v1/content/d56dbd8ab7d14086029681ee71679e14aea53723/icons/checkmark-icon.svg) !
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 
 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 
 Europe Frankfurt (eu-de) https://app.eu-de.logging.cloud.ibm.com 
 Europe London (eu-gb) https://app.eu-gb.logging.cloud.ibm.com
Classic infrastructure

List the locations that are supported by IBM Cloud Kubernetes Service. For more information about the locations that are returned, see [IBM Cloud Kubernetes Service locations](https://cloud.ibm.com/docs/openshift?topic=openshift-regions-and-zoneslocations).

ibmcloud oc locations [--output json]

Minimum required permissions
: None

Command options:

--output json
: Optional: Prints the command output in JSON format.





 versions command 

Virtual Private Cloud

Classic infrastructure

List all the container platform versions that are available for IBM Cloud Kubernetes Service clusters. Update your [cluster master](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_update) and [worker nodes](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_worker_update) to the default version for the latest, stable capabilities.

The kube-versions alias for this command is deprecated.

ibmcloud oc versions [--show-version (KUBERNETES|OPENSHIFT)] [--output json] [-q]

Minimum required permissions
: None

Command options:

--show-version (KUBERNETES|OPENSHIFT)
: Show only the versions for the specified container platform. Supported values are kubernetes or openshift.

--output json
: Optional: Prints the command output in JSON format.

-q
: Optional: Do not show the message of the day or update reminders.

Example:

ibmcloud oc versions





 api command 

Virtual Private Cloud

Classic infrastructure

Target the API endpoint for IBM Cloud Kubernetes Service. If you don't specify an endpoint, you can view information about the current endpoint that is targeted.

Region-specific endpoints are deprecated.
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/b698ea8660e1f51664f7479f870bbf8840335d06/icons/checkmark-icon.svg) 
 Toronto 4 ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/b698ea8660e1f51664f7479f870bbf8840335d06/icons/checkmark-icon.svg) 
 Toronto 5 ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/b698ea8660e1f51664f7479f870bbf8840335d06/icons/checkmark-icon.svg) 
 Washington DC 2 ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/b698ea8660e1f51664f7479f870bbf8840335d06/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/b698ea8660e1f51664f7479f870bbf8840335d06/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/b698ea8660e1f51664f7479f870bbf8840335d06/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/b698ea8660e1f51664f7479f870bbf8840335d06/icons/checkmark-icon.svg) 
 Washington DC 4 !
[IAM service access roles](https://cloud.ibm.com/docs/containers?topic=containers-iam-service-access-rolesiam-service-access-roles)



* [Kubernetes Service](https://cloud.ibm.com/docs/containers?topic=containers-iam-service-access-rolesiam-service-access-roles-include-containers-kubernetes-roles)
* [Kubernetes service access roles and corresponding RBAC roles](https://cloud.ibm.com/docs/containers?topic=containers-iam-service-access-rolesrbac_service)
* [Kubernetes resource permissions per RBAC role](https://cloud.ibm.com/docs/containers?topic=containers-iam-service-access-rolesrbac_ref)
* [IBM Cloud IAM issuer details for RBAC users](https://cloud.ibm.com/docs/containers?topic=containers-iam-service-access-rolesiam-issuer-users)



[Classic infrastructure roles](https://cloud.ibm.com/docs/containers?topic=containers-classic-rolesclassic-roles)



* [Required classic infrastructure permissions](https://cloud.ibm.com/docs/containers?topic=containers-classic-rolesrequired-classic-rbac)
* [Suggested classic infrastructure permissions](https://cloud.ibm.com/docs/containers?topic=containers-classic-rolesclassic-rbac-suggested)



[Cloud Foundry roles](https://cloud.ibm.com/docs/containers?topic=containers-cloud-foundry-rolescloud-foundry-roles)





 Locations 

[Locations](https://cloud.ibm.com/docs/containers?topic=containers-regions-and-zonesregions-and-zones)



* [IBM Cloud Kubernetes Service locations](https://cloud.ibm.com/docs/containers?topic=containers-regions-and-zoneslocations)
Locations 

IBM Log Analysis is available in the following locations:

Zoom

![The image shows the locations where the IBM Log Analysis service is available.](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/Log-Analysis-09-Locations.svg)

Figure 1. Displays the regions where you can create and manage IBM Log Analysis resources.

This image is an artistic representation and does not reflect actual political or geographic boundaries.

You can create IBM Log Analysis resources in one of the supported IBM Cloud locations, which represent the geographic area where your IBM Log Analysis requests are handled and processed.

The following table lists the locations where the service is available:



Table 1. List of locations where the service is available

 Geography        Region                   EU-Supported   HA Status 

 Asia Pacific     Chennai (in-che)         N/A            SZR       
 Asia Pacific     Tokyo (jp-tok)           N/A            MZR       
 Asia Pacific     Sydney (au-syd)          N/A            MZR       
 Asia Pacific     Osaka (jp-osa)           N/A            MZR       
 Europe           Frankfurt (eu-de) ()     YES            MZR       
 Europe           London (eu-gb)           NO             MZR       
 North America    Dallas (us-south)        N/A            MZR       
 North America    Washington (us-east)     N/A            MZR       
 North America    Toronto (ca-tor)         N/A            MZR       
 South America    Sao Paulo (br-sao)       N/A            MZR       



Where



*  A geography is a geographic area or larger political body that contains one or more regions.
*  A region is a defined geographic territory. A region could be a specific postal code area, a town, a city, a state, a group of states, or even a group of countries.
*  N/A means feature that is not applicable to that geography.



() For more information, see [Enabling the EU Supported setting](https://cloud.ibm.com/docs/account?topic=account-eu-hipaa-supportedbill_eusupported).
The following list displays the website URL and local phone number for a selection of locations that IBM Cloud sales supports across the world.



* United States [https://www.ibm.com/cloud](https://www.ibm.com/cloud) / telephone: +18449525683
* Brazil [https://www.ibm.com/br-pt/cloud](https://www.ibm.com/br-pt/cloud) / telephone: +558007071426
* France [https://www.ibm.com/fr-fr/cloud](https://www.ibm.com/fr-fr/cloud) / telephone: +33810005810
* Germany [https://www.ibm.com/de-de/cloud](https://www.ibm.com/de-de/cloud) / telephone: +491805426014
* Japan [https://www.ibm.com/jp-ja/cloud](https://www.ibm.com/jp-ja/cloud) / telephone: 81-3-6667-1111
* Korea [https://www.ibm.com/kr-ko/cloud](https://www.ibm.com/kr-ko/cloud) / telephone: +82237815156
* Italy [https://www.ibm.com/it-it/cloud](https://www.ibm.com/it-it/cloud) / telephone: +390270316122
* Spain [https://www.ibm.com/es-es/cloud](https://www.ibm.com/es-es/cloud) / telephone: +34902022007
* China [https://www.ibm.com/cn-zh/cloud](https://www.ibm.com/cn-zh/cloud) / telephone: +864006682350
* [lon](https://cloud.ibm.com/docs/openshift?topic=openshift-classic-flavorslon)
* [mil](https://cloud.ibm.com/docs/openshift?topic=openshift-classic-flavorsmil)
* [mon](https://cloud.ibm.com/docs/openshift?topic=openshift-classic-flavorsmon)
* [osa](https://cloud.ibm.com/docs/openshift?topic=openshift-classic-flavorsosa)
* [par](https://cloud.ibm.com/docs/openshift?topic=openshift-classic-flavorspar)
* [sao](https://cloud.ibm.com/docs/openshift?topic=openshift-classic-flavorssao)
* [sjc](https://cloud.ibm.com/docs/openshift?topic=openshift-classic-flavorssjc)
* [sng](https://cloud.ibm.com/docs/openshift?topic=openshift-classic-flavorssng)
* [syd](https://cloud.ibm.com/docs/openshift?topic=openshift-classic-flavorssyd)
* [tok](https://cloud.ibm.com/docs/openshift?topic=openshift-classic-flavorstok)
* [tor](https://cloud.ibm.com/docs/openshift?topic=openshift-classic-flavorstor)
* [wdc](https://cloud.ibm.com/docs/openshift?topic=openshift-classic-flavorswdc)







 FAQs 

[FAQs](https://cloud.ibm.com/docs/openshift?topic=openshift-faqsfaqs)



* [How does Red Hat OpenShift on IBM Cloud work?]
30 August 2019 

New! Paris, France par01 single zone location for Red Hat OpenShift clusters
: For more locations, see [Single and multizone locations in Red Hat OpenShift on IBM Cloud](https://cloud.ibm.com/docs/openshift?topic=openshift-regions-and-zones).





 29 August 2019 

Forwarding Kubernetes API audit logs to IBM Log Analysis
: Added steps to [create an audit webhook in your cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-health-audit) to collect Kubernetes API audit logs from your cluster and forward them to IBM Log Analysis.





 28 August 2019 

CLI change log
: Updated the IBM Cloud Kubernetes Service CLI plug-in change log page for the [release of version 0.3.112](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_cli_changelog).

Version change log
: Change log added for master fix pack [3.11.135_1522_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_311311135_1522).





 26 August 2019 

Cluster autoscaler
: With the latest version of the cluster autoscaler, you can [enable autoscaling for worker pools during the Helm chart installation](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster-scaling-helm) instead of modifying the config map after installation.

Ingress ALB change log
: Updated the ALB [nginx-ingress image to build 524 and ingress-auth image to build 337](https://cloud.ibm.com/docs/containers?topic=containers-cluster-add-ons-changelogkube_ingress_changelog).

New! Seoul, Korea seo01 single zone location for Red Hat OpenShift clusters
private.us-east.kms.cloud.ibm.com crn:v1:bluemix:public:kms:us-east:::endpoint:private.us-east.kms.cloud.ibm.com 
 private.eu-gb.kms.cloud.ibm.com crn:v1:bluemix:public:kms:eu-gb:::endpoint:private.eu-gb.kms.cloud.ibm.com 
 private.eu-de.kms.cloud.ibm.com crn:v1:bluemix:public:kms:eu-de:::endpoint:private.eu-de.kms.cloud.ibm.com 
 private.au-syd.kms.cloud.ibm.com crn:v1:bluemix:public:kms:au-syd:::endpoint:private.au-syd.kms.cloud.ibm.com 
 private.jp-tok.kms.cloud.ibm.com crn:v1:bluemix:public:kms:jp-tok:::endpoint:private.jp-tok.kms.cloud.ibm.com 
 Frankfurt 
 private.us-south.kms.cloud.ibm.com crn:v1:bluemix:public:kms:us-south:::endpoint:private.us-south.kms.cloud.ibm.com 
 private.us-east.kms.cloud.ibm.com crn:v1:bluemix:public:kms:us-east:::endpoint:private.us-east.kms.cloud.ibm.com 
 private.eu-gb.kms.cloud.ibm.com crn:v1:bluemix:public:kms:eu-gb:::endpoint:private.eu-gb.kms.cloud.ibm.com 
 private.eu-de.kms.cloud.ibm.com crn:v1:bluemix:public:kms:eu-de:::endpoint:private.eu-de.kms.cloud.ibm.com
* [Feature gates](https://cloud.ibm.com/docs/openshift?topic=openshift-service-settingsfeature-gates)
* [Global settings](https://cloud.ibm.com/docs/openshift?topic=openshift-service-settingsglobal-settings)







 Related links 

[OpenShift Container Platform documentation](https://docs.openshift.com/)

[IBM Developer - Red Hat OpenShift on IBM Cloud](https://developer.ibm.com/components/redhat-openshift-ibm-cloud/)

[OpenShift interactive learning portal](https://developers.redhat.com/learn)





 VPC flavors 

[VPC flavors](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-flavorsvpc-flavors)



* [au-syd](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-flavorsau-syd)
* [br-sao](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-flavorsbr-sao)
* [ca-tor](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-flavorsca-tor)
* [eu-de](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-flavorseu-de)
* [eu-gb](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-flavorseu-gb)
* [jp-osa](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-flavorsjp-osa)
* [jp-tok](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-flavorsjp-tok)
: [Non-RHCOS locations in London](https://cloud.ibm.com/docs/satellite?topic=satellite-reqs-host-network-outbound-lon)
: [Non-RHCOS locations in Osaka](https://cloud.ibm.com/docs/satellite?topic=satellite-reqs-host-network-outbound-osa)
: [Non-RHCOS locations in Sao Paulo](https://cloud.ibm.com/docs/satellite?topic=satellite-reqs-host-network-outbound-sao)
: [Non-RHCOS locations in Sydney](https://cloud.ibm.com/docs/satellite?topic=satellite-reqs-host-network-outbound-syd)
: [Non-RHCOS locations in Tokyo](https://cloud.ibm.com/docs/satellite?topic=satellite-reqs-host-network-outbound-tok)
: [Non-RHCOS locations in Toronto](https://cloud.ibm.com/docs/satellite?topic=satellite-reqs-host-network-outbound-tor)
: [Non-RHCOS locations in Washington D.C.](https://cloud.ibm.com/docs/satellite?topic=satellite-reqs-host-network-outbound-wdc)

Outbound connectivity requirements for Red Hat CoreOS (RHCOS) locations
: [RHCOS enabled locations in Dallas](https://cloud.ibm.com/docs/satellite?topic=satellite-reqs-host-rhcos-outbound-dal)
: [RHCOS enabled locations in Frankfurt](https://cloud.ibm.com/docs/satellite?topic=satellite-reqs-host-rhcos-outbound-fra)
: [RHCOS enabled locations in London](https://cloud.ibm.com/docs/satellite?topic=satellite-reqs-host-rhcos-outbound-lon)
* [eu-gb](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-flavorseu-gb)
* [jp-osa](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-flavorsjp-osa)
* [jp-tok](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-flavorsjp-tok)
* [us-east](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-flavorsus-east)
* [us-south](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-flavorsus-south)







 Classic flavors 

[Classic flavors](https://cloud.ibm.com/docs/openshift?topic=openshift-classic-flavorsclassic-flavors)



* [ams](https://cloud.ibm.com/docs/openshift?topic=openshift-classic-flavorsams)
* [che](https://cloud.ibm.com/docs/openshift?topic=openshift-classic-flavorsche)
* [dal](https://cloud.ibm.com/docs/openshift?topic=openshift-classic-flavorsdal)
* [fra](https://cloud.ibm.com/docs/openshift?topic=openshift-classic-flavorsfra)
* [lon](https://cloud.ibm.com/docs/openshift?topic=openshift-classic-flavorslon)
* [mil](https://cloud.ibm.com/docs/openshift?topic=openshift-classic-flavorsmil)
* [mon](https://cloud.ibm.com/docs/openshift?topic=openshift-classic-flavorsmon)
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/b698ea8660e1f51664f7479f870bbf8840335d06/icons/checkmark-icon.svg) 
 Dallas 13 ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/b698ea8660e1f51664f7479f870bbf8840335d06/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/b698ea8660e1f51664f7479f870bbf8840335d06/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/b698ea8660e1f51664f7479f870bbf8840335d06/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/b698ea8660e1f51664f7479f870bbf8840335d06/icons/checkmark-icon.svg) 
 Denver 1 ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/b698ea8660e1f51664f7479f870bbf8840335d06/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/b698ea8660e1f51664f7479f870bbf8840335d06/icons/checkmark-icon.svg) !
Regions 

A list of supported regions for the IBM Cloud Monitoring service.

The IBM Cloud Monitoring service is available in the following regions:

Zoom

![The image shows the locations where the IBM Cloud Monitoring service is available.](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/world-map_min.png)

Figure 1. Displays the regions where you can create and manage IBM Cloud Monitoring resources.

This image is an artistic representation and does not reflect actual political or geographic boundaries.

You can create IBM Cloud Monitoring resources in one of the supported IBM Cloud locations, which represent the geographic area where your IBM Cloud Monitoring requests are handled and processed.

The following table lists the locations where the service is available:



Table 1. List of locations where the service is available

 Geography        Region                   EU-Supported   HA Status 

 Asia Pacific     Sydney (au-syd)          N/A            MZR       
 Asia Pacific     Osaka (jp-osa)           N/A            N/A       
 Asia Pacific     Tokyo (jp-tok)           N/A            MZR       
 Europe           Frankfurt (eu-de) ()     YES            MZR       
 Europe           London (eu-gb)           NO             MZR       
 North America    Dallas (us-south)        N/A            MZR       
 North America    Washington (us-east)     N/A            MZR       
 North America    Toronto (ca-tor)         N/A            MZR       
 South America    Sao Paulo (br-sao)       N/A            MZR       



Where



*  A geography is a geographic area or larger political body that contains one or more regions.
*  A region is a defined geographic territory. A region could be a specific postal code area, a town, a city, a state, a group of states, or even a group of countries.
*  N/A means feature that is not applicable to that geography.



() For more information, see [Enabling the EU Supported setting](https://cloud.ibm.com/docs/account?topic=account-eu-hipaa-supportedbill_eusupported).
Asia Pacific Sydney (au-syd) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/bcd8b79ca2ed73bfcaefb20051f12cb6400286ab/atracker/images/checkmark-icon.svg) 
 Asia Pacific Osaka (jp-osa) 
 Europe Frankfurt (eu-de) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/bcd8b79ca2ed73bfcaefb20051f12cb6400286ab/atracker/images/checkmark-icon.svg) 
 Europe London (eu-gb) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/bcd8b79ca2ed73bfcaefb20051f12cb6400286ab/atracker/images/checkmark-icon.svg) 
 North America Dallas (us-south) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/bcd8b79ca2ed73bfcaefb20051f12cb6400286ab/atracker/images/checkmark-icon.svg) 
 North America Washington (us-east) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/bcd8b79ca2ed73bfcaefb20051f12cb6400286ab/atracker/images/checkmark-icon.svg) 
 North America Toronto (ca-tor) 
 South America Sao Paulo (br-sao) 



You can use Activity Tracker Event Routing to manage events from enabled-services in the account. To see the list of services that generate events that you can manage by using Activity Tracker Event Routing, see [Services generating events](https://cloud.ibm.com/docs/atracker?topic=atracker-cloud_services_atracker).