NTL laggg really bad anyone know wtf

CoolNitro

NTL laggg really bad anyone know wtf is wrong

illumin

dont know but its taking an age to display any sites, even google

Mr. Presentable

I'm in Tallaght, its working OK. However this morning I lost patience waiting for my on-line banking to load.

johntf008

Phew! I thought it was just me. It's awful, been like that for about an hour now...

MickFarr

Its working fine here in Lucan. Downloading at 175KBps all day

spockety

It's ****e for me at the moment, in Old Bawn Tallaght, ping times of 840ms to my first hop default gateway!

Infini

No problems in Dublin 7. Exceeding 140kb/s.

BeatFreak

B0rked in Templeogue too atm

Infini

Maybe they're doing a service on one of their exchanges. Should try again tomorrow. Also have you tried shutting the cable modem down and restarting it after 5 minutes.

spockety

Just called tech support. They are getting 'an awful lot of calls' about it, but guess f*****g what, no engineers work on this kind of thing after 6 pm, so it won't be getting looked at tonight!!!!!!!!!!!!!!!!!

I nearly had a nervous breakdown dealing with my connection and NTL about two years ago, and my blood is starting to boil again!! AGGGGGGGGGHHH

spockety

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

Request timed out.
Reply from 82.195.131.130: bytes=32 time=52ms TTL=48
Reply from 82.195.131.130: bytes=32 time=48ms TTL=48
Reply from 82.195.131.130: bytes=32 time=55ms TTL=48
Request timed out.
Reply from 82.195.131.130: bytes=32 time=47ms TTL=48
Request timed out.
Reply from 82.195.131.130: bytes=32 time=53ms TTL=48
Request timed out.
Request timed out.
Reply from 82.195.131.130: bytes=32 time=49ms TTL=48

Ping statistics for 82.195.131.130:
Packets: Sent = 11, Received = 6, Lost = 5 (45% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 55ms, Average = 50ms

TwoShedsJackson

Taking an eternity here in Crumlin too.

spongebob

Run Traceroutes to Jolt , Boards , BBc.co.Uk and Google.com and paste in here.

1. From sw Dub (affected)
2. From elesewhere (seemingly unaffected)

M

spockety

I'm getting a downstream SNR of only 27.. what are the rest of you getting?

kin9pin

Muck wrote:

Run Traceroutes to Jolt , Boards , BBc.co.Uk and Google.com and paste in here.

1. From sw Dub (affected)
2. From elesewhere (seemingly unaffected)

M

Tracing route to clarity.jolt.co.uk [195.149.21.11]
over a maximum of 30 hops:

1 11 ms 7 ms 7 ms 10.135.71.254
2 9 ms 8 ms 7 ms host82-9-147-13.not-set-yet.ntli.net [82.9.147.1
3]
3 8 ms 9 ms 10 ms host82-9-145-129.not-set-yet.ntli.net [82.9.145.
129]
4 8 ms 8 ms 10 ms dbln-bb-b-ge-230-0.inet.ntl.com [213.105.174.57]

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

6 14 ms 14 ms 15 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
7 21 ms 20 ms 21 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]

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

9 58 ms 59 ms 57 ms tele-ic-2-so-100-0.inet.ntl.com [62.253.185.74]

10 23 ms 23 ms 23 ms lon1-10.nildram.net [213.208.106.169]
11 24 ms 24 ms 23 ms lon1-9.nildram.net [195.149.20.130]
12 23 ms 24 ms 23 ms jolt-gw.nildram.net [195.149.20.126]
13 23 ms 23 ms 24 ms clarity.jolt.co.uk [195.149.21.11]

Trace complete.

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

1 11 ms 8 ms 7 ms 10.135.71.254
2 9 ms 7 ms 8 ms host82-9-147-13.not-set-yet.ntli.net [82.9.147.1
3]
3 9 ms 10 ms 9 ms host82-9-145-129.not-set-yet.ntli.net [82.9.145.
129]
4 8 ms 10 ms 8 ms dbln-bb-b-ge-230-0.inet.ntl.com [213.105.174.57]

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

6 16 ms 15 ms 20 ms lee-bb-b-so-700-0.inet.ntl.com [62.253.185.194]

7 17 ms 15 ms 16 ms lee-bb-a-ae0-0.inet.ntl.com [62.253.187.185]
8 21 ms 22 ms 21 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]

9 24 ms 23 ms 23 ms tele-ic-1-so-000-0.inet.ntl.com [62.253.185.82]

10 22 ms 23 ms 24 ms cr02.ldn01.pccwbtn.net [195.66.224.167]
11 34 ms 33 ms 34 ms 84.203.130.1
12 34 ms 33 ms 34 ms h365.stisp.net [84.203.138.14]
13 35 ms 39 ms 35 ms boards.ie [82.195.131.130]

Trace complete.



everything fine here

spockety

Tracing route to www.bbc.net.uk [212.58.224.125]
over a maximum of 30 hops:

1 43 ms 82 ms 44 ms 10.135.55.254
2 18 ms 58 ms 17 ms host82-9-146-9.not-set-yet.ntli.net [82.9.146.9]

3 20 ms 21 ms 20 ms host82-9-145-5.not-set-yet.ntli.net [82.9.145.5]

4 * 18 ms 27 ms dbln-bb-a-ge-230-0.inet.ntl.com [213.105.174.53]

5 23 ms * 21 ms ren-bb-b-so-100-0.inet.ntl.com [213.105.174.41]

6 * * 36 ms man-bb-a-so-600-0.inet.ntl.com [62.253.185.170]

7 28 ms 33 ms * man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
8 * * 179 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]

9 42 ms * 34 ms gfd-bb-b-so-500-0.inet.ntl.com [213.105.172.130]

10 74 ms 83 ms * tele-ic-2-so-100-0.inet.ntl.com [62.253.185.74]

11 48 ms 37 ms * 212.58.239.217
12 64 ms * 36 ms 212.58.238.129
13 * * 36 ms www25.thdo.bbc.co.uk [212.58.224.125]

Trace complete.

C:\Documents and Settings\Everybody>tracert www.google.com

Tracing route to www.google.akadns.net [66.102.9.99]
over a maximum of 30 hops:

1 475 ms 351 ms 460 ms 10.135.55.254
2 19 ms 21 ms 19 ms host82-9-146-9.not-set-yet.ntli.net [82.9.146.9]

3 24 ms * 19 ms host82-9-145-5.not-set-yet.ntli.net [82.9.145.5]

4 19 ms 18 ms * dbln-bb-a-ge-230-0.inet.ntl.com [213.105.174.53]

5 * 26 ms 28 ms ren-bb-b-so-100-0.inet.ntl.com [213.105.174.41]

6 27 ms * 32 ms man-bb-a-so-600-0.inet.ntl.com [62.253.185.170]

7 30 ms 29 ms * man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
8 * * * Request timed out.
9 37 ms * 35 ms bre-bb-b-so-100-0.inet.ntl.com [213.105.172.234]

10 * 42 ms * telc-ic-1-so-100-0.inet.ntl.com [62.253.188.117]

11 37 ms 38 ms * 195.66.226.125
12 65 ms * * 216.239.49.254
13 138 ms 143 ms 142 ms 64.233.174.42
14 * 140 ms 143 ms 64.233.174.14
15 * 68 ms * 66.102.9.99
16 * * 66 ms 66.102.9.99

Trace complete.

Canaboid

Old Bawn, Tallaght. 1.5mbit

1 <1 ms <1 ms <1 ms 192.168.10.1
2 148 ms 112 ms 95 ms 10.135.55.254
3 * * 23 ms host82-9-146-9.not-set-yet.ntli.net [82.9.146.9]

4 21 ms * * host82-9-145-5.not-set-yet.ntli.net [82.9.145.5]

5 * * 23 ms dbln-bb-a-ge-230-0.inet.ntl.com [213.105.174.53]

6 30 ms 29 ms 24 ms ren-bb-b-so-100-0.inet.ntl.com [213.105.174.41]

7 * 32 ms 38 ms man-bb-a-so-600-0.inet.ntl.com [62.253.185.170]

8 * 38 ms 83 ms man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
9 44 ms * 37 ms win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]

10 * * * Request timed out.
11 * 77 ms 76 ms tele-ic-2-so-100-0.inet.ntl.com [62.253.185.74]

12 86 ms 40 ms * lon1-10.nildram.net [213.208.106.169]
13 40 ms * 39 ms lon1-9.nildram.net [195.149.20.130]
14 * * * Request timed out.
15 * 40 ms * clarity.jolt.co.uk [195.149.21.11]
16 39 ms 48 ms * clarity.jolt.co.uk [195.149.21.11]
17 39 ms * * clarity.jolt.co.uk [195.149.21.11]
18 40 ms 40 ms 57 ms clarity.jolt.co.uk [195.149.21.11]

Trace complete.

Hmm.

spockety

canaboid, I take it your connection is pants at the moment too then?

I really can't believe that NTL don't have engineers on call for this type of thing, it's probably a dodgy network card in one of their routers that needs to be swapped out or something.

kida

same in lucan - uploads are full speed though - I am on the 1.5GB package

MartMax

download and upload speeds are prefectly fine here in IFSC, D1.

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

Reply from 82.195.131.130: bytes=32 time=34ms TTL=47
Reply from 82.195.131.130: bytes=32 time=36ms TTL=47
Reply from 82.195.131.130: bytes=32 time=34ms TTL=47
Reply from 82.195.131.130: bytes=32 time=36ms TTL=47

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

useeme

terrible in templeogue

ando

could be contention causing problems. Maybe a few of your neighbors are warezing. Afaik Coax broadband is shared amongst neighbours, not like DSL were you have a connection direct to exchange

RicardoSmith

Not very consistent here in D.15 These were run one after another.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

C:\>ping www.boards.ie

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

Reply from 82.195.131.130: bytes=32 time=64ms TTL=47
Reply from 82.195.131.130: bytes=32 time=77ms TTL=47
Reply from 82.195.131.130: bytes=32 time=82ms TTL=47
Reply from 82.195.131.130: bytes=32 time=77ms TTL=47

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

C:\>ping www.boards.ie

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

Reply from 82.195.131.130: bytes=32 time=66ms TTL=47
Reply from 82.195.131.130: bytes=32 time=196ms TTL=47
Reply from 82.195.131.130: bytes=32 time=233ms TTL=47
Reply from 82.195.131.130: bytes=32 time=48ms TTL=47

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

C:\>ping www.boards.ie

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

Reply from 82.195.131.130: bytes=32 time=62ms TTL=47
Reply from 82.195.131.130: bytes=32 time=98ms TTL=47
Reply from 82.195.131.130: bytes=32 time=58ms TTL=47
Reply from 82.195.131.130: bytes=32 time=79ms TTL=47

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

C:\>ping www.boards.ie

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

Reply from 82.195.131.130: bytes=32 time=151ms TTL=47
Reply from 82.195.131.130: bytes=32 time=66ms TTL=47
Reply from 82.195.131.130: bytes=32 time=60ms TTL=47
Reply from 82.195.131.130: bytes=32 time=161ms TTL=47

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

C:\>ping www.boards.ie

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

Reply from 82.195.131.130: bytes=32 time=161ms TTL=47
Reply from 82.195.131.130: bytes=32 time=68ms TTL=47
Reply from 82.195.131.130: bytes=32 time=46ms TTL=47
Reply from 82.195.131.130: bytes=32 time=48ms TTL=47

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

C:\>

spongebob

Looks like a borked concentrator/mux unit in SW Dub , can someone contact NTL and ask them to reset the affected units from the crap traces, reboots can clear these sometimes.

Try 00 44 845 6500121 for the NOC team .

M

mad m

cream crackered also,kimmage area.Wouldnt mind i emailed them over christmas about how my connection was ok around 2am and no connection during day but this only went on for a couple of days.An engineer called out to house yesterday wanting to have a look at it and they phoned me and left a message to say that one of there engineers called but no one was in.Wouldnt mind i didnt even know he was coming,they never said in email about a time.

Its a pity because they responded to my email very quickly

The_Conductor

I'm in Lucan village.
Getting over 95% packet loss.
Only up here at all through a GPRS cable connection- and I only have a 10Mb monthly account, so I'm not hanging around. I failed to manage to get through to Tech Support at all earlier- the number I have is 1800 924 424 If there is a different number can someone please PM me with it, and I'll sort it in work tomorrow. Bollocks to this.

seamus

Yeah bursty at best here in Lucan. Couldn't believe it when I saw AV updates downloaded at < 1KB/sec!

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

  1     1 ms     1 ms     1 ms  (none) [192.168.1.1]
  2    21 ms    30 ms    41 ms  10.135.47.254
  3    20 ms     *       26 ms  host82-9-146-9.not-set-yet.ntli.net [82.9.146.9]

  4    26 ms    19 ms    22 ms  host82-9-145-5.not-set-yet.ntli.net [82.9.145.5]

  5    21 ms    21 ms    20 ms  dbln-bb-a-ge-230-0.inet.ntl.com [213.105.174.53]

  6     *        *        *     Request timed out.
  7    40 ms    40 ms     *     man-bb-a-so-600-0.inet.ntl.com [62.253.185.170]

  8    40 ms    33 ms     *     lee-bb-b-so-700-0.inet.ntl.com [62.253.185.194]

  9     *      346 ms    35 ms  lee-bb-a-ae0-0.inet.ntl.com [62.253.187.185]
 10    48 ms    38 ms     *     pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]

 11    38 ms    40 ms    48 ms  tele-ic-1-so-000-0.inet.ntl.com [62.253.185.82]

 12     *       38 ms     *     cr02.ldn01.pccwbtn.net [195.66.224.167]
 13    48 ms    50 ms    49 ms  84.203.130.1
 14    55 ms    51 ms     *     h365.stisp.net [84.203.138.14]
 15     *       51 ms     *     boards.ie [82.195.131.130]
 16    47 ms    50 ms    50 ms  boards.ie [82.195.131.130]

Trace complete.

Tracing route to clarity.jolt.co.uk [195.149.21.11]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  (none) [192.168.1.1]
  2   426 ms   152 ms    50 ms  10.135.47.254
  3    18 ms    21 ms    19 ms  host82-9-146-9.not-set-yet.ntli.net [82.9.146.9]

  4    22 ms    20 ms    19 ms  host82-9-145-5.not-set-yet.ntli.net [82.9.145.5]

  5    21 ms    25 ms    22 ms  dbln-bb-a-ge-230-0.inet.ntl.com [213.105.174.53]

  6    23 ms     *       26 ms  ren-bb-b-so-100-0.inet.ntl.com [213.105.174.41]

  7    82 ms     *        *     man-bb-a-so-600-0.inet.ntl.com [62.253.185.170]

  8    31 ms    29 ms    27 ms  man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
  9    37 ms     *       39 ms  win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]

 10    38 ms    38 ms    36 ms  gfd-bb-b-so-500-0.inet.ntl.com [213.105.172.130]

 11    79 ms    82 ms    80 ms  tele-ic-2-so-100-0.inet.ntl.com [62.253.185.74]

 12    44 ms    38 ms    37 ms  lon1-10.nildram.net [213.208.106.169]
 13     *        *       40 ms  lon1-9.nildram.net [195.149.20.130]
 14     *       46 ms    38 ms  jolt-gw.nildram.net [195.149.20.126]
 15    38 ms    39 ms     *     clarity.jolt.co.uk [195.149.21.11]
 16    39 ms     *       38 ms  clarity.jolt.co.uk [195.149.21.11]

Trace complete.

Tracing route to www.bbc.net.uk [212.58.224.116]
over a maximum of 30 hops:

  1     1 ms     1 ms     2 ms  (none) [192.168.1.1]
  2    49 ms    21 ms    35 ms  10.135.47.254
  3    20 ms    21 ms    34 ms  host82-9-146-9.not-set-yet.ntli.net [82.9.146.9]

  4    20 ms    22 ms    23 ms  host82-9-145-5.not-set-yet.ntli.net [82.9.145.5]

  5    23 ms    20 ms    24 ms  dbln-bb-a-ge-230-0.inet.ntl.com [213.105.174.53]

  6    27 ms    25 ms    29 ms  ren-bb-b-so-100-0.inet.ntl.com [213.105.174.41]

  7    29 ms     *        *     man-bb-a-so-600-0.inet.ntl.com [62.253.185.170]

  8    33 ms     *        *     man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
  9    38 ms    38 ms    38 ms  win-bb-a-so-300-0.inet.ntl.com [62.253.185.138]

 10    38 ms    35 ms    38 ms  gfd-bb-b-so-500-0.inet.ntl.com [213.105.172.130]

 11    84 ms     *      139 ms  tele-ic-2-so-100-0.inet.ntl.com [62.253.185.74]

 12   174 ms    89 ms    38 ms  212.58.239.217
 13    40 ms    42 ms     *     212.58.238.129
 14    39 ms     *       43 ms  www16.thdo.bbc.co.uk [212.58.224.116]

Trace complete.

Tracing route to www.google.akadns.net [66.102.11.104]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  (none) [192.168.1.1]
  2    86 ms    29 ms    36 ms  10.135.47.254
  3    21 ms    26 ms    21 ms  host82-9-146-9.not-set-yet.ntli.net [82.9.146.9]

  4    22 ms    22 ms    19 ms  host82-9-145-5.not-set-yet.ntli.net [82.9.145.5]

  5    27 ms    26 ms    21 ms  dbln-bb-a-ge-230-0.inet.ntl.com [213.105.174.53]

  6    25 ms     *        *     ren-bb-b-so-100-0.inet.ntl.com [213.105.174.41]

  7    33 ms     *        *     man-bb-a-so-600-0.inet.ntl.com [62.253.185.170]

  8     *       31 ms     *     man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
  9     *        *        *     Request timed out.
 10    37 ms    39 ms     *     bre-bb-b-so-100-0.inet.ntl.com [213.105.172.234]

 11    38 ms    41 ms     *     telc-ic-1-so-210-0.inet.ntl.com [62.253.188.121]

 12     *       39 ms    38 ms  195.66.226.125
 13    68 ms     *       68 ms  216.239.49.254
 14    67 ms    71 ms    66 ms  216.239.48.50
 15    56 ms     *       59 ms  216.239.49.62
 16    60 ms    59 ms    57 ms  66.102.11.104

Trace complete.

Good excuse to go to bed early.

The_Conductor

Muck wrote:

Looks like a borked concentrator/mux unit in SW Dub , can someone contact NTL and ask them to reset the affected units from the crap traces, reboots can clear these sometimes.

Try 00 44 845 6500121 for the NOC team .

M

They are blocked at the UK end from accessing anything other than our billing and customer service info- and unable to call the Dublin team after 8PM...... wonderful......

The_Conductor

Code:
Tracing route to www.ntlworld.com [62.253.162.30]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms (none) [192.168.1.1]
2 986 ms 729 ms 1136 ms 10.135.47.254
3 * * 45 ms host82-9-146-9.not-set-yet.ntli.net [82.9.146.9]

4 42 ms 32 ms 11 ms host82-9-145-5.not-set-yet.ntli.net [82.9.145.5]

5 35 ms 32 ms 24 ms dbln-bb-a-ge-230-0.inet.ntl.com [213.105.174.53]

6 44 ms * * ren-bb-b-so-100-0.inet.ntl.com [213.105.174.41]

7 38 ms * * man-bb-a-so-600-0.inet.ntl.com [62.253.185.170]

8 * 41 ms * man-bb-b-ae0-0.inet.ntl.com [62.253.187.178]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12

(It hung here for 10 minutes without managing to complete the trace).
I see from the route that its almost identical to all the others.

I give up. I'm going to bed.

Eldarin

lads can we bare in mind that when it comes to ping rates and the likes on a cable modem your going to get a crap rate. totally unavoidable. with regards to physical download rates in the areas that NTL is available in your going to get anyone with a bit of common sense using their service as its the best Ireland is offering. So your bound to get some kinds of lag.

I have it in Saggart (Tallaght) an its bang on, however there are three pcs running of the one connection and one of them is constantly downloading something so on that note I can get a bad connection speed but thats understandable.

Infini

You said you're in Lucan. Maybe that storm the other day fecked up exchange.

Mantel

traceroute to www.boards.ie (82.195.131.130), 30 hops max, 38 byte packets
1 10.135.63.254 (10.135.63.254) 473.458 ms 279.061 ms 169.076 ms

traceroute to www.google.akadns.net (66.102.9.104), 30 hops max, 38 byte packets
1 10.135.63.254 (10.135.63.254) 156.732 ms 228.781 ms 164.923 ms

traceroute to clarity.jolt.co.uk (195.149.21.11), 30 hops max, 38 byte packets
1 10.135.63.254 (10.135.63.254) 257.961 ms 209.104 ms 185.082 ms

--- clarity.jolt.co.uk ping statistics ---
21 packets transmitted, 18 packets received, 14% packet loss
round-trip min/avg/max = 32.8/40.3/54.5 ms


*shakes fist at NTL*

I'm getting withdrawl symptoms now.

In Walkinstown, greenhills area.

seamus

Eldarin wrote:

lads can we bare in mind that when it comes to ping rates and the likes on a cable modem your going to get a crap rate. totally unavoidable.

Why? You don't expect massive packet loss. Anything above 25% loss (sustained) is completely disgraceful.

with regards to physical download rates in the areas that NTL is available in your going to get anyone with a bit of common sense using their service as its the best Ireland is offering. So your bound to get some kinds of lag.

That'd be a fair comment if it was always like this. But it's not. I've had it four months now and this is the first time I've had anything but perfect rates. Note that I'm not actually complaining, but if this keeps up I will be since I pay for the service.

Infini

I'm on ntl but i've never had any problems with packet loss.

The_Conductor

Infini wrote:

I'm on ntl but i've never had any problems with packet loss.

Eldarin and Infini- we are not moaning about about the general service provided by NTL- we are moaning about specific problems yesterday and today, that have not been resolved as yet. I run 4 PCs off the modem, through a 3Com office connect router- and normally have full 100kbps on all ports (and if I'm feeling greedy often plug a gig connection directly into the modem and get full connection speed too).

I agree with the statement that NTLs broadband service is about as good as anyone is going to get in Ireland.
Those of us complaining here are not bitching about the service in general- which is brilliant, having had gone through every possible offering that Eircom and Esat-BT have on offer.
What we are complaining about is the fact that the service in large tracts of Dublin failed yesterday, and none of us succeeded in resolving the problem.

In general my NTL connection is brilliant- yesterday evening (and this morning) I was getting packet loss in excess of 90%, and downloads below 5kbps (i.e. GPRS on my mobile phone is approximately 9 times faster than my broadband at present). The only reason I can post here now, is because I'm in work.

The fact that there is no provision for out-of-hours support, particularly when most of us on the service are home users, who would most likely not be at home during the daytime, is a problem, encountered yesterday for the first time.

Wavey

Has any noticed if the problem has been fixed yet today?
Mine was awful lastnight aswell. - Knocklyon.

The_Conductor

Talking to them a few minutes ago.
Its not back, but they are working on it.
Unwilling to give an eta on when it can be expected back.

S.

wideband

smccarrick wrote:

Eldarin and Infini- we are not moaning about about the general service provided by NTL- we are moaning about specific problems yesterday and today, that have not been resolved as yet. I run 4 PCs off the modem, through a 3Com office connect router- and normally have full 100kbps on all ports (and if I'm feeling greedy often plug a gig connection directly into the modem and get full connection speed too).

I agree with the statement that NTLs broadband service is about as good as anyone is going to get in Ireland.
Those of us complaining here are not bitching about the service in general- which is brilliant, having had gone through every possible offering that Eircom and Esat-BT have on offer.
What we are complaining about is the fact that the service in large tracts of Dublin failed yesterday, and none of us succeeded in resolving the problem.

In general my NTL connection is brilliant- yesterday evening (and this morning) I was getting packet loss in excess of 90%, and downloads below 5kbps (i.e. GPRS on my mobile phone is approximately 9 times faster than my broadband at present). The only reason I can post here now, is because I'm in work.

The fact that there is no provision for out-of-hours support, particularly when most of us on the service are home users, who would most likely not be at home during the daytime, is a problem, encountered yesterday for the first time.

very well said, echoing my feelings exactly.

spockety

Yes they just called me, expect it to be resolved by early afternoon.

To all the people saying that it could be a contention issue, or that you 'expect' to get crap ping rates with cable modems, with all due respect, you're not correct.

I've had cable for over 3 years now, and last night and today was the first time I've had serious problems in 2 years (the problem 2 years ago was absolutely dreadful and took 6 months to resolve, say no more). ANY packet loss at all is completely and totally unacceptable. There is no acceptable reason for any packet loss, no matter what type of network it is (be it cable, DSL, ethernet etc). My cable connection runs with ping times of less than 20ms to the first 2 hops quite consistently, and with 0% packet loss. If this changes for any reason, there is something wrong. Once you get even 2% of packets getting lost, your service is interrupted to a degree where it becomes a pain in the ass to use (anyone who uses ssh or gaming will understand why).

NTL's cable service is nowhere near reaching a threshold where contention becomes an issue. It's true that the connection is 'shared', but ALL internet connections are 'shared' at some point along the line, it makes no difference if that sharing happens on your street, or in an ISP datacentre, what does matter is how fat the pipe is and how thin each connection is. Cable pipes are well fat enough in each localised area to cope with the number of users NTL have.

Eldarin

my Apologies guys i didn't realize that the post was referring to a problem that just started yesterday or the day before. myself i'm having absolutely no difficulty with my 1.5meg connection. I downloaded Chronicles of riddick from torrentspy.com last night without any problems. somewhere in the region of 120k transfers the whole time pretty much, again I as I said earlier thats in Saggart not far from Tallaght. hopefully it doesn't work its way out to me as i'd probably top my self without internet.

CoolNitro

its fixed well mine is thay must have taken down my network area cos my moden could not even connect with NTL from 3am to 11.30 I was starting to think it was my modem.

anyone know what it was??

seamus

CoolNitro wrote:

its fixed well mine is thay must have taken down my network area cos my moden could not even connect with NTL from 3am to 11.30 I was starting to think it was my modem.

anyone know what it was??

Yeah my service just went dead around 11 last night. I went to bed. I assume Muck was right in his diagnosis, and they rebooted some things.

talla

yeh its back up now, was very bad from 5 onwards yesterday and went completely dead from 11pm onwards till a few minutes ago. I'm in the Old Bawn area in Tallaght.

CoolNitro

it just crashed again then came back up lets hope it doen not continue this way

ballycragh tallaght area

PPC

Its still down in Templeogue it seems can't ssh into my server yet.
Unless the dns hasnt updated yet to match the ip

Infini

CoolNitro wrote:

its fixed well mine is thay must have taken down my network area cos my moden could not even connect with NTL from 3am to 11.30 I was starting to think it was my modem.

I experienced the same problem a while back but it came back online when I connected the computer to the modem using the USB cable instead of the Ethernet cable. Did you try that and did it work?

PiE

Infini wrote:

No problems in Dublin 7. Exceeding 140kb/s.

Sorry for off-topic, but where exactly in D7 are you?

CoolNitro

its fffed again here goes for another night without internet the lagg has started up again

The_Conductor

A lot better than last night, but still not back properly.
Packet loss now below 20%, and response times have improved.

10.135.47.254 still has high lag associated with it. (60-70 ms)

CuLT

i know that Knocklyon/Templeogue is getting an upgrade atm; where I live this area wasn't serviced by NTL broadband until last week.

(which means cable for me! hoorah!)

The_Conductor

Think I spoke too soon. Packet loss up about 60% now, and taking forever to load anything. Arrrrggghhhhhh