# Getting API throttled (?) by Elastic, cannot understand why **URL:** \ **Category:** Elastic Search\ **Created:** [October 24, 2025, 3:19pm UTC](https://discuss.elastic.co/t/getting-api-throttled-by-elastic-cannot-understand-why/382955 "2025-10-24T15:19:35Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![maxxer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/maxxer/32/50472_2.png) [@maxxer](https://discuss.elastic.co/u/maxxer)\ **Post date:** [October 24, 2025, 3:19pm UTC](https://discuss.elastic.co/t/getting-api-throttled-by-elastic-cannot-understand-why/382955/1 "2025-10-24T15:19:35Z")
Hi. We have an Elastic Cloud 7.17.18 managed instance we use for our staging app, along with two others we use for Training and Production. In the staging environment we’re rather frequently unable to connect to our Elasticsearch instance due to connection refused or similar errors. It really looks like a throttling mechanism, but we’re unable to identify the cause of this blocking, as we’re not doing anything that could lead to this behavior. Well, of course this could be accidental, and we don’t know (yet). What I’m looking for, here, is help on identifying proofs of this blocks, if it can happen in Elastic and where should I look for such errors. I tried in _Monitoring \> Logs and metrics_, _Access and security \> Network security_, I see no error logs or other evidence. Where should I find **if** our app is being blocked for too many attempts, or for unkind usage? As a background, our app is PHP8.2 based, using Elastica library to connect over HTTPS. The error happens at: ```auto Elastica\Exception\Connection\HttpException Couldn't connect to host, Elasticsearch down? vendor/ruflin/elastica/src/Transport/Http.php:186 Elastica\Transport\Http::exec vendor/ruflin/elastica/src/Request.php:183 Elastica\Request::send vendor/ruflin/elastica/src/Client.php:545 Elastica\Client::request vendor/ruflin/elastica/src/Client.php:580 Elastica\Client::requestEndpoint vendor/ruflin/elastica/src/Cluster.php:60 Elastica\Cluster::refresh vendor/ruflin/elastica/src/Cluster.php:48 Elastica\Cluster::__construct ``` thanks ---
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [October 24, 2025, 6:54pm UTC](https://discuss.elastic.co/t/getting-api-throttled-by-elastic-cannot-understand-why/382955/2 "2025-10-24T18:54:19Z")
Hi @maxxer In general Elastic Cloud does not throttle API requests... There are some throttles on the Elastic Coud Hosted Admin APIs itself such as billing requests and things like that. So you'll have to provide more information about exactly which API you are hitting And kind of what the volume you're hitting. If you are hitting normal elasticsearch endpoints APIs and they're not responding, that's probably more a function of the capacity of the cluster. We have clusters that are ingesting a quarter million events per second or 10s of thousands search requests on a properly sized cluster So provide a little more information and maybe we can help... Be precise on exactly what API endpoint you're hitting and what you're trying to accomplish and what the volume is All that said... There certainly could be an issue with something along the chain Also, keep in mind since it's elastic cloud, depending on your subscription level, you'd be able to open a support ticket. ---
**Author:** ![Danny\_M](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danny_m/32/140180_2.png) [@Danny\_M](https://discuss.elastic.co/u/Danny_M)\ **Post date:** [October 25, 2025, 5:12am UTC](https://discuss.elastic.co/t/getting-api-throttled-by-elastic-cannot-understand-why/382955/3 "2025-10-25T05:12:51Z")
(post deleted by author) ---
**Author:** ![RainTown](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raintown/32/140206_2.png) [@RainTown](https://discuss.elastic.co/u/RainTown)\ **Post date:** [October 25, 2025, 10:00am UTC](https://discuss.elastic.co/t/getting-api-throttled-by-elastic-cannot-understand-why/382955/4 "2025-10-25T10:00:24Z")
welcome to the forum @Danny_M But did you intend to post this on this thread? ---
**Author:** ![Danny\_M](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danny_m/32/140180_2.png) [@Danny\_M](https://discuss.elastic.co/u/Danny_M)\ **Post date:** [October 25, 2025, 11:37pm UTC](https://discuss.elastic.co/t/getting-api-throttled-by-elastic-cannot-understand-why/382955/5 "2025-10-25T23:37:54Z")
No I'm playing around with Claude and must've posted it on accident sorry…. Nice that tho ---
**Author:** ![maxxer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/maxxer/32/50472_2.png) [@maxxer](https://discuss.elastic.co/u/maxxer)\ **Post date:** [January 8, 2026, 11:33am UTC](https://discuss.elastic.co/t/getting-api-throttled-by-elastic-cannot-understand-why/382955/6 "2026-01-08T11:33:06Z")
I haven’t updated yet because I wasn’t able to debug this furtherly… Now the issue _seem_ to be gone. So, either we deployed something that was triggering this problem, or we _accidentally_ fixed it in the meantime. I’ll likely come back to this in the future, unluckily. Thank you for your answers!