Being rate limited (427) when way below 15 concurrent connections

[leaden hound]

Hello! Around 1/3 to 1/2 of all requests we're making are being rate limited, even though we're nowhere near 15 concurrent connections

In the past day, we used 51 minutes (on pay as you go plan), with 172 requests.

We are using nova-3 on the streaming /listen endpoint. This is what we normally use:

/v1/listen?model=nova-3&punctuate=true&smart_format=true&dictation=false&diarize=false&numerals=false&no_delay=true&interim_results=true&encoding=linear16&vad_events=true&sample_rate=16000&channels=1&endpointing=100&filler_words=true&profanity_filter=false&language=multi

The project ID is 2220bdcd-5575-49de-8d05-de48de593b5f

A few of the rate limited requests are 67f6fa65-6ad1-4d07-93fe-fe750d495817,
27f2a813-3db1-4a88-ac8a-6bc226410cf2, and a4299ea0-3132-4864-aff6-062e9c6621c1

[brazen pebble]

Thanks for asking your question. Please be sure to reply with as much detail as possible so the community can assist you efficiently.
-# If you haven't done so, ensure your Discord and Github profiles are linked to Deepgram so you can earn points to redeem on cool stuff just by being active!

It looks like we're missing some important information to help debug your issue. Would you mind providing us with the following details in a reply?

• The programming language you are working in (e.g. JavaScript, Python).

[leaden hound]

We're using JavaScript to connect to the websocket ans stream audio to it, but this issue is before when implementation would be relevant

[leaden hound]

This seems to be resolved now. Hasn't been erroring due to the rate limit for a little bit.

Thank you Deepgram!

[magic kayak]

Thanks for letting us know! Glad to hear it’s back to normal for you.