This site is closed to new comments and posts.

Notice: This site uses cookies to function.
If you are not comfortable with cookies then please don't browse this website.

Time Warner internet super slow lately? — Brooklynian

Time Warner internet super slow lately?

8thandprez
edited November -1 in Park Slope
Has anyone else in North Slope noticed how slow TWC internet is the past few days? It's excruciatingly slow.

Comments

  • Maybe it is your modem? How old is it? When I had that problem, that turned out to be the issue.
  • Actually it has been faster than usual. 18-20 down, 5 up. Used to be only 8-10 down, 5 up on the basic rate. FiOS on the way, you know.
  • Subject: Re: Time Warner internet super slow lately?

    8thandPrez wrote: Has anyone else in North Slope noticed how slow TWC internet is the past few days? It's excruciatingly slow.
    I notice my google gmail takes forever to send an email, refresh, etc. I just chalked it up to TWC doing its crappy thang again.
  • Extremely slow in the past few days in center slope are also - extremely slooooow. I thought it was just the contrarians on the "foodie" thread fucking up my ability to x out of their posts as fast as possible, but I guess it could be a TW technical problem.
  • One of the wonderful things about cable. If there is someone close to you that is sucking up bandwidth, all the people around them on that node will suffer. TWC has been up to some sneakiness of late with bandwidth caps and throttling. Are you a high use consumer of the internet tubes? Perhaps they are metering you... Is are the tubes clogged overall or just one pipe? (what is slow, everything or a certain service)

    Have you done a bandwidth test etc...
  • no problems on my end. sorry.
  • nor mine.
  • If you manage to saturate your upstream that can cause incredibly slow response times.
    Try pinging google.com and see what you get. In windows open a command prompt, in os X or linux open a terminal window and type:
    ping google.com
    and see the numbers that come back they should all be below 100ms (in os X you have to press ctrl^c to make this stop).

    the output will look like this:
    d108:~ jm$ ping google.com
    PING google.com (72.14.207.99): 56 data bytes
    64 bytes from 72.14.207.99: icmp_seq=0 ttl=248 time=62.736 ms
    64 bytes from 72.14.207.99: icmp_seq=1 ttl=248 time=76.724 ms
    64 bytes from 72.14.207.99: icmp_seq=2 ttl=248 time=59.261 ms
    64 bytes from 72.14.207.99: icmp_seq=3 ttl=248 time=75.865 ms
    64 bytes from 72.14.207.99: icmp_seq=4 ttl=248 time=35.549 ms
    ^C
    --- google.com ping statistics ---
    5 packets transmitted, 5 packets received, 0% packet loss
    round-trip min/avg/max/stddev = 35.549/62.027/76.724/14.945 ms

    If those numbers are well above 100ms (in this case you can see mine are averaging 64ms) then you're probably saturating your upstream and screwing yourself, this can happen if you run bittorrent processes and don't throttle them, or someone is leeching your wifi and doing so.

    People like to talk about how with cable one person can wreck the whole node, but tw's lines don't really cause that to happen any more.

    http://www.speakeasy.net/speedtest/ is a good site to see just how fast your connection really is.

    I hadn't noticed the bump from 10-20 but I'll check for it when I get home, I'd much rather get fios but I'll take any extra bw tw gives me.
  • My results from speakeasy were:

    Download Speed: 25163 kbps (3145.4 KB/sec transfer rate)
    Upload Speed: 496 kbps (62 KB/sec transfer rate)

    My ping results:

    Pinging google.com [72.14.207.99] with 32 bytes of data:

    Reply from 72.14.207.99: bytes=32 time=37ms TTL=240
    Reply from 72.14.207.99: bytes=32 time=38ms TTL=240
    Reply from 72.14.207.99: bytes=32 time=39ms TTL=240
    Reply from 72.14.207.99: bytes=32 time=44ms TTL=240

    Ping statistics for 72.14.207.99:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 37ms, Maximum = 44ms, Average = 39ms
Sign In or Register to comment.