[VFKD] Hohe Pingwerte immer Abends von 19-23 Uhr

[maik005]

Lass Mal eine traceroute zu 1.1.1.1 8.8.8.8 und 2001:4860:4860::8888 laufen.

Einfach in der Windows Eingabeaufforderung
tracert "IP"

Die ersten IPs von deinem PC/WLAN Router kannst/solltest du unkenntlich machen.

[schwenno]

...ich bin nicht sehr smart - ich machs nochmal.

[schwenno]

Lass Mal eine traceroute zu 1.1.1.1 8.8.8.8 und 2001:4860:4860::8888 laufen.

jetzt aber!

[Esska]

Same issue here, also in Berlin 10999. High ping after 8pm (usually in the range of 120ms).

Got the support on the line too, they said "we can't do anything against that issue, we also don't know when it's gonna be 'solved'".

Considering changing to DSL line (since their the bandwith characteristics aren't shared amongst customers). Also thinking about upgrading to 1000MB/s, but not sure this would make any difference.

The issue seems to obviously come from network saturation, it is claimed it's because of COVID...

Any suggestions? Do vodafone usually adresse those king of problems, or they just let the network be as it is and don't invest further?

------

Gleiches Thema hier, ebenfalls in Berlin 10999. Hoher Ping nach 20 Uhr (normalerweise im Bereich von 120ms).

Habe auch die Unterstützung in der Leitung, sie sagten, "wir können nichts gegen dieses Problem tun, wir wissen auch nicht, wann es 'gelöst' wird".

Sie zogen in Betracht, auf eine DSL-Leitung umzusteigen (da ihre Bandbreiteneigenschaften nicht unter den Kunden geteilt werden). Wir denken auch über ein Upgrade auf 1000MB/s nach, sind aber nicht sicher, ob dies einen Unterschied machen würde.

Das Problem scheint offensichtlich von der Netzwerksättigung herrührend zu sein, es wird behauptet, es sei wegen COVID...

Irgendwelche Vorschläge? Wendet sich Vodafone normalerweise an diese König der Probleme, oder lassen sie das Netzwerk einfach so sein, wie es ist, und investieren nicht weiter?

Übersetzt mit www.DeepL.com/Translator

[schwenno]

Same issue here, also in Berlin 10999. High ping after 8pm (usually in the range of 120ms).

Hi esska,

I got in touch with the Twitter-Support today - they confirmed there is a high workload at the primetime and opened a ticket - I'll keep this post updated, if I know more.

Regards!
Sven

[Esska]

Same issue here, also in Berlin 10999. High ping after 8pm (usually in the range of 120ms).

Hi esska,

I got in touch with the Twitter-Support today - they confirmed there is a high workload at the primetime and opened a ticket - I'll keep this post updated, if I know more.

Regards!
Sven

Thanks for the update !

Also realised it wasn't only the ping yesterday, at 10pm I had like 20MB Download and 22 MB upload (+ 140 ping)...

[schwenno]

@Esska - Does the problem still persist for you? I sent you a DM.

[Esska]

@Esska - Does the problem still persist for you? I sent you a DM.

Definitively does. As I mentioned on DM, here are the results over the evening:

Time / Ping / Download (Mbps) / Upload (Mbps)
19:54: 76 / 308 / 24
20:04: 35 / 386 / 24
20:21: 22 / 397 / 25
20:47: 75 / 247 / 24
21:56: 110 / 30 / 23

[Esska]

So, a technician came today. He was scheduled for 5PM, and I mentioned in the messages it would be too early to see any problem on the network.

The technician obviously didn't find problems, thefull speed is and was available at that time.

Now, they say they will charge us for 90-100€ since if the technician cannot find anything, his cost falls into the customer's hands.

This is obvious racketing, I was never given any information about that cost in any form, and would never have agreed to pay if he didn't find anything. I would definitively have said: "Sure, come, you will find something" had he come in the evening, but certainly not during the day when everything is normal.

This is pure nonesense at that stage.

[schwenno]

So - seit drei Tagen scheint der Spuk vorbei zu sein - Pingwerte und Bandbreite wieder im Normalmaß. Keine Ahnung, was da geklöppelt wurd, ich kanns nicht nachvollziehen - hab spaßenshalber nochmal Twitter kontaktiert ob die was wissen, ansonsten verbuch ich das unter "fixed itself" und hoff, dass das nich mehr auftritt

Schöne Grüße, bleibt Gesund!
Sven