Connection problems?

[ducky22]

M:\>ping bbc.co.uk

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=158ms TTL=122
Reply from 212.58.224.138: bytes=32 time=164ms TTL=122
Reply from 212.58.224.138: bytes=32 time=170ms TTL=122
Reply from 212.58.224.138: bytes=32 time=163ms TTL=122

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

M:\>

[Glenn]

Here you are



[attachment deleted by admin]

[davej99]

They are upgrading their network so I would bear with them ... teething problems I suspect.

Uxbod has a point. We all know work is ongoing. Though it is irritating to have frequent interruptions, I see no reason to throw the toys out of the pram yet, and certainly not before we know the cause. Though pings are well up.

[Rik]

Same sort of pattern, thanks guys.  

[jaydub]

A detailed explanation of what has gone wrong from either Tim or Simon would help settle people's somewhat frayed nerves (including mine).

[Rik]

I agree.

[ducky22]

Uxbod has a point. We all know work is ongoing. Though it is irritating to have frequent interruptions, I see no reason to throw the toys out of the pram yet, and certainly not before we know the cause. Though pings are well up.

Fair enough if this had not been occuring regularly for the last 3 months...but oh wait it has.  

It was also refreshing to see the status page showing green across the board throughout the entire outage.

[Aaron]

Thought this downtime was to fix the load balancing to get the pings down, but still seems quite all over the place here

[Sebby]

Everything you've said is factually correct, ducky; no one is disputing that. But it's not worth ranting here as this is just an unofficial forum - complaints need to go to IDNet directly.

[VaderDSL]

I was with Be* and for 3 and a half weeks I had a virtually useless connection to which they wouldn't aknowledge, basically a local piece of LLU equipment at the exchange broke, meaning I was getting pings > 250ms and 75% packet loss and downloads would always fail. For nearly a month, I phoned them up 3-4 times a week, while I wasn't at work trying desperately to get through to their support/supervisors, each time it was, have you unplugged the router, have you left it for 30 minutes, have you plugged the microfilter into the master plate etc.

I kept telling them it wasn't a fault my end and it must be the exchange, nah it's probably BT or your line idiots. In the end maybe half a dozen of us on a forum managed to get our evidence together and it was sent numerous times to Be* as well as the CS rep on there iirc. Finally they acknowledged and fixed it, by which time I had moved to IDNet.

BT have been so much worse for me in the past, and Virgin Media, dear god how do people use their oversubscribed service? I was paying for 20mb connection, with horrible upload speeds and getting just shy of 1mb speeds due to them packing people onto the UBR's so ultimately I love IDNet, i do miss the old days of 512kb ultra stable broadband though, I was with Zen when ADSL was first rolled out

[golden]

I am on GW5 and got disconnected from my online game for an hour went to the chippy to get some grub. came back and saw I was back online but went to check the pings and godamn they are back into the 100's.

[karvala]

Same problems here, needless to say since it's clearly a problem at IDNet.  Down completely (bar two minutes in the middle) for over an hour, and now with unacceptable high pings.  Phone seemed to be deliberately left off the hook so they didn't have to answer any calls while it was down.

I have to say, I share the disappointment expressed by one or two of the other posters.  I used to be a big fan of IDNet, and I've brought quite a few customers to them over the last three years, but now I'm feeling very let down.  Let's be clear about this: we pay way over the odds at IDNet, and we do so because we want a no-nonsense premium quality service.  Until relatively recently, this was delivered without any fuss, and I was happy to pay more.  But now we've had goodness knows how many outages over the last month (my router logs show other occasional small outages in in addition to the ones documented on here as well, not for very long each time, and on every occasion it is not a loss of sync that causes it, it's the PPPoA layer only), and now a no-phone-support-during-outage stunt worthy of Tiscali (and what the hell is the service status page for, if it always claims everything is hunky dory?!), and I'm wondering why I bother to pay more.

As far as I'm concerned, they have until the end of today to sort out the ping fiasco, apologise for the appalling lack of service (customer and internet service) that occurred today, and not have a single other screw-up until the end of this month at least.  Failing that, I will asking for my MAC code and recommending to the other 20+ customers that I've brought to them, to do likewise.

[Rik]

Careful, Vader, you'll get me reminiscing about 300 baud modems soon.

[Sebby]

I think Be have got a lot better with maintenance and upgrades now, Vader.

I agree with you about 512k - well fixed services in general. There's certainly something to be said for the stability they offered.

[Mohux_Jnr]

 I was just thinking everything was sorted.....the first graph was taken at 11pm last night = 20 average ping

                                                         ....the second graph at 2pm today = 159 average ping

I am sure it is only a matter of time



[attachment deleted by admin]

[skwark]

Anyone else seeing pings through the roof again, mine have gone out from an average of 24ms to around 130...

Yup, 153ms up from 24ms!

Also dropped to 1Mbps from nearly 7...  

[Rik]

I was just thinking everything was sorted.....the first graph was taken at 11pm last night = 20 average ping

                                                         ....the second graph at 2pm today = 159 average ping

I am sure it is only a matter of time

I sincerely hope so.  

[Rik]

Yup, 153ms up from 24ms!

Also dropped to 1Mbps from nearly 7...  

That shouldn't have happened, only PPP actually dropped. Is your sync speed the same?

[skwark]

Sync still 8128 as always....

[ducky22]

As far as I'm concerned, they have until the end of today to sort out the ping fiasco, apologise for the appalling lack of service (customer and internet service) that occurred today, and not have a single other screw-up until the end of this month at least.  Failing that, I will asking for my MAC code and recommending to the other 20+ customers that I've brought to them, to do likewise.

Couldn't have put it better myself. Zen for sure.

If Rik can't get information out of IDNet, the rest of us are completely screwed.

[Sebby]

Nope, sync still 8128 as always....

Could you run a BT speed test and post the results. I wonder if it's a profile issue.

[Rik]

If Rik can't get information out of IDNet, the rest of us are completely screwed.

I try, but ultimately I'm just another customer.

[MattBeard]

Hmm, it looks like we are "back online" but not running as expected!



Edit: This is with an 8128 sync!

[skwark]

Your DSL connection rate: 8128 kbps(DOWN-STREAM),  448 kbps(UP-STREAM)
   IP profile for your line is - 7150 kbps
   Actual IP throughput achieved during the test was - 1282 kbps

[Captain K]

Near normal pings here:

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:

Reply from 212.58.224.138: bytes=32 time=27ms TTL=122
Reply from 212.58.224.138: bytes=32 time=25ms TTL=122
Reply from 212.58.224.138: bytes=32 time=28ms TTL=122
Reply from 212.58.224.138: bytes=32 time=27ms TTL=122

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