---
title: Meter Ingest Automatic Failover
slug: EsQORHtOYXQ42ClJY5NTy
docTags: 
createdAt: 2024-07-11T14:59:32.011Z
---

For **continuous** and resilient production ingestion, Amberflo provides a high-availability endpoint: `ingest.amberflo.io`.

This endpoint is backed by a multi-regional deployment, ensuring that even if the primary ingestion region experiences issues, your meter events will still be [received and processed](docId\:NsJPk3F7DuAkP-05PFyHV)  through a failover path.

To take full advantage of this failover capability, we recommend implementing a **retry policy** in your API client.
**Retry guidelines:**

- Use an **exponential backoff strategy**
- Ensure at least a couple of retry attempts are made **after 20 seconds** from the first failure
- Retry specifically on the following HTTP status codes:
  - 429 (Too Many Requests)
  - Any 5xx server error

If you use one of our SDKs, they have built-in logic for a suitable **retry policy**.&#x20;

- `3.1.0` for [Python](docId\:UlRadkCjdq9zXsR6x8jR-)&#x20;
- `2.6.0` for [TypeScript / JavaScript](docId\:MttOVIPbolHY78UPshT4L)&#x20;
- `2.1.0` for [Go](docId\:LBcsMk_jRBKJ_yRnsRTqM)&#x20;
- `2.1.0` for [Java](docId:0yua0Xf8JxOFq5gx48tor)&#x20;