Rate limiting
Rate limiting in Templass Panel caps how fast a protocol or listener may pass toward your origin. Use it when a port must stay open but should not accept unlimited clean-looking floods.
When to use it
- A game or voice port must remain reachable, but a flood still consumes your clean budget
- You want a ceiling per source or per service, if Panel offers that control
- Default mitigation is working, yet one listener is still hotter than the rest of the host
Do not use rate limiting as the first response to "the site is down" if Attacks is empty. Fix routing first.
How to change a limit
- Open Rate limiting for the service.
- Set the limit using the units Panel shows (Panel is the source of truth for units).
- Save once.
- Wait. Like firewall rules, provisioning can take time.
- Watch Attacks and the origin. If legitimate users stall, relax the limit instead of stacking extra rules.
Honest limits of this page
Templass does not publish a hidden global PPS table in these docs. Any number you type should come from:
- What your application can actually handle
- What your plan bandwidth can carry
- What Panel accepts
If you need a limit that the UI cannot express, write [email protected] or ask in Discord. Do not invent a second control plane.
Rate limiting vs the plan
A rate limit does not raise Essential / Standard / Premium Mbps. It only shapes what is allowed through within (or toward) that budget. Overage still follows 95th percentile rules if you pull more clean traffic than the plan includes.