Menu
Reply
  • 1
  • 0
  • 0
AndyHippo
Just joined
215 Views
Message 1 of 2
Flag for a moderator

Slow browsing - Tracert showing timeouts

First post, so Im not sure if this is in the right place.

Noticed yesterday that webpages were slow in rendering, images slow to load etc.

Rebooted the modem, tried wired and wifi, also appears consistant across Windows and Linux.

Tried a tracert to Imgur.com, lots of timeouts.

Tracing route to imgur.com [151.101.60.193]
over a maximum of 30 hops:

  1     2 ms     2 ms     5 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3    11 ms    11 ms     9 ms  perr-core-2a-ae20-99.network.virginmedia.net [62
.255.149.205]
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6    29 ms    25 ms    24 ms  pres-core-2a-ae16-0.network.virginmedia.net [62.
254.42.26]
  7    26 ms    24 ms    34 ms  know-wblk-1a-xe-200-0.network.virginmedia.net [6
2.254.1.214]
  8     *        *        *     Request timed out.
  9   657 ms   602 ms   596 ms  213.46.174.110
 10    30 ms    46 ms    28 ms  ae-2-3212.edge6.London1.Level3.net [4.69.141.250
]
 11    35 ms    27 ms    30 ms  FASTLY-INC.edge6.London1.Level3.net [212.113.9.2
02]
 12    27 ms    32 ms    43 ms  151.101.60.193

Trace complete.

C:\Windows\system32>

Is there a fault at the moment? Im in Area 12.

0 Kudos
Reply
  • 11.8K
  • 1.08K
  • 2.56K
griffin
Alessandro Volta
203 Views
Message 2 of 2
Flag for a moderator

Re: Slow browsing - Tracert showing timeouts

The tracert is fine, it is the last hop that counts.

The timeouts are due to servers configured not to respond to ICMP timeout requests as they have better things to do like make the coffee.
More on Tracerts HERE.

Whilst Tracerts are useful in tracing sources of high ping to a particular server, they are not very good at diagnosing slow speeds as they only give a snapshot of what is happening on route to one particular server at that split second in time.
A Broadband Quality Monitor is much more useful, as it monitors pings at a set interval to your Hub from TBB's Firebrick servers.

The main cause of slow wired speeds is a circuit problem between the Hub and VM's servers, although there are many other causes including your own equipment.

The first step would be to post some basic diagnostic info which may help.

Navigate to the hub's GUI using http://192.168.0.1
Don't log in, click the Router Status button
Copy \ Paste the Downstream, Upstream, and Network Logs.

Don't worry about the formatting, but do obscure personal information like your WAN IP address.

 

0 Kudos
Reply