Xbox multi player

[#1]

@JonoH  wrote:

We believe it's resolved  

Tracing route to aptgm87544.lithium.com [46.19.168.229]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms dsldevice.lan [172.16.0.1]
2 * * * Request timed out.
3 * * * Request timed out.
4 10 ms 10 ms 10 ms 140.hiper04.sheff.dial.plus.net.uk [195.166.143.140]
5 10 ms 9 ms 10 ms 195.99.125.138
6 10 ms 10 ms 10 ms peer1-et-0-0-2.interxion.ukcore.bt.net [62.172.103.124]
7 * * * Request timed out.
8 17 ms 17 ms 17 ms 216.52.199.38
9 16 ms 16 ms 16 ms core1.be3.ams004.pnap.net [216.52.199.50]
10 17 ms 17 ms 17 ms border3.ae1-bbnet1.ams004.pnap.net [95.172.78.38]
11 17 ms 17 ms 17 ms lithiumtechinc-5.edge1.ams004.pnap.net [95.172.78.146]
12 17 ms 16 ms 16 ms aptgm87544.lithium.com [46.19.168.229]

Trace complete.

Erm, is it? 141.hyper..... still timing out here (just this very moment checked). I'm not sure about hop 7 either.

[#2]

Not sure what that is!

I’ve asked my son to check to see if he has any issues and I’ll update you if we do

Thanks again

[#3]

---

@DS wrote:

@JonoH  wrote:

We believe it's resolved  

Erm, is it? 141.hyper..... still timing out here (just this very moment checked). I'm not sure about hop 7 either.

You're not impacted by this issue though.  I know this because I know what IP you're using and it's not in the impacted range.

---

[#4]

I'm more confused than is was before!! It's not hard to confuddle me, but

@JonoH  wrote earlier:

@DS wrote:
For the sake of my sanity, is this just an XB360 and/or XB1 issue only?

No, it can be anything.

Or a small number, as in it's affecting other customers (me included) using other devices too?

yes, it seems to be an issue with the routing rather than with the customers' device.

But now I'm not affected by this

You're not impacted by this issue though.  I know this because I know what IP you're using and it's not in the impacted range.

I therefore, reside myself to slowly rock back and forth, mumbling garbage to myself!!

Was it just the 31.***.***.*** or 82.132.***.*** or 80.189.***.*** or 146.198.*.** IP ranges affected - you'll see the recent drop in my connection gave me a dynamic 146.199.***.*** address?

I also surmise, that my issues recently (not the drops or SNR or forum oddities) are caused by factors that I simply can't fathom out

[#5]

--- edited, wrong thread!

[#6]

Hi @AvengerUK01 

From what I can see you've previously been on a static IP until tonight so it doesn't look like the issues are entirely the same. Are you experiencing the problems as described in the initial few posts of this thread?

[#7]

---

@DS wrote:

@JonoH  wrote:

We believe it's resolved  

Tracing route to aptgm87544.lithium.com [46.19.168.229]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms dsldevice.lan [172.16.0.1]
2 * * * Request timed out.
3 * * * Request timed out.
4 10 ms 10 ms 10 ms 140.hiper04.sheff.dial.plus.net.uk [195.166.143.140]
5 10 ms 9 ms 10 ms 195.99.125.138
6 10 ms 10 ms 10 ms peer1-et-0-0-2.interxion.ukcore.bt.net [62.172.103.124]
7 * * * Request timed out.
8 17 ms 17 ms 17 ms 216.52.199.38
9 16 ms 16 ms 16 ms core1.be3.ams004.pnap.net [216.52.199.50]
10 17 ms 17 ms 17 ms border3.ae1-bbnet1.ams004.pnap.net [95.172.78.38]
11 17 ms 17 ms 17 ms lithiumtechinc-5.edge1.ams004.pnap.net [95.172.78.146]
12 17 ms 16 ms 16 ms aptgm87544.lithium.com [46.19.168.229]

Trace complete.

Erm, is it? 141.hyper..... still timing out here (just this very moment checked). I'm not sure about hop 7 either.

---

Hey @DS, those timed out responses don't indicate a problem, just that the host didn't respond to the traceroute.  Routers can be configured to ignore or de-prioritise ICMP traffic like traceroutes.

[#8]

Hey @DS, those timed out responses don't indicate a problem, just that the host didn't respond to the traceroute.  Routers can be configured to ignore or de-prioritise ICMP traffic like traceroutes.

@Kelly 

What I was pointing out, was most of the times I've tested, the 3rd hop sometimes is there (141.hyper) with * * x ms, * x x ms or indeed not there at all (as above).

I know hop2 won't be there, plus I wasn't sure if hop 7 should be there either.

I'm not too up on why I sometimes see '141 hyper' then why I don't - same tracert to xyz and it always is either there (but not x x x ms) or not there.

Although I'm too concerned, why would I sometimes see the 3rd hop and sometimes not see a complete 3rd hop when testing to the same destination?

[#9]

Routing changes when it needs to/is forced to.  It might indicate an issue, or not!  I'll have a closer look though as the 141.hyper thing popped up in a separate conversation internally today.

[#10]

I know going to the BeeBeeCee ain't the one I normally use, here's what I'm saying:

Tracing route to bbc.co.uk [151.101.0.81]
over a maximum of 30 hops:

3 * * 11 ms 141.hiper04.sheff.dial.plus.net.uk [195.166.143.141]
4 11 ms 12 ms 11 ms 140.hiper04.sheff.dial.plus.net.uk [195.166.143.140]
5 10 ms 10 ms 11 ms 195.99.125.138
6 10 ms 12 ms 13 ms peer7-et-3-1-2.telehouse.ukcore.bt.net [109.159.252.230]
7 11 ms 11 ms 14 ms peer5-te0-9-0-32.telehouse.ukcore.bt.net [195.99.126.81]
8 10 ms 10 ms 11 ms 151.101.0.81
---
Tracing route to bbc.co.uk [151.101.0.81]
over a maximum of 30 hops:

3 10 ms 11 ms 10 ms 141.hiper04.sheff.dial.plus.net.uk [195.166.143.141]
4 12 ms 11 ms 10 ms 140.hiper04.sheff.dial.plus.net.uk [195.166.143.140]
5 10 ms 10 ms 10 ms 195.99.125.138
6 12 ms 10 ms 14 ms peer7-et-3-1-2.telehouse.ukcore.bt.net [109.159.252.230]
7 11 ms 13 ms 11 ms peer5-te0-9-0-32.telehouse.ukcore.bt.net [195.99.126.81]
8 9 ms 10 ms 10 ms 151.101.0.81

Bonkers! First time I've seen a full hop 3 - someone looking already...?

edit. Might be noting 137.hiper too. I did point this out a while back also

eg.

3 * 11 ms 10 ms 137.hiper04.sheff.dial.plus.net.uk [195.166.143.137]
4 12 ms 10 ms 12 ms 136.hiper04.sheff.dial.plus.net.uk [195.166.143.136]

sometimes

3 * * * Request timed out.
4 12 ms 12 ms 12 ms 136.hiper04.sheff.dial.plus.net.uk [195.166.143.136]