Rate limits and bounded retries
Rate limits and bounded retries
Limits can vary by route, account and resource. Follow the actual status and headers instead of treating illustrative numbers as a service-wide promise. Where present, inspect X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset and Retry-After.
For 429, pause and follow a valid Retry-After; otherwise use capped exponential backoff with jitter. Bound the number of retries, set timeouts and report the final failure clearly.
Read-only requests can be retried when appropriate. Do not blindly repeat backup, command, power or delete operations after a timeout: first determine whether they took effect. Cache non-live data and reduce polling. Do not rely on an unavailable webhook service.
Events and webhook integrations
Updated steps and current-interface reference for events and webhook integrations.
Malaysia Lite (MY-L)
Suitable for survival servers, friends playing together and small plugin servers. HDD RAID and older Xeon processors differ from the Economy NVMe platform; more RAM alone does not resolve CPU or disk bottlenecks.