### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

When virtual keys make a failed request to the proxy, the request appears to not be counted towards the key's RPM limits unless it is replied to successfully.

We have observed this behaviour causing service degradation in some instances where the liteLLM proxy struggles after a virtual key keeps making requests that fail without hitting the RPM limit.

Would it be possible to address this, either correcting the behaviour or (If this behaviour is intended) adding a configuration to count incorrect requests towards the limit?

### Steps to Reproduce

1. Configure a virtual key with a given TPM (e.g. 20) 2. Make incorrect request consistently (e.g. returning 400) 3. Virtual key is allowed to make over 20RPM

### Relevant log output

```shell

```

### What part of LiteLLM is this about?

Proxy

### What LiteLLM version are you on ?

1.81.3

### Twitter / LinkedIn details

_No response_