Rate Limits on Xurrent IMR

Xurrent IMR is committed to providing reliable incident alerts. To protect our systems from being overwhelmed due to excessive alerts and to provide better throughput, Xurrent IMR applies rate limits at the account level to all integration alerts and API requests.

If a request exceeds the rate limit, the request is either rejected with the HTTP status 429 - Too Many Requests or a HTTP status 404 or HTTP sttus 401 in case an integration does not exist or is disabled. Your client or integration should be setup in such a way that the client retries after some time(1 minute) once it encounters a 4xx code. Please ensure that the reties are spaced out, or exponential backoff is enabled within your integration applications. You can also look at splitting your service into multiple integrations or services. In case there are consistent rate limit excesses, Xurrent IMR will block further traffic based on either the Integration, API Key, IP, User or Account.

Xurrent IMR limits the number of alerts sent to a specific integration to approximately 100 alerts/minute and incidents triggered to approximately 60/minute.

Limits also apply to number of SMS/Phone call alerts sent to a user, which depends on their subscription plan as follows:

Xurrent IMR applies certain rate limits to some API requests to ensure proper and orderly access of Xurrent IMR's incident and alert data.