---
name: cloud-logs-endpoints_ingress
title: Ingress endpoints
description: Logs can be sent to IBM Cloud Logs by using the listed endpoints for each supported IBM Cloud location.
last-updated: 2026-05-12
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/cloud-logs?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Ingress endpoints
{: #endpoints_ingress}

Logs can be sent to IBM Cloud Logs by using the listed endpoints for each supported IBM Cloud [location](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-regions&format=markdown).
{: shortdesc}

The endpoints can be found on the [service instance details page](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-observe&interface=ui&format=markdown#observe-cloud-ui).
{: important}

## Public endpoints
{: #ingress-public-endpoints}

Public endpoints can be accessed from the public internet.

| Geography | Region                           | Endpoint |
|-----------|----------------------------------|---------------------|
| Asia Pacific  | Osaka (`jp-osa`) | `<service-instance-guid>.ingress.jp-osa.logs.cloud.ibm.com` |
| Asia Pacific  | Sydney (`au-syd`) | `<service-instance-guid>.ingress.au-syd.logs.cloud.ibm.com` |
| Asia Pacific  | Tokyo (`jp-tok`) | `<service-instance-guid>.ingress.jp-tok.logs.cloud.ibm.com` |
| Asia Pacific  | Chennai (`in-che`) | `<service-instance-guid>.ingress.in-che.logs.cloud.ibm.com` |
| Asia Pacific  | Mumbai (`in-mum`) | `<service-instance-guid>.ingress.in-mum.logs.cloud.ibm.com` |
| Europe  | Frankfurt (`eu-de`) | `<service-instance-guid>.ingress.eu-de.logs.cloud.ibm.com` |
| Europe  | London (`eu-gb`) | `<service-instance-guid>.ingress.eu-gb.logs.cloud.ibm.com` |
| Europe  | Madrid (`eu-es`) | `<service-instance-guid>.ingress.eu-es.logs.cloud.ibm.com` |
| North America  | Toronto (`ca-tor`) | `<service-instance-guid>.ingress.ca-tor.logs.cloud.ibm.com` |
| North America | Montreal (`ca-mon`) | `<service-instance-guid>.ingress.ca-mon.logs.cloud.ibm.com` |
| North America  | Dallas (`us-south`) | `<service-instance-guid>.ingress.us-south.logs.cloud.ibm.com` |
| North America  | Washington (`us-east`) | `<service-instance-guid>.ingress.us-east.logs.cloud.ibm.com` |
| South America  | Sao Paulo (`br-sao`) | `<service-instance-guid>.ingress.br-sao.logs.cloud.ibm.com` |
{: caption="List of IBM Cloud Logs ingress endpoints" caption-side="top"}

## Private endpoints
{: #ingress-private-endpoints}

Private endpoints restrict access to the IBM Cloud private network. After creation, a service instance can be accessed using private endpoints.

| Geography | Region                           | Endpoint | Purpose |
|-----------|----------------------------------|---------------------|--------------------|
| Asia Pacific  | Osaka (`jp-osa`) | `<service-instance-guid>.ingress.private.jp-osa.logs.cloud.ibm.com` |
| Asia Pacific  | Sydney (`au-syd`) | `<service-instance-guid>.ingress.private.au-syd.logs.cloud.ibm.com` |
| Asia Pacific  | Tokyo (`jp-tok`) | `<service-instance-guid>.ingress.private.jp-tok.logs.cloud.ibm.com` |
| Asia Pacific  | Chennai (`in-che`) | `<service-instance-guid>.ingress.private.in-che.logs.cloud.ibm.com` |
| Asia Pacific  | Mumbai (`in-mum`) | `<service-instance-guid>.ingress.private.in-mum.logs.cloud.ibm.com` |
| Europe  | Frankfurt (`eu-de`) | `<service-instance-guid>.ingress.private.eu-de.logs.cloud.ibm.com` |
| Europe  | London (`eu-gb`) | `<service-instance-guid>.ingress.private.eu-gb.logs.cloud.ibm.com` |
| Europe  | Madrid (`eu-es`) | `<service-instance-guid>.ingress.private.eu-es.logs.cloud.ibm.com` |
| North America  | Montreal (`ca-mon`) | `<service-instance-guid>.ingress.private.ca-mon.logs.cloud.ibm.com` |
| North America  | Toronto (`ca-tor`) | `<service-instance-guid>.ingress.private.ca-tor.logs.cloud.ibm.com` |
| North America  | Dallas (`us-south`) | `<service-instance-guid>.ingress.private.us-south.logs.cloud.ibm.com` |
| North America  | Washington (`us-east`) | `<service-instance-guid>.ingress.private.us-east.logs.cloud.ibm.com` |
| South America  | Sao Paulo (`br-sao`) | `<service-instance-guid>.ingress.private.br-sao.logs.cloud.ibm.com` |
{: caption="List of IBM Cloud Logs private ingress endpoints" caption-side="top"}


The private ingress endpoint is only supported in Montreal (`ca-mon`) using a [VPE](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-vpe-connection&interface=cli&format=markdown).
{: note}


When connecting to a private endpoint using a [VPE](https://cloud.ibm.com/docs/cloud-logs?topic=cloud-logs-vpe-connection&interface=cli&format=markdown), use port 443. When connecting to a private endpoint using a [CSE](https://cloud.ibm.com/docs/account?topic=account-service-endpoints-overview&format=markdown), use port 3443.
{: important}