Seems bt.com is down again :(

I can connect to home.bt.com fine, but as soon as it redirects me to bt.com/... via the link on the site it times our and is unable to connect.

Here is a trace route to home.bt.com:

tracert home.bt.com

Tracing route to btgroup-5.hs.llnwd.net [178.79.206.253]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  BTHUB4 [x.x.x.x]
  2    20 ms    20 ms    20 ms  x.x.x.x
  3    27 ms    48 ms    60 ms  217.32.146.126
  4    55 ms    53 ms    53 ms  213.120.156.210
  5    32 ms    35 ms    35 ms  217.41.168.55
  6    33 ms    31 ms    31 ms  217.41.168.107
  7    21 ms    23 ms    26 ms  109.159.249.108
  8    26 ms    25 ms    29 ms  core3-te0-10-0-28.faraday.ukcore.bt.net [109.159.249.29]
  9    31 ms    31 ms    33 ms  peer2-et-1-1-0.telehouse.ukcore.bt.net [213.121.193.163]
 10    39 ms    34 ms    38 ms  peer2-xe0-0-2.telehouse.ukcore.bt.net [195.99.126.17]
 11    28 ms    29 ms    29 ms  178.79.195.86
 12    26 ms    27 ms    35 ms  https-178-79-206-253.lon.llnw.net [178.79.206.253]

Trace complete.

And as you can see its fine, now here is the trace route for bt.com:

tracert bt.com

Tracing route to bt.com [193.113.9.164]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  BTHUB4 [x.x.x.x]
  2    20 ms    20 ms    20 ms  x.x.x.x
  3    20 ms    20 ms    20 ms  217.32.146.126
  4    21 ms    21 ms    21 ms  217.32.147.234
  5    20 ms    23 ms    20 ms  217.41.168.55
  6    21 ms    22 ms    21 ms  217.41.168.107
  7    22 ms    20 ms    21 ms  acc1-10GigE-0-0-0-5.l-far.21cn-ipp.bt.net [109.159.249.78]
  8    20 ms    21 ms    21 ms  core3-te0-19-0-18.faraday.ukcore.bt.net [109.159.249.35]
  9    22 ms    23 ms    22 ms  193.113.9.164
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

Now as you can see it has reached the ip for bt.com, but it seems it doesn't want to stop routing.

So my guesses is its a routing issue.

Anyone else having this issue?

Paul

Edited by PaulKirby (Wed 17-Aug-16 08:56:20)

At what point does it do the redirect to bt.com? I enter www.bt.com and that redirects to home.bt.com and three or four links on that all just change what is in front of "bt".

Works fine for me with almost exactly the same tracert. I don't see any redirect to bt.com though, only home.bt.com.

In reply to a post by RobertoS:

At what point does it do the redirect to bt.com? I enter www.bt.com and that redirects to home.bt.com and three or four links on that all just change what is in front of "bt".

Well its back up for me now.

I was referring to when you go to home.bt.com its all fine, but when I tried to login to check up on our FTTP order it re-directs to https://bt.com/..... etc, sadly I was unable to reach that page at that location and it timed out.

Also clicking on the ?Help link takes you to bt.com, that was failing for me, but is now back up.

Also when I try to tracert to bt.com it just went completely past the ip for bt.com where it should of stopped.

What do you get when you tracert to bt.com ?

Paul

I get the same as you - the tracert reaches bt.com and then continues past it until it stops after 30 hops.

In reply to a post by BatBoy:

I get the same as you - the tracert reaches bt.com and then continues past it until it stops after 30 hops.

Shouldn't it normally stop when it reaches the required IP ?
I also tried it on my Development Box running Linux and it does the same when I tell it to do the traceroute using UDP, however, when I tell it to use ICMP it stops in the correct place.

bt.com is the only site that this happens on for me.

Strange.

Paul

Could it depend on their firewall config?

Do they block/drop such packets?

In reply to a post by B31:

Could it depend on their firewall config?

Do they block/drop such packets?

Well Traceroutes using ICMP works fine, but UDP ones just continues after it reaches the required IP and doesn't end.

Here is the tracerout tests I did on my Linux box:

# traceroute -w 3 -q 3 --type=icmp bt.com
traceroute to bt.com (193.113.9.164), 64 hops max
  1   xxx.xxx.xxx.xxx	 0.758ms   0.731ms   0.760ms
  2   xxx.xxx.xxx.xxx	20.078ms  19.916ms  19.925ms
  3   217.32.146.126	20.171ms  19.643ms  20.650ms
  4   217.32.147.234	20.870ms  20.373ms  25.017ms
  5   217.41.168.55	20.923ms  20.618ms  20.382ms
  6   217.41.168.107	20.425ms  20.801ms  21.112ms
  7   109.159.249.78	20.386ms  20.107ms  19.851ms
  8   109.159.249.35	20.888ms  20.837ms  20.369ms
  9   193.113.9.164	22.576ms  23.058ms  22.813ms
#

# traceroute -w 3 -q 3 --type=udp bt.com
traceroute to bt.com (193.113.9.164), 64 hops max
  1   xxx.xxx.xxx.xxx	 0.761ms   0.410ms   0.398ms
  2   xxx.xxx.xxx.xxx	19.532ms  19.410ms  18.513ms
  3   217.32.146.126	19.741ms  21.037ms  18.479ms
  4   217.32.147.234	20.839ms  20.406ms  19.624ms
  5   217.41.168.55	19.665ms  19.658ms  19.160ms
  6   217.41.168.107	21.600ms  20.162ms  18.860ms
  7   109.159.255.192	19.727ms  19.604ms  19.874ms
  8   109.159.249.55	20.661ms  19.842ms  19.620ms
  9   193.113.9.164	22.063ms  21.902ms  22.034ms
 10   *  *  *
 11   * ^C
#

I cancelled the second test due to it goes on and on.

But yeah, they could.

Paul

Edited by PaulKirby (Wed 17-Aug-16 11:25:36)