Edgegap · Rate Limits

Edgegap Rate Limits

The Edgegap Arbitrium API enforces per-account request rate limits and concurrency quotas on management operations (creating deployments, sessions, matchmaking tickets, and relay sessions). Concurrent deployment counts are also bounded by the account tier. Specific per-endpoint values are not reconciled in this artifact; excess requests return HTTP 429.

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

It captures 4 rate-limit definitions, measuring requests, deployments, tickets, and sessions.

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

Tagged areas include Game Servers, Orchestration, Edge Computing, Matchmaking, and Hosting.

4 Limits Throttle: 429
Game ServersOrchestrationEdge ComputingMatchmakingHostingRate LimitingQuotasThrottling

Limits

Management API Requests account
requests
see provider documentation
Per-account request rate on Arbitrium management endpoints.
Concurrent Deployments account
deployments
see provider documentation
Maximum simultaneous running deployments, varies by tier.
Matchmaking Tickets account
tickets
see provider documentation
Ticket creation rate on the matchmaker service.
Relay Sessions account
sessions
see provider documentation
Concurrent relay session count, varies by tier.

Policies

Tiered Limits
Quotas and concurrency raise as accounts move from free to paid and via Enterprise agreements.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources