Too Many Requests Error

You've hit AliasFleet's rate limit. This is a temporary block — your account is fine, nothing is broken, and it clears on its own.

Why this happens

Every account has a limit on how many API requests it can make per minute. When you go over that limit, the server responds with a 429 Too Many Requests error until the window resets.

This can happen if you:

• Refresh a page very quickly several times in a row
• Have multiple tabs open doing background syncing simultaneously
• Run a script or automation that makes rapid requests
• Have a browser extension that's polling frequently

Normal use of AliasFleet — browsing aliases, sending emails, checking activity — won't trigger this.

What to do

Wait. The limit resets automatically, usually within 60 seconds. You'll see a message telling you how long to wait. Once it clears, everything works normally again.

Don't keep retrying — repeated attempts during a block just extend the frustration. One reload after the wait is all you need.

Login-specific blocks

If the error occurs on the login page, it means there have been too many failed login attempts from your IP. This block lasts up to 10 minutes and is a security measure against brute-force attacks.

Wait 10 minutes, then try logging in again. If you've forgotten your password, use Forgot Password instead of guessing repeatedly.

If you're a developer or building an integration

Your plan's per-minute limit applies to all API usage. The 429 response includes a Retry-After header that tells you exactly how many seconds to wait. Implement exponential backoff in your integration to handle this gracefully.

Limits by plan:

If you're regularly hitting limits, upgrading your plan is the cleanest solution. See API Rate Limits by Plan.

Still seeing the error after waiting?

If the error persists for more than a few minutes and you haven't been making rapid requests, open a support ticket so we can investigate.