Question re: 30 Gb limit

I'm thinking of moving from Pipex to another ISP.

IDNet is on the list 'cos:

Fast.co.uk seem the most futureproof given the expensive price of the package keeping the migrating Nildram and Pipex lemmings out, but otherwise excellent CS and no traffic shaping etc.

Zen's another on the list, but 20 Gb for

Edited by BlobbyBlobby (Wed 01-Nov-06 17:58:06)

I'm sorry to disapoint you but there is no catch on any IDNet packages what you see is what you get.
But i do understand you asking that putting up with Pipex

Edited by stevelondon (Wed 01-Nov-06 18:44:31)

In reply to:

---

So, can anyone explain any 'limitations' and small print on this 30 Gb allowance?

---

Yup- none.

No throttling, no peak times, no prioritisation- it's your 30Gig, use it how you like. Use it all in one day if you like, provided you don't use any the rest of that month, that's fine.

Even if you do, it's only

Well, thank you for the reassuring replies.

Shame there's no news server, but I can live without that.

Has the ping problem definitely been sorted now too?

I'm not a gamer, so I'm not the best one to ask about pings... but the complaints seem to have disappeared, so I assume that at least most of the problems have done likewise....

>>>Has the ping problem definitely been sorted now too?<<<

I suffered with bad pings a couple of months ago but they have been fine for ages.


Pinging www.bbc.co.uk with 32 bytes of data:

Reply from 212.58.224.116 bytes:32 Time:35ms TTL:249
Reply from 212.58.224.116 bytes:32 Time:31ms TTL:249
Reply from 212.58.224.116 bytes:32 Time:31ms TTL:249
Reply from 212.58.224.116 bytes:32 Time:30ms TTL:249
Reply from 212.58.224.116 bytes:32 Time:39ms TTL:249
Reply from 212.58.224.116 bytes:32 Time:30ms TTL:249
Reply from 212.58.224.116 bytes:32 Time:31ms TTL:249
Reply from 212.58.224.116 bytes:32 Time:31ms TTL:249
Reply from 212.58.224.116 bytes:32 Time:42ms TTL:249
Reply from 212.58.224.116 bytes:32 Time:30ms TTL:249
Reply from 212.58.224.116 bytes:32 Time:33ms TTL:249
Reply from 212.58.224.116 bytes:32 Time:34ms TTL:249
Reply from 212.58.224.116 bytes:32 Time:40ms TTL:249
Reply from 212.58.224.116 bytes:32 Time:40ms TTL:249
Reply from 212.58.224.116 bytes:32 Time:32ms TTL:249
Reply from 212.58.224.116 bytes:32 Time:33ms TTL:249
Reply from 212.58.224.116 bytes:32 Time:30ms TTL:249
Reply from 212.58.224.116 bytes:32 Time:32ms TTL:249
Reply from 212.58.224.116 bytes:32 Time:30ms TTL:249
Reply from 212.58.224.116 bytes:32 Time:31ms TTL:249
Reply from 212.58.224.116 bytes:32 Time:30ms TTL:249
Reply from 212.58.224.116 bytes:32 Time:33ms TTL:249
Reply from 212.58.224.116 bytes:32 Time:40ms TTL:249
Reply from 212.58.224.116 bytes:32 Time:33ms TTL:249
Reply from 212.58.224.116 bytes:32 Time:30ms TTL:249
Reply from 212.58.224.116 bytes:32 Time:40ms TTL:249
Reply from 212.58.224.116 bytes:32 Time:32ms TTL:249
Reply from 212.58.224.116 bytes:32 Time:35ms TTL:249
Reply from 212.58.224.116 bytes:32 Time:33ms TTL:249
Reply from 212.58.224.116 bytes:32 Time:30ms TTL:249
Ping statistics for www.bbc.co.uk :
Packets: Sent = 30, Received = 30, Lost = 0 (0%) loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 42ms, Average = 33ms

Here's the Pipex comparison:

Pinging www.bbc.net.uk [212.58.224.113] with 32 bytes of data:

Reply from 212.58.224.113: bytes=32 time=15ms TTL=247
Reply from 212.58.224.113: bytes=32 time=13ms TTL=247
Reply from 212.58.224.113: bytes=32 time=12ms TTL=247
Reply from 212.58.224.113: bytes=32 time=13ms TTL=247

Ping statistics for 212.58.224.113:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 15ms, Average = 13ms

:P

It depends where you are, I think, and also which BBC server you end up pinging:

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

Reply from 212.58.226.229: bytes=32 time=13ms TTL=121
Reply from 212.58.226.229: bytes=32 time=13ms TTL=121
Reply from 212.58.226.229: bytes=32 time=14ms TTL=121
Reply from 212.58.226.229: bytes=32 time=14ms TTL=121
Reply from 212.58.226.229: bytes=32 time=15ms TTL=121
Reply from 212.58.226.229: bytes=32 time=14ms TTL=121
Reply from 212.58.226.229: bytes=32 time=13ms TTL=121
Reply from 212.58.226.229: bytes=32 time=13ms TTL=121
Reply from 212.58.226.229: bytes=32 time=14ms TTL=121
Reply from 212.58.226.229: bytes=32 time=15ms TTL=121
Reply from 212.58.226.229: bytes=32 time=14ms TTL=121
Reply from 212.58.226.229: bytes=32 time=15ms TTL=121
Reply from 212.58.226.229: bytes=32 time=15ms TTL=121
Reply from 212.58.226.229: bytes=32 time=15ms TTL=121
Reply from 212.58.226.229: bytes=32 time=17ms TTL=121
Reply from 212.58.226.229: bytes=32 time=14ms TTL=121
Reply from 212.58.226.229: bytes=32 time=15ms TTL=121

Ping statistics for 212.58.226.229:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 17ms, Average = 14ms

Bill do you live in the exchange ?

I've often been accused of that

I'm about 1Km away (straight line), just lucky with pings I suppose. But I'll tell you- I'd happily live with double the pings if it would cut the contention at the exchange

At times I can do two speed tests thirty minutes apart and get over 6000Kbps on one and under 1000Kbps on the other