Ongoing DNS Issues? Timeouts....

[#1]

Cheers Bob 

[#2]

pings  variably unable to complete
Pinging www.amazon.co.uk [178.236.6.251] with 64 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for www.amazon.co.uk
  Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

[#3]

I'll add a me too here. We were hit by it at 9am this morning originally - totally unusable - but all had seemed clear from around 10am. However, I'm now starting to see ropy behaviour.

[#4]

Our networks team have been called out on this and are currently investigating. The problem ref:79818 from earlier has been reopened for this.
I've posted a service status to which I'm waiting for it to propagate.
Apologies for the inconvenience all
EDIT - A Service Status is now up.

[#5]

Cheers Chris

[#6]

I was just coming back here to post about your update. Efficient PN as normal.

[#7]

I am experiencing problems watching streaming services like iPlayer, I am getting timeout error on iPlayer, dont know if its related to this problem.
Cheers

[#8]

Getting annoying now;

[#9]

I don't know if this is related but my internet connects for 30 seconds then disconnects for a couple of minutes. This has been on repeat since the past 2 hours at least

[#10]

SamKnows Failed DNS Queries for the last week and today attached.

[#11]

Obligatory DNS performance graph.

[#12]

Noticed eBay was slow loading, this could be why?
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>ping ebay.co.uk
Pinging ebay.co.uk [66.135.215.61] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 66.135.215.61:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\WINDOWS\system32>tracert ebay.co.uk
Tracing route to ebay.co.uk [66.135.215.61]
over a maximum of 30 hops:
  1    2 ms    1 ms    1 ms  BTHUB5 [192.168.1.254]
  2    9 ms    9 ms    13 ms  lo0-central10.ptw-ag03.plus.net [195.166.128.197]
  3    9 ms    9 ms    9 ms  link-a-central10.ptw-gw01.plus.net [212.159.2.152]
  4    9 ms    8 ms    8 ms  xe-4-3-0.ptw-cr01.plus.net [212.159.0.244]
5    13 ms    *        *    te-4-2.car5.London1.Level3.net [217.163.45.249]
  6    9 ms    9 ms    9 ms  ae-11-51.car1.London1.Level3.net [4.69.139.66]
  7    10 ms    10 ms    9 ms  sl-crs1-lon-.sprintlink.net [213.206.131.21]
  8    82 ms    82 ms    82 ms  sl-bb20-tuk-11-0-0.sprintlink.net [144.232.9.209
]
  9    84 ms    85 ms    85 ms  sl-crs1-pen-0-0-3-0.sprintlink.net [144.232.9.18
5]
10    93 ms    94 ms    93 ms  sl-crs1-pen-0-0-5-0.sprintlink.net [144.232.4.17
5]
11    92 ms    95 ms    93 ms  sl-crs1-dc-0-4-0-3.sprintlink.net [144.232.20.14
]
12  103 ms  103 ms  102 ms  144.232.10.45
13  124 ms  124 ms  124 ms  144.232.5.208
14  125 ms  130 ms  125 ms  144.232.11.225
15  127 ms  127 ms  127 ms  144.232.25.188
        *

[#13]

DNS broke again for a few minutes, I've just switched to Google's DNS servers.
Plusnet need to sort this out as it's becoming a joke.

[#14]

Broke here again too - just for a few minutes.
Now OK again, could do with an update on the status, last thing we heard was late last night ....
EDIT: no sooner said than update arrived.

[#15]

This won't have been affecting slow pings/traceroutes.  You'd have seen slow DNS resolution times, i.e. pages white paging or images failing to load.