(1) , (2) , (3) A 502 error from the Cloud PDP is not normal behavior and suggests either a temporary service issue or you may be hitting rate limits (2) . The Cloud PDP includes built-in rate limiting to prevent abuse . Rate limits are applied per IP address over a 1-minute window, and if exceeded, the Cloud PDP returns an HTTP 429 response (not 502) . However, corporate networks where many users share a single public IP could contribute to rate limit issues . For the

/user-permissions

endpoint specifically, the limit is 500 requests per minute . If you exceed this, you should receive a 429 response with this body :

{
  "error": "rate_limited",
  "message": "You have exceeded the rate limit. Please try again later."
}

Since you're getting 502 errors instead, this points to a different issue. For latency-sensitive deployments or high-volume workloads, deploying a local Edge PDP is recommended to minimize network latency and ensure high availability (3) . To help investigate this issue, could you please provide: 1. Which Workspace / Project / Env you are using 2. What calls you are performing (as SDK code or CURL) 3. Which PDP version you are running 4. Relevant logs from your PDP Additionally, if you're experiencing frequent 502 errors, you may want to consider deploying an Edge PDP as a sidecar or centralized service inside your own infrastructure

To learn more, see the sources I considered: [[1] Permit's PDP (Policy Decision Point)](https://docs.permit.io/concepts/pdp/overview) [[2] Cloud PDP Capabilities](https://docs.permit.io/concepts/pdp/cloud-pdp-capabilities) [[3] Run your First Policy Check (Managed Cloud PDP)](https://docs.permit.io/overview/perform-policy-check-with-cloud-pdp)

We are deploying a fix to this issue soon. Ill update you when its in place

By the way, do you have a timeline for this fix? As we are looking to have users access our application soon. Thank you @david

Hi, as of now, all our requests to the Cloud PDP is returning the same error.