Jump to content
SAU Community

Recommended Posts

I can't do the tracert's here at work for security reasons but I can tell you that its no faster at work (using a completely different ISP) than at home.

I'll do a few tracerts tonight and let you know.

Maybe it is the Internode servers? But why is everything else quicker?

Strange one this one.

  • Replies 56
  • Created
  • Last Reply

Top Posters In This Topic

it took 20+ seconds for this reply to load lol..

C:\>tracert www.skylinesaustralia.com

Tracing route to www.skylinesaustralia.com [209.62.28.18]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms my router [10.0.0.1]

2 116 ms 69 ms 69 ms loop0.lns2.bne1.internode.on.net [150.101.180.194]

3 69 ms 69 ms 69 ms gi0-3.cor2.bne1.internode.on.net [150.101.180.115]

4 266 ms 265 ms 265 ms pos4-2.bdr1.syd6.internode.on.net [203.16.212.13]

5 266 ms 265 ms 266 ms pos4-0.bdr1.lax1.internode.on.net [203.16.213.189]

6 344 ms 435 ms 475 ms ge-7-11.car3.LosAngeles1.Level3.net [4.71.32.61]

7 301 ms 302 ms 301 ms ae-1-53.edge3.LosAngeles1.Level3.net [4.68.102.84]

8 299 ms 298 ms 299 ms savvis-level3-10ge.LosAngeles1.Level3.net [4.68.110.94]

9 * 268 ms 348 ms cr1-pos-0-3-5-0-losangeles.savvis.net [208.172.44.105]

10 299 ms 299 ms 300 ms dcr2-so-3-3-0.dallas.savvis.net [204.70.192.246]

11 329 ms 327 ms 328 ms cr2-tengige0-7-5-0.dallas.savvis.net [204.70.196.29]

12 307 ms 307 ms 308 ms 208.172.139.134

13 344 ms 344 ms 337 ms gphou2-209-85-0-105.ev1servers.net [209.85.0.105]

14 333 ms 333 ms 333 ms www.skylinesaustralia.com [209.62.28.18]

Trace complete.

C:\Documents and Settings\Jonathan>

ok, and to www.disney.com :

C:\>tracert www.disney.com

Tracing route to disney.com [199.181.132.250]

over a maximum of 30 hops:

1 1 ms <1 ms <1 ms my router [10.0.0.1]

2 70 ms 70 ms 69 ms loop0.lns2.bne1.internode.on.net [150.101.180.194]

3 70 ms 69 ms 69 ms gi0-3.cor2.bne1.internode.on.net [150.101.180.115]

4 299 ms 299 ms 298 ms pos2-0.bdr1.syd6.internode.on.net [150.101.180.237]

5 266 ms 266 ms 265 ms pos4-0.bdr1.lax1.internode.on.net [203.16.213.189]

6 268 ms 268 ms 268 ms sl-st20-la-8-0-0.sprintlink.net [144.223.44.9]

7 264 ms 263 ms 264 ms sl-bb21-ana-13-0.sprintlink.net [144.232.20.66]

8 299 ms 298 ms 299 ms sl-bb23-ana-13-0.sprintlink.net [144.232.1.186]

9 277 ms 278 ms 277 ms sl-bb25-sj-9-0.sprintlink.net [144.232.20.159]

10 304 ms 304 ms 304 ms sl-bb22-sj-12-0.sprintlink.net [144.232.3.209]

11 322 ms 322 ms 322 ms sl-bb23-tac-14-0.sprintlink.net [144.232.20.9]

12 296 ms 295 ms 295 ms sl-bb22-tac-9-0.sprintlink.net [144.232.17.181]

13 300 ms 299 ms 299 ms sl-bb20-sea-0-0.sprintlink.net [144.232.9.150]

14 301 ms 299 ms 300 ms sl-gw11-sea-7-0.sprintlink.net [144.232.6.126]

15 327 ms 327 ms 325 ms sl-disne-3-0.sprintlink.net [144.232.219.254]

16 * * * Request timed out.

17 * * * Request timed out.

18 301 ms 301 ms 301 ms www.disney.com [199.181.132.250]

Trace complete.

hmmm...Where it jumps up to 250+ seems to be where it hits international.... So that response is probably ok.... except where it timesout at the end of disney.com

Only thing i could think of which could cause it on your end would maybe be the MTU settings, have you tried changing them?

ATM, we're hosting with EV1/theplanet, who are supposed to have one of the biggest backbones in the US, but it'll still be a tad delayed as the server's running at max load and because of the number of hops.

we as in SAU? Cause we're far from max load.

it's definitely not universal cause the site loads quite fast for me. using verizon at work and swiftel at home. even though my work connection is approx 10 times faster than home the load time of pages is not that much different unless they have lots of images.

we as in SAU? Cause we're far from max load.

hmm... wierd, we're not atm, but when I was logged in just before posting I could've sworn the load average was sitting on 3.4 or thereabouts. atho I could've misread that.

hmm... wierd, we're not atm, but when I was logged in just before posting I could've sworn the load average was sitting on 3.4 or thereabouts. atho I could've misread that.

Yeah it'll get up there occasionally when a cron or rsync is running (SAU is backed up daily to my local machine) but 3.4 is ok when you consider the CPU power available. Also MySQL uses a LOT of memory atm because I was very generous in the my.cnf.

Here is mine for you all, rarely have a drama for me.

1 2 ms 2 ms 1 ms *.*.*.*

2 21 ms 22 ms 21 ms [*.*.*.*]

3 34 ms 22 ms 21 ms gi1-2.mel-pipe-bdr1.ii.net [203.215.6.22]

4 35 ms 35 ms 57 ms gi0-15-1-3.syd-ult-core1.ii.net [203.215.20.12]

5 35 ms 35 ms 85 ms 202.139.19.33

6 192 ms 192 ms 198 ms 203.208.192.201

7 192 ms 192 ms 193 ms g11-0.core01.lax04.atlas.cogentco.com [154.54.12.221]

8 192 ms 205 ms 215 ms p0-0.core01.lax01.atlas.cogentco.com [154.54.6.241]

9 244 ms 191 ms 190 ms t3-1.mpd01.lax01.atlas.cogentco.com [154.54.2.102]

10 224 ms 224 ms 224 ms t2-2.mpd01.iah01.atlas.cogentco.com [154.54.3.37]

11 224 ms 230 ms 223 ms g2-0-0.core01.iah01.atlas.cogentco.com [154.54.2.241]

12 225 ms 240 ms 224 ms v3527.na22.b015619-0.iah01.atlas.cogentco.com [66.28.65.106]

13 224 ms 224 ms 224 ms everyones-internet.demarc.cogentco.com [38.99.215.154]

14 247 ms 225 ms 227 ms gphou2-209-85-0-105.ev1servers.net [209.85.0.105]

15 241 ms 224 ms 225 ms ev1s-209-62-28-18.ev1servers.net [209.62.28.18]

Trace complete.

Hi Christian,

Thank you for your support request with Internode.

Unfortunately a traceroute will not show very good results on the Internode network due to the way our MPLS network works. As such you need to run an extended ping test to the destination to determine latency issues.

Traceroute is only for determining the routing that packets take.

There is more information about our MPLS network available at the link below, however this is only viewable on an Internode connection.

http://www.internode.on.net/faq/internode-...-traceroute.php

Below is a ping from our servers which indicates a standard ping time of about 220ms, which is standard for connections to America.

> ping skylinesaustralia.com

PING skylinesaustralia.com (209.62.28.18): 56 data bytes

64 bytes from 209.62.28.18: icmp_seq=0 ttl=51 time=219.316 ms ...

64 bytes from 209.62.28.18: icmp_seq=74 ttl=51 time=219.219 ms

64 bytes from 209.62.28.18: icmp_seq=75 ttl=51 time=219.300 ms

64 bytes from 209.62.28.18: icmp_seq=76 ttl=51 time=217.861 ms ^C

--- skylinesaustralia.com ping statistics ---

77 packets transmitted, 77 packets received, 0% packet loss round-trip min/avg/max/stddev = 217.723/218.718/219.757/0.639 ms

I can browse the site fine, and do not notice any particularly bad connections. Should there still be issues, we would need more detail regarding the Internode customers that are having an issue before we can do any more troubleshooting.

If you have any further queries, please don't hesitate to contact us in the Helpdesk on 1300 788 233.

Kind regards,

  • 2 weeks later...

There would have been a few IPS driver errors towards the end of last week and over the weekend, but there shouldnt have been any this week. If there have been, can you tell me at approx what times?

As for the slowness, I am going to look into our DNS, but apart from that, I dont think there is anything I can do.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



  • Similar Content

  • Latest Posts

    • Yup. You can get creative and make a sort of "bracket" with cable ties. Put 2 around the sender with a third passing underneath them strapped down against the sender. Then that third one is able to be passed through some hole at right angles to the orientation of the sender. Or some variation on the theme. Yes.... ummm, with caveats? I mean, the sender is BSP and you would likely have AN stuff on the hose, so yes, there would be the adapter you mention. But the block end will either be 1/8 NPT if that thread is still OK in there, or you can drill and tap it out to 1/4 BSP or NPT and use appropriate adapter there. As it stands, your mention of 1/8 BSPT male seems... wrong for the 1/8 NPT female it has to go into. The hose will be better, because even with the bush, the mass of the sender will be "hanging" off a hard threaded connection and will add some stress/strain to that. It might fail in the future. The hose eliminates almost all such risk - but adds in several more threaded connections to leak from! It really should be tapered, but it looks very long in that photo with no taper visible. If you have it in hand you should be able to see if it tapered or not. There technically is no possibility of a mechanical seal with a parallel male in a parallel female, so it is hard to believe that it is parallel male, but weirder things have happened. Maybe it's meant to seat on some surface when screwed in on the original installation? Anyway, at that thread size, parallel in parallel, with tape and goop, will seal just fine.
    • How do you propose I cable tie this: To something securely? Is it really just a case of finding a couple of holes and ziptying it there so it never goes flying or starts dangling around, more or less? Then run a 1/8 BSP Female to [hose adapter of choice?/AN?] and then the opposing fitting at the bush-into-oil-block end? being the hose-into-realistically likely a 1/8 BSPT male) Is this going to provide any real benefit over using a stainless/steel 1/4 to 1/8 BSPT reducing bush? I am making the assumption the OEM sender is BSPT not BSPP/BSP
    • I fashioned a ramp out of a couple of pieces of 140x35 lumber, to get the bumper up slightly, and then one of these is what I use
    • I wouldn't worry about dissimilar metal corrosion, should you just buy/make a steel replacement. There will be thread tape and sealant compound between the metals. The few little spots where they touch each other will be deep inside the joint, unable to get wet. And the alloy block is much much larger than a small steel fitting, so there is plenty of "sacrificial" capacity there. Any bush you put in there will be dissimilar anyway. Either steel or brass. Maybe stainless. All of them are different to the other parts in the chain. But what I said above still applies.
    • You are all good then, I didn't realise the port was in a part you can (have!) remove. Just pull the broken part out, clean it and the threads should be fine. Yes, the whole point about remote mounting is it takes almost all of the vibration out via the flexible hose. You just need a convenient chassis point and a cable tie or 3.
×
×
  • Create New...