Menu
Reply
  • 4
  • 0
  • 0
philbarker66
Tuning in
258 Views
Message 1 of 8
Flag for a moderator

Issue routing to web host; packets lost.

I'm having problems connecting to my web and email host. It's very slow and often times out. The problem only happens when I connect via Virgin Cable, not when connecting via Wifi hotspot on phone (GiffGaff/O2).

When I try to ping my hosts IP I get up 50% packet loss (again, all this is a problem on Virgin Cable, not when going via phone hotspot).

The problem seems to be with the last hop or so to my host (see traceroute and ping output below). I get similar results whether pinging from linux command line or the Virgin Media Hub.

Any ideas on how to fix this? I'm at a loss even to work out who's problem it is.

TIA Phil

phil@shuttle:$ nslookup blogs.pjjk.net
Server: 192.168.0.100
Address: 192.168.0.100#53

Non-authoritative answer:
Name: blogs.pjjk.net
Address: 167.99.190.14

phil@shuttle:$ traceroute 167.99.190.14
traceroute to 167.99.190.14 (167.99.190.14), 30 hops max, 60 byte packets
1 _gateway (192.168.0.1) 1.515 ms 2.146 ms 2.726 ms
2 10.234.172.1 (10.234.172.1) 20.326 ms 20.964 ms 21.210 ms
3 sgyl-core-2b-xe-220-0.network.virginmedia.net (62.252.46.141) 21.444 ms 21.631 ms 21.815 ms
4 * * *
5 * * *
6 * 86.85-254-62.static.virginmediabusiness.co.uk (62.254.85.86) 34.043 ms *
7 * * *
8 be2869.ccr42.lon13.atlas.cogentco.com (154.54.57.161) 25.399 ms * be2870.ccr41.lon13.atlas.cogentco.com (154.54.58.173) 28.606 ms
9 * * be3487.ccr51.lhr01.atlas.cogentco.com (154.54.60.6) 27.782 ms
10 * be2391.ccr21.lpl01.atlas.cogentco.com (154.54.39.150) 32.977 ms 32.905 ms
11 be3042.ccr21.ymq01.atlas.cogentco.com (154.54.44.162) 121.929 ms be3043.ccr22.ymq01.atlas.cogentco.com (154.54.44.166) 120.882 ms 120.299 ms
12 * * be3260.ccr32.yyz02.atlas.cogentco.com (154.54.42.89) 138.294 ms
13 be3528.rcr51.b054249-0.yyz02.atlas.cogentco.com (66.28.4.246) 142.087 ms be3529.rcr51.b054249-0.yyz02.atlas.cogentco.com (154.54.24.194) 142.365 ms *
14 38.104.159.10 (38.104.159.10) 141.318 ms * 38.104.159.18 (38.104.159.18) 146.909 ms
15 * * 138.197.249.91 (138.197.249.91) 150.826 ms
16 clash.reclaimhosting.com (167.99.190.14) 154.378 ms 153.839 ms 136.014 ms

[ping my host]
phil@shuttle:$ ping -c 10 167.99.190.14
PING 167.99.190.14 (167.99.190.14) 56(84) bytes of data.
64 bytes from 167.99.190.14: icmp_seq=1 ttl=48 time=136 ms
64 bytes from 167.99.190.14: icmp_seq=3 ttl=48 time=135 ms
64 bytes from 167.99.190.14: icmp_seq=4 ttl=48 time=134 ms
64 bytes from 167.99.190.14: icmp_seq=6 ttl=48 time=133 ms
64 bytes from 167.99.190.14: icmp_seq=8 ttl=48 time=138 ms
64 bytes from 167.99.190.14: icmp_seq=10 ttl=48 time=140 ms

--- 167.99.190.14 ping statistics ---
10 packets transmitted, 6 received, 40% packet loss, time 9048ms
rtt min/avg/max/mdev = 133.319/136.484/140.059/2.336 ms

[ping hop before the host, doesn't want to play]
phil@shuttle:$ ping -c 10 138.197.249.91
PING 138.197.249.91 (138.197.249.91) 56(84) bytes of data.

--- 138.197.249.91 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 9211ms

[ping hop host-2, no problem]
phil@shuttle:$ ping -c 10 38.104.159.10
PING 38.104.159.10 (38.104.159.10) 56(84) bytes of data.
64 bytes from 38.104.159.10: icmp_seq=1 ttl=50 time=139 ms
64 bytes from 38.104.159.10: icmp_seq=2 ttl=50 time=138 ms
64 bytes from 38.104.159.10: icmp_seq=3 ttl=50 time=132 ms
64 bytes from 38.104.159.10: icmp_seq=4 ttl=50 time=132 ms
64 bytes from 38.104.159.10: icmp_seq=5 ttl=50 time=134 ms
64 bytes from 38.104.159.10: icmp_seq=6 ttl=50 time=131 ms
64 bytes from 38.104.159.10: icmp_seq=7 ttl=50 time=132 ms
64 bytes from 38.104.159.10: icmp_seq=8 ttl=50 time=134 ms
64 bytes from 38.104.159.10: icmp_seq=9 ttl=50 time=132 ms
64 bytes from 38.104.159.10: icmp_seq=10 ttl=50 time=131 ms

--- 38.104.159.10 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9011ms
rtt min/avg/max/mdev = 131.752/134.157/139.830/2.602 ms

 

0 Kudos
Reply
  • 3.66K
  • 240
  • 607
Roger_Gooner
Community elder
250 Views
Message 2 of 8
Flag for a moderator

Re: Issue routing to web host; packets lost.

It's working for me although it's a bit slow.

C:\>ping blogs.pjjk.net

Pinging blogs.pjjk.net [167.99.190.14] with 32 bytes of data:
Reply from 167.99.190.14: bytes=32 time=135ms TTL=48
Reply from 167.99.190.14: bytes=32 time=130ms TTL=48
Reply from 167.99.190.14: bytes=32 time=128ms TTL=48
Reply from 167.99.190.14: bytes=32 time=127ms TTL=48

Ping statistics for 167.99.190.14:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 127ms, Maximum = 135ms, Average = 130ms

 

C:\>tracert blogs.pjjk.net

Tracing route to blogs.pjjk.net [167.99.190.14]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    29 ms    16 ms    26 ms  haye-core-2a-xe-233-0.network.virginmedia.net [62.253.8.121]
  4     *        *        *     Request timed out.
  5    12 ms    11 ms     9 ms  m686-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.174]
  6     9 ms     9 ms    28 ms  213.46.174.118
  7   129 ms   127 ms   127 ms  ldn-bb4-link.telia.net [62.115.134.138]
  8     *      126 ms   125 ms  nyk-bb3-link.telia.net [62.115.112.244]
  9   123 ms   116 ms   116 ms  motl-b1-link.telia.net [62.115.137.143]
 10   124 ms   135 ms   124 ms  toro-b1-link.telia.net [62.115.134.48]
 11   126 ms   126 ms   127 ms  digitalocean-ic-313814-toro-b1.c.telia.net [62.115.55.30]
 12     *        *        *     Request timed out.
 13   134 ms   130 ms   128 ms  clash.reclaimhosting.com [167.99.190.14]

Trace complete.

--
Hub 3.0, TP-Link Archer C8, TP-Link TL-SG1008D 8-port gigabit switch, V6
My Broadband Ping - Roger's VM Broadband Connection
  • 4
  • 0
  • 0
philbarker66
Tuning in
238 Views
Message 3 of 8
Flag for a moderator

Re: Issue routing to web host; packets lost.

Thank you Roger. Interesting that you're getting a different route to me. 

 

0 Kudos
Reply
  • 3.66K
  • 240
  • 607
Roger_Gooner
Community elder
228 Views
Message 4 of 8
Flag for a moderator

Re: Issue routing to web host; packets lost.

Another thing to note is that Firefox gives the following when attempting to connect to 167.99.190.14:

167.99.190.14 uses an invalid security certificate.

The certificate is only valid for the following names: mail.richardmoorepersonal.com, richardmoorepersonal.com, www.richardmoorepersonal.com

Error code: SSL_ERROR_BAD_CERT_DOMAIN

--
Hub 3.0, TP-Link Archer C8, TP-Link TL-SG1008D 8-port gigabit switch, V6
My Broadband Ping - Roger's VM Broadband Connection
  • 31
  • 0
  • 2
mackerbootle
Tuning in
205 Views
Message 5 of 8
Flag for a moderator

Re: Issue routing to web host; packets lost.

Having problems here too

Only seems to affect some sites. Works fine on Wi-Fi but not on computers connected directly by cable - 3 computers.

Getting the below error messages...

This site can’t be reached www.bootlehistory.co.uk took too long to respond.
Try:Checking the connection
Checking the proxy and the firewall
Running Windows Network Diagnostics

ERR_TIMED_OUT


This site can’t be reached www.bootlehistory.co.uk is currently unreachable.
Try:Checking the connection
Checking the proxy and the firewall
ERR_SSL_VERSION_INTERFERENCE


This page isn’t working www.bootlehistory.co.uk didn’t send any data.
ERR_EMPTY_RESPONSE

As I mentioned works fine on Wi-Fi. Checked with my web host and they are not seeing any issues there. They may be using Wi-Fi or a different broadband supplier.

This only started happening today. Tested with Firefox, Chrome, Edge and IE11.

 

0 Kudos
Reply
  • 4
  • 0
  • 0
philbarker66
Tuning in
201 Views
Message 6 of 8
Flag for a moderator

Re: Issue routing to web host; packets lost.

Thanks for the info @mackerbootle 

0 Kudos
Reply
  • 4
  • 0
  • 0
philbarker66
Tuning in
195 Views
Message 7 of 8
Flag for a moderator

Re: Issue routing to web host; packets lost.

This seems fixed now. (Happened after I stopped trying to do anything about it)

My best guess is that a router somewhere needed kicking, or that bad routing info got cached somewhere, but is now cleared.

0 Kudos
Reply
  • 31
  • 0
  • 2
mackerbootle
Tuning in
192 Views
Message 8 of 8
Flag for a moderator

Re: Issue routing to web host; packets lost.

Hi Phil,

Yep! Can confirm, it's suddenly started working again. Will keep an eye on this to make sure all is well.