Ping times Jan 28 onwards

Started by MarkE, Jan 28, 2009, 13:49:28

Previous topic - Next topic

0 Members and 4 Guests are viewing this topic.

psp83

Quote from: Rik on Feb 07, 2009, 11:22:59
Try support@idnet.net if you still have problems, Paul.

I will forward the email to that address from my work emaill account just incase it happens again,

Simon

Quote from: jameshurrell on Feb 07, 2009, 11:14:06
There's obviously something going on and yes I have had downtime in the last few weeks, but I must say that my pings have been very stable throughout.

Pinging idnet.com [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=19ms TTL=60
Reply from 212.69.36.10: bytes=32 time=22ms TTL=60
Reply from 212.69.36.10: bytes=32 time=21ms TTL=60
Reply from 212.69.36.10: bytes=32 time=19ms TTL=60

Ping statistics for 212.69.36.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:
    Minimum = 19ms, Maximum = 22ms, Average = 20ms

Thanks for your input, James, and :welc:  :karma:
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

Simon_idnet

Quote from: psp83 on Feb 07, 2009, 11:20:16
I've resent the email now, Just checked my mailbox. Got this message back from my hosts.

This message was created automatically by mail delivery software.
A message that you sent has not yet been delivered to one or more of its recipients after more than 24 hours on the queue on hp13.hostpapa.com.

The message identifier is:     1LVAd5-0003Sw-GO
The subject of the message is: high pings.
The date of the message is:    Thu, 5 Feb 2009 20:15:14 -0000

The address to which the message has not yet been delivered is:

  support@idnet.com
    Delay reason: SMTP error from remote mail server after RCPT TO:<support@idnet.com>:
    host mx2.idnet.net [212.69.40.49]: 450 <*****@psp83.com>:
    Sender address rejected: Greylisted for 5 minutes

No action is required on your part. Delivery attempts will continue for some time, and this warning may be repeated at intervals if the message remains undelivered. Eventually the mail delivery software will give up, and when that happens, the message will be returned to you.



So just incase it happens again, i will also forward you the email from my work email address.

Hi Paul

A 5xx SMTP response is a permanent error code. We gave a 4xx response which is the Greylisting. It might be worth querying this with your mail host.

Regards
Simon




cavillas

Doesn't Simon_idnet ever sleep or rest? ;D
------
Alf :)

Rik

No, he is Superman - and I have a signed photo to prove it. ;D
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

cavillas

------
Alf :)

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

psp83

Quote from: Simon_idnet on Feb 07, 2009, 11:25:54
Hi Paul

A 5xx SMTP response is a permanent error code. We gave a 4xx response which is the Greylisting. It might be worth querying this with your mail host.

Regards
Simon

Talk to my hosts? haha, nice joke there :P they are the Tiscali of webhosting and i'm changing this week if i get time so no point :)

I will just email idnet from my work address from now on.

conneh

Things have sorted themself out - to an extent.

I was told it would be sorted by Thursday and it may creep into Friday... However i still have 150ms!

Lovely.


Rik

I'm averaging 25ms, with spikes to 86 maximum.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Ray

Mine were fine running at an average of 23-25ms from o8:00 and went haywire at 12:43 now running anywhere between 35ms and 180ms.
Ray
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

Same here, Ray, things have worsened since my last post. A reset of the PPP session effected no improvement.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

I'm going to go and worry about lunch. ;D
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Steve

I only worry about lack of lunch ;D
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Ray

Quote from: Rik on Feb 07, 2009, 13:46:52
I'm going to go and worry about lunch. ;D

You're late, Rik, had mine an hour ago, I was hungry.  ;)
Ray
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

cavillas

Had brunch at 10.45.  A nice alld day Brekkie in Walton...luverly ;D
------
Alf :)

Rik

Quote from: Sheltieuk on Feb 07, 2009, 13:55:58
You're late, Rik, had mine an hour ago, I was hungry.  ;)

I was, I'm much better now. :)
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Mohux_Jnr

 Frustrating is not the word, games unplayable all week unless you play at 4am and having to reboot the router every hour is becoming tiresome.
Any news on when we can expect a resolution?, I keep hearing it is down to congestion but surely it is no worse than before the upgrade?.





[attachment deleted by admin]

Rik

As I understand it, the problem has been that since the new central was connected, everyone has ended up on a single pipe, and IDNet have been having to rebalance manually. Unfortunately, the router failure on Tuesday undid all the work until that point, and they have had to start again from scratch.

Certainly, since PPP dropped for me just before lunch, pings have become bad, ie averaging 150ms rather than 24ms.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

cavillas

I am still averageing 34ms.  It has been at this forever, I must be lucky.
------
Alf :)

Rik

You're on the frequent flyer connection, Alf. :)
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

davej99

Things certainly seem sluggish today and logoff/on some times changes thinks for better/worse. This does feel like some central are congested. I guess we will have to let Simon and the IDNET Team finish the job.

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

JB


Pings at the moment are about the worst I have seen. My browsing is sluggish and it is impacting on my VOIP calls.

I really hope that this can be rectified within the next week or I will be forced to look for another ISP, something that I don't want to do.

I can log into my router in Spain and ping bbc.co.uk five times more quickly than from here in Cheshire. Rebooting the router makes no difference.

I really hope a solution is forthcoming.


[attachment deleted by admin]
JB

'Keyboard not detected ~ Press F1 to continue'

Rik

I've just re-booted my router and got back to normal, JB. Might be worth a try. IDNet are working on peering today, so possibly it's some sort of caching process getting in the way? (Can you tell I have no idea why it worked? :D)
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.