Gcore · Rate Limits

Gcore Rate Limits

Gcore applies per-service rate limits on its unified REST API at api.gcore.com. The Streaming API documents a general limit of about four requests per second; the CDN purge operation is constrained to one "purge all" request per CDN resource per minute and two "purge by URL" requests per resource per minute, with a single URL purge limited to 100 URLs and a single pattern purge limited to 10 patterns. Cloud, DNS, Storage, WAAP, Inference, and FastEdge enforce their own per-account quotas and request limits that are not fully enumerated in public docs. Specific values beyond the ones noted here are not reconciled in this artifact.

Gcore Rate Limits is the machine-readable rate-limit profile for Gcore on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 6 rate-limit definitions, measuring requests.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Edge Cloud, CDN, Streaming, Edge AI, and Infrastructure.

6 Limits Throttle: 429
Edge CloudCDNStreamingEdge AIInfrastructureRate LimitingQuotasThrottling

Limits

Streaming API Requests account
requests
~4 requests per second
Documented general limit on the Streaming API.
CDN Purge All resource
requests
1 per minute per CDN resource
One "purge all cache" request per CDN resource per minute.
CDN Purge by URL resource
requests
2 per minute per CDN resource
Up to 100 URLs per request; pattern purge limited to 10 patterns per request.
Cloud API Requests account
requests
see provider documentation
Per-account request limits; resource quotas are project/region scoped.
DNS API Requests account
requests
see provider documentation
Per-account limits vary by plan.
WAAP / Inference / FastEdge Requests account
requests
see provider documentation
Per-service quotas; not fully enumerated publicly.

Policies

Per-Service Limits
Limits are enforced per product (CDN, Cloud, DNS, Streaming, etc.) rather than as a single global token bucket.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Quota Increases
Cloud resource quotas can be raised by contacting Gcore support.

Sources