Are there gateway problems this morning?

[#1]

Update:
Connection was fine after initial reconnect (looks like I hit the same gateway as the 'bad' connection as well)..
C:\Users\M>tracert 8.8.8.8
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
 1    <1 ms    <1 ms    <1 ms  10.0.0.249
 2     9 ms     9 ms    10 ms  lo0-central10.ptw-ag01.plus.net [195.166.128.195
]
 3     8 ms     8 ms     8 ms  84.93.248.14.broadband.plus.dyn.plus.net [84.93.
248.14]
 4     8 ms     8 ms     8 ms  xe-0-2-0.ptw-cr02.plus.net [212.159.1.18]
 5     8 ms     8 ms     8 ms  ae2.ptw-cr01.plus.net [195.166.129.4]
 6     8 ms     8 ms     8 ms  72.14.222.97
 7     8 ms     8 ms     8 ms  209.85.240.63
 8     9 ms     8 ms     8 ms  209.85.253.196
 9    14 ms    14 ms    17 ms  209.85.240.28
10    17 ms    17 ms    17 ms  216.239.49.36
11    29 ms    18 ms    17 ms  209.85.255.126
12    18 ms    18 ms    17 ms  google-public-dns-a.google.com [8.8.8.8]
Trace complete.

Hopped over a few more gateways that were fine:
C:\Users\M>tracert 8.8.8.8
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
 1    <1 ms    <1 ms    <1 ms  10.0.0.249
 2     9 ms     8 ms     8 ms  lo0-central10.pcl-ag05.plus.net [195.166.128.186
]
 3     8 ms     8 ms     8 ms  84.93.249.148.broadband.plus.dyn.plus.net [84.93
.249.148]
 4     8 ms     8 ms     7 ms  unknown.plus.net [212.159.1.8]
 5    54 ms     8 ms     8 ms  ae1.ptw-cr01.plus.net [195.166.129.0]
 6     8 ms    19 ms     8 ms  ae2.ptw-cr02.plus.net [195.166.129.5]
 7     8 ms     8 ms     8 ms  72.14.223.32
 8     8 ms     8 ms     8 ms  209.85.252.188
 9     8 ms     8 ms     8 ms  209.85.253.196
10    13 ms    14 ms    13 ms  209.85.240.28
11    17 ms    18 ms    28 ms  216.239.49.36
12    24 ms    17 ms    17 ms  209.85.255.126
13    18 ms    17 ms    17 ms  google-public-dns-a.google.com [8.8.8.8]
Trace complete.
C:\Users\M>tracert 8.8.8.8
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
 1    <1 ms    <1 ms    <1 ms  10.0.0.249
 2    11 ms    15 ms    50 ms  lo0-central10.pcl-ag08.plus.net [195.166.128.189
]
 3     8 ms     8 ms     8 ms  84.93.249.244.broadband.plus.dyn.plus.net [84.93
.249.244]
 4     8 ms     8 ms     8 ms  pth-ag2.plus.net [212.159.1.12]
 5    16 ms    13 ms     8 ms  ae1.ptw-cr01.plus.net [195.166.129.0]
 6     8 ms     8 ms     8 ms  72.14.222.97
 7     8 ms     8 ms     8 ms  209.85.240.63
 8     9 ms     8 ms     8 ms  209.85.253.196
 9    14 ms    14 ms    13 ms  209.85.240.28
10    17 ms    17 ms    17 ms  216.239.49.36
11    28 ms    17 ms    17 ms  209.85.255.126
12    18 ms    18 ms    17 ms  google-public-dns-a.google.com [8.8.8.8]
Trace complete.

Then after a few tries I got a 'bad' one again - on a different gateway this time (testing on web pages as well as the traceroutes, but dropped packets in the traces = non-loading pages):
C:\Users\M>tracert 8.8.8.8
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
 1    <1 ms    <1 ms    <1 ms  10.0.0.249
 2    16 ms    15 ms     9 ms  lo0-plusnet.pcl-ag05.plus.net [195.166.130.29]
 3     8 ms     8 ms     9 ms  gi7-8-654.pcl-gw02.plus.net [84.93.254.13]
 4     8 ms     7 ms     7 ms  ae3.pcl-cr02.plus.net [195.166.129.42]
 5     9 ms     *        *     ae1.ptw-cr02.plus.net [195.166.129.2]
 6     *        7 ms     7 ms  72.14.223.32
 7     8 ms     *        8 ms  209.85.252.186
 8     8 ms     8 ms     8 ms  209.85.253.94
 9     *       13 ms    14 ms  209.85.243.33
10    17 ms    17 ms    17 ms  216.239.49.28
11    22 ms     *        *     209.85.255.118
12    17 ms    17 ms    17 ms  google-public-dns-a.google.com [8.8.8.8]
Trace complete.
C:\Users\M>tracert community.plus.net
Tracing route to community.plus.net [212.159.8.110]
over a maximum of 30 hops:
 1    <1 ms    <1 ms    <1 ms  10.0.0.249
 2     8 ms     8 ms     *     lo0-plusnet.pcl-ag05.plus.net [195.166.130.29]
 3     8 ms     7 ms     *     gi7-8-654.pcl-gw02.plus.net [84.93.254.13]
 4     8 ms     *        *     ae3.pcl-cr02.plus.net [195.166.129.42]
 5     8 ms     8 ms     7 ms  ae2.pcl-cr01.plus.net [195.166.129.6]
 6     8 ms     8 ms     8 ms  ae1.ptw-cr01.plus.net [195.166.129.0]
 7    19 ms    19 ms     *     te9-4.ptn-gw01.plus.net [195.166.129.33]
 8     *       20 ms     *     gi3-0.pih-cr1.plus.net [212.159.1.177]
 9    19 ms     *       19 ms  if25.pih-lb03.plus.net [212.159.0.17]
10     *       19 ms     *     community.plus.net [212.159.8.110]
11     *       19 ms    19 ms  community.plus.net [212.159.8.110]
Trace complete.
C:\Users\M>tracert www.bbc.co.uk
Tracing route to www.bbc.net.uk [212.58.244.71]
over a maximum of 30 hops:
 1    <1 ms    <1 ms    <1 ms  10.0.0.249
 2     8 ms     9 ms    18 ms  lo0-plusnet.pcl-ag05.plus.net [195.166.130.29]
 3     8 ms     7 ms     8 ms  gi7-8-654.pcl-gw02.plus.net [84.93.254.13]
 4     8 ms     *        8 ms  po4.pcl-gw01.plus.net [212.159.1.128]
 5    13 ms     8 ms     8 ms  ae3.pcl-cr01.plus.net [195.166.129.40]
 6     8 ms     7 ms     7 ms  ae1.ptw-cr01.plus.net [195.166.129.0]
 7    35 ms     8 ms     *     kingston-gw.thdo.bbc.co.uk [212.58.239.6]
 8     *        *        *     Request timed out.
 9     *        *        *     Request timed out.
10     8 ms     *        8 ms  ae0.er01.telhc.bbc.co.uk [132.185.254.109]
11     8 ms    12 ms    11 ms  132.185.255.148
12     *        8 ms     *     bbc-vip116.telhc.bbc.co.uk [212.58.244.71]
13     8 ms     8 ms     *     bbc-vip116.telhc.bbc.co.uk [212.58.244.71]
14     8 ms     *        8 ms  bbc-vip116.telhc.bbc.co.uk [212.58.244.71]
Trace complete.
C:\Users\M>tracert www.google.co.uk
Tracing route to www-cctld.l.google.com [74.125.132.94]
over a maximum of 30 hops:
 1    <1 ms    <1 ms    <1 ms  10.0.0.249
 2     *       10 ms    14 ms  lo0-plusnet.pcl-ag05.plus.net [195.166.130.29]
 3     9 ms     8 ms     7 ms  gi7-8-654.pcl-gw02.plus.net [84.93.254.13]
 4     *        *        *     Request timed out.
 5     9 ms     7 ms     8 ms  ae1.ptw-cr02.plus.net [195.166.129.2]
 6     9 ms     7 ms     7 ms  72.14.223.32
 7   108 ms    74 ms    66 ms  209.85.252.186
 8     8 ms     *        *     209.85.253.90
 9    14 ms     *       14 ms  72.14.232.134
10    14 ms    14 ms    14 ms  216.239.49.45
11     *        *        *     Request timed out.
12    13 ms    13 ms    14 ms  wb-in-f94.1e100.net [74.125.132.94]
Trace complete.
C:\Users\M>tracert community.plus.net
Tracing route to community.plus.net [212.159.8.110]
over a maximum of 30 hops:
 1    <1 ms    <1 ms    <1 ms  10.0.0.249
 2     8 ms     8 ms     8 ms  lo0-plusnet.pcl-ag05.plus.net [195.166.130.29]
 3     9 ms     7 ms     8 ms  gi7-8-654.pcl-gw02.plus.net [84.93.254.13]
 4     8 ms     *       10 ms  ae3.pcl-cr02.plus.net [195.166.129.42]
 5    27 ms     8 ms     7 ms  ae2.pcl-cr01.plus.net [195.166.129.6]
 6     8 ms     8 ms     *     ae1.ptw-cr01.plus.net [195.166.129.0]
 7     *       19 ms    19 ms  te9-4.ptn-gw01.plus.net [195.166.129.33]
 8    20 ms     *       20 ms  gi3-0.pih-cr1.plus.net [212.159.1.177]
 9    19 ms    19 ms    19 ms  if25.pih-lb03.plus.net [212.159.0.17]
10    24 ms    19 ms    19 ms  community.plus.net [212.159.8.110]
Trace complete.
C:\Users\M>tracert www.plus.net
Tracing route to portal.plus.net [212.159.8.2]
over a maximum of 30 hops:
 1    <1 ms    <1 ms    <1 ms  10.0.0.249
 2     9 ms    22 ms    23 ms  lo0-plusnet.pcl-ag05.plus.net [195.166.130.29]
 3   116 ms    89 ms   267 ms  gi7-8-654.pcl-gw02.plus.net [84.93.254.13]
 4    19 ms    36 ms    19 ms  po4.pcl-gw01.plus.net [212.159.1.128]
 5     8 ms     *       17 ms  ae3.pcl-cr01.plus.net [195.166.129.40]
 6     8 ms     8 ms     7 ms  ae1.ptw-cr01.plus.net [195.166.129.0]
 7     *       19 ms    19 ms  te9-4.ptn-gw01.plus.net [195.166.129.33]
 8    19 ms    19 ms     *     gi3-0.pih-cr1.plus.net [212.159.1.177]
 9     *        *        *     Request timed out.
10     *       19 ms    19 ms  portal.plus.net [212.159.8.2]
Trace complete.
Been able to hit the problem on different accounts (same connection though) and on different gateways (which seem to work fine sometimes too!).   Tried to post here using the bad connection but trying to load any page is hopeless it seems).

[#2]

Thanks folks.
This backs up some of the patterns we were seeing. Further analysis has located further patterns and we are now looking at internal reporting that backs it all up.
A service status is going out in a moment to update this, as this looks to be a BT problem to a specific portion of our network.