I'm located in Sydney, Australia and on my first hit to any Stack Exchange site after I haven't been active for a period of time (say, an hour or so), I can see FireFox waiting on cdn.sstatic.net
for a period between 3 and 5 seconds, but as high as 12 seconds.
Tracert to cdn.sstatic.net:
C:\Users\mark.henderson>tracert cdn.sstatic.net Tracing route to sstatic.stackexchange.netdna-cdn.com [69.174.57.102] over a maximum of 30 hops: 1 <1 ms * <1 ms tmg.enets.local [192.168.161.17] 2 19 ms 18 ms 19 ms lns20.syd6.internode.on.net [150.101.199.159] 3 19 ms 20 ms 18 ms te3-3.cor2.syd6.internode.on.net [150.101.195.9] 4 200 ms 200 ms 200 ms gi6-0-0-112.bdr1.syd7.internode.on.net [150.101. 120.229] 5 201 ms 200 ms 199 ms pos5-0.bdr1.sjc2.internode.on.net [203.16.213.16 2] 6 179 ms 191 ms 179 ms xe2-0.cr01.sjc01.mzima.net [206.223.116.62] 7 178 ms 176 ms 179 ms te0-1.cr1.lax1.us.packetexchange.net [69.174.120 .85] 8 209 ms 178 ms 177 ms 69.174.36.2 9 177 ms 178 ms 179 ms 69.174.57.102 Trace complete.
9 hops - that's gotta be one of the shortest trips to the US I've ever seen.
And
You are hitting the NetDNA Los Angeles Datacenter
Sorry guys, I don't wanna be rude, just wondering if there's been any updates on this issue? Is anyone else seeing the same behaviour? It's starting to get quite irritating, but of course if I'm the only one it's affecting then I'll start digging into our own network here.
This issue seems to be gone this week. I'll update this if it comes back.
I spoke too soon. The issue isn't gone, but it's now a lot less frequent and doesn't last quite as long. It now happens once or twice a day, and holds up for about 5 seconds.
Did you change something today (2011-07-13)? All of a sudden the site is back to its pre-CDN speed!
Nope, spoke to soon. Back to crappy waiting again.
Sorry to bring this up again, but it's recently got worse again. I was finally able to catch one in Firebug:
that was after waiting almost 30 seconds. Those requests that are still in progress never actually finish. I suspect maybe Firebug is not showing them correctly, because the site functions fine if you sit through the 16 second load time.
You are hitting the NetDNA Los Angeles Datacenter
(that page took about 20 seconds to load)
C:\Users\mark.henderson>tracert sstatic.stackexchange.netdna-cdn.com Tracing route to sstatic.stackexchange.netdna-cdn.com [67.201.31.70] over a maximum of 30 hops: 1 * * * Request timed out. 2 390 ms 354 ms 342 ms lns20.syd6.internode.on.net [150.101.199.159] 3 374 ms 271 ms 198 ms te3-3.cor2.syd6.internode.on.net [150.101.195.9] 4 382 ms 368 ms 506 ms gi3-1-0.bdr1.syd7.internode.on.net [150.101.120.225] 5 534 ms 543 ms 517 ms pos2-0.bdr1.sjc2.internode.on.net [203.16.213.50] 6 624 ms 610 ms 575 ms xe2-0.cr01.sjc01.mzima.net [206.223.116.62] 7 574 ms 538 ms 505 ms te0-1.cr1.lax1.us.packetexchange.net [69.174.120.85] 8 582 ms 521 ms 501 ms te2-0.cr2.lax1.us.packetexchange.net [69.174.120.142] 9 550 ms 529 ms 502 ms 69.174.36.2 10 448 ms 421 ms 424 ms 67.201.31.70 Trace complete. C:\Users\mark.henderson>tracert sstatic.net Tracing route to sstatic.net [64.34.119.12] over a maximum of 30 hops: 1 * * * Request timed out. 2 333 ms 344 ms 386 ms lns20.syd6.internode.on.net [150.101.199.159] 3 397 ms 350 ms 344 ms te3-3.cor2.syd6.internode.on.net [150.101.195.9] 4 617 ms 605 ms 572 ms gi3-1-0.bdr1.syd7.internode.on.net [150.101.120.225] 5 592 ms 533 ms 545 ms pos2-0.bdr1.sjc2.internode.on.net [203.16.213.50] 6 510 ms 461 ms 483 ms equinix-sjo.peer1.net [206.223.116.30] 7 477 ms 506 ms 536 ms 10ge.ten1-1.sj-mkp2-dis-1.peer1.net [216.187.89.101] 8 483 ms 536 ms 540 ms 10ge-ten1-3.la-600w-cor-1.peer1.net [216.187.88.130] 9 505 ms 513 ms 546 ms 10ge.ten1-1.la-600w-cor-2.peer1.net [216.187.88.146] 10 532 ms 530 ms 433 ms 10ge-ten1-2.dal-eqx-cor-1.peer1.net [216.187.124.122] 11 499 ms 419 ms 427 ms 10ge-ten1-1.dal-eqx-cor-2.peer1.net [216.187.124.134] 12 502 ms 512 ms 532 ms 10ge-ten2-1.atl-telx-cor-1.peer1.net [216.187.124.118] 13 467 ms 512 ms 507 ms 10ge-ten1-1.atl-101mar-cor-1.peer1.net [216.187.120.226] 14 506 ms 520 ms 493 ms 10ge.xe-1-0-0.wdc-eqx-dis-1.peer1.net [216.187.115.37] 15 489 ms 501 ms 501 ms 10ge.ten1-2.wdc-sp2-cor-1.peer1.net [216.187.115.234] 16 513 ms 506 ms 514 ms 216.187.120.254 17 482 ms 506 ms 503 ms 10ge.xe-2-0-0.nyc-telx-dis-1.peer1.net [216.187.115.221] 18 544 ms 521 ms 528 ms 10ge.xe-0-0-0.nyc-telx-dis-2.peer1.net [216.187.115.182] 19 491 ms 514 ms 519 ms oc48-po3-0.nyc-75bre-dis-1.peer1.net [216.187.115.134] 20 549 ms 505 ms 518 ms gwny01.stackoverflow.com [64.34.41.58] 21 559 ms 523 ms 520 ms stackoverflow.com [64.34.119.12] Trace complete.
tracert
to cdn.sstatic.net? And what datacenter does 67.201.31.56 tell you you're hitting?tracert
times. Is this happening on every request? E.g. if you request cdn.sstatic.net/js/full.js a few times, do you have those sucky values every time?cdn.sstatic.net
and stackoverflow has rendered without stylesheets three times today. I know SO puts a lot of effort in being as fast as possible so it's a waste that a CDN intermittently slows down requests to all SO sites...