LogoLogo
DiscordPanelPricing
  • TCPShield
  • FAQ
  • Commonly asked questions
  • Features
  • Contact
  • Billing
  • Vxlan
    • VXLAN Features
    • VXLAN Tunnel Setup Guide
    • Common issues and Debugging
  • Premium Features
    • Asia Network
    • Geyser
    • Panel Features
  • Panel
    • Setup Process
    • Panel Configuration
    • DNS Setup
    • TCPShield Plugin
  • Troubleshooting
    • Setup Checklist
    • Invalid Hostname
    • Disconnected on Login
    • High Latency and General Lag
    • How to Read a Traceroute
    • Connection Complaint Policy
  • Miscellaneous
    • TCPShield API
    • Protect a website
    • Wildcard DNS
    • Protect a home hosted server
    • Account sharing
    • Transfer Packets
  • Useful Links
  • TCPShield Panel
Powered by GitBook
LogoLogo

Useful links

  • Pricing
  • Twitter
  • Contact

Need help?

  • Discord
  • Network Status

Panel

  • Sign Up
  • Login
On this page

Was this helpful?

  1. Troubleshooting

Connection Complaint Policy

We try our best to deliver the most performant network we can for our customers. Unfortunately, there are some things are are simply out of our control (congestion on ISPs, unstable mobile data signal, microwave ovens turned on, or similar).

Therefore, TCPShield requires the following before considering a connection degradation event:

  • A minimum of 5 players in similar region experiencing similar issue(s)

  • A traceroute from at least one player, to TCPShield tracert play.yourserver.com

  • Source IP or usernames from at least 3 players.

TCPShield will not impose fixes for one-off connection complains, and must see evidence of widespread issues. The internet is large and complex, and does not route ideally at times. As such, imposing fixes for one player may create unexpected issues for others.

PreviousHow to Read a TracerouteNextTCPShield API

Last updated 2 years ago

Was this helpful?