Matomo Cloud uses rate limiting on some resources to ensure fair and reliable service for all customers. Most API consumers may never encounter rate limiting, but a very small amount of consumers may encounter rate limiting.

Matomo Cloud primarily rate limits by individual IP, but some resources are rate limited by subdomain or account. Resources that are rate limited are restricted to the dashboard usage and Reporting API, we do not rate limit the Tracking API or tracking endpoints.

If you do encounter a 429 Too Many Requests HTTP code in a response from Matomo Cloud then you are likely being rate limited. In this case, please configure your application to stand down and reattempt the request at a later time. Please use the below table as a reference to the various configured rate limits. They are applied by the order in which they are listed. For example, if a request is blocked by rule #1, then the following rules will not be evaluated.

Note: These limits are subject to change without prior notice and may be adjusted based on network conditions.

# Resource Rate limit Path Scope
1 Non-tracking requests / API requests 2,000 / 10 mins
or
350 / 1 min
(whichever occurs first)
Is a non-tracking path.
This applies to Reporting API requests, Dashboard-related paths, and UI paths.
Per IP
2 Live resources 200 / 1 min Contains method=live or module=live Per IP
3 Transitions resources 500 / 5 mins Contains method=transitions or module=transitions Per IP
4 Raw data resources 8 simultaneous queries Contains Live.getCounters, Live.getLastVisitsDetails,
Live.getVisitorProfile, CustomReports.previewReport,
or AdvertisingConversionExport.generateConversionExport
Per subdomain/account

Please note that there are 2 different types of rate limiting utilised on Matomo Cloud. One of these is traditional rate limiting of the amount of request over a period of time, the second type is a limit of the current amount of simultaneous queries being run at any one time.

Next FAQ: