Can someone tracert a site for me please

Plusnet support say there is no problem after turning my modem off overnight but the problem persists and I have tried two routers (including the Plusnet supplied router) and two PC's with the same results.

Can you please do a tracert of virtualdjradio.com and post results here? Thanks in advance.

Mine.

Tracing route to ec2-52-0-120-216.compute-1.amazonaws.com [52.0.120.216]
over a maximum of 30 hops:

1 6 ms 6 ms 6 ms lo0.11.Central11.ptw-bng02.plus.net [195.166.130.204]
2 7 ms 7 ms 6 ms irb.11.PTW-CR01.plus.net [84.93.249.17]
3 7 ms 7 ms 7 ms 195.99.126.138
4 7 ms 7 ms 7 ms core3-hu0-3-0-0.faraday.ukcore.bt.net [213.121.193.160]
5 7 ms 7 ms 7 ms peer2-et-9-3-0.faraday.ukcore.bt.net [62.6.201.167]
6 7 ms 7 ms 7 ms 213.137.183.36
7 101 ms 91 ms 91 ms t2c2-p0-2-0.cz-pra.eu.bt.net [166.49.208.121]
8 151 ms 149 ms 153 ms 166-49-169-18.eu.bt.net [166.49.169.18]
9 * * * Request timed out.
10 * * * Request timed out.
11 92 ms 92 ms 92 ms 205.251.245.244
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.

Edited by deleted (Fri 04-Sep-15 13:31:08)

Tracing route to virtualdjradio.com [52.0.120.216]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway.home.gateway [192.168.1.254]
2 18 ms 25 ms 18 ms lo0-central10.ptw-ag01.plus.net [195.166.128.195]
3 18 ms 17 ms 17 ms link-a-central10.ptw-gw01.plus.net [212.159.2.144]
4 17 ms 17 ms 17 ms xe-4-2-0.ptw-cr01.plus.net [212.159.0.240]
5 17 ms 18 ms 18 ms 195.99.126.138
6 18 ms 18 ms 18 ms core3-hu0-3-0-0.faraday.ukcore.bt.net [213.121.193.160]
7 17 ms 17 ms 17 ms peer2-et-3-3-0.faraday.ukcore.bt.net [62.6.201.165]
8 18 ms 17 ms 17 ms 213.137.183.32
9 98 ms 97 ms 97 ms ixp1-xe-0-0-1-0.us-ash.eu.bt.net [166.49.208.43]
10 97 ms 98 ms 97 ms 166-49-169-18.eu.bt.net [166.49.169.18]
11 * * * Request timed out.
12 * * * Request timed out.
13 98 ms 99 ms 99 ms 205.251.245.123
14 * * * Request timed out.
15 * *

It seems to be down.

Linky.

AH! But when testing that link, it is now back up.

It's not just me then and Plusnet support are telling me porky pies that there is no issue to that URL. Well maybe not for them anyhow.

I get the above stats even when I can reach the site. I have had lots of issues with their online chat eating my text (packet loss) and freezing. There appears to be some kind of routing issue I think.

I have no problem getting to the site even though the tracert is borked so that doesn't prove anything

It seems to be getting stuck in the amazon network for me, on AAISP.

C:\Users\Bob>tracert virtualdjradio.com

Tracing route to virtualdjradio.com [52.0.120.216]
over a maximum of 30 hops:

  1     2 ms     1 ms     1 ms  192.168.1.254
  2    13 ms    13 ms    12 ms  alt.a.gormless.thn.aa.net.uk [90.155.53.71]
  3    13 ms    13 ms    15 ms  d.aimless.thn.aa.net.uk [90.155.53.44]
  4    14 ms    13 ms    14 ms  83.217.238.93
  5    29 ms    13 ms    14 ms  ae-6.r22.londen03.uk.bb.gin.ntt.net [129.250.4.20]
  6    82 ms    80 ms    14 ms  ae-0.r22.londen03.uk.bb.gin.ntt.net [129.250.4.85]
  7    81 ms    80 ms    92 ms  ae-4.r22.nycmny01.us.bb.gin.ntt.net [129.250.3.126]
  8    81 ms    82 ms    81 ms  ae-11.amazon.nycmny01.us.bb.gin.ntt.net [129.250.201.138]
  9    81 ms    80 ms    84 ms  ae-6.amazon.nycmny01.us.bb.gin.ntt.net [129.250.201.118]
 10    99 ms    99 ms     *     54.240.229.78
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *       98 ms  205.251.245.250
 16    98 ms     *        *     205.251.245.250
 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.

That Hop 16 is still Amazon.

Ping fails completely.

Edited by RobertoS (Fri 04-Sep-15 13:42:57)

I'm not sure what you're trying to prove. I get similar results to you and Bob (I intended to copy and paste but accidentally closed the window and can't be bothered to do it again as it takes too long) but the site seems to be up, albeit slow to load.

I've had issues with the online chat eating my text but they moved the server to a new one a few days ago and changed code completely so it could just be teething problems. The tracerts made me think there might be some issue with my end so I wanted to check with others.

Tracert is of limited use. It can potentially pinpoint a poor performing node but in most cases it doesn't and all it does is confuse things (mainly because most nodes are set to either not respond to ICMP or to treat it as low priority). Likelihood is the issues you are seeing is their end - servers or code.