Ingest Endpoint Failover

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, we've updated them to use this endpoint with a suitable retry policy the sdk versions using the new endpoint start at 3 1 0 for python docid\ ulradkcjdq9zxsr6x8jr 2 6 0 for typescript / javascript docid\ mttovipbolhy78upsht4l 2 1 0 for go docid\ lbcsmk jrbkj yrnsrtqm 2 1 0 for java docid 0yua0xf8jxofq5gx48tor