Ingest Endpoint Failover

for continuous production workloads, we provide an ingestion endpoint with automatic failover ingest amberflo io this endpoint is backed by a multi regional deployment, so that if our main endpoint is having problems, you'll still be able to ingest meter records docid\ t8ybtn9tmllhzvbed2w2p your meter events to fully benefit from using this endpoint, we recommend you set up a retry policy on your api client here is a general guideline use a backoff strategy and make sure a couple of atempts happen after 20 seconds from the first failure; retry for http status codes 429 and 5xx 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 5jsiauw8o2hndzr7lws8v 2 6 0 for typescript and javascript docid\ zhbfifwlrpoewatgq7qbq 2 1 0 for go docid\ gphdsv22qekldehx 5xbu 2 1 0 for java docid 6jk1paotnsnjrrp7itmtx