Yes... I do mean London... Take a look at this example
quote:
Tracing route to mail1.tech911solutions.com [99.247.245.217]
over a maximum of 30 hops:
1 8 ms 7 ms 7 ms 10.42.8.1
2 7 ms 6 ms 9 ms gw03.lndn.phub.net.cable.rogers.com [66.185.90.65]
3 * * * Request timed out.
4 6 ms 8 ms 9 ms gw01.wdstck.phub.net.cable.rogers.com [66.185.81.73]
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
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.
This is a direct copy and paste of what I received from my technical office in London when going through troubleshooting to determine where the problem was. Fortunately, it just so happens that we have a DSL line in that facility also, so it just meant some temporary re-routing and dealing with a somewhat slower internet, but we were still able to conduct business.
This is how I know that Rogers was affected in the same point also. In normal circumstances, the next hop in that route is gw01.brntfd.phub.net.cable.rogers.com, which happens to be a connection going from Woodstock to Brantford. It seems a little convenient that the connection would drop between Woodstock and Brantford when the exact problem that TekSavvy was having also happened to be between Woodstock and Brantford.
Coincidence? I think not...