# Coralogix endpoints Copy as Markdown[Open in ChatGPT](https://chatgpt.com/?q=Read%20https%3A%2F%2Fcoralogix.com%2Fdocs%2Fintegrations%2Fcoralogix-endpoints.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)[Open in Claude](https://claude.ai/new?q=Read%20https%3A%2F%2Fcoralogix.com%2Fdocs%2Fintegrations%2Fcoralogix-endpoints.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.) Coralogix provides regional endpoints for all observability and management traffic to ensure optimal performance and reliability. Action required by September 30, 2026: legacy log ingestion endpoints The following ingestion endpoints will be permanently disabled on **September 30, 2026**: * `api./api/v1/logs` * `api./logs/rest/singles` * `api./logs/rest/bulk` * `private-link.` and `private-link-api.` Update your ingestion URLs, authentication headers, and IP allowlists before the cutoff to avoid data loss. See the [legacy log ingestion endpoints deprecation notice](https://coralogix.com/docs/user-guides/latest-updates/deprecations/endpoints.md) for full migration steps. For all other endpoint updates and deprecations, see the [Coralogix endpoint updates and deprecations](https://coralogix.com/docs/integrations/endpoint-updates.md) page. ## Coralogix endpoint domain[​](#coralogix-endpoint-domain "Direct link to Coralogix endpoint domain") * Determined by the URL your team uses to sign in (your team hostname) * Used to identify the correct region and base domain for all ingestion and management endpoints For example: * Team hostname `my-team.coralogix.com` → domain `eu1.coralogix.com` (EU1 region) * Team hostname `my-team.app.coralogix.us` → domain `us1.coralogix.com` (US1 region) ## How to find the correct endpoints[​](#how-to-find-the-correct-endpoints "Direct link to How to find the correct endpoints") ### 1. Identify your Coralogix domain[​](#1-identify-your-coralogix-domain "Direct link to 1. Identify your Coralogix domain") Your Coralogix domain is determined by the URL your team uses to log in (your team hostname). This domain determines which regional endpoints your integrations should use. Each team hostname maps directly to a specific Coralogix domain and region. If you’re unsure which domain applies to your account, check your login URL and refer to the domain mapping table below. | **Coralogix domain** | **Coralogix region** | **Region** | **Team hostname** | | -------------------- | -------------------- | ------------------------------ | --------------------------------- | | us1.coralogix.com | US1 | AWS us-east-2 (Ohio) | `.app.coralogix.us` | | us2.coralogix.com | US2 | AWS us-west-2 (Oregon) | `.app.cx498.coralogix.com` | | us3.coralogix.com | US3 | GCP us-central1 (Iowa) | `.app.us3.coralogix.com` | | eu1.coralogix.com | EU1 | AWS eu-west-1 (Ireland) | `.coralogix.com` | | eu2.coralogix.com | EU2 | AWS eu-north-1 (Stockholm) | `.app.eu2.coralogix.com` | | ap1.coralogix.com | AP1 | AWS ap-south-1 (Mumbai) | `.app.coralogix.in` | | ap2.coralogix.com | AP2 | AWS ap-southeast-1 (Singapore) | `.app.coralogixsg.com` | | ap3.coralogix.com | AP3 | AWS ap-southeast-3 (Jakarta) | `.app.ap3.coralogix.com` | | gov1.coralogixgov.us | GOV1 | AWS GovCloud us-gov-west-1 | `.app.gov1.coralogixgov.us` | FedRAMP customers `gov1.coralogixgov.us` is the Coralogix FedRAMP environment in AWS GovCloud. It is a separate authorization boundary from the commercial regions, and only logs, metrics, and traces are in scope. Select GOV1 in the domain selector to see its endpoints, and read [FedRAMP](https://coralogix.com/docs/user-guides/account-management/fedramp.md) for what the environment covers and how to reach it. ### 2. Select your domain[​](#2-select-your-domain "Direct link to 2. Select your domain") In the upper-right corner of this page, open the domain selector and select the domain correlated with your team's login URL (e.g., eu1.coralogix.com, us1.coralogix.com, etc.). ### 3. View updated endpoints[​](#3-view-updated-endpoints "Direct link to 3. View updated endpoints") The tables below will automatically refresh to show the correct ingress and management endpoints for your region. Look for the badge to confirm the selected domain. ## Endpoints[​](#endpoints "Direct link to Endpoints") The tables below provide the most up-to-date, generally available endpoints provided by Coralogix. [AWS PrivateLink](https://docs.aws.amazon.com/vpc/latest/privatelink/what-is-privatelink.html) endpoints can be found [here](https://coralogix.com/docs/integrations/aws/aws-privatelink/aws-privatelink.md). For endpoints scheduled for future deprecation, see [Upcoming deprecations](https://coralogix.com/docs/integrations/endpoint-updates/upcoming-deprecations.md). **Use the [domain selector](https://coralogix.com/docs/user-guides/account-management/account-settings/coralogix-domain.md) in the upper right corner of the page to automatically display the correct endpoints for your Coralogix domain in the tables below.** ### Ingress endpoints[​](#ingress-endpoints "Direct link to Ingress endpoints") | Integration | Endpoint | | -------------------------- | ---------------------------------- | | AWS events | https\://ingress./aws/event-bridge | | AWS Firehose | https\://ingress./aws/firehose | | Coralogix Logs | https\://ingress. | | Coralogix REST API singles | https\://ingress./logs/v1/singles | | OpenTelemetry | ingress.:443 | | Prometheus RemoteWrite | https\://ingress./prometheus/v1 | | TLS / TCP Syslog | syslog.:6514 | Note No need to include the `https://` prefix when using grpcurl with the gRPC Management endpoint. Note The OpenTelemetry endpoint accepts OTLP/gRPC and OTLP/HTTP, with HTTP payloads encoded as binary protobuf (`Content-Type: application/x-protobuf`) or JSON (`Content-Type: application/json`). For OTLP/HTTP, append the signal path to the endpoint (`/v1/logs`, `/v1/metrics`, `/v1/traces`). See [custom logs](https://coralogix.com/docs/developer-portal/apis/data-ingestion/opentelemetry-custom-logs.md), [custom metrics](https://coralogix.com/docs/developer-portal/apis/data-ingestion/opentelemetry-custom-metrics.md), and [custom traces](https://coralogix.com/docs/developer-portal/apis/data-ingestion/opentelemetry-custom-traces.md) for examples. ### Management endpoints[​](#management-endpoints "Direct link to Management endpoints") | Integration | Endpoint | | ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------- | | Bitbucket version tags | https\://api./api/v1/external/bitbucket | | Custom enrichment | https\://api./api/v1/external/custom-enrichments | | DataPrime | https\://api./api/v1/dataprime/query | | External alerts | https\://api./api/v2/external/alerts | | GitLab version tags | https\://api./api/v1/external/gitlab | | Grafana API | https\://api./grafana/api | | gRPC Management | https\://api.:443 | | Guardrails | https\://api./api/v1/guardrails/guard | | MCP | https\://api./mgmt/api/v1/mcp | | Metrics | https\://api./metrics | | Metrics cardinality | https\://api./api/metrics/cardinality | | Microsoft Azure DevOps server version tags | https\://api./api/v1/external/tfs?application=YOUR\_APPLICATION\_NAME\&subsystem=YOUR\_SUBSYSTEM\_NAME\&name=YOUR\_TAG\_NAME | | OpenAPI | https\://api./mgmt/openapi | | OpenSearch | https\://api./data/os-api | | SCIM | https\://api./scim | | Security report | https\:///xdr/get-report | | SQL | https\://api./sql | | TCO Optimizer | https\://api./api/v1/external/tco | | Uploading Debug Symbols: iOS | https\://api.:443 | | Version tags | https\://api./api/v1/external/tags | | Webhooks | https\://api./api/v1/external/integrations | ## Egress outbound IPs[​](#egress-outbound-ips "Direct link to Egress outbound IPs") Static IP ranges and regional DNS endpoints Coralogix has rolled out static Elastic IP ranges and standardized regional DNS endpoints. For the complete inbound and outbound allowlist per region, the region CIDR blocks, and the endpoints you should not allowlist, see [Static IPs and regional DNS endpoints](https://coralogix.com/docs/integrations/endpoint-updates/ingestion-deprecation.md). Outbound traffic leaves a region over more than one network path, and a given request can use any of them. Allow every address listed for your region. | Coralogix domain | Cloud region | Egress
outbound IPs | | -------------------- | ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | us3.coralogix.com | us-central1
\[US3 - Iowa, GCP] | Contact Support | | eu1.coralogix.com | eu-west-1
\[EU1 - Ireland] | 54.194.244.111
34.250.16.124
52.17.67.46
3.254.248.34
34.250.243.8
54.155.189.136 | | ap1.coralogix.com | ap-south-1
\[AP1 - India] | 15.207.141.107
15.207.139.137
13.232.75.108
3.110.253.1
43.204.47.19
13.202.150.227 | | us1.coralogix.com | us-east-2
\[US1 - Ohio] | 3.14.38.38
18.220.187.63
3.16.8.72
18.190.11.135
3.132.208.6
13.58.152.171 | | eu2.coralogix.com | eu-north-1
\[EU2 - Stockholm] | 16.170.136.62
13.49.242.97
13.51.99.107
13.48.169.70
13.53.237.6
16.170.144.103
51.20.231.161
51.20.48.212
16.171.130.8 | | ap2.coralogix.com | ap-southeast-1
\[AP2 - Singapore] | 52.76.36.24
52.221.151.232
13.213.144.73
52.74.217.199
54.251.250.35
52.76.54.183 | | us2.coralogix.com | us-west-2
\[US2 - Oregon] | 35.83.61.173
52.10.88.176
34.218.132.57
16.147.201.66
35.88.120.58
54.202.185.211
35.81.105.176
52.24.128.51
44.246.101.81 | | ap3.coralogix.com | ap-southeast-3
\[AP3 - Jakarta] | 108.137.52.186
108.137.194.153
16.78.128.198
16.78.209.125
16.78.195.213
43.218.142.155
16.78.211.53 | | gov1.coralogixgov.us | us-gov-west-1
\[GOV1 - AWS GovCloud] | Contact Support | Note Some outbound addresses in US2 and AP3 can still change. Allow the full list for the region, and re-check this page if outbound connections from Coralogix start failing. ## Limits and quotas[​](#limits-and-quotas "Direct link to Limits and quotas") Coralogix places the following limits on endpoints: * A hard limit of 10MB of data to our OpenTelemetry endpoint, with a recommendation of 2MB * A hard limit of 2411724 bytes of data to our Prometheus RemoteWrite endpoint, with a recommendation for any amount less than this limit Limits apply to single requests, regardless of timespan. ## Additional resources[​](#additional-resources "Direct link to Additional resources") | | | | ------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | GitHub | [Coralogix Telemetry Shippers](https://github.com/coralogix/telemetry-shippers)
[Coralogix OpenTelemetry Exporter](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/coralogixexporter) | | Docs | [Coralogix Domain](https://coralogix.com/docs/user-guides/account-management/account-settings/coralogix-domain.md)
[Coralogix Lambda Telemetry](https://coralogix.com/docs/integrations/aws/aws-lambda-telemetry-exporter.md) |