NTL BB and Irish sites, what is the story?

REDZ

Hey Folks
My NTL BB has difficulty connecting to irish sites, aerlingus, irishrail,vodaphone, boards, iol etc, i get timed out connections and it seems slower.
no issues with anyother sites, just those related to ireland.
Forgive my ignorance but could this have something to do with how NTL connects with the rest of the Irish network,if so what can done about it, because it wrecks my head?
Redz

Tech Pete

Its fine for me in D16.

Have you rang them and reported this yet?

bk

When did this problem start happening, was it yesterday?

There was a thread yesterday about how NTL connects to Irish sites and they changed the routing to boards.ie, perhaps they are changing the routing for all Irish sites now:

http://www.boards.ie/vbulletin/showthread.php?t=262477

Basically, NTL doesn't peer for residential customers in the INEX (Internet Neutral Exchange) here in Ireland, instead all traffic destined for Ireland goes to the UK first, before returning to Ireland.

This is the opposite to most other Irish ISPs who peer in INEX and therefore have better latency to Irish servers. However the slightly higher latency on NTL certainly shouldn't cause you to time out.

What is weird is that NTL actually holds the Chair at INEX and have been members for years. It seems they use INEX for their business traffic, but not their residential traffic.

However yesterday when I posted about this, suddenly traces to boards.ie started been routed through INEX and the pings went from about 40ms to 14ms , however all other Irish sites remained the same as before, maybe they are changing that now.

tabatha

its also fine for me in dublin also

REDZ

Hey folks
that INEX thing is what i suspected, but if its only happening to me, then its prob my setup, i'm using firefox and xp pro.based in Dublin near Leeson street. Its been happening for a while,there are times when every site connected with Ireland timesout. ah well at least its working now i suppose.
thanks for your time
Redz

Tech Pete

Next time it goes down try to ping the site or access it by the IP address.
See if that works.

Lexmark.Printer

run a tracert to see where your problem is.

REDZ

cheers pete and lex
i will google a tracert

Lexmark.Printer

Go to Start->Run and type CMD hit return. This will pop up a MS-Dos command prompt dialog. Type in tracert www.boards.ie hit return

C:\>tracert www.boards.ie

Tracing route to www.boards.ie [82.195.136.36]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  my.firewall [192.168.0.254]
  2    34 ms    35 ms    44 ms  217.67.137.38
  3    38 ms   111 ms    48 ms  217.67.143.45
  4    48 ms    49 ms    40 ms  217.67.131.1
  5   114 ms    44 ms    40 ms  217.67.131.6
  6    39 ms    39 ms    45 ms  217.67.143.134
  7    45 ms    45 ms    44 ms  82.195.128.7
  8    38 ms    40 ms    44 ms  boards.ie [82.195.136.36]

Trace complete.

C:\>

You should be able to find the route your taking to access boards.ie and where it falls over. As you can see that is the route I take to boards.ie. NTL will take a different route than the above route.

If you have a problem you will see it and the location, then you can ring NTL and give them the info.

REDZ

thanks for the help lexmark

paulm17781

Oddly I time out when I try to tracert boards.ie? I can ping it and get low times but tracert doesn't want to work.

Lexmark.Printer

Working fine for me!

Here's my tracert using NTL Max

C:\>tracert www.boards.ie

Tracing route to www.boards.ie [82.195.136.36]
over a maximum of 30 hops:

  1    12 ms     7 ms     8 ms  10.135.31.254
  2    43 ms     8 ms     8 ms  dbln-cam-1a-ge02-100.inet.ntl.com [82.9.146.5]
  3     9 ms    40 ms     8 ms  dbln-t2core-a-ge-210-0.inet.ntl.com [82.9.145.5
  4     7 ms     7 ms     8 ms  dbln-bb-a-ge-230-0.inet.ntl.com [213.105.174.53
  5     9 ms    11 ms    36 ms  dbln-bb-b-ae0-0.inet.ntl.com [213.105.174.49]
  6    37 ms    29 ms    35 ms  inex-ic-1-pos000.inet.ntl.com [213.105.174.94]
  7    18 ms    10 ms    10 ms  fe-0-1-2.core1.dublin2.stisp.net [193.1.208.203
  8    11 ms    13 ms    12 ms  84.203.130.94
  9    11 ms    13 ms    11 ms  84.203.138.118
 10    11 ms    12 ms    11 ms  82.195.128.7
 11    18 ms    28 ms    12 ms  boards.ie [82.195.136.36]

Trace complete.
C:\>

and pinging boards.ie

C:\>ping www.boards.ie

Pinging www.boards.ie [82.195.136.36] with 32 bytes of data:

Reply from 82.195.136.36: bytes=32 time=12ms TTL=55
Reply from 82.195.136.36: bytes=32 time=11ms TTL=55
Reply from 82.195.136.36: bytes=32 time=12ms TTL=55
Reply from 82.195.136.36: bytes=32 time=13ms TTL=55

Ping statistics for 82.195.136.36:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 11ms, Maximum = 13ms, Average = 12ms

C:\>

causal

My pings to boards have dropped from ~35ms to 14ms since the change bk mentioned yesterday.
Pings to jolt.co.uk remain unchanged.

C:\>ping www.boards.ie

Pinging www.boards.ie [82.195.136.36] with 32 bytes of data:

Reply from 82.195.136.36: bytes=32 time=15ms TTL=54
Reply from 82.195.136.36: bytes=32 time=13ms TTL=54
Reply from 82.195.136.36: bytes=32 time=15ms TTL=54
Reply from 82.195.136.36: bytes=32 time=14ms TTL=54

Ping statistics for 82.195.136.36:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 13ms, Maximum = 15ms, Average = 14ms

C:\>ping www.jolt.co.uk

Pinging www.jolt.co.uk [82.133.85.65] with 32 bytes of data:

Reply from 82.133.85.65: bytes=32 time=29ms TTL=50
Reply from 82.133.85.65: bytes=32 time=29ms TTL=50
Reply from 82.133.85.65: bytes=32 time=29ms TTL=50
Reply from 82.133.85.65: bytes=32 time=29ms TTL=50

Ping statistics for 82.133.85.65:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 29ms, Maximum = 29ms, Average = 29ms

causal

REDZ

I got this when i couldn't connect to vodaphone, any insights please

Tracing route to www.vodafone.ie [213.233.129.155]
over a maximum of 30 hops:

1 10 ms 22 ms 51 ms 10.135.95.254
2 26 ms 10 ms 11 ms dbln-cam-1b-ge02-102.inet.ntl.com [82.9.147.13]

3 9 ms 60 ms 13 ms dbln-t2core-b-ge-210-0.inet.ntl.com [82.9.145.12
9]
4 10 ms 10 ms 8 ms dbln-bb-b-ge-230-0.inet.ntl.com [213.105.174.57]

5 50 ms 15 ms 16 ms man-bb-a-so-500-0.inet.ntl.com [213.105.174.45]

6 19 ms 16 ms 17 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
7 24 ms 24 ms 30 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]

8 22 ms 26 ms 28 ms gfd-bb-b-so-500-0.inet.ntl.com [213.105.172.130]

9 24 ms 28 ms 36 ms tele-ic-2-so-110-0.inet.ntl.com [62.253.185.74]

10 24 ms 27 ms 24 ms fa5-0-0.core1.thn.london.eircom.net [195.66.224.
79]
11 35 ms 85 ms 36 ms pos5-0-0.core2.adl.dublin.eircom.net [159.134.19
2.246]
12 37 ms 43 ms 35 ms fe1-0.edge3.adl.dublin.eircom.net [159.134.239.1
34]
13 39 ms 37 ms 38 ms vodafone-retail-ce-atm6-0-33.edge3.adl.dublin.ei
rcom.net [159.134.202.230]
14 36 ms 51 ms 44 ms fe-0-0.sf-7206-1.e-merge.ie [213.233.129.20]
15 51 ms 45 ms 41 ms 213.233.129.90
16 47 ms 40 ms 41 ms 213.233.129.77
17 39 ms 38 ms 41 ms 213.233.129.68
18 39 ms 68 ms 45 ms 213.233.129.77
19 54 ms 41 ms 38 ms 213.233.129.68
20 40 ms 38 ms 41 ms 213.233.129.77
21 39 ms 43 ms 42 ms 213.233.129.68
22 56 ms 41 ms 41 ms 213.233.129.77
23 54 ms 39 ms 47 ms 213.233.129.68
24 44 ms 38 ms 41 ms 213.233.129.77
25 41 ms 43 ms 41 ms 213.233.129.68
26 43 ms 42 ms 40 ms 213.233.129.77
27 48 ms 43 ms 41 ms 213.233.129.68
28 45 ms 48 ms 53 ms 213.233.129.77
29 40 ms 40 ms 42 ms 213.233.129.68
30 40 ms 87 ms 43 ms 213.233.129.77

Trace complete.