in need for english communication service - packet loss outside my router

vor 6 Stunden

in short: my local ping is fine but my ping to 8.8.8.8 drops often and my average speed is consistently 10 Mbs while it should have been higher according to my contract

more detailed:

 example ping to 8.8.8.8:

Reply from 8.8.8.8: bytes=32 time=42ms TTL=118

Reply from 8.8.8.8: bytes=32 time=97ms TTL=118

Request timed out.

Reply from 8.8.8.8: bytes=32 time=67ms TTL=118

Reply from 8.8.8.8: bytes=32 time=48ms TTL=118

Reply from 8.8.8.8: bytes=32 time=48ms TTL=118

Reply from 8.8.8.8: bytes=32 time=54ms TTL=118

Reply from 8.8.8.8: bytes=32 time=82ms TTL=118

Reply from 8.8.8.8: bytes=32 time=75ms TTL=118

Reply from 8.8.8.8: bytes=32 time=48ms TTL=118

Reply from 8.8.8.8: bytes=32 time=98ms TTL=118

Reply from 8.8.8.8: bytes=32 time=74ms TTL=118

Reply from 8.8.8.8: bytes=32 time=96ms TTL=118

Request timed out.

Reply from 8.8.8.8: bytes=32 time=78ms TTL=118

Request timed out.

Reply from 8.8.8.8: bytes=32 time=139ms TTL=118

Reply from 8.8.8.8: bytes=32 time=64ms TTL=118

Request timed out.

Reply from 8.8.8.8: bytes=32 time=76ms TTL=118

Reply from 8.8.8.8: bytes=32 time=69ms TTL=118

Reply from 8.8.8.8: bytes=32 time=79ms TTL=118

Reply from 8.8.8.8: bytes=32 time=89ms TTL=118

Reply from 8.8.8.8: bytes=32 time=96ms TTL=118

Reply from 8.8.8.8: bytes=32 time=56ms TTL=118

Reply from 8.8.8.8: bytes=32 time=94ms TTL=118

Reply from 8.8.8.8: bytes=32 time=96ms TTL=118

Request timed out.

Reply from 8.8.8.8: bytes=32 time=91ms TTL=118

Reply from 8.8.8.8: bytes=32 time=34ms TTL=118

Reply from 8.8.8.8: bytes=32 time=71ms TTL=118

Request timed out.

Reply from 8.8.8.8: bytes=32 time=75ms TTL=118

Reply from 8.8.8.8: bytes=32 time=65ms TTL=118

Reply from 8.8.8.8: bytes=32 time=96ms TTL=118

Reply from 8.8.8.8: bytes=32 time=74ms TTL=118

Reply from 8.8.8.8: bytes=32 time=41ms TTL=118

Reply from 8.8.8.8: bytes=32 time=98ms TTL=118

Reply from 8.8.8.8: bytes=32 time=89ms TTL=118

Reply from 8.8.8.8: bytes=32 time=60ms TTL=118

Reply from 8.8.8.8: bytes=32 time=97ms TTL=118

Reply from 8.8.8.8: bytes=32 time=89ms TTL=118

Reply from 8.8.8.8: bytes=32 time=70ms TTL=118

Reply from 8.8.8.8: bytes=32 time=80ms TTL=118

Reply from 8.8.8.8: bytes=32 time=64ms TTL=118

Reply from 8.8.8.8: bytes=32 time=54ms TTL=118

Request timed out.

Request timed out.

Reply from 8.8.8.8: bytes=32 time=99ms TTL=118

Reply from 8.8.8.8: bytes=32 time=27ms TTL=118

Reply from 8.8.8.8: bytes=32 time=94ms TTL=118

Reply from 8.8.8.8: bytes=32 time=55ms TTL=118

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Reply from 8.8.8.8: bytes=32 time=41ms TTL=118

Reply from 8.8.8.8: bytes=32 time=90ms TTL=118

Reply from 8.8.8.8: bytes=32 time=63ms TTL=118

Reply from 8.8.8.8: bytes=32 time=2761ms TTL=118

Reply from 8.8.8.8: bytes=32 time=90ms TTL=118

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Request timed out.

ping to local IP address:

Pinging 192.168.2.34 with 32 bytes of data:

Reply from 192.168.2.34: bytes=32 time<1ms TTL=128

Reply from 192.168.2.34: bytes=32 time<1ms TTL=128

Reply from 192.168.2.34: bytes=32 time<1ms TTL=128

Reply from 192.168.2.34: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.2.34:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 0ms, Maximum = 0ms, Average = 0ms

Pinging 192.168.2.34 with 32 bytes of data:

Reply from 192.168.2.34: bytes=32 time<1ms TTL=128

Reply from 192.168.2.34: bytes=32 time<1ms TTL=128

Reply from 192.168.2.34: bytes=32 time<1ms TTL=128

Reply from 192.168.2.34: bytes=32 time<1ms TTL=128

Reply from 192.168.2.34: bytes=32 time<1ms TTL=128

Reply from 192.168.2.34: bytes=32 time<1ms TTL=128

Reply from 192.168.2.34: bytes=32 time<1ms TTL=128

Reply from 192.168.2.34: bytes=32 time<1ms TTL=128

Reply from 192.168.2.34: bytes=32 time<1ms TTL=128

Reply from 192.168.2.34: bytes=32 time<1ms TTL=128

Reply from 192.168.2.34: bytes=32 time<1ms TTL=128

Reply from 192.168.2.34: bytes=32 time<1ms TTL=128

Reply from 192.168.2.34: bytes=32 time<1ms TTL=128

Reply from 192.168.2.34: bytes=32 time<1ms TTL=128

Reply from 192.168.2.34: bytes=32 time<1ms TTL=128

Reply from 192.168.2.34: bytes=32 time<1ms TTL=128

Reply from 192.168.2.34: bytes=32 time<1ms TTL=128

Reply from 192.168.2.34: bytes=32 time<1ms TTL=128

Reply from 192.168.2.34: bytes=32 time<1ms TTL=128

Reply from 192.168.2.34: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.2.34:

    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 0ms, Maximum = 0ms, Average = 0ms

ping to local gateaway: 

Pinging 192.168.2.1 with 32 bytes of data:

Reply from 192.168.2.1: bytes=32 time=2ms TTL=64

Reply from 192.168.2.1: bytes=32 time=2ms TTL=64

Reply from 192.168.2.1: bytes=32 time=1ms TTL=64

Reply from 192.168.2.1: bytes=32 time=2ms TTL=64

Reply from 192.168.2.1: bytes=32 time=2ms TTL=64

Reply from 192.168.2.1: bytes=32 time=2ms TTL=64

Reply from 192.168.2.1: bytes=32 time=2ms TTL=64

Reply from 192.168.2.1: bytes=32 time=2ms TTL=64

Reply from 192.168.2.1: bytes=32 time=15ms TTL=64

Reply from 192.168.2.1: bytes=32 time=2ms TTL=64

Reply from 192.168.2.1: bytes=32 time=1ms TTL=64

Reply from 192.168.2.1: bytes=32 time=1ms TTL=64

Reply from 192.168.2.1: bytes=32 time=1ms TTL=64

Reply from 192.168.2.1: bytes=32 time=1ms TTL=64

Reply from 192.168.2.1: bytes=32 time=1ms TTL=64

Reply from 192.168.2.1: bytes=32 time=1ms TTL=64

Reply from 192.168.2.1: bytes=32 time=1ms TTL=64

Reply from 192.168.2.1: bytes=32 time=1ms TTL=64

Reply from 192.168.2.1: bytes=32 time=1ms TTL=64

Reply from 192.168.2.1: bytes=32 time=1ms TTL=64

Reply from 192.168.2.1: bytes=32 time=1ms TTL=64

Reply from 192.168.2.1: bytes=32 time=1ms TTL=64

Reply from 192.168.2.1: bytes=32 time=1ms TTL=64

Reply from 192.168.2.1: bytes=32 time=1ms TTL=64

Reply from 192.168.2.1: bytes=32 time=1ms TTL=64

Reply from 192.168.2.1: bytes=32 time=1ms TTL=64

Reply from 192.168.2.1: bytes=32 time=1ms TTL=64

Reply from 192.168.2.1: bytes=32 time=2ms TTL=64

Reply from 192.168.2.1: bytes=32 time=2ms TTL=64

Reply from 192.168.2.1: bytes=32 time=1ms TTL=64

Reply from 192.168.2.1: bytes=32 time=1ms TTL=64

Reply from 192.168.2.1: bytes=32 time=1ms TTL=64

Reply from 192.168.2.1: bytes=32 time=2ms TTL=64

Reply from 192.168.2.1: bytes=32 time=1ms TTL=64

Reply from 192.168.2.1: bytes=32 time=1ms TTL=64

Reply from 192.168.2.1: bytes=32 time=2ms TTL=64

Reply from 192.168.2.1: bytes=32 time=1ms TTL=64

Reply from 192.168.2.1: bytes=32 time=1ms TTL=64

Reply from 192.168.2.1: bytes=32 time=2ms TTL=64

Reply from 192.168.2.1: bytes=32 time=1ms TTL=64

Reply from 192.168.2.1: bytes=32 time=2ms TTL=64

Reply from 192.168.2.1: bytes=32 time=1ms TTL=64

Reply from 192.168.2.1: bytes=32 time=2ms TTL=64

Reply from 192.168.2.1: bytes=32 time=2ms TTL=64

Reply from 192.168.2.1: bytes=32 time=2ms TTL=64

Reply from 192.168.2.1: bytes=32 time=1ms TTL=64

Reply from 192.168.2.1: bytes=32 time=1ms TTL=64

Reply from 192.168.2.1: bytes=32 time=2ms TTL=64

Reply from 192.168.2.1: bytes=32 time=1ms TTL=64

Reply from 192.168.2.1: bytes=32 time=22ms TTL=64

Ping statistics for 192.168.2.1:

    Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 1ms, Maximum = 22ms, Average = 2ms

traceroute data:

Tracing route to dns.google [8.8.8.8]

over a maximum of 30 hops:

  1     *        *        *     Request timed out.

  2    50 ms    57 ms    65 ms  p3e9bf7ea.dip0.t-ipconnect.de [62.155.247.234]

  3  1057 ms     *        *     f-ed11-i.F.DE.NET. DTAG .DE [62.154.3.166]

  4     *        *        *     Request timed out.

  5     *        *        *     Request timed out.

  6     *        *        *     Request timed out.

  7     *        *        *     Request timed out.

  8     *        *        *     Request timed out.

  9     *        *        *     Request timed out.

 10     *       61 ms    65 ms  dns.google [8.8.8.8]

Trace complete.

Tracing route to dns.google [8.8.8.8]

over a maximum of 30 hops:

  1     *        *        *     Request timed out.

  2    33 ms    30 ms    24 ms  p3e9bf7ea.dip0.t-ipconnect.de [62.155.247.234]

  3    27 ms    28 ms    30 ms  f-ed11-i.F.DE.NET. DTAG .DE [62.154.3.166]

  4    74 ms    80 ms    77 ms  87.128.238.134

  5    49 ms    50 ms    45 ms  192.178.109.167

  6    49 ms    43 ms    52 ms  209.85.241.75

  7    76 ms    76 ms    78 ms  dns.google [8.8.8.8]

Trace complete.

additional information:

my contract is non-fiber and uses SIM cell device

if possible i would love to get an english service, and even better if its possible to be communicated through the phone

thank you very much for your time!

25

0

4

    • vor 5 Stunden

      Hi @user_1851f0 ,

      since you seem to already have entered your customer ID and a number for a return call, the support agents (called "teamies" in these parts) should be able to call you back.

      HOWEVER, troubleshooting might be quicker if you (also) work with the volunteers in this community, at least up to a certain point should the issue turn out to be an actual network issue.

      The traces and the slow speed you mentioned make it look like a bad/weak mobile connection. So some input is needed:

      • What tariff did you book from Telekom?
      • What router (make/model) are you using?
      • Can you get a report on RSRP ( LTE / 5G signal strength) and RSRQ ( LTE / 5G signal quality) out of the router? If you could find out what Cell-ID the router is using, that would be helpful too.
      • How is your computer connected to the router? Wifi? LAN?

      3

      von

      vor 5 Stunden

      thank you for the reply:

      im using

      MagentaZuhause M Hybrid + WLAN Comfort und 5G -Empfänger

      device name is:  Speedport Smart 4 Typ B

      my computer is connected through WiFi

      DSL link: Synchronous

      Downstream: 16.62 Mbit/s

      Upstream: 2.581 Mbit/s

      5G / LTE connection: Not active Info

      Internet connection Active since 2025-09-12 16:48

      Download bandwidth up to 13.63 Mbit/s

      Upload bandwidth up to 2.115 Mbit/s

      PPPoE concentrator EILJ00

      SmartHome function

      Active

      Wi-Fi in the 2.4 GHz frequency band

      Channel 1 (Automatically)

      Wi-Fi name ( SSID )

      MagentaWLAN-ZZU8

      Logged-in Wi-Fi devices

      0

      Wi-Fi in the 5 GHz frequency band

      Channel 100, 104, 108, 112 (Automatically)

      Wi-Fi name ( SSID )

      MagentaWLAN-ZZU8

      Logged-in Wi-Fi devices

      2

       

      0

      von

      vor 4 Stunden

      update: thank you for your help, the issue was that the 5G device was disconnected - thank you!

      0

      von

      vor 4 Stunden

      Hello @user_1851f0,

       

      thank you for the post. 😊

      Great that you were able to figure out the issue.

       

      If you need any further assistance, feel free to let me know.

       

      Kind regards

      Belana

      0

      Uneingeloggter Nutzer

      von

    Uneingeloggter Nutzer

    von

    Das könnte Ihnen auch weiterhelfen

    Beliebte Tags letzte 7 Tage

    Loading...Loading...Loading...Loading...Loading...Loading...Loading...Loading...Loading...Loading...