Astraweb/US, Possible Changes To Front-End Plant

Over the last (insert months/years here), Astraweb/US (maybe Eu as well...) has had front-end problems with their connection processor; resulting in dropping of connections, excessive time-outs, that kind of stuff (this is all on SSL).

The last couple of days, I've noticed that when the front-end drops or otherwise has problems with a connection, instead of dropping and re-negotiating that single connection, several (usually three) connections are dropped and re-negotiated. So far (will of course be watching) this seems to have eliminated what I'll call 'tripping', where one connection 'trips out', re-negotiates, then trips yet again (sometimes over and over).

Now, it seems to be re-negotiating a 'triple' (or triplet) of connections, and that seems to perhaps 'calm' (or resets) the multiple connections one may be using.

Again, I'll see if it continues to perform better in the long run, perhaps someone there actually took my advice and started looking hard at their logs and such, and decided to do some proactive maintenance.

One CAN hope....!?! :w00t:

Has anyone been having connection timeouts recently?

Specifically during the upload process... it drives me mad.. uploading something larger than 15G has become unbearable..
sometimes trying different server ip address helps..

Newsbin Pro usually shows for me some connection issues with Astraweb. However I don't think much about if my line is still maxed out. I hope they are doing some much needed maintenance.

Quote:

---

Originally Posted by Hypatia

Has anyone been having connection timeouts recently?

Specifically during the upload process... it drives me mad.. uploading something larger than 15G has become unbearable..
sometimes trying different server ip address helps..

---

If one is using anything other than JBinUP to post these days, especially with a fast connection (>1Mb/s) on large (>10MB) rar posts, they need their head examined; I did use PowerPost a ways back (still do on small quick posts) but quickly found out that on large postings it wasn't up to the task.

I run my line pretty near at 100% cycle either posting or downloading, and I get maybe one error in 60+ days with JBinUp that has to be manually 'restarted', if that. All on Astraweb. But I am a bit (some might say more than a bit) watching like a hawk all the time. If my plans to move in the next year or two and get on fiber at 5-10 times my current speed (I'll have to upgrade my router plant at a minimum to handle the speed) then there's no way older s/w will handle it.

I really can't say enough about JBinUp, run 24/7, and even on a plant with the 'more than occasional' hiccup (Mr. Astraweb), it goes through all these kinds of hiccups pretty well, Astra does have excellent propagation and that's the key.

well..ive been using jbinup for a long time now =)

it seems to me the problem might happen when jbinup tries to do its header check while still uploading
at least it looks that way

pS it seems to be working OK again..

Having some connection issues with Astraweb this morning. Speed shoots up to max then just drops to almost nothing after grabbing a few articles. The connections in Newsbin show all 3 of their servers doing the same thing at the same time. IDK wtf they are doing...

It would really be nice if folks reporting something 'going on' with a particular plant would properly identify WHICH plant they are talking about.

For instance, simply saying 'Astraweb' when there are two different plants on opposite sides of the planet tell me nothing.

Be that as it may, Astraweb/US did take a 'burp' around 3am local San Jose time this morning. From the logs it recovered quickly and has been running fine since.

Although Filesharing Talk is acting strage today.... very slow on the uptake and then seems to have problems posting.

Quote:

---

It would really be nice if folks reporting something 'going on' with a particular plant would properly identify WHICH plant they are talking about.

For instance, simply saying 'Astraweb' when there are two different plants on opposite sides of the planet tell me nothing.

---

I thought I made that abundantly clear in my post:

Quote:

---

he connections in Newsbin show all 3 of their servers doing the same thing at the same time.

---

All 3 of their SSL servers (really 2 but they list 3) that is to clarify even further.

Delete, double post.

Nope, still don't.

Astraweb has TWO plants, one in the Netherlands (Amsterdam) and one in the US (San Jose/Santa Clara, CA). The SSL connections are simply through an additional 'front end' at each plant, and the IP address some users use do provide a 'non-specific' set of addresses that will (supposedly) auto-route to the nearest (internet hop count/delay) plant.

I think everybody is, or should be, of the opinion NOT to use those addresses and instead use the direct ones to whichever of the two plants is 'closer' and provides the most stable connection, and not rely on whatever intelligence (or lack thereof) of some auto-route scheme. That will help in the long run.

And yes, it looks like the server for Filesharing Talk is getting a bit weird today with the double postings...

I use all 3 server addresses they list for SSL. I don't Know anything about routing it somewhere else but I do know that they have 2 servers.

Quote:

---

Tracing route to ssl.astraweb.com [207.246.207.136]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 23 ms 19 ms 29 ms cpe-024-074-160-001.carolina.res.rr.com [24.74.1
60.1]
3 11 ms 12 ms 44 ms cpe-024-074-254-137.carolina.res.rr.com [24.74.2
54.137]
4 13 ms 12 ms 12 ms ae18.chrlncpop-rtr1.southeast.rr.com [24.93.64.6
]
5 26 ms 74 ms 31 ms ae-3-0.cr0.atl20.tbone.rr.com [66.109.6.82]
6 29 ms 66 ms 78 ms 107.14.19.11
7 188 ms 232 ms 221 ms te3-4.ccr01.atl02.atlas.cogentco.com [154.54.12.
109]
8 47 ms 47 ms 47 ms te0-0-0-1.ccr22.atl01.atlas.cogentco.com [154.54
.0.161]
9 49 ms 47 ms 47 ms te0-3-0-2.ccr22.iah01.atlas.cogentco.com [66.28.
4.90]
10 78 ms 79 ms 79 ms te0-0-0-3.ccr22.lax01.atlas.cogentco.com [154.54
.44.254]
11 268 ms 219 ms 220 ms te4-1.ccr02.sjc01.atlas.cogentco.com [154.54.5.6
9]
12 94 ms 91 ms 92 ms te3-3.mpd01.sjc06.atlas.cogentco.com [154.54.7.1
02]
13 92 ms 92 ms 92 ms 38.122.94.6
14 93 ms 91 ms 92 ms 136.sjc.astraweb.com [207.246.207.136]

Trace complete.

---

Quote:

---

Tracing route to ssl-us.astraweb.com [216.151.153.136]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 32 ms 19 ms 29 ms cpe-024-074-160-001.carolina.res.rr.com [24.74.1
60.1]
3 11 ms 12 ms 12 ms cpe-024-074-254-137.carolina.res.rr.com [24.74.2
54.137]
4 14 ms 12 ms 12 ms ae18.chrlncpop-rtr1.southeast.rr.com [24.93.64.6
]
5 27 ms 28 ms 28 ms 107.14.19.18
6 29 ms 28 ms 37 ms ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
7 * 96 ms 222 ms te3-4.ccr01.atl02.atlas.cogentco.com [154.54.12.
109]
8 47 ms 47 ms 47 ms te0-0-0-1.mpd21.atl01.atlas.cogentco.com [154.54
.40.249]
9 47 ms 47 ms 47 ms te0-1-0-2.mpd21.iah01.atlas.cogentco.com [154.54
.5.202]
10 78 ms 79 ms 79 ms te0-1-0-6.mpd21.lax01.atlas.cogentco.com [154.54
.5.102]
11 293 ms 219 ms 216 ms te4-1.mpd01.sjc01.atlas.cogentco.com [154.54.6.3
0]
12 93 ms 92 ms 93 ms te4-2.mpd01.sjc06.atlas.cogentco.com [154.54.6.1
50]
13 93 ms 92 ms 92 ms 38.122.94.6
14 95 ms 91 ms 92 ms unknown.sj.astraweb.com [216.151.153.136]

Trace complete.

---

Quote:

---

Tracing route to ssl-eu.astraweb.com [193.202.122.116]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 24 ms 29 ms 18 ms cpe-024-074-160-001.carolina.res.rr.com [24.74.1
60.1]
3 15 ms 12 ms 44 ms cpe-024-074-254-137.carolina.res.rr.com [24.74.2
54.137]
4 13 ms 12 ms 12 ms ae18.chrlncpop-rtr1.southeast.rr.com [24.93.64.6
]
5 27 ms 28 ms 28 ms ae-3-0.cr0.atl20.tbone.rr.com [66.109.6.82]
6 28 ms 37 ms 45 ms ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
7 27 ms 28 ms 28 ms te3-4.ccr01.atl02.atlas.cogentco.com [154.54.12.
109]
8 27 ms 28 ms 28 ms te0-0-0-1.mpd21.atl01.atlas.cogentco.com [154.54
.40.249]
9 25 ms 28 ms 28 ms te0-0-0-7.mpd21.dca01.atlas.cogentco.com [154.54
.28.197]
10 34 ms 34 ms 34 ms te0-4-0-1.mpd21.jfk02.atlas.cogentco.com [154.54
.40.46]
11 110 ms 108 ms 108 ms te0-4-0-3.ccr21.bos01.atlas.cogentco.com [154.54
.44.18]
12 104 ms 108 ms 108 ms te0-3-0-1.ccr21.lpl01.atlas.cogentco.com [154.54
.31.230]
13 119 ms 114 ms 118 ms te0-2-0-6.ccr21.ams03.atlas.cogentco.com [154.54
.37.89]
14 114 ms 114 ms 114 ms te4-3.mpd01.ams04.atlas.cogentco.com [130.117.50
.222]
15 113 ms 111 ms 111 ms 149.11.38.34
16 112 ms 110 ms 112 ms unknown.ams.astraweb.com [193.202.122.116]

Trace complete.

---

The names don't tell you anything about how many front ends there are, they're just names.

For years now, Astraweb has been using a load balancing contraption that I've never seen with any other provider.

If you don't have a free app like CyberKit, there are DNS websites that show the changing lists of 8 IP addresses.

Try IPTools, http://www.iptools.com/dnstools.php?tool=hostresolve

Refresh the page with 'F5' on a PC.

Since I'm in the USA, the names 'ssl.astraweb.com' and 'ssl-us.astraweb.com' always resolve to 8 IP addresses from the same master list of about 2 dozen front end addresses. With CyberKit, the small list of 8 addresses changes every 5 seconds. The IPTools site doesn't show the list of addresses remaining the same for 5 seconds, the list always changes by hitting F5.

Quote:

---

Originally Posted by Hypatia

Has anyone been having connection timeouts recently?

Specifically during the upload process... it drives me mad.. uploading something larger than 15G has become unbearable..
sometimes trying different server ip address helps..

---

That's why I have multiple block accounts via blocknews, etc, and use them to upload, since uploading doesn't count for data :D


and JBinup is used by spammers and assholes (no offense) but it's the truth.

Quote:

---

Originally Posted by SonsOfLiberty

Quote:

---

Originally Posted by Hypatia

Has anyone been having connection timeouts recently?

Specifically during the upload process... it drives me mad.. uploading something larger than 15G has become unbearable..
sometimes trying different server ip address helps..

---

and JBinup is used by spammers and assholes (no offense) but it's the truth.

---

I hurd Newsbin is used by trolls and dickheads. (It's the truth).

Quote:

---

via blocknews,

---

uploading on BN is even slower than downloading...

Quote:

---

Originally Posted by heiska

Quote:

---

Originally Posted by SonsOfLiberty

and JBinup is used by spammers and assholes (no offense) but it's the truth.

---

I hurd Newsbin is used by trolls and dickheads. (It's the truth).

---

Newsbin, :lol: ppl use that?

let me see how you would use sabnzbd working with headers.
Im waiting =))