Port requests

Port requests is how you open or close TCP and UDP ports on this service. Applied changes show as Active or Closed. Mitigation is worse when the platform does not know you serve 443/tcp or a game port.

The heading line is Open or close TCP and UDP ports on this service.

Request a port change

1. Open Port requests. Confirm the service window is open.

2. Under Request a port change, set:

   Field	What it does
   Direction	OPEN or CLOSE
   Protocol	TCP or UDP
   Port start	First port
   Port end	Optional. Leave equal to start for a single port
   Purpose	Short reason (for example Minecraft, HTTPS, SSH)

3. Click Submit request.

4. Confirm the row under Port changes: Direction, Protocol, Port, Purpose, Status, Applied.

The edge applies the change once it is validated. Status moves to Active (open) or Closed.

What to request

• Ports your origin listens on for customers
• Both TCP and UDP when the application uses both
• New ports before you advertise them

Need a wide range? Open a Ticket or write [email protected] rather than requesting 1–65535 by default.

After acceptance

Confirm:

• Firewall still allows the port if you added DENY rules
• Rate limiting is not clipping the new listener
• Clients use the protected address, not the origin

During an attack

A brand-new port request mid-event may not land in time. Say that you have a pending row when you file a Ticket, and keep the existing listener on Templass. See Under attack.