View Full Version : 4webspace Users.
-Edward- 04-03-2002, 11:58 AM Anyone else having problems connecting to servers hosted by 4webspace(Tera-byte) im having very slow ftp downloads and uploads and forget about editing a file via ftp thats just pointless.
its a 1 in 10 chance i can connect via http .. I did think it was just me but the person i co-share the server with at 4webspace whos in texas has this problem. My isp for some reason has blocked me from doing tracerouts so i cannot provide one which isnt good for when im mailing tera-byte as Tim says there are no network problems.
iplexx 04-03-2002, 12:07 PM same here...
tracert is not bad when it reaches 4ws/tb (now: 232ms) however working is nearly impossible; can't hardly work on the servers for at least last 8 hours... shell connections drop after some minutes, http connections are working max. 50%
IMHO there must be a large paket loose somewhere on the route, but I really don't see where.... my guess is the link london-new york
Technics, are you located in Europe (like me) or in the USA?
24 231 ms 231 ms 231 ms edtnabxmdr01.bb.telus.com [205.233.111.100]
25 232 ms 232 ms 233 ms 209.115.218.238
26 * 240 ms 240 ms cat6006-vlan400.edm.tera-byte.com [216.234.160.22]
27 239 ms * * fw-4ws-fxp0.edm.tera-byte.com [216.234.160.54]
28 * * * Zeitüberschreitung der Anforderung.
29 * * 216 ms www.xxxxxx.at [xx.xx.xx.xx]
-Edward- 04-03-2002, 12:27 PM I'm from England. Everything was fine until about 3pm yesterday afternoon. I've run traceroutes from places like http://combat.uxn.com and they seem fine accessing tera-byte when i cannot.
like now i currently cannot access my server. When i finally can get access too it it takes ages and i mean ages to even load a 5k page. But heres what im getting from uxn's site
5 0.so-0-0-0.XL1.LAX2.ALTER.NET (152.63.115.217) 80.073 ms 6 0.so-1-0-0.TL1.LAX9.ALTER.NET (152.63.115.142) 124.016 ms 7 0.so-4-0-0.TL1.CAL1.ALTER.NET (152.63.0.65) 124.992 ms 8 197.at-1-0-0.XR1.CAL1.ALTER.NET (152.63.136.65) 125.968 ms 9 193.ATM7-0.GW1.CAL1.ALTER.NET (152.63.136.161) 126.945 ms10 sprnt4-gw.customer.alter.net (157.130.157.94) 137.686 ms11 gigabitethernet5-0-0.gw4.cal1.sprint-canada.net (204.50.251.197) 162.099 ms12 * * *13 cat6006-vlan12.edm.tera-byte.com (216.234.160.34) 161.122 ms14 fw3-4ws-fxp0.edm.tera-byte.com (216.194.65.10) 162.099 ms
Anyone know of any sites that i can use to check from england so i can see if theres a problem ???
iplexx 04-03-2002, 01:08 PM no matter what ISP I use, my route goes thru psi.net (concert-> psi.net, ebone-> psi.net, ip-plus.net -> psinet) and that's where IMHO the bottleneck is
maybe some other Euros can quote on this?
technics, don't think you'll see much on tracert's, most of them just look fine; anywhere here's a link for you: http://www.traceroute.org/ provides links traceroute servers worldwide... :)
-Edward- 04-03-2002, 02:09 PM Well i can't access my server at all now unless i use a proxy from cyberarmy.com, It's rather annoying as ive got some important stuff to upload to fix bugs on our site.
I am starting to think that this is something todo with the way traffic is routed to tera-byte through europe. Since people in America cept my friend in texas find everything ok.
Next thing is to get tera-byte to acknowledge there is a problem somewhere between europe and there noc :) Wonder if they will try do anything? :D prolly not since its not really there problem is it? now im regreting moving from rackshack back to tera-byte lol.
iplexx 04-03-2002, 02:18 PM I'll bet they tell you that for sure. And IMHO it's not their problem at all. To me it seems that all US traffic is f**king slow at all, rackshack is just as hard to browse as 4WS/TB....
even also webhostingtalk is hard to read (>8sec loadtime per thread)....
you shouldn't move rackshack to 4ws, you should haved moved yorself from england to US.... :D
iplexx 04-03-2002, 02:23 PM 7 55 ms 52 ms 59 ms fra2-vie2-oc12-1.fra2.above.net [64.125.31.13]
8 53 ms 54 ms 56 ms core1-fra2-oc48.fra1.above.net [62.4.64.30]
9 235 ms 235 ms * core1-fra1-oc3.cph1.above.net [62.4.68.209]
10 * * 720 ms lhr3-cph1-stm1.lhr3.above.net [208.184.231.181]
11 733 ms * * core2-core1-stm64.lhr3.above.net [208.184.231.146]
12 807 ms 789 ms 797 ms lga1-lhr3-stm64.lga1.above.net [64.125.31.182]
13 797 ms 847 ms * main1-core2-oc48.lga1.above.net [216.200.127.198]
14 * 787 ms 779 ms www.webhostingtalk.com [209.249.55.203]
:bawling: :bawling: :bawling:
6 44 ms 39 ms 38 ms core1-main1-oc12.vie2.above.net [208.184.231.89]
7 55 ms 53 ms 52 ms fra2-vie2-oc12-1.fra2.above.net [64.125.31.13]
8 54 ms 52 ms 53 ms core1-fra2-oc48.fra1.above.net [62.4.64.30]
9 * * * Zeitüberschreitung der Anforderung.
10 * 715 ms * lhr3-cph1-stm1.lhr3.above.net [208.184.231.181]
11 711 ms 722 ms 721 ms core2-core1-stm64.lhr3.above.net [208.184.231.146]
12 * 793 ms 795 ms lga1-lhr3-stm64.lga1.above.net [64.125.31.182]
13 * 802 ms 791 ms main1-core2-oc48.lga1.above.net [216.200.127.198]
14 810 ms * 801 ms www.webhostingtalk.com [209.249.55.203]
:bawling: :bawling: :bawling:
-Edward- 04-03-2002, 02:40 PM I'm now actually gaining access access to my server but its extremly slow i guess thats better than no access at all :) I've done a few trace routes from various places in the uk.
1 core.lon-th1.mailbox.net.uk (195.82.125.1) 0.665 ms 0.534 ms 0.522 ms
2 fe5-0-0-20-vl20-b-mailbox-gw.LTNr2.core.band-x.net (213.166.0.69) 1.436 ms 1.83 ms 1.273 ms
3 213.232.64.50 (213.232.64.50) 2.516 ms 1.562 ms 1.5 ms
4 p2-2.london2-cr4.bbnplanet.net (212.133.14.69) 0.87 ms 0.987 ms 1.258 ms
5 p1-0.london2-cr3.bbnplanet.net (195.16.175.173) 1.074 ms 1.951 ms 1.024 ms
6 p2-0.phlapa1-br1.bbnplanet.net (195.16.175.249) 72.845 ms 72.868 ms 72.479 ms
7 p9-0.iplvin1-br1.bbnplanet.net (4.24.10.182) 87.851 ms 87.681 ms 87.853 ms
8 so-6-0-0.chcgil2-br1.bbnplanet.net (4.24.9.57) 91.671 ms 91.451 ms 91.265 ms
9 so-7-0-0.chcgil2-br2.bbnplanet.net (4.24.5.218) 91.28 ms 91.328 ms 91.169 ms
10 p1-0.chcgil2-cr2.bbnplanet.net (4.24.9.34) 91.369 ms 91.393 ms 91.709 ms
11 p0-0.bctel2.bbnplanet.net (4.24.203.38) 91.545 ms 91.518 ms 91.485 ms
12 toroonxnbr00.bb.telus.com (209.115.138.53) 102.129 ms 102.127 ms 101.992 ms
13 toroonnlbr00.bb.telus.com (154.11.6.2) 102.109 ms 102.196 ms 102.238 ms
14 edtnabkdbr01.bb.telus.com (209.115.137.237) 148.543 ms 148.107 ms 148.118 ms
15 edtnabxmdr01.bb.telus.com (205.233.111.131) 148.371 ms 148.227 ms 148.629 ms
16 209.115.218.238 (209.115.218.238) 149.314 ms 151.133 ms 149.883 ms
17 cat6006-vlan400.edm.tera-byte.com (216.234.160.22) 149.817 ms 149.667 ms 149.759 ms
18 fw3-4ws-fxp0.edm.tera-byte.com (216.194.65.10) 149.612 ms 149.274 ms 149.527 ms
19 fw3-4ws-fxp0.edm.tera-byte.com (216.194.65.10) 151.714 ms 149.459 ms 151.827 ms
20 fw3-4ws-fxp0.edm.tera-byte.com (216.194.65.10) 151.007 ms 149.315 ms 152.643 ms
21 fw3-4ws-fxp0.edm.tera-byte.com (216.194.65.10) 149.854 ms 149.773 ms 150.205 ms
22 fw3-4ws-fxp0.edm.tera-byte.com (216.194.65.10) 150.186 ms 152.071 ms 149.542 ms
23 fw3-4ws-fxp0.edm.tera-byte.com (216.194.65.10) 149.686 ms 149.213 ms 149.157 ms
24 fw3-4ws-fxp0.edm.tera-byte.com (216.194.65.10) 150.999 ms 150.922 ms 149.223 ms
25 fw3-4ws-fxp0.edm.tera-byte.com (216.194.65.10) 149.361 ms 201.222 ms 149.32 ms
26 fw3-4ws-fxp0.edm.tera-byte.com (216.194.65.10) 149.697 ms 149.369 ms 149.408 ms
27 fw3-4ws-fxp0.edm.tera-byte.com (216.194.65.10) 149.717 ms 149.4 ms 235.815 ms
28 fw3-4ws-fxp0.edm.tera-byte.com (216.194.65.10) 242.842 ms 149.54 ms 149.116 ms
29 fw3-4ws-fxp0.edm.tera-byte.com (216.194.65.10) 149.978 ms 150.396 ms 149.691 ms
30 fw3-4ws-fxp0.edm.tera-byte.com (216.194.65.10) 148.94 ms 149.681 ms 151.084 ms
1 gw-195-82-119.core.lon-sw6.mailbox.net.uk (195.82.119.1) 0.611 ms (ttl=64!) 0.314 ms (ttl=64!) 0.296 ms (ttl=64!)
2 sw6-gw-fe.core.lon-th1.mailbox.net.uk (195.82.97.1) 1.39 ms 1.17 ms 1.17 ms
3 fe5-0-0-20-vl20-b-mailbox-gw.LTNr2.core.band-x.net (213.166.0.69) 446 ms 69.6 ms 66.0 ms
4 213.232.64.50 (213.232.64.50) 77.9 ms 53.0 ms 36.4 ms
5 p6-2.london2-cr4.bbnplanet.net (212.133.14.89) 29.6 ms 4.87 ms 2.49 ms
6 p1-0.london2-cr3.bbnplanet.net (195.16.175.173) 1.60 ms 2.61 ms 3.48 ms
7 p2-0.phlapa1-br1.bbnplanet.net (195.16.175.249) 76.7 ms 81.0 ms 74.1 ms
8 p9-0.iplvin1-br1.bbnplanet.net (4.24.10.182) 91.5 ms 88.3 ms 88.0 ms
9 so-6-0-0.chcgil2-br1.bbnplanet.net (4.24.9.57) 141 ms (ttl=246!) 155 ms (ttl=246!) 177 ms (ttl=246!)
10 so-7-0-0.chcgil2-br2.bbnplanet.net (4.24.5.218) 139 ms (ttl=245!) 119 ms (ttl=245!) 139 ms (ttl=245!)
11 p1-0.chcgil2-cr2.bbnplanet.net (4.24.9.34) 106 ms 143 ms 164 ms
12 p0-0.bctel2.bbnplanet.net (4.24.203.38) 170 ms 177 ms 169 ms
13 toroonxnbr00.bb.telus.com (209.115.138.53) 264 ms 103 ms 104 ms
14 toroonnlbr00.bb.telus.com (154.11.6.2) 105 ms 105 ms 103 ms
15 edtnabkdbr01.bb.telus.com (209.115.137.237) 156 ms (ttl=242!) 149 ms (ttl=242!) 149 ms (ttl=242!)
16 edtnabxmdr01.bb.telus.com (205.233.111.100) 149 ms (ttl=242!) 442 ms (ttl=242!) 152 ms (ttl=242!)
17 209.115.218.238 (209.115.218.238) 150 ms (ttl=241!) 151 ms (ttl=241!) 150 ms (ttl=241!)
18 cat6006-vlan400.edm.tera-byte.com (216.234.160.22) 151 ms (ttl=240!) 160 ms (ttl=240!) 150 ms (ttl=240!)
19 fw3-4ws-fxp0.edm.tera-byte.com (216.194.65.10) 150 ms (ttl=48!) !U 151 ms (ttl=48!) !U 156 ms (ttl=48!) !U
That one i noticed a rather large jump when it got to telus.com
1 60 ms 40 ms 30 ms 158.152.1.222 demon-du.demon.co.uk
2 100 ms 41 ms 30 ms 194.159.171.61 anchor-ndu-rs01-fe1.access.demon.net
3 30 ms 80 ms 80 ms 195.173.57.251 anchor-core-1-fxp3.router.demon.net
4 100 ms 60 ms 30 ms 158.152.0.181 tele-backbone-1-ge022.router.demon.net
5 30 ms 40 ms 151 ms 194.159.176.78 tele-border-1-138.router.demon.net
6 30 ms 40 ms 100 ms 213.206.130.81 sl-gw10-lon-3-0.sprintlink.net
7 71 ms 80 ms 70 ms 213.206.128.45 sl-bb21-lon-8-0.sprintlink.net
8 110 ms 110 ms 111 ms 144.232.19.69 sl-bb20-msq-10-0.sprintlink.net
9 110 ms 150 ms 140 ms 144.232.9.102 sl-bb20-nyc-11-3.sprintlink.net
10 110 ms 110 ms 110 ms 144.232.7.9 sl-bb21-nyc-9-0.sprintlink.net
11 150 ms 130 ms 160 ms 144.232.18.249 sl-bb21-chi-11-1.sprintlink.net
12 140 ms 150 ms 120 ms 144.232.26.30 sl-gw31-chi-10-0.sprintlink.net
13 151 ms 160 ms 210 ms 144.224.114.170 sl-callnet-6-0.sprintlink.net
14 191 ms 150 ms 200 ms 204.50.251.133 gigabitethernet10-0-0.gw4.cal1.sprint-canada.net
15 231 ms 160 ms 180 ms 207.107.204.158 Z-serial3-0-0.gw4.cal1.sprint-canada.net
16 310 ms 211 ms 280 ms 216.234.160.26 cat6006-vlan10.edm.tera-byte.com
17 181 ms 190 ms 170 ms 216.194.65.10 fw3-4ws-fxp0.edm.tera-byte.com
18 170 ms 221 ms 160 ms 216.194.66.10 kchat.org
So it doesnt say any packets lost but its extremly slow this is very strange :(
webtech 04-03-2002, 03:26 PM I had 3 servers at 4webspace but the speed of ftp and web were unbearable (1-2k a second) on a 1mbps DSL line so i have purchased colo area in Atlanta and have moved them slowly. I will continue to leave the 1 server left up at 4webspace as long as speeds are good for the client in the UK. If speeds drop, it will be moved. Anyone else have other solutions? Willing to talk.
-Edward- 04-03-2002, 05:14 PM i found my problem its with France Telecom :
13 P13-0.PASCR1.Pastourelle.opentransit.net (193.251.154.225) 4181.650 ms 4164.755 ms 4123.615 ms
14 P12-0.NYKCR2.New-york.opentransit.net (193.251.241.134) 4283.976 ms 4285.466 ms 4397.640 ms
15 P13-0.NYKCR3.New-york.opentransit.net (193.251.241.218) 4289.110 ms
So i just gotta wait till they pull the finger out and fix things.
-Edward- 04-03-2002, 05:29 PM i do have to say thanks to Steve Keyser for all the help hes giving me via email hes being extremly helpful and has been swapping emails with me for an hour, Now i know why i went back to tera-byte it was for the quality support :)
iplexx 04-03-2002, 05:53 PM technics, glad you solved your problem
however, i don't see a the reason why france telecom/opentransit is the problem...
for me, i don't go thru them... did you change ISP, are you as fast as usual now? i admit, it's better now than over the day, but this may be thru the time (short before midnight) where a lot of other Europeans are sleeping... !?
And yes, Steve's really doing his job very excellent ! :)
-Edward- 04-03-2002, 06:00 PM Well actually just after posting this and a few emails exchanged with Tim the route of the problem was found and everything is fixed and i must say ftp and http are both superfast infact faster than they were before.
|