---
title: "Comment by melonape on \"Rate Limiting Algorithms: How to Protect Your API Without Annoying Your Users\" | Hashnode"
description: "One more thing for the IP section: on IPv6, key on the /64, not the full address. One machine usually gets a whole /64 and can rotate through addresses for free"
url: "https://hashnode.com/posts/rate-limiting-algorithms-how-to-protect-your-api-without-annoying-your-users-hdp4e/6adf13f827c3f1dc1e9bccfc/comment/6ae087e273c73827adacde05"
---

[Discussion](https://hashnode.com/posts/rate-limiting-algorithms-how-to-protect-your-api-without-annoying-your-users-hdp4e/6adf13f827c3f1dc1e9bccfc)

Comment [Rate Limiting Algorithms: How to Protect Your API Without Annoying Your Users](https://hashnode.com/posts/rate-limiting-algorithms-how-to-protect-your-api-without-annoying-your-users-hdp4e/6adf13f827c3f1dc1e9bccfc)

[melonape](https://hashnode.com/@melonape)

[Oct 27](https://hashnode.com/posts/rate-limiting-algorithms-how-to-protect-your-api-without-annoying-your-users-hdp4e/6adf13f827c3f1dc1e9bccfc/comment/6ae087e273c73827adacde05)

One more thing for the IP section: on IPv6, key on the /64, not the full address. One machine usually gets a whole /64 and can rotate through addresses for free, so per-address limits barely slow it down.

Mobile carriers are the opposite problem. A lot of people sit behind carrier-grade NAT, so in some regions one IPv4 can be a whole neighborhood. Per-IP limits only really make sense as a loose outer layer.

[ZyVOP](https://hashnode.com/@zyvop)

[Oct 27](https://hashnode.com/posts/rate-limiting-algorithms-how-to-protect-your-api-without-annoying-your-users-hdp4e/6adf13f827c3f1dc1e9bccfc/comment/6ae087e273c73827adacde05#reply-6ae08be3dd51a132862d202b)

Great points! IPv6 address rotation makes per-address limits much easier to bypass, so aggregating requests by a /64 prefix is a useful additional safeguard. On the other hand, carrier-grade NAT shows why strict IP-based limits can unfairly affect legitimate users sharing the same IPv4 address.

I’d treat IP-based throttling as one layer in a broader strategy, combining it with account-level limits, API keys where applicable, and endpoint-specific quotas. The challenge is balancing abuse prevention with avoiding false positives for legitimate users. Thanks for highlighting both sides!
