DNS/Routing issues for the last 36 hours

[#1]

bobpullen

Whatever the fault was it was affecting xbox live users from using multiplayer services which relied upon teredo tunneling. If you look here I did a trace route using a different router with the same result as the one you have quoted:

https://community.plus.net/t5/Fibre-Broadband/DNS-Routing-issues-for-the-last-36-hours/m-p/1349178#M...

Anyway, whatever was done today has solved the problem, after disconnecting and reconnecting to plusnet I can confirm that I can finally connect to xbox live services again. Absolutely nothing had changed at my end in the week and a few days since it last worked. Plusnet dns, no router fault, ports forwarded, clearly the routing issues were the cause of the problem.

[#2]

I'm getting the same,

Web pages still taking forever to load (actually load quicker when I tether my 3 internet and that's through my PC's Wifi card use Ethernet for Plusnet).

Online gaming on PC is still spiking the latency is good and consistent but the spikes don't relate to latency spikes, something I've never experienced before.

Also like the person above my Xbox live is the same.

C:\Users\Alistair>tracert xeas.gtm.xboxlive.com

Tracing route to xeas.gtm.xboxlive.com [157.56.71.22]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 15 ms 15 ms 15 ms 133.hiper04.sheff.dial.plus.net.uk [195.166.143.
133]
4 14 ms 14 ms 14 ms be3-3102.pcn-ir02.plus.net [195.166.143.132]
5 15 ms 15 ms 15 ms 195.99.125.140
6 15 ms 14 ms 14 ms peer1-et-1-3-0.telehouse.ukcore.bt.net [195.99.1
27.19]
7 16 ms 17 ms 17 ms 195.99.126.57
8 15 ms 15 ms 16 ms ae11-0.lon04-96cbe-1b.ntwk.msn.net [207.46.44.15
5]
9 158 ms 158 ms 158 ms 104.44.5.28
10 159 ms 159 ms 159 ms be-1-0.ibr01.nyc04.ntwk.msn.net [104.44.4.50]
11 158 ms 157 ms 159 ms be-3-0.ibr01.was02.ntwk.msn.net [104.44.4.34]
12 159 ms 158 ms 158 ms be-4-0.ibr03.ch1.ntwk.msn.net [104.44.4.33]
13 158 ms 159 ms 159 ms be-2-0.ibr02.ch1.ntwk.msn.net [104.44.4.56]
14 159 ms 157 ms 159 ms be-5-0.ibr01.dm2.ntwk.msn.net [104.44.4.76]
15 159 ms 158 ms 157 ms be-3-0.ibr01.dm3.ntwk.msn.net [104.44.4.74]
16 158 ms 158 ms 158 ms be-4-0.ibr02.den07.ntwk.msn.net [104.44.4.97]
17 160 ms 159 ms 159 ms be-1-0.ibr01.den07.ntwk.msn.net [104.44.4.58]
18 157 ms 157 ms 157 ms be-3-0.ibr01.cys01.ntwk.msn.net [104.44.4.112]
19 159 ms 159 ms 159 ms be-1-0.ibr02.cys01.ntwk.msn.net [104.44.4.98]
20 160 ms 160 ms 160 ms be-3-0.ibr01.co2.ntwk.msn.net [104.44.4.122]
21 157 ms 159 ms 157 ms ae71-0.co1-96c-1a.ntwk.msn.net [104.44.8.237]
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 * *:

Hopefully by 2017 this is sorted out  

[#3]

And it looks like I spoke too soon!

1st router: TL-WR841N dd-wrt

C:\Users\DMA>tracert xeas.gtm.xboxlive.com

Tracing route to xeas.gtm.xboxlive.com [157.56.71.22]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms DD-WRT [192.168.1.1]
2 * * * Request timed out.
3 * * * Request timed out.
4 20 ms 21 ms 20 ms be3-3102.pcn-ir02.plus.net [195.166.143.132]
5 20 ms 20 ms 20 ms 195.99.125.140
6 21 ms 21 ms 21 ms 62.172.103.13
7 22 ms 22 ms 21 ms 195.99.126.55
8 164 ms 163 ms 164 ms 104.44.5.28
9 163 ms 164 ms 164 ms be-1-0.ibr01.nyc04.ntwk.msn.net [104.44.4.50]
10 163 ms 164 ms 163 ms be-3-0.ibr01.was02.ntwk.msn.net [104.44.4.34]
11 164 ms 164 ms 163 ms be-4-0.ibr03.ch1.ntwk.msn.net [104.44.4.33]
12 165 ms 164 ms 164 ms be-2-0.ibr02.ch1.ntwk.msn.net [104.44.4.56]
13 163 ms 164 ms 165 ms be-5-0.ibr01.dm2.ntwk.msn.net [104.44.4.76]
14 165 ms 163 ms 165 ms be-3-0.ibr01.dm3.ntwk.msn.net [104.44.4.74]
15 165 ms 164 ms 165 ms be-4-0.ibr02.den07.ntwk.msn.net [104.44.4.97]
16 164 ms 163 ms 166 ms be-1-0.ibr01.den07.ntwk.msn.net [104.44.4.58]
17 164 ms 164 ms 165 ms be-3-0.ibr01.cys01.ntwk.msn.net [104.44.4.112]
18 164 ms 164 ms 164 ms be-1-0.ibr02.cys01.ntwk.msn.net [104.44.4.98]
19 165 ms 163 ms 165 ms be-3-0.ibr01.co2.ntwk.msn.net [104.44.4.122]
20 163 ms 163 ms 163 ms ae72-0.co1-96c-1b.ntwk.msn.net [104.44.8.241]
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.

2nd router: TL-WR841N factory firmware

C:\Users\DMA>tracert xeas.gtm.xboxlive.com

Tracing route to xeas.gtm.xboxlive.com [157.56.71.22]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms TL-WR841N [192.168.1.1]
2 * * * Request timed out.
3 * * * Request timed out.
4 20 ms 20 ms 21 ms be3-3102.pcn-ir02.plus.net [195.166.143.132]
5 20 ms 20 ms 20 ms 195.99.125.140
6 21 ms 20 ms 21 ms 62.172.103.13
7 22 ms 22 ms 21 ms 195.99.126.55
8 165 ms 164 ms 165 ms 104.44.5.28
9 165 ms 163 ms 165 ms be-1-0.ibr01.nyc04.ntwk.msn.net [104.44.4.50]
10 165 ms 165 ms 165 ms be-3-0.ibr01.was02.ntwk.msn.net [104.44.4.34]
11 165 ms 163 ms 164 ms be-4-0.ibr03.ch1.ntwk.msn.net [104.44.4.33]
12 164 ms 165 ms 163 ms be-2-0.ibr02.ch1.ntwk.msn.net [104.44.4.56]
13 163 ms 164 ms 163 ms be-5-0.ibr01.dm2.ntwk.msn.net [104.44.4.76]
14 165 ms 165 ms 164 ms be-3-0.ibr01.dm3.ntwk.msn.net [104.44.4.74]
15 165 ms 165 ms 164 ms be-4-0.ibr02.den07.ntwk.msn.net [104.44.4.97]
16 165 ms 164 ms 165 ms be-1-0.ibr01.den07.ntwk.msn.net [104.44.4.58]
17 164 ms 164 ms 165 ms be-3-0.ibr01.cys01.ntwk.msn.net [104.44.4.112]
18 164 ms 164 ms 165 ms be-1-0.ibr02.cys01.ntwk.msn.net [104.44.4.98]
19 164 ms 165 ms 163 ms be-3-0.ibr01.co2.ntwk.msn.net [104.44.4.122]
20 164 ms 163 ms 163 ms ae72-0.co1-96c-1b.ntwk.msn.net [104.44.8.241]
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.

[#4]

Still cannot connect to PSN (Playstation network)

>ping 54.219.129.104

Pinging 54.219.129.104 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 54.219.129.104:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

tracert 54.219.129.104

Tracing route to ec2-54-219-129-104.us-west-1.compute.amazonaws.com [54.219.129.104]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms dsldevice.lan [192.168.1.254]
2 * * * Request timed out.
3 * * 7 ms 141.hiper04.sheff.dial.plus.net.uk [195.166.143.141]
4 8 ms 7 ms 7 ms be3-3106.psb-ir02.plus.net [195.166.143.140]
5 8 ms 7 ms 7 ms 195.99.125.138
6 9 ms 8 ms 8 ms peer5-hu0-11-0-1.telehouse.ukcore.bt.net [195.99.127.5]
7 8 ms 8 ms 8 ms 166-49-211-232.eu.bt.net [166.49.211.232]
8 9 ms 9 ms 8 ms 82.112.101.73
9 8 ms 8 ms 15 ms ae-6.r24.londen12.uk.bb.gin.ntt.net [129.250.4.20]
10 80 ms 80 ms 80 ms ae-5.r24.nycmny01.us.bb.gin.ntt.net [129.250.2.18]
11 158 ms 150 ms 151 ms ae-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.4.13]
12 152 ms 149 ms 148 ms ae-0.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.54]
13 166 ms 166 ms 166 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
14 162 ms 163 ms 163 ms ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119]
15 164 ms 164 ms 164 ms ae-4.r06.plalca01.us.bb.gin.ntt.net [129.250.4.118]
16 163 ms 163 ms 163 ms ae-1.amazon.plalca01.us.bb.gin.ntt.net [140.174.21.182]
17 * * * Request timed out.
18 * * * Request timed out.
19 164 ms 164 ms 164 ms 72.21.222.19
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.

[#5]

Thinking about taking the plunge with PN.  With that in mind, is the static Ip address workaround a 100% cure for all these problems?.  I know its not ideal (its their fault after all), but would rather pay the fiver one-off if it means getting that initial smoother ride as a new user..

[#6]

It's a bit better today but still not the way it was prior to the 8th, i'll be calling in to notify you of my leaving tomorrow anyway so i don't care anymore.

[#7]

Envy you nightstalker still 9 months for me, I've added April to my calander so I don't forget to ring up and cancel. No matter what happens now I'm gone after this. Unless they compensate for this month.

[#8]

The price increase allows you to get out of the contract with no early termination fees.

Moderator's note by Mike (Mav): Full quote of preceding post removed as per Forum rules

[#9]

---

@nightstalk3r wrote:

It's a bit better today but still not the way it was prior to the 8th, 

I agree, my packet loss is back. It started around 4pm at about 2% but around 8pm it started to be typically 10% with spikes to 20%. If it follows the usual pattern it will vanish around midnight.

---

[#10]

Thanks Night, dropped you a PM

[#11]

---

bobpullen wrote:

@splont, I'm not 100% convinced your problems are related to any of the issues we've been working on. For you, issues only seemed to start on the 15th and seem to be affecting you whether you are assigned a static IP or not i.e. you have problems whether you're routed through our 'old' or new broadband networks. Are you experiencing these issues when using a wireless connection? Do the problems go away if you connect the laptop to the router using an ethernet cable?

Save

---

@bobpullen - I only noticed psn problems on Friday evening,, Sky a couple of days earlier. I only put two and two together on Saturday, and my problems at that time were pretty much the same as everyone on here. On Sunday morning someone switched me to a static ip and most problems went away. However during yesterday the service degraded for browsing. 

I have rebooted the router and connected by cable, speed tests now complete but I only get 16.29mbps down, on wireless this same test pulls back around 19mbps. Both of the figures are pretty shocking considering I had around 50 mbps when a first joined you! For what it is worth I have done the same tracert to xeas.gtm.xboxlive.com, with the same results.

[#12]

@splont

Just checked your account and the connection profile was set incorrectly, limiting the speeds on your line.  Possibly when you added the static IP to your account.  It should be back to normal now.

[#13]

My issues seem to be sorted now - Sky On Demand is working again.....

[#14]

Still constant disconnects.

[#15]

Still poo, 

C:\Users\Alistair>tracert xeas.gtm.xboxlive.com

Tracing route to xeas.gtm.xboxlive.com [157.56.71.22]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 * * * Request timed out.
4 94 ms 93 ms 96 ms be3-3102.pcn-ir02.plus.net [195.166.143.132]
5 95 ms 96 ms 97 ms 195.99.125.140
6 15 ms 15 ms 14 ms peer1-et-1-3-0.telehouse.ukcore.bt.net [195.99.
27.19]
7 17 ms 17 ms 17 ms 195.99.126.57
8 18 ms 16 ms 17 ms ae12-0.lon04-96cbe-1b.ntwk.msn.net [207.46.44.1
3]
9 159 ms 159 ms 159 ms 104.44.5.28
10 166 ms 162 ms 163 ms be-1-0.ibr01.nyc04.ntwk.msn.net [104.44.4.50]
11 161 ms 161 ms 158 ms be-3-0.ibr01.was02.ntwk.msn.net [104.44.4.34]
12 159 ms 161 ms 161 ms be-4-0.ibr03.ch1.ntwk.msn.net [104.44.4.33]
13 160 ms 159 ms 160 ms be-2-0.ibr02.ch1.ntwk.msn.net [104.44.4.56]
14 159 ms 157 ms 158 ms be-5-0.ibr01.dm2.ntwk.msn.net [104.44.4.76]
15 160 ms 159 ms 158 ms be-3-0.ibr01.dm3.ntwk.msn.net [104.44.4.74]
16 159 ms 158 ms 158 ms be-4-0.ibr02.den07.ntwk.msn.net [104.44.4.97]
17 158 ms 161 ms 159 ms be-1-0.ibr01.den07.ntwk.msn.net [104.44.4.58]
18 157 ms 159 ms 159 ms be-3-0.ibr01.cys01.ntwk.msn.net [104.44.4.112]
19 159 ms 160 ms 159 ms be-1-0.ibr02.cys01.ntwk.msn.net [104.44.4.98]
20 182 ms 158 ms 158 ms be-3-0.ibr01.co2.ntwk.msn.net [104.44.4.122]
21 156 ms 156 ms 156 ms ae71-0.co1-96c-1a.ntwk.msn.net [104.44.8.237]
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 *

At least I got some good news, customer service told me I'm part of a batch of customers getting the price increase email on Thursday (21stJuly).

Someone at Plusnet didn't think about the potential issues a new network could cause and then inflict price increases. 
Thinking about BT