Roleplay UK

Pop a response there if you have a static IP and Wilco will whitelist your IP on the firewall 

@KevinP Unfortunately I spoke to Wilco, he said that only affects S1 / S2 logins, not TS.

ooooo

Working fine here @JohnJoeegan whats your ISP ?

Thanks for the replys everyone! And @WilcoVirgin media. However I can connect on my phones WiFi so its a issue with my PC I Believe. I Just ran out of ideas :/

I'm having this issue too, I'm on BT.

Strange... maybe a reinstall of teamspeak is worth ago, Also have you changed or installed anything since you last joined teamspeak on your PC ?

It has just started happening, I got kicked off about 10 minutes ago and can't connect any more. So from my side nothing has changed. 

@WilcoIve already tried. The only thing what I can possibly think it may be is windows update. However who knows! Back to trouble shooting!

Happened to me, happens to me before and just had to wait for it to come back.

Welcome to my world....

@BennyBaitThanks for the information buddy! I'm just sat here curled up into a ball xD

@JohnJoeeganTry switching DNS servers, couple be a problem with your local DNS caches which haven't properly cached a response. Once you've followed this guide below, go to the command prompt and type: "ipconfig /flushdns" which will clear existing cached responses.

http://www.howtogeek.com/164981/how-to-switch-to-opendns-or-google-dns-to-speed-up-web-browsing/

Only a problem with Altis Life. At the moment I cant connect to the server and TS..... Like I'm not wanted...

I've tried that and it didn't work for me Any other advice anyone! 

Thank you all for your replies. Sadly still no luck! More trouble shooting tomorrow! (When I wake up)

Must be something server side then

If you can't even ping: 185.38.151.194, then it's most likely a Firewall issue (could be either end) or possibly a routing issue. Try doing a "Tracert 185.38.151.194" into a command prompt. It might highlight a routing issue.

Rather suspect that we all suddenly can't connect at the same time

Wow I can finally connect

@BennyBait, very true, there must be something that is related to you all that's causing an issue. Right now it's all about ruling out issues.

Below is that my trace route reveals.
(Please note that I can connect to TS with no issues).

Basically you can clearly see I'm leaving the BT network and hitting the DDOS filter most likely for the data centre wilco's servers are hosted in (after that the trace dies most likely because ICMP is blocked by firewalls from there on. If you run a trace route and it doesn't even get that far, then it might highlight an issue with your ISP's network.

Tracing route to 185.38.151.194 over a maximum of 30 hops
  1    <1 ms     1 ms    <1 ms  BThomehub.home [192.168.1.254]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4    16 ms    16 ms    16 ms  31.55.187.180
  5    15 ms    20 ms    16 ms  core1-hu0-8-0-1.southbank.ukcore.bt.net [195.99.127.176]
  6    16 ms    16 ms    16 ms  peer1-et-10-1-0.telehouse.ukcore.bt.net [195.99.127.3]
  7    17 ms    17 ms    17 ms  lon-tel-01gw.voxility.net [195.66.226.180]
  8     *        *        *     Request timed out.
  9    18 ms    17 ms    17 ms  FILTER-DDoS [5.254.107.1]

I can not ping the server. And this is my Trace results.

Tracing route to 185.38.151.194 over a maximum of 30 hops

  1     3 ms     1 ms     1 ms  192.168.0.1
  2    95 ms     8 ms     9 ms  10.7.164.1
  3     8 ms     8 ms     9 ms  wolv-core-2b-xe-300-0.network.virginmedia.net [80.3.146.77]
  4     *        *        *     Request timed out.
  5    11 ms    10 ms    10 ms  brhm-bb-1c-ae0-0.network.virginmedia.net [62.254.42.110]
  6    20 ms    14 ms    13 ms  tcl5-ic-2-ae0-0.network.virginmedia.net [212.250.15.210]
  7    39 ms    34 ms    31 ms  lon-tel-01gw.voxility.net [195.66.226.180]
  8     *        *        *     Request timed out.
  9    31 ms    32 ms    31 ms  FILTER-DDoS [5.254.107.1]
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *       19 ms    18 ms  185.38.151.194