On another note.....Rage....Zombie Strippers??? really???
Pinging carigamers.com [72.52.247.183] with 32 bytes of data:Reply from 72.52.247.183: bytes=32 time=532ms TTL=45Reply from 72.52.247.183: bytes=32 time=516ms TTL=45Reply from 72.52.247.183: bytes=32 time=224ms TTL=45Reply from 72.52.247.183: bytes=32 time=246ms TTL=45Ping statistics for 72.52.247.183: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 224ms, Maximum = 532ms, Average = 379ms
Network buffer measurements (?): Uplink 5900 ms, Downlink 1200 msWe estimate your uplink as having 5900 msec of buffering. This is quite high, and you may experience substantial disruption to your network performance when performing interactive tasks such as web-surfing while simultaneously conducting large uploads. With such a buffer, real-time applications such as games or audio chat can work quite poorly when conducting large uploads at the same time.We estimate your downlink as having 1200 msec of buffering. This is quite high, and you may experience substantial disruption to your network performance when performing interactive tasks such as web-surfing while simultaneously conducting large downloads. With such a buffer, real-time applications such as games or audio chat can work quite poorly when conducting large downloads at the same time.
Network buffer measurements (?): Uplink 1600 ms, Downlink 840 msWe estimate your uplink as having 1600 msec of buffering. This is quite high, and you may experience substantial disruption to your network performance when performing interactive tasks such as web-surfing while simultaneously conducting large uploads. With such a buffer, real-time applications such as games or audio chat can work quite poorly when conducting large uploads at the same time.We estimate your downlink as having 840 msec of buffering. This level can in some situations prove somewhat high, and you may experience degraded performance when performing interactive tasks such as web-surfing while simultaneously conducting large downloads. Real-time applications, such as games or audio chat, may also work poorly when conducting large downloads at the same time.
lol, ok Emo-Awesome. We've heard your anti-flow rant a billion times. Same can be said for Blink as they have scorned many a gamer with dismal performance and lack luster customer service as well.but enough on the ISP love/hate relationships, lets try and help Apprentice with something on topic.Here's my offpeak results (ran a few seconds ago)Hit us your results for comparison.Apprentice, if you can, try running this test as well....it gives some very detailed analysis on your connection. May help pinpoint the source of the problem.http://netalyzr.icsi.berkeley.edu/index.htmlIn my results, the section on buffering is a bit worrying.QuoteNetwork buffer measurements (?): Uplink 5900 ms, Downlink 1200 msWe estimate your uplink as having 5900 msec of buffering. This is quite high, and you may experience substantial disruption to your network performance when performing interactive tasks such as web-surfing while simultaneously conducting large uploads. With such a buffer, real-time applications such as games or audio chat can work quite poorly when conducting large uploads at the same time.We estimate your downlink as having 1200 msec of buffering. This is quite high, and you may experience substantial disruption to your network performance when performing interactive tasks such as web-surfing while simultaneously conducting large downloads. With such a buffer, real-time applications such as games or audio chat can work quite poorly when conducting large downloads at the same time.Would be interested in seeing the results on a TSTT connection
We estimate your uplink as having 1400 msec of buffering. This is quite high, and you may experience substantial disruption to your network performance when performing interactive tasks such as web-surfing while simultaneously conducting large uploads. With such a buffer, real-time applications such as games or audio chat can work quite poorly when conducting large uploads at the same time. We estimate your downlink as having 230 msec of buffering. This level may serve well for maximizing speed while minimizing the impact of large transfers on other traffic.
lol, you still quarrellin? lets see the results from the test on a tstt connection por favor.http://netalyzr.icsi.berkeley.edu/index.htmlEspecially interested in the buffer results
Network buffer measurements (?): Uplink 210 ms, Downlink is goodWe estimate your uplink as having 210 msec of buffering. This level may serve well for maximizing speed while minimizing the impact of large transfers on other traffic.We were not able to produce enough traffic to load the downlink buffer, or the downlink buffer is particularly small. You probably have excellent behavior when downloading files and attempting to do other tasks.
DNS resolver properties (?): Lookup latency 4000msYour ISP's DNS resolver requires 4000 msec to conduct an external lookup. It takes 130 msec for your ISP's DNS resolver to lookup a name on our server. This is particularly slow, and you may see significant performance degradation as a result.
Anyway this does not give Flow CSR's any excuse to HANG UP on their customers.One of my friends having the same issue with his connection called 30mins after I called in last night.The CSR rudely spoke to him saying "is this the same person that called with the same problem" and hangs up.I did post this issue to their facebook page as well.. Maybe they did look into it after those phone calls last night as well as the facebook post.O well... Hopefully things run good for some time, which really means about a few weeks before more problems.
