blueface tracert

dkane

When i do a tracert on sip.blueface.ie I am getting the following route:

217.173.97.177
217.173.97.109
pos11-0-pr1.LON.router.COLT.NET [212.74.64.18]
GigabitEthernet5-0.linx1.lon1.level3.net [195.66

so-1-3-0.gar2.London1.Level3.net [212.113.3.29]

ae-0-54.bbr2.London1.Level3.net [4.68.116.98]
so-2-0.hsa2.Dublin1.Level3.net [4.68.128.118]
213.242.106.14
hippo.blueface.ie [213.168.225.133]

As you can see it is going to London and back.

Is this normal? Does anyone else get a similar result?

ac00785

dkane wrote:

When i do a tracert on sip.blueface.ie I am getting the following route:

217.173.97.177
217.173.97.109
pos11-0-pr1.LON.router.COLT.NET [212.74.64.18]
GigabitEthernet5-0.linx1.lon1.level3.net [195.66

so-1-3-0.gar2.London1.Level3.net [212.113.3.29]

ae-0-54.bbr2.London1.Level3.net [4.68.116.98]
so-2-0.hsa2.Dublin1.Level3.net [4.68.128.118]
213.242.106.14
hippo.blueface.ie [213.168.225.133]

As you can see it is going to London and back.

Is this normal? Does anyone else get a similar result?

I get the following:

Tracing route to sip.blueface.ie [213.168.225.133]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.2.1
2 9 ms 7 ms 11 ms 10.26.135.254
3 13 ms 10 ms 11 ms dbln-cam-2b-ge02-100.inet.ntl.com [82.9.148.129]

4 29 ms 9 ms 12 ms dbln-t2core-b-ge-220-0.inet.ntl.com [82.9.145.14
5]
5 23 ms 12 ms 10 ms dbln-bb-b-ae1-0.inet.ntl.com [213.105.174.57]
6 12 ms 13 ms 10 ms dbln-bb-a-ae0-0.inet.ntl.com [213.105.174.50]
7 18 ms 32 ms 11 ms 213.242.106.37
8 23 ms 30 ms 28 ms so-6-0.hsa2.Dublin1.Level3.net [4.68.115.26]
9 31 ms 22 ms 22 ms 213.242.106.14
10 25 ms 23 ms 24 ms hippo.blueface.ie [213.168.225.133]

Think it depends on your ISP

dkane

Thanks for that ac00785

tis odd.
Anyone got any ideas? ac looks to be using ntl. Im on netsource DSL if that makes any differance

Yook

Thats what I got. LOL, maybe i should get blueface.

Tracing route to sip.blueface.ie [213.168.225.133]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 5 ms 3 ms 4 ms 213.168.230.1
3 5 ms 4 ms 3 ms 213.168.225.241
4 4 ms 4 ms 5 ms hippo.blueface.ie [213.168.225.133]

Trace complete.

jimmycrackcorm

Yook wrote:

Thats what I got. LOL, maybe i should get blueface.

Tracing route to sip.blueface.ie [213.168.225.133]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 5 ms 3 ms 4 ms 213.168.230.1
3 5 ms 4 ms 3 ms 213.168.225.241
4 4 ms 4 ms 5 ms hippo.blueface.ie [213.168.225.133]

Trace complete.

How are you getting only 5ms ping and 3 hops?

Yook

jimmycrackcorm wrote:

How are you getting only 5ms ping and 3 hops?

I'm with icecomms. I get that to most irish backbone servers. Unfortunately, its wireless which means the ping from here to the base station is ALWAYS terrible.

unkel

ac00785 wrote:

I get the following:

Mine's very similar to that

bhickey

dkane wrote:

As you can see it is going to London and back.

I think that might be related to your ISP and how they route their own traffic.

Blaster99

Blueface will allegedly get INEX connectivity in the near future which should sort out the Dublin->London->Dublin thing.

Smart's got INEX connectivity, as does Broadtalk. If you want to consider alternatives.

aaronc

Just so all the facts are known the reason INEX is often touted as being a superior way to route traffic is because an ISP is likely to have less congestion on their INEX link than they will on an internet link, this because INEX traffic costs an ISP a lot less than internet traffic. However assuming an ISP will never have capacity issues on INEX is wrong and there is currently one major ISP with exactly that problem.

A hop to London and back will typically introduce 20 to 30ms of latency which is going to be impercetible to just about any kind of traffic and certainly VoIP.

I'd agree that people should try out alternatives if quality is poor with one provider or another but just assuming an INEX connection path will improve things will not always be correct although in the majority of circumstances it should help.

Aaron
(caveat: I work for Blue Face)