BT mega slow last couple of days!! Anyone else?

Profiler wrote: »

Just tested it again and I'm now getting



Now I rang BT this afternoon and told them I knew that there was a problem country wide and the guy didn't deny it.

I've been promised a call back sometime in the next 48 hours so I'm expected to hear nothing from them.

I also told them there was a snowballs chance in hell that I was paying them for this month bearing in mind I've had at BEST dial up service since the 9th of Aug.

Yeah tried that, all you get is your line is fine.

Pings have gone back to 60-70 on boards.ie for me.
Like when i had my up to 7.6mb
but i'm on 3mb now, thought that woud sort it.
Looks like Eircom screwed us over. If only bt had more control.
Although it wasn't great before 9th of august either(once a month i'd get a bad ping) but now its daily but usually weekly.

Last night around 12:00 my connection dropped. Tried the usual, but nothing worked. Eventually figured out my router could not connect to the BT server to authenticate my username and p/w (ie it was offline). Was down till 2, then I just went to bed ^^

Hi!

It would be really interesting if people would keep posting their tracerts

Tracerts sometimes, can help identify where the problem occurs.

Obviously you should only run a tracert when the problem is happening and make sure that your line is good condition, like synching at the right speed and things like that.

For ex

This tracert

1 1 ms 1 ms 1 ms 192.168.1.2
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.

That’s totally unrelated and it seems like a router issue. Reset the router and try again, that should do the trick… your packets are not even reaching the BRAS.


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

1 1 ms 1 ms 1 ms 10.0.1.1
2 5 ms 2 ms 2 ms voyager.home [192.168.1.1]
3 20 ms 19 ms 19 ms bas503.cwt.esat.net [193.95.136.239]
4 23 ms 20 ms 18 ms vlan500.rt502.cwt.esat.net [193.95.136.125]
5 39 ms 90 ms 431 ms vlan52.rt001.cwt.esat.net [193.95.130.145]
6 74 ms 182 ms 70 ms ge1-0.core002.cwt.esat.net [193.95.129.2]
7 124 ms 35 ms 259 ms pos2-0.br002.ldn.esat.net [193.95.131.50]
8 422 ms 45 ms 297 ms bbc-gw1-linx.prt0.thdoe.bbc.co.uk [195.66.226.10
3]
9 92 ms * 60 ms 212.58.238.133
10 61 ms 61 ms 57 ms te12-1.hsw0.cwwtf.bbc.co.uk [212.58.239.222]
11 60 ms 58 ms 59 ms www.bbc.co.uk [212.58.253.67]

Trace complete.

This one is a bit confusing as you are using some sort of router between the Voyager and your computer (probably a wireless access point). If you look closely the first thing you notice is that the hop between 1 and 2 takes 5 ms, 2 ms, 2 ms where it should be 1 ms. This would indicate that the first part of the problem happens between the access point (or whatever that is) and the voyager. There is some high latency on hops 5 to 7 but it will be better if you connect the computer directly to the voyager to get a much clearer picture.

Another

Tracing route to wwww.bbc.co.uk [208.69.34.132]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.1.1
2 21 ms 24 ms 24 ms bas508.cwt.esat.net [193.95.136.245]
3 24 ms 22 ms 25 ms vlan500.rt502.cwt.esat.net [193.95.136.125]
4 444 ms 412 ms 360 ms vlan54.rt002.cwt.esat-x.com [193.95.130.161]
5 23 ms 25 ms 24 ms ge1-0.core001.cwt.esat.net [193.95.129.17]
6 78 ms 79 ms 80 ms pos2-0.br001.ldn.esat.net [193.95.131.14]
7 37 ms * 39 ms 195.66.224.185
8 39 ms 39 ms 39 ms te3-1.mpd01.lon01.atlas.cogentco.com [130.117.3.
225]
9 85 ms 79 ms 64 ms opendns.demarc.cogentco.com [149.6.146.158]
10 59 ms 59 ms 58 ms hit-nxdomain.opendns.com [208.69.34.132]

Trace complete.

This tracert is a perfect example… and it seems to address a problem with vlan500-vlan54… or at least high latency

I have seen that some people have come to the conclusion that the problem happens when you get an ip 78.16.x.x. It could be possible but unfortunately the ip range 78.16.x.x probably does not belong to a single BRAS, that’s why tracerts are so important. A tracert will show the exact route…

Bare in mind that a high response doesn’t necessarily mean a problem as normally, network admin will set up routers/switches to consider ICMPs request as low priority, but sometimes it gives a good view of the situation…

There is no harm in trying!

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

  1     1 ms     1 ms    <1 ms  192.168.0.1
  2    16 ms    16 ms    16 ms  bas508.cwt.esat.net [193.95.136.245]
  3    16 ms    15 ms    16 ms  vlan500.rt501.cwt.esat.net [193.95.136.124]
  4   227 ms   655 ms   781 ms  vlan53.rt002.cwt.esat-x.com [193.95.130.153]
  5    34 ms    35 ms    35 ms  193.95.129.20
  6    55 ms    59 ms    57 ms  to-inex-dub-deg-gw.digiweb.ie [193.242.111.20]
  7    39 ms    40 ms    38 ms  ip-89-234-66-107.dedi.digiweb.ie [89.234.66.107]


Trace complete.

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

  1     1 ms    <1 ms    <1 ms  192.168.0.1
  2    16 ms    15 ms    15 ms  bas508.cwt.esat.net [193.95.136.245]
  3    16 ms    16 ms    17 ms  vlan501.rt501.cwt.esat.net [193.95.137.124]
  4    17 ms    17 ms    15 ms  vlan51.rt001.cwt.esat.net [193.95.130.137]
  5    16 ms    17 ms    16 ms  ge1-0.core002.cwt.esat.net [193.95.129.2]
  6    32 ms    32 ms    33 ms  pos2-0.br002.ldn.esat.net [193.95.131.50]
  7    33 ms    33 ms    33 ms  bbc-gw1-linx.prt0.thdoe.bbc.co.uk [195.66.226.10
3]
  8    55 ms    54 ms    53 ms  212.58.238.149
  9    34 ms    33 ms    33 ms  212.58.239.62
 10    34 ms    33 ms    34 ms  www-vip.telhc.bbc.co.uk [212.58.251.195]

Trace complete.

tried ip 76. and 192. both are bad.

does seem to be like you said bohrio

4 540 ms 763 ms 749 ms vlan53.rt002.cwt.esat-x.com [193.95.130.153]
4/5 times its like that

if you you dont get the vlan53.rt002.cwt.esat-x.com [193.95.130.153] it seems ok?

No ip i get is perfect. a 78 is good then bad, same with 192 and 202...

sometimes i get a 1mb download and others 2.6mb once it went to 2.7 but it wasn't stable.

my previous max was 2.66

pings jump from 40-140 when they should be 25-45

switched to pppoe, i've always used pppoa but pppoe seems stable. not as good as it was but hey.

PPPOE 212


PPPOA 78


PPPOA 213


PPPOE 78 was bad as well, it has to be that.

New tracert with PPPoa 213

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

1 1 ms 1 ms <1 ms 192.168.0.1
2 27 ms 25 ms 25 ms bas001.bmt.esat.net [193.95.142.242]
3 26 ms 24 ms 24 ms vlan103.rt002.bmt.esat.net [193.95.142.1]
4 24 ms 25 ms 23 ms ge1-0.core001.bmt.esat.net [193.95.140.17]
5 25 ms 24 ms 24 ms pos3-0.core001.cwt.esat.net [193.95.131.41]
6 25 ms 25 ms 29 ms ge0-0.br001.cwt.esat.net [193.95.129.4]
7 25 ms 25 ms 27 ms to-inex-dub-deg-gw.digiweb.ie [193.242.111.20]
8 28 ms 25 ms 27 ms ip-89-234-66-107.dedi.digiweb.ie [89.234.66.107]


Trace complete.

EDIT:

PPPOA is still the best after testing, as long as i dont get a 78 ip, its the same with pppoe.
PPPOA gives me more speed though and lower pings.

Vunderground wrote: »

Hi
I've posted my trace figures above, but don't have a clue how to interpret them. Could somebody please explain it. I've learned lots from this forum so many thanks again to those who have helped in the past

btw I understand the speed test info its the tracelet one I don't get.

Traceroute is often used for network troubleshooting. By showing a list of routers traversed, it allows the user to identify the path taken to reach a particular destination on the network. This can help identify routing problems or firewalls that may be blocking access to a site. Traceroute is also used by penetration testers to gather information about network infrastructure and IP ranges around a given host. It can also be used when downloading data, and if there are multiple mirrors available for the same piece of data, one can trace each mirror to get a good idea of which mirror would be the fastest to use.

Profiler wrote: »

boopolo wrote:

OK. They Have Finally Admitted What The Problem Is

The problem is directly related to the countrywide upgrade last month
It is not just confined to BT
It is with the integration of BT (and UTV etc) into the Eircom
There are several teams from internet providers and Eircom working round the clock changing and testing
It is not helped by the fact that the Eircom system is not the same as say the Cisco system of BT

They do not have a date they expect this to be sorted out

I take it you got this admission over the phone.

I wonder if they will post that on their website, I mean what price a wee bit of consideration for their customers :rolleyes:

I've been on hold now try to get through for over 30mins... oh and if they they "encourage" me to use their automated call back service one more time I swear I'm going to go radio rental :mad:

(edit - The ****ers just cut me off, their hold music ended and I heard about a second of what sounds like a call centre (more than one voice and the odd keyboard sound) and then they hung up AAAGGGGGGGHHHHHHHHHHHHH

Yeps Profiler.
Only got the information after getting angry and asked for a supervisor. Then I was put on hold for 5-10 mins.

When the guy came back, he told me all this.

I did suggest that they put it on their website. Obviously that would not be up to him.

Without him saying so,
I think that the lack of investment on infrastructure by Eircom over several years is now showing it's face

im with perlico and my connection has been unstable since my exchange was upgraded. im begining to lose hope that my connection will ever be fixed. are all isp's effected by this upgrade by eircom ? what sickens me is they did not even give me a upgrade im still on 2mb, but pings of over 150ms

im getting this on my 3mb line

Hi Jermey

I think you may have missed my follow on post:

boopolo wrote: »

OK. They Have Finally Admitted What The Problem Is

• The problem is directly related to the countrywide upgrade last month
• It is not just confined to BT
• It is with the integration of BT (and UTV etc) into the Eircom
• There are several teams from internet providers and Eircom working round the clock changing and testing
• It is not helped by the fact that the Eircom system is not the same as say the Cisco system of BT

They do not have a date they expect this to be sorted out

BT 3mb here and pings are atrocious this evening.

youtube has been bad on BT for a good while now. So I'm not holding my breath for that to be fixed. First time online in a while so I can't speak about any issues. Downloading some news shows over bittorrent now and I'm getting nice speeds on my 7.6MB connection

Hmm odd that i'm now back to full speed... Ping is still crap.




while the sun shins i'll be making hay!

tracert tests

P1erce wrote: »

I posted about this on boards.ie a few days ago:

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

Im in an even worse situation were my modem wont even get dsl sync between 7pm and 1am. I am on the option 3 package of BT (which is @ 3mbits max).

I tried calling last night and was on hold for 40 minutes, between 8:20 and 9:00pm I just hung up because I know everybody left at that time.

I called today and they said they would not address it remotely.

I said to the guy:

I have 2 modems a linksys + prestige 600
Happening on both
Roughly the same time each day

It works in the morning, just. At the weekend it worked but it was only syncing at 1905 while it was syncing at 3078 for the last 2 years!

I asked if they had any reported issues around "BARNA" and he was like, um... no. I also asked why I was on hold for 40 minutes last night and he said "we were very busy last night for whatever reason". HELLO!!!! I am experiencing issues between 7pm and midnight... join the dots!!! Maybe others are too!!!!

This is a total joke, im now spending 25euro a month more on 3 mobile broadband just to make sure I have a connection I am already paying 56euro a month for a landline!!!

Pierce

Hello there

This issue is unrelated. Your problem is just a line issue. Ask them to log this as intermittent service and ask them to check your telephone line.

The reason why you are disconnected is because your line can't handle it. This could be due to a fault on the line.

My advice is for you to check your internal setup. In most cases the problem is there.

This morning I was enjoying 740KB/sec but now I'm looking at 8.1... hmmm 31hr 20min till file download complete... grrr.

18mb connection in swords now at a lovely 100kbps download.

What the hell is going on?