Well telstra.net looks to be (registered) in Australia. It�s possible your IPv6 is going there then back, which would account for the time. But if all IDNet did that I�m sure we would hear a lot about it.

What happens with tracert -4 bbc.com

Edited by RobertoS (Sun 04-Nov-18 09:40:55)

In reply to a post by steve195527:

trace shows this:-

Tracing route to bbc.com [2a04:4e42:200::81]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 2a02:390:7aaa:0:6203:47ff:fe37:3cb5
2 12 ms 11 ms 12 ms 2a02:390:ffff:ffff:ffff:ffff:ffff:fff6
3 11 ms 11 ms 11 ms 2a02:390:0:ff28::
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 298 ms 298 ms 298 ms 2403:e800:ff00:110::3f
9 * * 297 ms 2403:e800:105:36::2
10 * * * Request timed out.
11 * * 328 ms bundle-ether20.cha-core10.brisbane.telstra.net [2001:8000:0:2000:3001:6001:0:a]
12 * * * Request timed out.
13 * * * Request timed out.
14 332 ms 332 ms 332 ms fas2991580.lnk.telstra.net [2001:8000:106:b0::2]
15 334 ms 334 ms 335 ms 2a04:4e42:200::81

Trace complete.
not sure what it means or how to fix,if I can from my end?

ipv4 pings are ok:-

Microsoft Windows [Version 10.0.17134.376]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\Users\steve>ping bbc.com -4

Pinging bbc.com [151.101.128.81] with 32 bytes of data:
Reply from 151.101.128.81: bytes=32 time=11ms TTL=61
Reply from 151.101.128.81: bytes=32 time=12ms TTL=61
Reply from 151.101.128.81: bytes=32 time=11ms TTL=61
Reply from 151.101.128.81: bytes=32 time=11ms TTL=61

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

I think I would be asking your ISP why ipv6 traffic to bbc.com is being routed via Brisbane Australia and increasing the transit time from 12ms to 300ms.

ipv4 is okish one slightly slow hop of 56ms

icrosoft Windows [Version 10.0.17134.376]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\Users\steve>tracert -4 bbc.com

Tracing route to bbc.com [151.101.128.81]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway.home.gateway [192.168.1.254]
2 12 ms 11 ms 12 ms telehouse-gw11-10G.idnet.net [212.69.63.36]
3 59 ms 51 ms 56 ms telehouse-gw8-10G.idnet.net [212.69.63.138]
4 12 ms 12 ms 12 ms telehouse-gw7-10G.idnet.net [212.69.63.142]
5 12 ms 13 ms 12 ms ip81-59.fastly-gw1.lonap.net [5.57.81.59]
6 12 ms 12 ms 12 ms bbc.com [151.101.128.81]

Trace complete.
even that is ok 5 mins later:-


C:\Users\steve>tracert -4 bbc.com

Tracing route to bbc.com [151.101.64.81]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway.home.gateway [192.168.1.254]
2 12 ms 12 ms 12 ms telehouse-gw11-10G.idnet.net [212.69.63.36]
3 12 ms 12 ms 12 ms telehouse-gw8-10G.idnet.net [212.69.63.138]
4 12 ms 12 ms 12 ms telehouse-gw7-10G.idnet.net [212.69.63.142]
5 12 ms 11 ms 12 ms ip81-59.fastly-gw1.lonap.net [5.57.81.59]
6 12 ms 12 ms 12 ms bbc.com [151.101.64.81]

Trace complete.
ident have issued an update saying some network issues are to blame,sorry guys for wasting you time

Edited by steve195527 (Sun 04-Nov-18 10:38:55)

In reply to a post by steve195527:

ident have issued an update saying some network issues are to blame,sorry guys for wasting you time

Fair enough. No problem.

At least you've learned about checking both IPv4 and IPv6, and using tracert to check for bottlenecks.

A tracert with a high line followed by lower ones just means the high one passes packets through OK but is slow to respond to pings. A high one followed by the rest the same or higher is a bottleneck at the first. (Or later as well if there is another step up).

All asterisks on a line probably means that router is set not to respond to pings. Some asterisks and some times on a line suggest it is working very hard and may be a bit congested.