Nice going Iburst.

[Daveogg]

Hopefully what we can expect in the new year.

Ping statistics for 64.233.183.99: (www.google.com)
Packets: Sent = 20, Received = 19, Lost = 1 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 244ms, Maximum = 294ms, Average = 275ms

 

[Syndyre]

Not bad, I'm getting 538ms on SAIX ADSL.

 

[DaGGa BuNNy]

Reply from 66.249.85.104: bytes=32 time=502ms TTL=242
Reply from 66.249.85.104: bytes=32 time=627ms TTL=242
Reply from 66.249.85.104: bytes=32 time=560ms TTL=242
Reply from 66.249.85.104: bytes=32 time=625ms TTL=242

Ping statistics for 66.249.85.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 502ms, Maximum = 627ms, Average = 578ms



:<<< Im pretty much over iBurst and thier pathetic speeds and **** technical service crap

 

[LabAnimal]

Daveogg is this from home or at work? - that place on the hill

 

[Daveogg]

Ha u tracked me down?? Yup that place on the hill.

 

[LabAnimal]

I'm that Klopper's other half - say no more

 

[PsyCLown]

Check this out. Im using iBurst and iv been throttled down to 64K

Google.com ping

 

[LabAnimal]

you've been capped?

 

[Trixanno]

Mine don't look too bad for a capped service:
Reply from 216.239.37.99: bytes=32 time=340ms TTL=239
Reply from 216.239.37.99: bytes=32 time=343ms TTL=238
Reply from 216.239.37.99: bytes=32 time=343ms TTL=238
Reply from 216.239.37.99: bytes=32 time=343ms TTL=239

Ping statistics for 216.239.37.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 340ms, Maximum = 343ms, Average = 342ms

 

[Daveogg]

I'm that Klopper's other half - say no more

LOL

Now the nick makes sense!!!
Say hi and a happy new year to that other lab rat!!

 

[LabAnimal]

lol - will do - have a good one

 

[Gatecrasher]

Also throttled. Lowest latency to Google I've ever seen. I've add a tracert. Maybe some clever bod can see why its so fast.

Pinging www.l.google.com [64.233.183.147] with 32 bytes of data:

Reply from 64.233.183.147: bytes=32 time=246ms TTL=236
Reply from 64.233.183.147: bytes=32 time=264ms TTL=236
Reply from 64.233.183.147: bytes=32 time=269ms TTL=236
Reply from 64.233.183.147: bytes=32 time=269ms TTL=236

Ping statistics for 64.233.183.147:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 246ms, Maximum = 269ms, Average = 262ms

Tracing route to www.l.google.com [64.233.183.147]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    64 ms    49 ms    46 ms  wbs-41-208-192-1.wbs.co.za [41.208.192.1]
  3    60 ms   177 ms    47 ms  192.168.0.97
  4    66 ms    85 ms    64 ms  192.168.0.100
  5    63 ms    49 ms    50 ms  ge0-2.gw10.jnb6.alter.net [66.8.42.21]
  6    73 ms    93 ms    48 ms  fe4-1-0.cr2.jnb6.alter.net [196.30.156.34]
  7   257 ms   244 ms   244 ms  other-side.s10-1-1.cr2.jnb6.alter.net [196.30.22
9.233]
  8   274 ms   239 ms   254 ms  at0-1-1.ir1.lnd19.alter.net [196.30.229.134]
  9   257 ms   239 ms   239 ms  so-0-0-1.IH2.LND9.ALTER.NET [146.188.2.241]
 10   260 ms   289 ms   239 ms  so-2-0-2.TR1.LND9.ALTER.NET [146.188.2.45]
 11   257 ms   239 ms   245 ms  POS1-0.BR1.LND9.ALTER.NET [146.188.7.242]
 12   256 ms   234 ms   239 ms  so-7-0-2.core2.London1.Level3.net [146.188.68.21
0]
 13   260 ms   250 ms   254 ms  ae-19-51.ebr1.London1.Level3.net [4.68.116.30]
 14     *      261 ms   239 ms  ae-1-100.ebr2.London1.Level3.net [4.69.132.118]

 15   306 ms   279 ms   269 ms  ae-2.ebr2.Amsterdam1.Level3.net [4.69.132.134]
 16   270 ms   249 ms   250 ms  ge-11-1.ipcolo2.Amsterdam1.Level3.net [4.68.120.
106]
 17   369 ms   274 ms   259 ms  212.72.44.66
 18   269 ms   249 ms   249 ms  64.233.175.246
 19   274 ms   250 ms   254 ms  72.14.233.83
 20   266 ms   269 ms   269 ms  216.239.43.34
 21   271 ms   264 ms   344 ms  nf-in-f147.google.com [64.233.183.147]

Trace complete.

 

[Roman4604]

Maybe some clever bod can see why its so fast.

No mystery, cos everyone's on holiday, especially Verizon's corporate customers.

 

[Basjohn]

Just a side note for those of you who don't know but CAPPING does NOT affect your ping WHATSOEVER.

Merely throttles your maximum speed.

 

[GreatBigMouth]

Speaking of capping, who here is capped, but not throttled?

 

[Trixanno]

I used to have that luck 'till round about the 27th, was flippen great stuff! The thoughts of iburst getting ready to give an uncapped service was going through my mind! Then they obviously tapped into my brain, discovered that I was having those obscure thoughts and...well now I'm throttled again!

 

[Alchemist]

Iburst seems to love throttling me. One moment i'm happily watching videos on YouTube, and the next thing, everything just dies. Pages just don't even bother to load. I generally have to refresh a page about 6 or 7 times before it loads. Oh, and dont get me started on the Iburst website. I can't even load the page once I'm throttled. It's actually quite funny, I can access their competitors websites easier than theirs.

 

[GreatBigMouth]

I take my words back in the previous post. After a modem reboot, they throttled me.