Skip to main content
Revyl drives your app from cloud devices, so traffic to your backend comes from Revyl’s infrastructure rather than a typical user’s network. If your app or its backend applies rate limiting, bot detection, or CAPTCHA challenges based on IP reputation or request volume, that traffic can get blocked. Allowlist Revyl’s IP addresses in your rate limiter, WAF, or CAPTCHA provider to prevent this. This applies to any Revyl-driven session against your app: tests, Atlas mapping, and cloud dev loop sessions.

​
IP Addresses

Traffic from Revyl’s backend comes from the following static IP addresses today:

​
Where to Add Them

Add these addresses to whichever layer is blocking Revyl’s traffic:
  • CAPTCHA providers (e.g. reCAPTCHA, hCaptcha, Cloudflare Turnstile): allowlist by IP or disable the challenge for these addresses.
  • Rate limiters and WAFs: add an allow rule so Revyl’s request volume isn’t throttled.
  • Bot/fraud detection: mark these IPs as known-good automated traffic, not abuse.

​
Troubleshooting

If a session unexpectedly hits a CAPTCHA, login block, or “too many requests” error partway through a test or Atlas exploration, confirm the allowlist is in place before assuming it’s a test or app bug.