Are you on the Ashbourne Exchange? Please help!

Steffano2002

Good evening,

Looking for some broadband subscribers on the Ashbourne Exchange.

I play Call of Duty 4 on PC and usually my ping to UK / Euro servers is around 50-60ms. For the past week however, my ping has been 95-125ms (on mutliple servers) and it fluctuates a lot (it's usually pretty steady)!

My connection has been perfect since May (when I connected) so I hope this is just a glitch!

Here are some ping tests / tracerts:

Pinging www.rte.ie.nsatc.net [89.207.56.140] with 32 bytes of data:

Reply from 89.207.56.140: bytes=32 time=79ms TTL=60
Reply from 89.207.56.140: bytes=32 time=79ms TTL=60
Reply from 89.207.56.140: bytes=32 time=82ms TTL=60
Reply from 89.207.56.140: bytes=32 time=78ms TTL=60
Reply from 89.207.56.140: bytes=32 time=78ms TTL=60
Reply from 89.207.56.140: bytes=32 time=83ms TTL=60
Reply from 89.207.56.140: bytes=32 time=81ms TTL=60
Reply from 89.207.56.140: bytes=32 time=103ms TTL=60
Reply from 89.207.56.140: bytes=32 time=86ms TTL=60
Reply from 89.207.56.140: bytes=32 time=84ms TTL=60
Reply from 89.207.56.140: bytes=32 time=75ms TTL=60
Reply from 89.207.56.140: bytes=32 time=81ms TTL=60
Reply from 89.207.56.140: bytes=32 time=86ms TTL=60
Reply from 89.207.56.140: bytes=32 time=92ms TTL=60
Reply from 89.207.56.140: bytes=32 time=100ms TTL=60
Reply from 89.207.56.140: bytes=32 time=91ms TTL=60
Reply from 89.207.56.140: bytes=32 time=90ms TTL=60
Reply from 89.207.56.140: bytes=32 time=75ms TTL=60
Reply from 89.207.56.140: bytes=32 time=73ms TTL=60
Reply from 89.207.56.140: bytes=32 time=65ms TTL=60

Ping statistics for 89.207.56.140:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 65ms, Maximum = 103ms, Average = 83ms

Tracing route to www.rte.ie.nsatc.net [89.207.56.140]
over a maximum of 30 hops:

  1    50 ms    99 ms    99 ms  smart.lan [192.168.1.1]
  2    75 ms     *       85 ms  ge0-1-0-100.core1.deg.dub.stisp.net [84.203.130.121]
  3    90 ms    94 ms    85 ms  ge0-1-0-100.core1.deg.dub.stisp.net [84.203.130.121]
  4    81 ms    79 ms     *     deg-gw-1.rte.ie [193.242.111.42]
  5    72 ms    65 ms    66 ms  www.rte.ie [89.207.56.140]

Trace complete.

Pinging 84.203.130.121 with 32 bytes of data:

Reply from 84.203.130.121: bytes=32 time=98ms TTL=63
Reply from 84.203.130.121: bytes=32 time=100ms TTL=63
Reply from 84.203.130.121: bytes=32 time=87ms TTL=63
Reply from 84.203.130.121: bytes=32 time=108ms TTL=63
Reply from 84.203.130.121: bytes=32 time=88ms TTL=63
Reply from 84.203.130.121: bytes=32 time=93ms TTL=63
Request timed out.
Reply from 84.203.130.121: bytes=32 time=127ms TTL=63
Reply from 84.203.130.121: bytes=32 time=92ms TTL=63
Reply from 84.203.130.121: bytes=32 time=100ms TTL=63
Reply from 84.203.130.121: bytes=32 time=96ms TTL=63
Reply from 84.203.130.121: bytes=32 time=92ms TTL=63
Reply from 84.203.130.121: bytes=32 time=96ms TTL=63
Reply from 84.203.130.121: bytes=32 time=86ms TTL=63
Reply from 84.203.130.121: bytes=32 time=83ms TTL=63
Reply from 84.203.130.121: bytes=32 time=84ms TTL=63
Reply from 84.203.130.121: bytes=32 time=89ms TTL=63
Reply from 84.203.130.121: bytes=32 time=96ms TTL=63
Reply from 84.203.130.121: bytes=32 time=89ms TTL=63
Reply from 84.203.130.121: bytes=32 time=105ms TTL=63

Ping statistics for 84.203.130.121:
    Packets: Sent = 20, Received = 19, Lost = 1 (5% loss),
Approximate round trip times in milli-seconds:
    Minimum = 83ms, Maximum = 127ms, Average = 95ms

These ping times aren't great at all... Can't get anything decent on second hop. Everything is 90ms minimum...

If you are on the Ashbourne Exchange could you please tell me who your provider is and could you please try the following commands in command prompt for me?

ping 213.186.54.82 -n 20
ping 89.207.56.140 -n 20
tracert 213.186.54.82:29100

Thank you in advance!

Xcellor

Steffano2002 wrote: »

Good evening,

Looking for some broadband subscribers on the Ashbourne Exchange.

I play Call of Duty 4 on PC and usually my ping to UK / Euro servers is around 50-60ms. For the past week however, my ping has been 95-125ms (on mutliple servers) and it fluctuates a lot (it's usually pretty steady)!

My connection has been perfect since May (when I connected) so I hope this is just a glitch!

Here are some ping tests / tracerts:

Pinging www.rte.ie.nsatc.net [89.207.56.140] with 32 bytes of data:

Reply from 89.207.56.140: bytes=32 time=79ms TTL=60
Reply from 89.207.56.140: bytes=32 time=79ms TTL=60
Reply from 89.207.56.140: bytes=32 time=82ms TTL=60
Reply from 89.207.56.140: bytes=32 time=78ms TTL=60
Reply from 89.207.56.140: bytes=32 time=78ms TTL=60
Reply from 89.207.56.140: bytes=32 time=83ms TTL=60
Reply from 89.207.56.140: bytes=32 time=81ms TTL=60
Reply from 89.207.56.140: bytes=32 time=103ms TTL=60
Reply from 89.207.56.140: bytes=32 time=86ms TTL=60
Reply from 89.207.56.140: bytes=32 time=84ms TTL=60
Reply from 89.207.56.140: bytes=32 time=75ms TTL=60
Reply from 89.207.56.140: bytes=32 time=81ms TTL=60
Reply from 89.207.56.140: bytes=32 time=86ms TTL=60
Reply from 89.207.56.140: bytes=32 time=92ms TTL=60
Reply from 89.207.56.140: bytes=32 time=100ms TTL=60
Reply from 89.207.56.140: bytes=32 time=91ms TTL=60
Reply from 89.207.56.140: bytes=32 time=90ms TTL=60
Reply from 89.207.56.140: bytes=32 time=75ms TTL=60
Reply from 89.207.56.140: bytes=32 time=73ms TTL=60
Reply from 89.207.56.140: bytes=32 time=65ms TTL=60

Ping statistics for 89.207.56.140:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 65ms, Maximum = 103ms, Average = 83ms

Tracing route to www.rte.ie.nsatc.net [89.207.56.140]
over a maximum of 30 hops:

  1    50 ms    99 ms    99 ms  smart.lan [192.168.1.1]
  2    75 ms     *       85 ms  ge0-1-0-100.core1.deg.dub.stisp.net [84.203.130.121]
  3    90 ms    94 ms    85 ms  ge0-1-0-100.core1.deg.dub.stisp.net [84.203.130.121]
  4    81 ms    79 ms     *     deg-gw-1.rte.ie [193.242.111.42]
  5    72 ms    65 ms    66 ms  www.rte.ie [89.207.56.140]

Trace complete.

Pinging 84.203.130.121 with 32 bytes of data:

Reply from 84.203.130.121: bytes=32 time=98ms TTL=63
Reply from 84.203.130.121: bytes=32 time=100ms TTL=63
Reply from 84.203.130.121: bytes=32 time=87ms TTL=63
Reply from 84.203.130.121: bytes=32 time=108ms TTL=63
Reply from 84.203.130.121: bytes=32 time=88ms TTL=63
Reply from 84.203.130.121: bytes=32 time=93ms TTL=63
Request timed out.
Reply from 84.203.130.121: bytes=32 time=127ms TTL=63
Reply from 84.203.130.121: bytes=32 time=92ms TTL=63
Reply from 84.203.130.121: bytes=32 time=100ms TTL=63
Reply from 84.203.130.121: bytes=32 time=96ms TTL=63
Reply from 84.203.130.121: bytes=32 time=92ms TTL=63
Reply from 84.203.130.121: bytes=32 time=96ms TTL=63
Reply from 84.203.130.121: bytes=32 time=86ms TTL=63
Reply from 84.203.130.121: bytes=32 time=83ms TTL=63
Reply from 84.203.130.121: bytes=32 time=84ms TTL=63
Reply from 84.203.130.121: bytes=32 time=89ms TTL=63
Reply from 84.203.130.121: bytes=32 time=96ms TTL=63
Reply from 84.203.130.121: bytes=32 time=89ms TTL=63
Reply from 84.203.130.121: bytes=32 time=105ms TTL=63

Ping statistics for 84.203.130.121:
    Packets: Sent = 20, Received = 19, Lost = 1 (5% loss),
Approximate round trip times in milli-seconds:
    Minimum = 83ms, Maximum = 127ms, Average = 95ms

These ping times aren't great at all... Can't get anything decent on second hop. Everything is 90ms minimum...

If you are on the Ashbourne Exchange could you please tell me who your provider is and could you please try the following commands in command prompt for me?

ping 213.186.54.82 -n 20
ping 89.207.56.140 -n 20
tracert 213.186.54.82:29100

Thank you in advance!

You are having the same problem that has plagued me for months with U.TV but I'm in the midlands. I think Eircom are doing upgrades. My area seems to be getting better...

Just complain to Eircom and give them a week. If they don't fix it phone up and lodge an official complaint. Log it with Comreg. Won't do much but will do more than just posting here.

Hopefully if enough people in your area complain something will be done.... Unfortunately not that many people really bother complaining so companies just get away with **** service. It's the Irish mentality... What more can we expect?? :rolleyes:

Steffano2002

Xcellor wrote: »

You are having the same problem that has plagued me for months with U.TV but I'm in the midlands. I think Eircom are doing upgrades. My area seems to be getting better...

Just complain to Eircom and give them a week. If they don't fix it phone up and lodge an official complaint. Log it with Comreg. Won't do much but will do more than just posting here.

Hopefully if enough people in your area complain something will be done.... Unfortunately not that many people really bother complaining so companies just get away with **** service. It's the Irish mentality... What more can we expect?? :rolleyes:

But I'm with SMART so I can't complain to Eircom. And my Broadband was perfect up to last week! The Ashbourne exchange has a good reputation so I don't think it needs upgrading... I have a 12MB connection and I get the full 12MB when I download (and my line can take up tp 24MB)!

Marlow

Xcellor wrote: »

Hopefully if enough people in your area complain something will be done.... Unfortunately not that many people really bother complaining so companies just get away with **** service. It's the Irish mentality... What more can we expect?? :rolleyes:

Actually, I need to correct you here. You bought a contended service. When the contention kicks in, your latency goes up. That's the one of the downsides of contention.

If you want a guaranteed latency and a quality service you'll need to look for something that has a low contention or is uncontended. If you don't have the choice of buying uncontended, you might want campaign for getting that offered, but you can not buy a contended service and then complain, when the contention kicks in.

The problem with that might be, that uncontended might cost more than you're willing to pay.

/M

Steffano2002

Marlow wrote: »

Actually, I need to correct you here. You bought a contended service. When the contention kicks in, your latency goes up. That's the one of the downsides of contention.

If you want a guaranteed latency and a quality service you'll need to look for something that has a low contention or is uncontended. If you don't have the choice of buying uncontended, you might want campaign for getting that offered, but you can not buy a contended service and then complain, when the contention kicks in.

The problem with that might be, that uncontended might cost more than you're willing to pay.

/M

Why would the contention start kicking last Thursday all of a sudden after 6 months of PERFECT service? That makes no sense to me. Something has happened somewhere, either on the Exchange or on the routing side of things.

I'll check my ping before going to work in the morning to make sure I can rule out the contention issue.

Sponge Bob

That shows packet loss , eg

His

Tracing route to www.rte.ie.nsatc.net [89.207.56.140]
over a maximum of 30 hops:

1 50 ms 99 ms 99 ms smart.lan [192.168.1.1]
2 75 ms * 85 ms ge0-1-0-100.core1.deg.dub.stisp.net

Hypothetical ( and yes legally) contended

Tracing route to www.rte.ie.nsatc.net [89.207.56.140]
over a maximum of 30 hops:

1 50 ms 99 ms 99 ms smart.lan [192.168.1.1]
2 175 ms 180ms 185 ms ge0-1-0-100.core1.deg.dub.stisp.net

But no packet loss , router might need a reboot there !!!

Steffano2002

Sponge Bob wrote: »

Router might need a reboot there !!!

Router is rebooted daily. I unplugged Sky. Tried from 3 different machines (my PC and 2 laptops). Tried with Network Cable (to rule out WiFi interference)... Same all the time...

Sponge Bob

I meant the Smart Router .

Steffano2002

Mmmmmhhhh... It's 23:48 and now ping is "back to normal" (i.e. what it has been for the previous 6 months). Maybe it is a contention issue... If it is I'm fooked!

Steffano2002

Sponge Bob wrote: »

I meant the Smart Router .

Me too!

Steffano2002

Is there some sort of application (or website?) you can leave running to keep checking your ping over long periods of time?

Thanks again for all your help lads!

Sponge Bob

get onto their support forum and paste all that info in there .

Marlow

Steffano2002 wrote: »

Is there some sort of application (or website?) you can leave running to keep checking your ping over long periods of time?

Thanks again for all your help lads!

Yes. I think there is pingplotter for windows. Smokeping for Linux (should also work on Windows, but messy to set up).

As for the reason you were asking, why it was good 6 months and then goes to crap: That's because 6 months ago, the DSLAM, that you are connected to or the exchange capacity, wasn't full. The second, enough DSL lines are sold and people use their connection more, contention kicks in.

Also have you looked outside ? It gets dark early, people aren't outside. They are inside using their broadband a lot earlier in the evening. In the last 6 months they've been out BBQ'ing or enjoying the weather instead. That's what it is. Most likely.

/M

Steffano2002

Sponge Bob wrote: »

get onto their support forum and paste all that info in there .

I did... No answer... Their going bust so I'm not expecting a reply either...

Steffano2002

Marlow wrote: »

Yes. I think there is pingplotter for windows. Smokeping for Linux (should also work on Windows, but messy to set up).

As for the reason you were asking, why it was good 6 months and then goes to crap: That's because 6 months ago, the DSLAM, that you are connected to or the exchange capacity, wasn't full. The second, enough DSL lines are sold and people use their connection more, contention kicks in.

Also have you looked outside ? It gets dark early, people aren't outside. They are inside using their broadband a lot earlier in the evening. In the last 6 months they've been out BBQ'ing or enjoying the weather instead. That's what it is. Most likely.

/M

Ping plotter! That's the one! Cheers!

I think you may be onto something with the contention... I just can't understand why it went from being perfect (and I mean PERFECT!) last Wednesday evening to completely cr@p the following evening... It happened so fast I assumed it was an issue on the Exchange or something...

Marlow

Steffano2002 wrote: »

I did... No answer... Their going bust so I'm not expecting a reply either...

Erh ? I think you got a bit confused. Being in examinership and going bust are two different things.

They will only go bust, if nobody buys them, which is highly unlikely, as there are enough interested companies.

Inside Smart, from a technical point of perspective, everything is business as usual. I actually just bought another fiber circuit of them.

So until they are declared bust, nothing is going to change.

As for going from good to complete crap, check my comments on "look outside". It's dark early now, so people use their broadband more. If it's contended, and more people use it now, that's the result you get. And you'll never know when it's gonna hit you. You have to expect this with a contended service.

/M

Xcellor

Marlow wrote: »

Actually, I need to correct you here. You bought a contended service. When the contention kicks in, your latency goes up. That's the one of the downsides of contention.

If you want a guaranteed latency and a quality service you'll need to look for something that has a low contention or is uncontended. If you don't have the choice of buying uncontended, you might want campaign for getting that offered, but you can not buy a contended service and then complain, when the contention kicks in.

The problem with that might be, that uncontended might cost more than you're willing to pay.

/M

i didn't realise the OP was on an unbundled exchange.

While I understand all resold Eircom residenial bitstream products are contended, the poor service many users have been experiencing is unacceptable. In my case latency exceeding 500ms going to 1000ms and drops from 7.6 to 0.32. On a 12:1 contended service that is fairly crappy. No one expects to get top speed all the time, but no one should be asked to suffer sub dial up performance while paying a premium for broadband.

Steffano2002

Marlow wrote: »

Erh ? I think you got a bit confused. Being in examinership and going bust are two different things.

They will only go bust, if nobody buys them, which is highly unlikely, as there are enough interested companies.

I say "they're going bust" because they are. That's why they have to find a buyer i.e. SMART is going bust. I'm using more simplistic terms...

Marlow wrote: »

Inside Smart, from a technical point of perspective, everything is business as usual. I actually just bought another fiber circuit of them.

So until they are declared bust, nothing is going to change.

IMO, their service has gone to complete cr@p... I subscribed in April/May and haven't been billed yet. Takes a minimum of 20 minutes of hold time before getting through to an Agent. The SMART Forum Admins don't reply to Customers anymore (check the forum for yourself).

Marlow wrote: »

As for going from good to complete crap, check my comments on "look outside". It's dark early now, so people use their broadband more. If it's contended, and more people use it now, that's the result you get. And you'll never know when it's gonna hit you. You have to expect this with a contended service.

/M

It's 24:1 and I really don't expext my service to get that bad in the evenings... And I still believe something happened last week between Thursday and Friday. It happened too suddenly to be just "dark evenings causing contention issues"...

Steffano2002

Xcellor wrote: »

On a 12:1 contended service that is fairly crappy. No one expects to get top speed all the time, but no one should be asked to suffer sub dial up performance while paying a premium for broadband.

Fully agree with you there!!!

Marlow

Steffano2002 wrote: »

It's 24:1 and I really don't expext my service to get that bad in the evenings... And I still believe something happened last week between Thursday and Friday. It happened too suddenly to be just "dark evenings causing contention issues"...

The problem with the 24:1 contention is actually not something Smart can do something about.

It is 24:1 contention because it's bitstream. You are hanging on an Eircom DSLAM. They apply the contention. Smarts own lines are uncontended.

So essentially, no matter what it is, it's actually Eircoms fault. Not that they would care

/M

Steffano2002

Marlow wrote: »

The problem with the 24:1 contention is actually not something Smart can do something about.

It is 24:1 contention because it's bitstream. You are hanging on an Eircom DSLAM. They apply the contention. Smarts own lines are uncontended.

So essentially, no matter what it is, it's actually Eircoms fault. Not that they would care

/M

Well at least SMART were offering 24:1. Eircom was going with 48:1! Madness! I wish I could get SMART LLU or MAGNET LLU or NTL... But I'm in the shticks now (well, as far as broadband is concerned, Ashbourne is in the shticks...).