CN Meltdown
View Full Version : CN Meltdown
Anyone else been having trouble getting into CN? I couldn't
get in all day. Of course doing a trace shows quite a few
hops and it timed out before I could complete the trace.
Quite a few routers, might be a few bottlenecks along the
way, but it looks like I will have to wait till late night
to read up on the Giroess and that other race, ah... the one
with Lance in it.
Tracing route to cyclingnews.com [210.10.97.10] over a
maximum of 30 hops:
1 * * * Request timed out. 2 130 ms 130 ms 130 ms
641181067.sierratel.com [64.118.106.7] 3 130 ms 130 ms 140
ms 641181061.sierratel.com [64.118.106.1] 4 130 ms 130 ms
130 ms 6411898241.sierratel.com [64.118.98.241] 5 140 ms
131 ms 130 ms 6411898226.sierratel.com [64.118.98.226] 6
140 ms 141 ms 120 ms sl-gw25-stk-4-0-TS1.sprintlink.net
[160.81.8.137 ] 7 131 ms 140 ms 140 ms sl-bb20-stk-8-
1.sprintlink.net
[160.81.8.1]8 140 ms 130 ms 130 ms sl-bb20-sj-9-
0.sprintlink.net
[160.81.8.2]9 140 ms 141 ms 130 ms sl-st20-pa-15-
2.sprintlink.net [144.232.9.8] 10 140 ms 141 ms
120 ms sl-newzeal-1-0.sprintlink.net
[160.81.8.3]11 290 ms 290 ms 291 ms 202.37.246.202 12 290 ms
291 ms 280 ms 202.37.245.253 13 290 ms 291 ms
290 ms 202.37.246.250 14 291 ms 290 ms 280 ms
so-3-0-3.cre1.syd.connect.com.au
[160.81.8.4]15 310 ms 321 ms 320 ms so-1-1-
0.cre1.mel.connect.com.au
[160.82..38] 16 310 ms 311 ms 310 ms
as2.cre1.ade.connect.com.au [202.10.0.225] 17 320 ms
321 ms 310 ms pos1-0.bdr2.ade.connect.com.au
[202.10.4.86] 18 320 ms 311 ms 320 ms fastethernet0-
0.cor3.ade.connect.com.au
[160.83.
160.84]19 320 ms 321 ms 330 ms ix140944-1.gw.connect.com.au
[210.8.6.237] 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.
It is a denial of service attack!!!
Or maybe there are lots of people all over the globe trying
to access it all at once?
"Sierraman" <riposa@sti.net> wrote in message news:Jt2dnZ-S7sTd13fdRVn-
sA@sti.net...
> Anyone else been having trouble getting into CN? I
> couldn't get in all
day.
> Of course doing a trace shows quite a few hops and it
> timed out before I could complete the trace. Quite a few
> routers, might be a few bottlenecks along the way, but it
> looks like I will have to wait till late night to
read
> up on the Giroess and that other race, ah... the one with
> Lance in it.
Giri? Italian tours? Tours of Italy? Please not "Giroess",
where did you get that? I thought it was some kind of
network protocol I had not heard of until I realized what
you were trying to say.
>
> Tracing route to cyclingnews.com [210.10.97.10] over a
> maximum of 30 hops:
>
> 1 * * * Request timed out. 2 130 ms 130 ms 130 ms
> 641181067.sierratel.com [64.118.106.7] 3 130 ms 130 ms
> 140 ms 641181061.sierratel.com [64.118.106.1] 4 130 ms
> 130 ms 130 ms 6411898241.sierratel.com [64.118.98.241] 5
> 140 ms 131 ms 130 ms 6411898226.sierratel.com
> [64.118.98.226] 6 140 ms 141 ms 120 ms sl-gw25-stk-4-0-
> TS1.sprintlink.net
> [160.81.8.137 ] 7 131 ms 140 ms 140 ms sl-bb20-stk-8-
> 1.sprintlink.net
> [144.232.4.217]8 140 ms 130 ms 130 ms sl-bb20-sj-9-
> 0.sprintlink.net
> [144.232.20.99]9 140 ms 141 ms 130 ms sl-st20-pa-15-
> 2.sprintlink.net
[144.232.9.8]
> 10 140 ms 141 ms 120 ms sl-newzeal-1-0.sprintlink.net
> [144.223.243.18]11 290 ms 290 ms 291 ms 202.37.246.202 12
> 290 ms 291 ms 280 ms 202.37.245.253 13 290
> ms 291 ms 290 ms 202.37.246.250 14 291 ms
> 290 ms 280 ms so-3-0-
> 3.cre1.syd.connect.com.au
> [202.10.4.11]15 310 ms 321 ms 320 ms so-1-1-
> 0.cre1.mel.connect.com.au
> [202.10..38] 16 310 ms 311 ms 310 ms
> as2.cre1.ade.connect.com.au [202.10.0.225] 17 320
> ms 321 ms 310 ms pos1-0.bdr2.ade.connect.com.au
[144.232.9.9]
> 18 320 ms 311 ms 320 ms fastethernet0-
> 0.cor3.ade.connect.com.au
> [203.63.
> 113.67]19 320 ms 321 ms 330 ms ix140944-
> 1.gw.connect.com.au [210.8.6.237] 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.
I think that Cyclingnews should plan for these huge events
(at least for the Tour!!!) and either rent some equipment or
buy a few strategically placed servers in important markets
(the US, Europe and ???) with dedicated connections back to
Australia (or is the Australian-French connection also a
problem?. That way the client PCs (ours) are only having to
get to one or two key places that are nice and fat. It seems
kind of nuts to have a global media outlet with excellent
market penetration throughout the world but is only serviced
in Australia (notorious for Internet bottlenecks and traffic
problems). Heck, even the Tour official site in France has
capacity problems even though France has much better
connectivity than Australia. Content wise Cyclingnews is THE
BEST site and has been for several years. They need to beef
up their distribution for this key event (at least). Maybe
they can set up a small server (or cluster) for the live
updates and have it served up from Europe instead of taking
it back to Australia first?
I hope the ads are up and working (I think those are
distributed like I suggest for the live updates).
Jeff, whaddya think about this?
On Tue, 6 Jul 2004 11:12:51 -0700, "Chris"
<chrismcreynolds@hotmail.com> wrote:
>Giri? Italian tours? Tours of Italy? Please not "Giroess",
>where did you get that?
I think that the -ess was a feminine ending rather than
a plural...
Duh!!!!!!! Don't you realize they are a little busy
right now??
On 7/5/04 11:44 PM, in article Jt2dnZ-S7sTd13fdRVn-
sA@sti.net, "Sierraman" <riposa@sti.net> wrote:
> Anyone else been having trouble getting into CN? I
> couldn't get in all day. Of course doing a trace shows
> quite a few hops and it timed out before I could complete
> the trace. Quite a few routers, might be a few bottlenecks
> along the way, but it looks like I will have to wait till
> late night to read up on the Giroess and that other race,
> ah... the one with Lance in it.
>
> Tracing route to cyclingnews.com [210.10.97.10] over a
> maximum of 30 hops:
>
> 1 * * * Request timed out. 2 130 ms 130 ms 130 ms
> 641181067.sierratel.com [64.118.106.7] 3 130 ms 130 ms
> 140 ms 641181061.sierratel.com [64.118.106.1] 4 130 ms
> 130 ms 130 ms 6411898241.sierratel.com [64.118.98.241] 5
> 140 ms 131 ms 130 ms 6411898226.sierratel.com
> [64.118.98.226] 6 140 ms 141 ms 120 ms sl-gw25-stk-4-0-
> TS1.sprintlink.net
> [160.81.8.137 ] 7 131 ms 140 ms 140 ms sl-bb20-stk-8-
> 1.sprintlink.net
> [144.232.4.217]8 140 ms 130 ms 130 ms sl-bb20-sj-9-
> 0.sprintlink.net
> [144.232.20.99]9 140 ms 141 ms 130 ms sl-st20-pa-15-
> 2.sprintlink.net [144.232.9.8] 10 140 ms
> 141 ms 120 ms sl-newzeal-1-
> 0.sprintlink.net
> [144.223.243.18]11 290 ms 290 ms 291 ms 202.37.246.202 12
> 290 ms 291 ms 280 ms 202.37.245.253 13 290
> ms 291 ms 290 ms 202.37.246.250 14 291 ms
> 290 ms 280 ms so-3-0-
> 3.cre1.syd.connect.com.au
> [202.10.4.11]15 310 ms 321 ms 320 ms so-1-1-
> 0.cre1.mel.connect.com.au
> [202.10..38] 16 310 ms 311 ms 310 ms
> as2.cre1.ade.connect.com.au [202.10.0.225] 17 320
> ms 321 ms 310 ms pos1-0.bdr2.ade.connect.com.au
> [202.10.4.86] 18 320 ms 311 ms 320 ms fastethernet0-
> 0.cor3.ade.connect.com.au
> [203.63.
> 113.67]19 320 ms 321 ms 330 ms ix140944-
> 1.gw.connect.com.au [210.8.6.237] 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.
"Chris" <chrismcreynolds@hotmail.com> wrote in message news:<40eaeba8$0$62163$812600b3@news.nntpaccess.com>...
> It is a denial of service attack!!!
>
> Or maybe there are lots of people all over the globe
> trying to access it all at once?
>
>
> "Sierraman" <riposa@sti.net> wrote in message news:Jt2dnZ-S7sTd13fdRVn-
> sA@sti.net...
> > Anyone else been having trouble getting into CN? I
> > couldn't get in all
> day.
> > Of course doing a trace shows quite a few hops and it
> > timed out before I could complete the trace. Quite a few
> > routers, might be a few bottlenecks along the way, but
> > it looks like I will have to wait till late night to
> read
> > up on the Giroess and that other race, ah... the one
> > with Lance in it.
>
> Giri? Italian tours? Tours of Italy? Please not "Giroess",
> where did you get that? I thought it was some kind of
> network protocol I had not heard of until I realized what
> you were trying to say.
>
> >
> > Tracing route to cyclingnews.com [210.10.97.10] over a
> > maximum of 30 hops:
> >
[rest of traceroute snipped]
> > 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.
>
> I think that Cyclingnews should plan for these huge events
> (at least for the Tour!!!)
You think it's bad now? Heck, wait for the TTT, mountain top
finishes of La Mongie, Plateau de Beille, l'Alpe d'Huez ITT,
Besançon ITT and final stage. You'll see saturation then.
I think they should move the server off that Tandy 1200 Jeff
has trussed up with bailing wire and bubble gum. Maybe live
dangerously and move up to a 60 MHz Pentium based system.
"Richard Adams" <ackthpt@concentric.net> wrote in message
news:c2352af0.0407061537.df4bfd6@posting.google.com...
>>
> You think it's bad now? Heck, wait for the TTT, mountain
> top finishes of La Mongie, Plateau de Beille, l'Alpe
> d'Huez ITT, Besançon ITT and final stage. You'll see
> saturation then.
>
No, it was to do with our page construction, which we have
now made more efficient. I'm not saying there won't be any
problems, especially after our sysadmins decided to change
the servers in the middle of the Tour. Calm blue ocean.
> I think they should move the server off that Tandy 1200
> Jeff has trussed up with bailing wire and bubble gum.
> Maybe live dangerously and move up to a 60 MHz Pentium
> based system.
Way out of our budget. I'm going to unwrap the VIC 20 for
the really big stages. Actually in the not too distant
past, our server was a souped up 486(!) with a single ISDN
line as a pipe.
Jeff
Richard Adams wrote:
>> I think they should move the server off that Tandy 1200
>> Jeff has trussed up with bailing wire and bubble gum.
>> Maybe live dangerously and move up to a 60 MHz Pentium
>> based system.
Jeff Jones wrote:
> Way out of our budget. I'm going to unwrap the VIC 20 for
> the really big stages. Actually in the not too distant
> past, our server was a souped up 486(!) with a single ISDN
> line as a pipe.
You mean you haven't found an ethernet card for your
Sinclair ZX81 yet ?
"Donald Munro" <me@privacy.net> wrote in message
news:pan.2004.07.08.09.05.41.578038@privacy.net...
>
> You mean you haven't found an ethernet card for your
> Sinclair ZX81 yet ?
>
What's the ethernet? Is that like the Internet or something?
Jeff
On Thu, 8 Jul 2004 20:03:41 +1000, Jeff Jones wrote:
> What's the ethernet? Is that like the Internet or
> something?
No it's wireless internet, with packet routing through the
ether http://www.ietf.org/rfc/rfc1149.txt
"Ewoud Dronkert" <me@privacy.net> wrote in message
news:m77qe056ac2hvtfkjpir9ilpupmmhr21ni@4ax.com...
> On Thu, 8 Jul 2004 20:03:41 +1000, Jeff Jones wrote:
> > What's the ethernet? Is that like the Internet or
> > something?
>
> No it's wireless internet, with packet routing through the
> ether http://www.ietf.org/rfc/rfc1149.txt
We must look into these Avian carriers.
Ewoud Dronkert wrote:
>> No it's wireless internet, with packet routing through
>> the ether http://www.ietf.org/rfc/rfc1149.txt
Jeff Jones wrote:
> We must look into these Avian carriers.
Actually bongo drums form a much cleaner and more reliable
transport layer (see
http://eagle.auc.ca/%7edreid/index.html (http://eagle.auc.ca/~dreid/index.html)).
I wonder if they tried running SAMBA over bongo drums ?
Ewoud Dronkert <me@privacy.net> wrote in message news:<m77qe056ac2hvtfkjpir9ilpupmmhr21ni@4ax.com>...
> On Thu, 8 Jul 2004 20:03:41 +1000, Jeff Jones wrote:
> > What's the ethernet? Is that like the Internet or
> > something?
>
> No it's wireless internet, with packet routing through the
> ether http://www.ietf.org/rfc/rfc1149.txt
Not necessarily wireless, ethernet can be wire, fibre or
wireless (or probably even bucket brigade if you had enough
people to work out the protocol with.)
On 8 Jul 2004 08:41:43 -0700, Richard Adams wrote:
>Ewoud Dronkert <me@privacy.net> wrote:
>> On Thu, 8 Jul 2004 20:03:41 +1000, Jeff Jones wrote:
>> > What's the ethernet? Is that like the Internet or
>> > something?
>>
>> No it's wireless internet, with packet routing through
>> the ether http://www.ietf.org/rfc/rfc1149.txt
>
>Not necessarily wireless, ethernet can be wire, fibre or
>wireless (or probably even bucket brigade if you had enough
>people to work out the protocol with.)
Please click the link.
Automatic Translations (Powered by
):
vBulletin, Copyright ©2000-2009, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by
vBSEO 3.3.0
