---
title: Deprecation of legacy log ingestion endpoints
description: Legacy Coralogix log ingestion endpoints stopped ingesting on September 30, 2026. Find affected configs and switch to region-specific endpoints.
url: https://coralogix.com/docs/user-guides/latest-updates/deprecations/endpoints/
product: ingress
feature: Ingress Overview
feature_id: ingress-general
feature_identifier: ingress/ingress-general
last_updated: '2026-11-02'
---

# Deprecation of legacy log ingestion endpoints

**Published**: July 1, 2025

**Effective**: September 30, 2026

## Deprecation notice

Coralogix permanently deprecated legacy data ingestion endpoints as of September 30, 2026.

These endpoints were originally built around a single global load balancer. Over the past three years, we’ve transitioned to region-specific endpoints and infrastructure to improve availability, observability, and security. Traffic to these endpoints is no longer ingested.

## Why this happened

Legacy ingestion traffic was routed through a shared global load balancer, which made it harder to isolate failures and scale efficiently. By moving to region-specific ingestion domains and dedicated infrastructure, we now offer:

* Domain isolation to reduce the impact of failures
* Improved production observability and monitoring
* Unified naming conventions (e.g., `us1.coralogix.com`, `eu1.coralogix.com`)
* Streamlined endpoint and IP management

## What’s affected

The following legacy ingestion endpoints have been permanently disabled.

### Deprecated public endpoints

* `api.<coralogix domain>/api/v1/logs`
* `api.<coralogix domain>/logs/rest/singles`
* `api.<coralogix domain>/logs/rest/bulk`

### Deprecated private endpoints

* `private-link.<coralogix domain>`
* `private-link-api.<coralogix domain>`

These endpoints may be used in:

* Log shipper configurations (e.g., OpenTelemetry, Filebeat, FluentBit)
* Kubernetes manifests or Helm values files
* AWS Lambda, ECS, or container environment variables
* CI/CD pipelines or automation scripts

Check your configurations for these patterns to identify usage.

## What you need to do

### Update your ingestion endpoints

Replace legacy URLs with the new regional format as follows:

| Legacy URL                                 | New URL                                      |
| ------------------------------------------ | -------------------------------------------- |
| `api.<coralogix domain>/api/v1/logs`       | `ingress.<coralogix domain>/logs/v1/bulk`    |
| `api.<coralogix domain>/logs/rest/singles` | `ingress.<coralogix domain>/logs/v1/singles` |
| `api.<coralogix domain>/logs/rest/bulk`    | `ingress.<coralogix domain>/logs/v1/bulk`    |

### Update authentication headers

Replace the legacy header format:

* **Old**: `token: <your_api_key>`
* **New**: `Authorization: Bearer <cx_api_key>`

Ensure all tools and scripts reflect this change.

### Update IP whitelisting (if applicable)

If your infrastructure restricts outbound access by IP, update to the new CIDR ranges.

**Examples**:

* US1 (Ohio): `18.97.138.64/26`
* EU1 (Ireland): `18.97.198.64/26`
* AP2 (Singapore): `18.99.41.64/26`

## Current state

The following changes are in effect as of September 30, 2026:

* Legacy ingestion endpoints have been permanently shut down.
* Tools using legacy endpoints can no longer ship logs. Some might fail silently.
* Outdated configurations lead to data loss.
* Platform monitoring and visibility might be affected.

## Additional resources

|                                            |                                                                                                                                                            |
| ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Use this guide to update your integrations | [Everything you need to know about the new Coralogix endpoints](https://coralogix.com/blog/everything-you-need-to-know-about-the-new-coralogix-endpoints/) |
| Coralogix Endpoints                        | [Coralogix Endpoints](https://coralogix.com/docs/integrations/coralogix-endpoints.md)                                                                      |

## Need help?

Reach out via our 24/7 in-app support or contact your Technical Account Manager directly. We’re here to help.