- Joined
- Jan 26, 2002
- Messages
- 1,460
Today 1st February, the site has been extremely slow... 
Did anybody notice? From Europe it was almost unaccessible.
Did anybody notice? From Europe it was almost unaccessible.
Problems again with SR :(
- Thread starter Prof.Wizard
- Start date
Tea
0
I was on at much the same time, Prof. It was working OK for me. But quite often I have problems. I suspect that SR's server belongs to an interconnected chain of some kind that a lot of places share. (Don't know the fancy terms for this stuff - help me out James?) I say this because often when SR goes into mega-slow mode, a number of other US-based sites do the same. But not all. It's almost as if the US is hooked up to two or three enormous backbones and from time to time one or other of them gets a case of gridlock.
But yesterday must have been a trans-atlantic issue, I think. At least if SR was down, I didn't notice it, and I flicked in several times through the day.
But yesterday must have been a trans-atlantic issue, I think. At least if SR was down, I didn't notice it, and I flicked in several times through the day.
James
0
US traffic congestion usually comes from public peering points like MAE East (where most European ISPs meet the US ones).
If you (or your hosting provider) buy your connectivity from the only two companies with a real global IP network - Worldcom and Cable & Wireless - then service should be better because both have an enormous number of self-provisioned private peering points, which are much more reliable (and less congested) than the public ones.
However, the network managers need to be competant and get rid of traffic destined for other networks as soon as possible.
Apparently Telstra doesn't peer properly with Worldcom, for example. Burst.Net gets its connectivity from Worldcom, and Telstra has an interconnect with Worldcom here in Australia. However, Telstra seems to prefer to carry the traffic to the US before giving it to them (BTW, those interested in the cable discussion in "Big Pong" thread can see from the traceroute below that Telstra has abandoned Southern Cross in favour of the new AJC cable and HKT's capacity on TPC5 via a cable switch in Guam) :
If you (or your hosting provider) buy your connectivity from the only two companies with a real global IP network - Worldcom and Cable & Wireless - then service should be better because both have an enormous number of self-provisioned private peering points, which are much more reliable (and less congested) than the public ones.
However, the network managers need to be competant and get rid of traffic destined for other networks as soon as possible.
Apparently Telstra doesn't peer properly with Worldcom, for example. Burst.Net gets its connectivity from Worldcom, and Telstra has an interconnect with Worldcom here in Australia. However, Telstra seems to prefer to carry the traffic to the US before giving it to them (BTW, those interested in the cable discussion in "Big Pong" thread can see from the traceroute below that Telstra has abandoned Southern Cross in favour of the new AJC cable and HKT's capacity on TPC5 via a cable switch in Guam) :
Code:
C:\>tracert [url]www.burst.net[/url]
Tracing route to root.burst.net [66.96.192.201]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms gateway.jwalker.com [10.0.0.1]
2 28 ms 24 ms 23 ms 172.31.18.24
3 25 ms 26 ms 25 ms sydney1-atm.nsw.bigpond.net.au [61.9.192.145]
4 28 ms 25 ms 27 ms chw-matrix-r01.nsw.ipm.bigpond.com [203.18.76.8]
5 25 ms 27 ms 26 ms GigabitEthernet5-0-0.chw16.Sydney.telstra.net [39.130.7.9]
6 24 ms 23 ms 22 ms GigabitEthernet4-2.chw-core2.Sydney.telstra.net [203.50.6.205]
7 23 ms 22 ms 22 ms GigabitEthernet0-2.pad-core5.Sydney.telstra.net [203.50.6.202]
8 81 ms 86 ms 94 ms GigabitEthernet0-0.syd-core02.Sydney.net.reach.com [203.50.13.250]
9 246 ms 250 ms 247 ms pos4-3.wil-core01.net.reach.com [202.84.249.137]
10 254 ms 256 ms 255 ms 202.84.249.177
11 251 ms 255 ms 248 ms ge1-0.paix04.hkt.net [202.84.251.20]
12 276 ms 263 ms 267 ms Serial2-4.GW9.PAO1.ALTER.NET [157.130.194.73]
13 263 ms 259 ms 263 ms 172.ATM4-0.XR2.PAO1.ALTER.NET [152.63.52.78]
14 259 ms 263 ms 263 ms 0.so-0-0-0.XL2.PAO1.ALTER.NET [152.63.54.77]
15 259 ms 256 ms 259 ms 0.so-3-0-0.TL2.SAC1.ALTER.NET [152.63.54.10]
16 332 ms 327 ms 332 ms 0.so-6-0-0.TL2.DCA6.ALTER.NET [152.63.13.9]
17 321 ms 321 ms 324 ms 0.so-6-0-0.XL2.DCA6.ALTER.NET [152.63.38.74]
18 325 ms 344 ms 334 ms 0.so-0-0-0.XR2.DCA6.ALTER.NET [152.63.35.117]
19 327 ms 335 ms 325 ms 184.at-5-0-0.XR2.DCA1.ALTER.NET [152.63.33.29]
20 332 ms 332 ms 329 ms 194.ATM5-0.GW8.PHL1.ALTER.NET [152.63.39.213]
21 336 ms 340 ms 336 ms hostnoc-gw.customer.alter.net [157.130.223.162]
22 338 ms 344 ms 371 ms burst.net [66.96.192.201]
Trace complete.
Ouch! Compared to here, that tracert has some high pings
How is the site running now?
Code:
C:\Documents and Settings\Doug>cd ..
C:\Documents and Settings>cd ..
C:\>cd \
C:\>tracert [url]www.burst.net[/url]
Tracing route to root.burst.net [66.96.192.201]
over a maximum of 30 hops:
1 8 ms 8 ms 10 ms 10.195.8.1
2 7 ms 9 ms 10 ms rtr01.townisp.com [216.195.0.1]
3 8 ms 10 ms 7 ms 12.125.39.25
4 19 ms 9 ms 12 ms gbr2-p70.cb1ma.ip.att.net [12.123.40.102]
5 11 ms 10 ms 16 ms gbr3-p80.cb1ma.ip.att.net [12.122.5.61]
6 14 ms 12 ms 14 ms gbr4-p80.n54ny.ip.att.net [12.122.2.190]
7 15 ms 58 ms 12 ms gbr5-p70.n54ny.ip.att.net [12.122.5.109]
8 15 ms 19 ms 18 ms ar2-p310.cdknj.ip.att.net [12.123.192.9]
9 26 ms 29 ms 77 ms 12.119.155.82
10 30 ms 28 ms 26 ms burst.net [66.96.192.201]
Trace complete.How is the site running now?
James
0
Well, I am 11,000km away. That's pretty standard for connections to the US, although on Optus it would be about 70ms quicker because they use Southern Cross.
In today's lesson, kids, we learn why it's a bad idea to use AT&T as your IP carrier.
The tracert to SR goes much the same until here :
In today's lesson, kids, we learn why it's a bad idea to use AT&T as your IP carrier.
The tracert to SR goes much the same until here :
Code:
11 248 ms 253 ms 252 ms ge1-0.paix04.hkt.net [202.84.251.20]
12 260 ms 260 ms 262 ms Serial2-4.GW9.PAO1.ALTER.NET [157.130.194.73]
13 260 ms 262 ms 261 ms 172.ATM2-0.XR1.PAO1.ALTER.NET [152.63.52.74]
14 260 ms 266 ms 263 ms 0.so-0-0-0.XL1.PAO1.ALTER.NET [152.63.54.73]
15 261 ms 264 ms 262 ms 0.so-4-0-0.XL1.SAC1.ALTER.NET [152.63.53.245]
16 261 ms 259 ms 260 ms POS6-0.BR5.SAC1.ALTER.NET [152.63.52.225]
17 271 ms 273 ms 272 ms uu-gw.sffca.ip.att.net [192.205.32.125]
18 273 ms 279 ms 279 ms tbr1-p013302.sffca.ip.att.net [12.122.11.217]
19 314 ms 335 ms 332 ms tbr1-p013902.cgcil.ip.att.net [12.122.11.205]
20 330 ms 332 ms 330 ms tbr1-p013202.n54ny.ip.att.net [12.122.11.1]
21 320 ms 321 ms 323 ms gbr5-p30.n54ny.ip.att.net [12.122.11.10]
22 326 ms 327 ms 330 ms ar16-p310.n54ny.ip.att.net [12.123.1.177]
23 338 ms 335 ms 340 ms 12.124.176.18
24 338 ms 335 ms 339 ms 199.93.71.37
25 337 ms 340 ms 336 ms www1.storagereview.com [198.76.30.88]
Trace complete.
Tannin
0
I'm out at Belinda's amongst the gum trees right now - a poor line, but what do you guys make of this?
Code:
Tracing route to storageforum.net [66.96.239.250] over a maximum of 30 hops:
1 130 ms 131 ms 130 ms bal-as2-loop0.netconnect.net.au [203.87.45.254]
2 120 ms 131 ms 130 ms bal-rt1-fe0.1.netconnect.net.au [203.7.198.14]
3 131 ms 130 ms 130 ms 203.208.171.237
4 140 ms 150 ms 151 ms 202.160.245.81
5 461 ms 331 ms 420 ms 203.208.154.49
6 360 ms 661 ms 361 ms sl-gw8-sj-0-0.sprintlink.net [144.228.44.93]
7 361 ms 751 ms 360 ms sl-bb25-sj-6-0.sprintlink.net [144.232.3.113]
8 440 ms 591 ms 761 ms sl-bb21-stk-10-2.sprintlink.net [144.232.9.170]
9 361 ms 370 ms 882 ms sl-bb22-pen-10-1.sprintlink.net [144.232.18.93]
10 451 ms 791 ms 591 ms sl-bb26-pen-9-0.sprintlink.net [144.232.16.58]
11 1071 ms 1292 ms 1162 ms sl-gw27-pen-4-0-0.sprintlink.net [144.232.5.198]
12 671 ms 591 ms 971 ms sl-burst-2-0.sprintlink.net [144.232.191.26]
13 421 ms 480 ms 852 ms 6696239250.hostnoc.net [66.96.239.250]
Trace complete.James
0
Sprint sucks?
Pradeep
0
- Tracing route to storageforum.net [66.96.239.250]
over a maximum of 30 hops:
1 141 ms 140 ms 125 ms acc01-fred-lau.comindico.com.au [203.220.249.177]
2 125 ms 140 ms 235 ms 203.220.249.157
3 141 ms 141 ms 140 ms 203.194.1.177
4 157 ms 156 ms 172 ms atm9-0-0-48.cor01-kent-syd.comindico.com.au [203.194.1.113]
5 359 ms 406 ms 407 ms ge6-0.cor02-kent-syd.comindico.com.au [203.194.1.250]
6 297 ms 296 ms 329 ms pos2-0.155.cor01-alex-scn.comindico.net.au [203.194.0.18]
7 156 ms 157 ms 172 ms pos1-0.622.cor01-broo-scn.comindico.net.au [203.194.0.26]
8 297 ms 313 ms 312 ms pos1-0.155.cor01-west-sea.comindico.net [203.194.0.34]
9 296 ms 329 ms 296 ms ge2-0.1000.bdr02-west-sea.comindico.net [203.194.0.82]
10 297 ms 312 ms 313 ms p3-0.evrtwa1-cr1.bbnplanet.net [4.24.125.49]
11 297 ms 312 ms 313 ms p3-0.evrtwa1-br1.bbnplanet.net [4.24.5.101]
12 297 ms 312 ms 313 ms so-4-2-0.sttlwa1-hcr1.bbnplanet.net [4.24.4.77]
13 328 ms 313 ms 343 ms p0-0.snjpca1-br2.bbnplanet.net [4.24.4.178]
14 328 ms 313 ms 313 ms p1-0.snjpca1-cr6.bbnplanet.net [4.24.9.154]
15 328 ms 328 ms 328 ms p1-1.xsnjpca2-sprint.bbnplanet.net [4.24.238.142]
16 328 ms 328 ms 329 ms sl-bb22-stk-11-0.sprintlink.net [144.232.8.189]
17 390 ms 406 ms 407 ms sl-bb21-pen-10-1.sprintlink.net [144.232.9.130]
18 390 ms 390 ms 407 ms sl-bb25-pen-9-0.sprintlink.net [144.232.5.238]
19 390 ms 391 ms 406 ms sl-gw27-pen-0-0-0.sprintlink.net [144.232.5.194]
20 438 ms 406 ms 422 ms sl-burst-2-0.sprintlink.net [144.232.191.26]
21 422 ms 421 ms 422 ms 6696239250.hostnoc.net [66.96.239.250]
Maybe netconnect sucks?
