Frage
Antwort
Lösung
am 23.01.2019 19:51
Dear Team,
I have been with Vodafon since the 1st of Januray. at my place i use internet for gaming thats why i have the 100Mbit contract.
At the begining everything was ok till the last 2 days, i have been encountering an Unstable internet connection with a lot of Package Loss from your side, below you will find the log forthe package los when i try to ping Google.
i would like also to clarify, that i have tried verious programs to ping the destnation IPs and all of them were shooting a 0 Package Loss between my computer and the Router.
I would like to have your support to help me solve this issue.
Thank you in advance,
A.Zaidan
am 24.01.2019 16:11
Hi Zaidan,
do you experience any issues with the connection besides the package loss?
Low bandwidth or loss of connection? Does your phone work normally?
Regards,
Jens
am 24.01.2019 18:44
I have the same problem, the worst of all is that the problem is in the route used and that the vodafone does not change anything! If I use only for games and inside the game I have this problem and I can not play, what good is the internet? For them if the connection test is hitting the contracted speed is ok, which is comic. I just want to know why this started only this year.
C: \ Users \ greenbox> tracert vodafone.de Tracking the route to vodafone.de [139.7.147.49] with a maximum of 30 jumps: 1 <1 ms <1 ms <1 ms 192.168.2.1 2 8 ms 7 ms 7 ms dslb-084-059-211-001.084.059.pools.vodafone-ip.de [84.59.211.1] 3 7 ms 7 ms 7 ms 88.79.15.88 4 10 ms 9 ms 9 ms 88.79.14.180 5 9 ms 9 ms 9 ms 188.111.129.42 6 17 ms 18 ms 17 ms 92.79.215.241 7 20 ms 16 ms 17 ms 92.79.230.14 8 16 ms 16 ms 16 ms 139.7.148.84 9 * * * The order timeout has expired. 10 * * * The order timeout has expired. 11 * * * The order timeout has expired. 12 * * * The order timeout has expired. 13 17 ms 17 ms 17 ms hilfe.vodafone.de [139.7.147.49] Tracking completed. C: \ Users \ greenbox> ping -t vodafone.de Shooting vodafone.de [139.7.147.49] with 32 bytes of data: Response of 139.7.147.49: bytes = 32 time = 17ms TTL = 246 Response of 139.7.147.49: bytes = 32 time = 17ms TTL = 246 Response of 139.7.147.49: bytes = 32 time = 17ms TTL = 246 Response of 139.7.147.49: bytes = 32 time = 17ms TTL = 246 Response of 139.7.147.49: bytes = 32 time = 17ms TTL = 246 Response of 139.7.147.49: bytes = 32 time = 17ms TTL = 246 Response of 139.7.147.49: bytes = 32 time = 17ms TTL = 246 Response of 139.7.147.49: bytes = 32 time = 17ms TTL = 246 Response of 139.7.147.49: bytes = 32 time = 17ms TTL = 246 Response of 139.7.147.49: bytes = 32 time = 17ms TTL = 246 Response of 139.7.147.49: bytes = 32 time = 18ms TTL = 246 Response of 139.7.147.49: bytes = 32 time = 17ms TTL = 246 Response of 139.7.147.49: bytes = 32 time = 17ms TTL = 246 Response of 139.7.147.49: bytes = 32 time = 17ms TTL = 246 Response of 139.7.147.49: bytes = 32 time = 168ms TTL = 246 Response of 139.7.147.49: bytes = 32 time = 327ms TTL = 246 Response of 139.7.147.49: bytes = 32 time = 17ms TTL = 246 Response of 139.7.147.49: bytes = 32 time = 270ms TTL = 246 Response of 139.7.147.49: bytes = 32 time = 196ms TTL = 246 Response of 139.7.147.49: bytes = 32 time = 17ms TTL = 246 Response of 139.7.147.49: bytes = 32 time = 280ms TTL = 246 Response of 139.7.147.49: bytes = 32 time = 17ms TTL = 246 Response of 139.7.147.49: bytes = 32 time = 17ms TTL = 246 Response of 139.7.147.49: bytes = 32 time = 17ms TTL = 246 Response of 139.7.147.49: bytes = 32 time = 17ms TTL = 246 Response of 139.7.147.49: bytes = 32 time = 17ms TTL = 246 Response of 139.7.147.49: bytes = 32 time = 18ms TTL = 246 Response of 139.7.147.49: bytes = 32 time = 17ms TTL = 246