cancel
Showing results for 
Search instead for 
Did you mean: 

Data Transfer Problems?

LiamM
Grafter
Posts: 5,636
Registered: ‎12-08-2007

Data Transfer Problems?

Anyone else getting any weird data transfer / routing problems to certain websites?
The following are all very slow or inaccessible for me at the moment (including my own) :-
www.o2.co.uk
www.originalorganics.co.uk
www.waterbuttsdirect.co.uk
www.openhosting.co.uk
I've hopped gateways and that doesn't seem to have worked.

traceroute to webpres-fe2-vip.london.02.net (82.132.141.84), 64 hops max, 40 byte packets
1  10.1.2.180 (10.1.2.180)  1.830 ms  1.190 ms  1.182 ms
2  lo0-plusnet.thn-ag3.plus.net (195.166.128.80)  28.874 ms  28.897 ms  27.831 ms
3  vl303.thn-gw1.plus.net (84.92.3.177)  27.826 ms  26.538 ms  25.508 ms
4  linx2.ukcore.bt.net (195.66.226.10)  26.355 ms  27.061 ms  28.606 ms
5  core2-pos0-14-4-0.ilford.ukcore.bt.net (195.99.125.230)  28.243 ms  27.918 ms  27.555 ms
6  iar1-tenge5-5.ilford.fixed.bt.net (194.74.77.222)  28.260 ms  32.943 ms  29.503 ms
7  ftip003089866-bgp.iar1.ilford.ilford.fixed.bt.net (62.172.57.202)  31.612 ms  32.079 ms  32.915 ms
8  193.113.199.129 (193.113.199.129)  33.493 ms  34.169 ms  37.913 ms
9  * * *
10  * * *

Quote
traceroute to www.originalorganics.co.uk (89.238.147.58), 64 hops max, 40 byte packets
1  10.1.2.180 (10.1.2.180)  1.734 ms  1.187 ms  1.180 ms
2  lo0-plusnet.thn-ag3.plus.net (195.166.128.80)  30.111 ms  26.892 ms  26.072 ms
3  vl303.thn-gw1.plus.net (84.92.3.177)  27.653 ms  25.354 ms  28.743 ms
4  * * *
5  * * *
6  * * *

6 REPLIES 6
scootie
Grafter
Posts: 4,799
Thanks: 1
Registered: ‎03-11-2007

Re: Data Transfer Problems?

Tracing route to webpres-fe2-vip.london.02.net [82.132.141.84]
over a maximum of 30 hops:
  1    *    1382 ms    1 ms  10.0.0.1
  2    24 ms    20 ms    21 ms  lo0-plusnet.pcl-ag03.plus.net [195.166.128.109]
  3    27 ms    18 ms    24 ms  gi1-6-703.pcl-gw01.plus.net [84.92.0.181]
  4    26 ms    22 ms    30 ms  te2-2.pte-gw1.plus.net [212.159.0.186]
  5    61 ms  162 ms    38 ms  vl22.thn-gw1.plus.net [212.159.4.3]
  6    23 ms    20 ms    21 ms  linx2.ukcore.bt.net [195.66.226.10]
  7    20 ms    18 ms    24 ms  core1-pos9-0-0.telehouse.ukcore.bt.net [194.74.6
5.117]
  8    19 ms    19 ms    21 ms  iar1-tenge5-5.ilford.fixed.bt.net [194.74.77.222
]
  9    18 ms    29 ms    21 ms  62.172.57.202
10    28 ms    20 ms    21 ms  193.113.199.129
11    *        *        *    Request timed out.
12    *        *        *    Request timed out.
Tracing route to originalorganics.co.uk [89.238.147.58]
over a maximum of 30 hops:
  1  1912 ms    1 ms    1 ms  10.0.0.1
  2    23 ms    21 ms    25 ms  lo0-plusnet.pcl-ag03.plus.net [195.166.128.109]
  3    22 ms    21 ms    35 ms  gi1-6-703.pcl-gw01.plus.net [84.92.0.181]
  4    *      33 ms    30 ms  te2-2.pte-gw1.plus.net [212.159.0.186]
  5    20 ms    18 ms    19 ms  te2-4.pte-gw2.plus.net [212.159.1.102]
  6    20 ms    21 ms    18 ms  195.66.224.185
  7    20 ms    18 ms    17 ms  te4-1.mpd01.lon02.atlas.cogentco.com [130.117.1.
202]
  8    74 ms  215 ms    74 ms  oh-tele.demarc.cogentco.com [149.6.148.10]
  9    *        *        *    Request timed out.
10    19 ms    20 ms    18 ms  owl-web1.originalwebware.co.uk [89.238.147.58]
Trace complete.
Oldjim
Resting Legend
Posts: 38,460
Thanks: 787
Fixes: 63
Registered: ‎15-06-2007

Re: Data Transfer Problems?

Through to all of them with no problems
hulls
Grafter
Posts: 1,699
Registered: ‎30-07-2007

Re: Data Transfer Problems?

No problems here either  Smiley
John
scootie
Grafter
Posts: 4,799
Thanks: 1
Registered: ‎03-11-2007

Re: Data Transfer Problems?

forgot to add that they all loaded o.k
Chris
Legend
Posts: 17,724
Thanks: 600
Fixes: 169
Registered: ‎05-04-2007

Re: Data Transfer Problems?

No problems here Liam, I'll hop a couple of gateways and try again.
Former Plusnet Staff member. Posts after 31st Jan 2020 are not on behalf of Plusnet.
Liam
Grafter
Posts: 2,083
Registered: ‎04-04-2007

Re: Data Transfer Problems?

Left the office shortly after posting and fine from Plusnet connection where I am now, so perhaps it was a minor routing blip that fixed itself.