Anyone losing their NTHELL service for about 3 hours every evening

Snake Plisken

This is wrecking my head, ever day from about 3 to 7pm, my service dies outside of those hours its fine, I ran some traceroutes to rte.ie and amazon.com and this is the log is posted below, just wondering if its just an issue in West Dublin or elsewhere, I just don't have the time to waste ringing customer service, anyway if anyone has similar issues or can work out the issue from the tracers below please post

Snake

traceroute to www.rte.ie (89.207.56.94), 30 hops max, 40 byte packets
1 10.91.128.1 (10.91.128.1) 16.038 ms 50.992 ms 8.424 ms
2 089-101-162017.ntlworld.ie (89.101.162.17) 53.986 ms 9.457 ms *
3 dbln-t2core-a-ge-2-1-0-0.aorta.net (213.46.165.5) 31.606 ms * 23.157

ms
4 nl-ams-rc-02-pos-2-0.chellonetwork.com (213.46.160.17) 25.235 ms

18.071 ms *
5 * uk-lon01a-rd1-ge-7-0.aorta.net (213.46.174.33) 21.094 ms *
6 fr-par02a-rd1-pos-0-0.aorta.net (213.46.160.229) 60.611 ms 44.242 ms

68.008 ms
7 * * fr-par02a-ra1-10ge-0-0-0-0.aorta.net (213.46.163.86) 47.270 ms
8 * * ae0-117.par22.ip.tiscali.net (213.200.76.133) 111.563 ms
9 * so-0-0-0.dub10.ip.tiscali.net (213.200.82.74) 74.444 ms 76.316 ms
10 * * * Request timed out.
11 89.207.56.94 (89.207.56.94) 50.108 ms * 52.230 ms
Trace complete



traceroute to www.amazon.com (72.21.210.11), 30 hops max, 40 byte

packets
1 10.91.128.1 (10.91.128.1) 27.876 ms * 61.844 ms
2 089-101-162049.ntlworld.ie (89.101.162.49) 22.889 ms * 17.088 ms
3 213.46.165.53 (213.46.165.53) 40.620 ms 13.397 ms 18.668 ms
4 nl-ams-rc-01-pos-0-1.chellonetwork.com (213.46.160.13) 78.397 ms

37.786 ms *
5 nl-ams02a-ra1-ge-4-0-0-0.aorta.net (213.46.183.97) 78.224 ms * 76.487

ms
6 ams04a-ri1-ge-9-0.aorta.net (213.46.183.62) 66.096 ms * 39.007 ms
7 pos5-1.mpr2.ams1.nl.above.net (62.4.95.241) 72.957 ms 50.986 ms

37.343 ms
8 * so-0-0-0.mpr1.ams5.nl.above.net (64.125.27.182) 54.564 ms 58.808 ms
9 so-2-0-0.mpr1.lhr2.uk.above.net (64.125.27.177) 85.008 ms 48.043 ms

42.789 ms
10 so-0-1-0.mpr1.dca2.us.above.net (64.125.27.57) 113.769 ms 123.515 ms

130.991 ms
11 so-6-0-0.mpr1.iad1.us.above.net (64.125.28.126) 116.258 ms * 118.227

ms
12 so-3-0-0.mpr1.iad5.us.above.net (64.125.29.230) 135.594 ms 105.679

ms 137.967 ms
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * amazon-above.mpr1.iad5.us.mfnx.net.175.185.208.in-addr.arpa

(208.185.175.66) 106.432 ms !X *
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * amazon-above.mpr1.iad5.us.mfnx.net.175.185.208.in-addr.arpa

(208.185.175.66) 136.154 ms !X
24 * * * Request timed out.
25 amazon-above.mpr1.iad5.us.mfnx.net.175.185.208.in-addr.arpa

(208.185.175.66) 124.269 ms !X * *
26 * * * Request timed out.
27 * * * Request timed out.
28 * amazon-above.mpr1.iad5.us.mfnx.net.175.185.208.in-addr.arpa

(208.185.175.66) 282.163 ms !X *
29 * amazon-above.mpr1.iad5.us.mfnx.net.175.185.208.in-addr.arpa

(208.185.175.66) 117.848 ms !X *
30 * * * Request timed out.

Nuttzz

I was about to post a new thread about NTL, i find it very slow in recent weeks although thankfully not at a stop like you are having

Snake Plisken

Yeah its weird it comes right again after a couple of hours, and its not due to network load, if I take an example of Sunday afternoon very sunny not many people using their PC's at 4pm in the afternoon get the same issue, its like a server is taken down or doing a backup or something thus causing the drop in service.

Snake

anonymousjunkie

Yeah, as I posted in another thread I've been having pretty much the same problem in West Dublin. Mine downtime tended to be worse though, it would go down around lunchtime and not come back up until about 8 or 8.30, this even got progressively worse...coming back up at 10pm then 11pm then not at all. Its been down for about a week now. Strange thing is though...I have the black motorola modem and when I swapped it out with a friend for his smaller blue modem (no make on it as far as I can see apart from the NTL logo) it actually connected and works, while my modem works fine on his connection. Its as if the signal coming into the area is too weak for this black modem...I know nothing about modems btw just my little theory. Anyone know if this could be the case?

Snake Plisken

Well I have the Blue modem and not getting any joy, I'm tempted to call Customer Service but they'll put me in a bad mood and I just don't want that also I don't need an Engineer out as its obviously an issue at their end. Then again I will look for discount for lack of service off my next bill

Snake

Snake Plisken

Service was fine today during the bad hours, maybe somebody in NTL reads these threads

Snake

Cabaal

I'm in Waterford and have noticed it goes down an awful lot while I'm in work (between 9-5), doesn'ty affect me massively as I'm working but it was down all last weekend which I was abit annoyed about.

I loose ready and sync when it does go down,

garlad

My NTL BB was unavailable last night (checked it around 11:30).
Restarted modem, but the ready light just kept flashing

sprogman

It has been especially bad in Lucan over the last few weeks.
(Modem keeps trying to sync every 20 to 25 mins)
Has been ok since last wednesday.

christophicus

today the ready light was stble and everything but I could not conect to any sites.

Snake Plisken

sprogman wrote:

It has been especially bad in Lucan over the last few weeks.
(Modem keeps trying to sync every 20 to 25 mins)
Has been ok since last wednesday.

Yeah thats when it seemed to come back ok for me as well. Must have been a localized Lucan issue

Snake