How to Report Network Performance Issues?

As the internet is a large, sometimes unpredictable network, not all issues that may occur are in our control. If a performance issue occurs and does not get resolved by our automatic systems, action may be required. Below you can find how you should report network performance issues.

 Step 1: Pre-Checklist for Server-Related Issues 

To ensure a fast resolution and rule out common local configuration issues, please verify the following on your server before creating a support ticket:

  • LACP Configuration: Confirm if your server is configured to use LACP. If you are unsure, please use our guides to ensure your setup is correct.

  • Hashing Mode: Verify that hashing is set to the Layer3+4 mode.

  • Port Negotiation: Check that both network ports have successfully negotiated their connection.

  • Multi-Stream Testing: If using multiple streams to test your connection, confirm they are correctly balanced and utilizing both ports.

  • Link Congestion: Ensure the server's network link is not already congested by other traffic outside of the test you are running.

  • Remote Server Capacity: Verify that the server you are testing to/from has enough network and processing capacity to handle the test at the full speed of your server's connection.

  • Official Speedtest Tool: If you are using the Ookla speedtest, you must use the official command-line tool. You can find the correct tool for your operating system here.

 Step 2: Information to Include in Your Support Ticket 

When you submit a support ticket in the portals, providing the following information is essential for our network engineers to begin their investigation:

  • Server Tag: The unique tag of the affected server (e.g., 123-456).

  • Evidence of the Issue: The specific data and output you used to conclude there is a performance issue. Please include the actual, unedited information for our team to review.

  • Remote Server IP Address: If applicable, the IP address of the remote server that was used for testing.

  • Link Status Command Output: The complete output of the following shell command: ip -s link

About the author

Sjoerd van Groning

Sjoerd van Groning brings a multidisciplinary technical background to his role as Product Manager at NovoServe. With deep experience spanning network architecture, server infrastructure, and application hosting (including previous leadership at software firm Phusion), Sjoerd understands the full IT stack—from the physical fiber layer to the application runtime. His expertise lies in translating complex operational requirements into robust hardware designs, ensuring that bare metal configurations are engineered to support specific software workloads. Sjoerd focuses on the intersection of engineering constraints and system performance, designing infrastructure that is technically sound and built for scale.