dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
6076
share rss forum feed

interestor

join:2013-01-17

[TWC] Super slow in Brooklyn, any idea why?

I have twc internet only, $100 (+4) / month 50/5 package.

It has been uncomfortably slow for many weeks, I keep hoping it will correct itself.

I get around 3Mbps download and 4Mbps upload on most speedtests. A movie downloads at about .1kBps. Watching Colbert often breaks up.

Here is the result from a Netalyzr test. I don't understand most of it. I did switch off the firewall and test again to find a very slight increase in download, but...

Why do you think this connection is so slow and what can I do about it?

Thanks

Summary of Noteworthy Events + + – – Minor Aberrations –•Fragmented UDP traffic is blocked
•The network blocks some or all EDNS replies
•Some DNS resolvers appear to be down
•Your computer's clock is slightly slow
Minor Aberrations +
Address-based Tests + + – – NAT detection (?): NAT Detected +Your global IP address is 24.164.133.76 while your local one is 192.168.0.13. You are behind a NAT. Your local address is in unroutable address space.
Your machine numbers TCP source ports sequentially. The following graph shows connection attempts on the X-axis and their corresponding source ports used by your computer on the Y-axis.

TCP ports are not renumbered by the network.

NAT detection (?): NAT Detected + Local Network Interfaces (?): OK +Your computer reports the following network interfaces, with the following IP addresses for each one: eth0: (an ethernet interface)eth1: (an ethernet interface)eth10: (an ethernet interface)eth11: (an ethernet interface)eth12: (an ethernet interface)eth13: (an ethernet interface)eth14: (an ethernet interface)eth15: (an ethernet interface)eth16: (an ethernet interface)eth17: (an ethernet interface)eth2: (an ethernet interface)eth3: (an ethernet interface)eth4: (an ethernet interface)fe80::81da:b9bf:718b:9edb (a link-local IPv6 address)eth5: (an ethernet interface)fe80::64bc:9725:b7df:6384 (a link-local IPv6 address)eth6: (an ethernet interface)eth7: (an ethernet interface)eth8: (an ethernet interface)eth9: (an ethernet interface)lo: (a local loopback interface)127.0.0.1 [gpsoft.com.au] (an IPv4 loopback address)::1 (an IPv6 loopback address)net0: net1: net10: 2001:0:9d38:6ab8:440:3a99:3f57:fff2 [Concentrated] (a Teredo IPv6 address)fe80::440:3a99:3f57:fff2 [Concentrated] (a link-local IPv6 address)net11: net12: fe80::5efe:c0a8:d (a link-local IPv6 address)net13: net14: net15: net16: net17: net18: net19: net2: net20: net21: net22: net23: net24: net3: net4: net5: net6: net7: net8: 192.168.0.13 (a private IPv4 address)fe80::6d56:a303:3f16:e7cb (a link-local IPv6 address)net9: fe80::d1a2:6fee:1c7:8499 (a link-local IPv6 address)ppp0: ppp1:
Local Network Interfaces (?): OK + DNS-based host information (?): OK +You are not a Tor exit node for HTTP traffic. You are listed on the Spamhaus Policy Based Blacklist, meaning that your provider has designated your address block as one that should only be sending authenticated email, email through the ISP's mail server, or using webmail. The SORBS DUHL believes you are using a dynamically assigned IP address.
DNS-based host information (?): OK + NAT support for Universal Plug and Play (UPnP) (?): Yes +We received UPnP responses from one device: 192.168.0.1: this device provided a valid device description via its UPnP URL. This description, viewable here, contains the following information about this gateway:Name: CentOS routerManufacturer: CentOSManufacturer URL: »www.kernel.org/Model name: CentOS routerModel number: 1Model URL: »www.kernel.org/Model Description: CentOS router
NAT support for Universal Plug and Play (UPnP) (?): Yes + Reachability Tests + + – – TCP connectivity (?): OK +Direct TCP access to remote FTP servers (port 21) is allowed. Direct TCP access to remote SSH servers (port 22) is allowed. Direct TCP access to remote SMTP servers (port 25) is allowed. Direct TCP access to remote DNS servers (port 53) is allowed. Direct TCP access to remote HTTP servers (port 80) is allowed. Direct TCP access to remote POP3 servers (port 110) is allowed. Direct TCP access to remote RPC servers (port 135) is allowed. Direct TCP access to remote NetBIOS servers (port 139) is allowed. Direct TCP access to remote IMAP servers (port 143) is allowed. Direct TCP access to remote SNMP servers (port 161) is allowed. Direct TCP access to remote HTTPS servers (port 443) is allowed. Direct TCP access to remote SMB servers (port 445) is allowed. Direct TCP access to remote SMTP/SSL servers (port 465) is allowed. Direct TCP access to remote secure IMAP servers (port 585) is allowed. Direct TCP access to remote authenticated SMTP servers (port 587) is allowed. Direct TCP access to remote IMAP/SSL servers (port 993) is allowed. Direct TCP access to remote POP/SSL servers (port 995) is allowed. Direct TCP access to remote OpenVPN servers (port 1194) is allowed. Direct TCP access to remote PPTP Control servers (port 1723) is allowed. Direct TCP access to remote SIP servers (port 5060) is allowed. Direct TCP access to remote BitTorrent servers (port 6881) is allowed. Direct TCP access to remote TOR servers (port 9001) is allowed.
TCP connectivity (?): OK + UDP connectivity (?): Note –Basic UDP access is available.
The applet was unable to send fragmented UDP traffic. The most likely cause is an error in your network's firewall configuration or NAT.

The maximum packet successfully sent was 1472 bytes of payload.
The applet was unable to receive fragmented UDP traffic. The most likely cause is an error in your network's firewall configuration or NAT.

The maximum packet successfully received was 1472 bytes of payload. Direct UDP access to remote DNS servers (port 53) is allowed. Direct UDP access to remote NTP servers (port 123) is allowed. Direct UDP access to remote NetBIOS NS servers (port 137) is allowed. Direct UDP access to remote NetBIOS DGM servers (port 138) is allowed. Direct UDP access to remote IKE key exchange servers (port 500) is allowed. Direct UDP access to remote OpenVPN servers (port 1194) is allowed. Direct UDP access to remote Slammer servers (port 1434) is allowed. Direct UDP access to remote L2 tunneling servers (port 1701) is allowed. Direct UDP access to remote IPSec NAT servers (port 4500) is allowed. Direct UDP access to remote RTP servers (port 5004) is allowed. Direct UDP access to remote RTCP servers (port 5005) is allowed. Direct UDP access to remote SIP servers (port 5060) is allowed. Direct UDP access to remote VoIP servers (port 7078) is allowed. Direct UDP access to remote VoIP servers (port 7082) is allowed. Direct UDP access to remote SCTP servers (port 9899) is allowed. Direct UDP access to remote Steam gaming servers (port 27005) is allowed. Direct UDP access to remote Steam gaming servers (port 27015) is allowed. UDP connectivity (?): Note +
Traceroute (?): OK +It takes 22 network hops for traffic to pass from our server to your system, as shown below. For each hop, the time it takes to traverse it is shown in parentheses.
10.209.112.3 (0 ms)ip-10-1-18-13.ec2.internal (0 ms)ip-10-1-172-134.ec2.internal (11 ms)ip-10-1-172-251.ec2.internal (0 ms)***100.64.16.221 (0 ms)72.21.222.148 (0 ms)72.21.222.148 (1 ms)ash-bb1-link.telia.net (62 ms)ash-bb3-link.telia.net (0 ms)atl-bb1-link.telia.net (16 ms)timewarner-ic-153453-atl-bb1.c.telia.net (16 ms)timewarner-ic-153454-atl-bb1.c.telia.net (14 ms)ae-2-0.cr1.atl20.tbone.rr.com (30 ms)107.14.17.142 (28 ms)bun6-nycmnytg-rtr001.nyc.rr.com (25 ms)bun116.nycmnys-rtr02.nyc.rr.com (23 ms)tenge18-10-nycmnys-c401a.nyc.rr.com (47 ms)cpe-24-164-133-76.nyc.res.rr.com (33 ms)cpe-24-164-133-76.nyc.res.rr.com (32 ms)
Traceroute (?): OK + Path MTU (?): OK +The path between our system and your network has an MTU of 1500 bytes.
Path MTU (?): OK + Network Access Link Properties + + – – Network latency measurements (?): Latency: 49ms Loss: 0.5% +The round-trip time (RTT) between your computer and our server is 49 msec, which is good. We recorded a packet loss of 0.5%. This loss rate is within the range commonly encountered and not usually inducing significant performance problems. Of the packet loss, at least 0.5% of the packets appear to have been lost on the path from your computer to our servers.

Network latency measurements (?): Latency: 49ms Loss: 0.5% + TCP connection setup latency (?): 42ms +The time it takes your computer to set up a TCP connection with our server is 42 msec, which is good.
TCP connection setup latency (?): 42ms + Network background health measurement (?): no transient outages +During most of Netalyzr's execution, the applet continuously measures the state of the network in the background, looking for short outages. During testing, the applet observed no such outages.
Network background health measurement (?): no transient outages + Network bandwidth (?): Failed to complete +The test failed to execute completely, or the required results did not get uploaded to our server completely.
Network bandwidth (?): Failed to complete + Network buffer measurements (?): Failed to complete +The test failed to execute completely, or the required results did not get uploaded to our server completely.
Network buffer measurements (?): Failed to complete + HTTP Tests + + – – Address-based HTTP proxy detection (?): OK +We detected no explicit sign of HTTP proxy via IP address changes.
Address-based HTTP proxy detection (?): OK + Content-based HTTP proxy detection (?): OK +No HTTP header or content changes hint at the presence of a proxy.
Content-based HTTP proxy detection (?): OK + HTTP proxy detection via malformed requests (?): OK +Deliberately malformed HTTP requests arrive at our server unchanged. We are not able to detect a proxy along the path to our server using this method.
HTTP proxy detection via malformed requests (?): OK + Filetype-based filtering (?): OK +We did not detect file-content filtering.
Filetype-based filtering (?): OK + HTTP caching behavior (?): OK +We detected no signs of a transparent HTTP cache in your network path.
HTTP caching behavior (?): OK + JavaScript-based tests (?): OK +The applet did not execute within a frame. Your web browser reports the following cookies for our web page: netAlizEd = BaR (set by our server)netalyzrStatus = running (set by our server)Your web browser was unable to fetch an image using IPv6.
JavaScript-based tests (?): OK + DNS Tests + + – – Restricted domain DNS lookup (?): OK +We can successfully look up a name which resolves to the same IP address as our webserver. This means we are able to conduct many of the tests on your DNS server.
Restricted domain DNS lookup (?): OK + Unrestricted domain DNS lookup (?): OK +We can successfully look up arbitrary names from within the Java applet. This means we are able to conduct all test on your DNS server.
Unrestricted domain DNS lookup (?): OK + Direct DNS support (?): OK +All tested DNS types were received OK.
Direct DNS support (?): OK + Direct EDNS support (?): Note –EDNS-enabled requests for small responses are answered successfully. EDNS-enabled requests for medium-sized responses are answered successfully. EDNS-enabled requests for large responses remain unanswered. This suggests that a proxy or firewall is unable to handle large extended DNS requests or fragmented UDP traffic. Direct EDNS support (?): Note +
DNS resolver address (?): OK +The IP address of your ISP's DNS Resolver is 24.29.103.62, which resolves to 24-29-103-62.nyc.rr.com. Additional nameservers observed for your host: 24.29.103.37, 24.29.103.35, 24.29.103.32, 24.29.103.44, 24.29.103.42.
DNS resolver address (?): OK + DNS resolver properties (?): Lookup latency 130ms +Your ISP's DNS resolver requires 130 msec to conduct an external lookup. It takes 86 msec for your ISP's DNS resolver to lookup a name on our server. Your resolver correctly uses TCP requests when necessary. Your resolver is using QTYPE=A for default queries. Your resolver is not automatically performing IPv6 queries. Your DNS resolver requests DNSSEC records. Your DNS resolver advertises the ability to accept DNS packets of up to 4096 bytes. Your DNS resolver can successfully receive a smaller (~1400 byte) DNS response. Your DNS resolver is unable to receive a large (>1500 byte) DNS response successfully, even though it advertises itself as EDNS-enabled. Your DNS resolver accepts DNS responses of up to 1472 bytes. Your resolver does not use 0x20 randomization, but will pass names in a case-sensitive manner. Your ISP's DNS server cannot use IPv6. Your DNS resolver may have significant transport-problems with the upcoming DNSSEC deployments. The resolver is incapable of handling UDP fragmentation.
DNS resolver properties (?): Lookup latency 130ms + Direct probing of DNS resolvers (?) –Your system is configured to use 5 DNS resolver(s). The resolver at 44.0.0.253 is not responding to requests. The resolver at 44.0.0.3 is not responding to requests. The resolver at 44.0.0.4 is not responding to requests. The resolver at 4.2.2.1 could not process the following tested types:
•Large (~3000B) TXT records fetched with EDNS0
It does not validate DNSSEC. It does not wildcard NXDOMAIN errors. The resolver at 192.168.0.1 could not process the following tested types:
•Medium (~1300B) TXT records
•Large (~3000B) TXT records
•Large (~3000B) TXT records fetched with EDNS0
It does not validate DNSSEC. It does not wildcard NXDOMAIN errors. The resolver reports a number of additional properties. Show them.
Version: dnsmasq-2.15Authors: Simon KelleyCopyright: Copyright (C) 2000-2004 Simon KelleyDirect probing of DNS resolvers (?): +
DNS glue policy (?): OK +Your ISP's DNS resolver does not accept generic additional (glue) records — good. Your ISP's DNS resolver does not accept additional (glue) records which correspond to nameservers. Your ISP's DNS resolver does not follow CNAMEs.
DNS glue policy (?): OK + DNS resolver port randomization (?): OK +Your ISP's DNS resolver properly randomizes its local port number. The following graph shows DNS requests on the x-axis and the detected source ports on the y-axis.

DNS resolver port randomization (?): OK + DNS lookups of popular domains (?): OK +90 of 90 popular names were resolved successfully. Show all names.In the following table reverse lookups that failed but for which a Start Of Authority (SOA) entry indicated correct name associations are shown using an "X", followed by the SOA entry. Absence of both IP address and reverse name indicates failed forward lookups. Name IP Address Reverse Name/SOA
6park.com 74.55.98.186 ba.62.374a.st[...]theplanet.com
www.6park.com 74.55.98.186 ba.62.374a.st[...]theplanet.com
www.abbey.co.uk 165.160.13.20 X (pdns1.cscdns.net)
ad.doubleclick.net 74.125.228.28 iad23s05-in-f28.1e100.net
www.amazon.com 205.251.242.54 X (dns-external-master.amazon.com)
www.ameritrade.com 216.105.251.222 kcg.tdameritrade.com
appspot.com 173.194.76.141 qc-in-f141.1e100.net
www.bankofamerica.com 171.161.199.100 X (primarydmz.bankofamerica.com)
www.bankofscotland.co.uk 195.171.195.92 bankofscotland.co.uk
www.blogimg.jp 125.6.190.4 125-6-190-4.data-hotel.net
blogpark.jp 125.6.146.13 125-6-146-13.data-hotel.net
www.capitalone.com 208.80.50.112 X (z.arin.net)
www.careerbuilder.com 208.82.6.22 www.careerbuilder.com
www.chase.com 159.53.44.140 X (ns1.jpmorganchase.com)
chaseonline.chase.com 159.53.64.54 resources-cdc2.chase.com
www.citi.com 192.193.103.222 citibank.com
www.citibank.com 192.193.219.58 citibank.com
www.citimortgage.com 192.193.218.222 citimortgage.com
www.desjardins.com 142.195.132.100 NAT-VS-www.desjardins.com
www.ebay.com 66.135.200.161 www.ebay.com
encrypted.google.com 74.125.228.101 iad23s08-in-f5.1e100.net
www.etrade.com 198.93.34.21 origin-www.etrade.com
www.f-secure.com 184.28.208.32 a184-28-208-32.[...]echnologies.com
www.facebook.com 66.220.158.27 edge-star-ecmp-[...]h4.facebook.com
www.fdic.gov 192.147.69.84 www.fdic.gov
www.friendfinder.com 208.88.180.81 X (ii53-30.friendfinderinc.com)
www.google.com 74.125.131.105 vc-in-f105.1e100.net
www.google-analytics.com 74.125.228.1 iad23s05-in-f1.1e100.net
www.halifax.co.uk 195.171.195.140 halifax.co.uk
hootsuite.com 107.20.75.27 ec2-107-20-75-2[...]1.amazonaws.com
www.hsbc.co.uk 91.214.6.98 X (ns3.hsbc.com)
www.jpmorganchase.com 159.53.64.105 X (ns1.jpmorganchase.com)
mail.google.com 74.125.228.86 iad23s07-in-f22.1e100.net
mail.live.com 65.55.237.103 origin.bl156w.[...].mail.live.com
mail.yahoo.com 98.139.237.162 l2.login.vip.bf1.yahoo.com
messenger.yahoo.com 98.139.200.98 myc1.msg.vip.bf1.yahoo.com
www.microsoft.com 64.4.11.42 X (msnhst.microsoft.com)
www.nationwide.co.uk 155.131.31.83 www.nationwide.co.uk
www.networksolutions.com 205.178.187.13 www.networksolutions.com
www.newegg.com 204.14.213.185 X (pdns1.ultradns.net)
online.wellsfargo.com 159.45.2.71 online.wellsfargo.com
www.orange.fr 193.252.148.241 vip1.dyn.hpo.s1.fti.net
partner.googleadservices.com 74.125.228.13 iad23s05-in-f13.1e100.net
www.rbs.co.uk 155.136.80.222 X (ns0-08.dns.pipex.net)
www.schwab.com 162.93.228.34 schwab.co.uk
search.yahoo.com 72.30.186.176 gsp2.syc.searc[...].ac2.yahoo.com
www.sears.com 72.247.209.99 a72-247-209-99.[...]echnologies.com
smartzone.comcast.net 68.87.26.168 hprxy.westchest[...]ail.comcast.net
www.smithbarney.com 192.193.224.59 X (ns.citicorp.com)
thepiratebay.org 194.71.107.50 X (ns0.thepiratebay.org)
www.thepiratebay.org 194.71.107.50 X (ns0.thepiratebay.org)
www.ticketmaster.com 72.247.196.199 a72-247-196-199[...]echnologies.com
www.torproject.org 86.59.30.40 nova.torproject.org
www.twitpic.com 50.23.200.230 50.23.200.230-s[...]e.softlayer.com
www.twitter.com 199.59.150.39 r-199-59-150-39.twttr.com
us.etrade.com 12.153.224.21 us.etrade.com
www.usbank.com 170.135.216.181 cdo.usbank.com
www.verisign.com 69.58.181.89 www-ilg.verisign.net
www.visa.com 72.247.209.100 a72-247-209-100[...]echnologies.com
www.wamu.com 159.53.62.63 X (ns1.jpmorganchase.com)
www.wellsfargo.com 151.151.88.133 www.wellsfargo.com
westernunion.com 206.201.227.250 wumt1.westernunion.com
windowsupdate.microsoft.com 65.55.27.220 X (msnhst.microsoft.com)
wireless.att.com 135.209.168.22 origin-b2b-al[...]eless.att.com
www.yahoo.com 98.139.183.24 ir2.fp.vip.bf1.yahoo.com
www.youtube.com 74.125.228.66 iad23s07-in-f2.1e100.net
20 popular names have a mild anomaly. The ownership suggested by the reverse name lookup does not match our understanding of the original name. The most likely cause is the site's use of a Content Delivery Network. Show all names.Name IP Address Reverse Name/SOA
www.alliance-leicester.co.uk 194.130.105.121 X (ns1.ioko.com)
www.barclays.co.uk 89.167.225.172 172-225-167-89[...]etexchange.net
bit.ly 69.58.188.39 X (ns1.verisign-grs.net)
www.cnn.com 157.166.240.11 X (ns1.timewarner.net)
www.deutsche-bank.de 160.83.8.79 deutschebank.tec.db.com
www.e-gold.com 24.173.168.101 rrcs-24-173-16[...].se.biz.rr.com
www.lloydstsb.com 141.92.130.226 X (ns0.bt.net)
www.mbna.com 206.17.87.35 X (xbru.br.ns.els-gms.att.net)
www.mbna.net 63.236.19.66 X (ns0.teb.qwest.net)
www.meebo.com 74.114.28.110 domain.not.configured
www.nordea.fi 92.43.121.130 X (ns01.tdchosting.dk)
online.citibank.com 184.28.208.106 a184-28-208-106[...]echnologies.com
www.paypal.com 23.54.210.234 a23-54-210-234.[...]echnologies.com
www.postbank.de 160.83.4.4 X (ns2.db.com)
www.secureworks.com 216.52.89.170 X (ns1.nym.pnap.net)
www.sparkasse.de 212.34.69.3 rev-212.34.69.3.rev.izb.net
www.tdameritrade.com 72.247.215.5 a72-247-215-5.d[...]echnologies.com
tinyurl.com 64.62.243.92
www.trendmicro.com 173.222.201.214 a173-222-201-21[...]echnologies.com
www.wachovia.com 159.45.2.100 mn2-wachovia-p[...]wellsfargo.com
4 popular names have a mild anomaly: we are unable to find a reverse name associated with the IP address provided by your ISP's DNS server. This is most likely due to a slow responding DNS server or misconfiguration on the part of the domain owner. Show all names.Name IP Address Reverse Name/SOA
www.bankofthewest.com 204.44.2.241 X
www.bing.com 24.143.194.27 X
www.irs.gov 24.143.194.43 X
www.sterlingsavingsbank.com 12.69.145.232 X

DNS lookups of popular domains (?): OK + DNS external proxy (?): OK +Your host ignores external DNS requests.
DNS external proxy (?): OK + DNS results wildcarding (?): OK +Your ISP correctly leaves non-resolving names untouched.
DNS results wildcarding (?): OK + DNS-level redirection of specific sites (?): OK +Your ISP does not appear to be using DNS to redirect traffic for specific websites.
DNS-level redirection of specific sites (?): OK + Direct probing of DNS roots (?) +We checked which DNS root server instances your computer can reach. All root servers responded. Show them.Name IP Address Reported Name
a.root-servers.net 198.41.0.4 ans10-nyc3
b.root-servers.net 192.228.79.201 b1
c.root-servers.net 192.33.4.12 jfk1b.c.root-servers.org
d.root-servers.net 128.8.10.90 css-d.net.umd.edu
e.root-servers.net 192.203.230.10 e3.arc.nasa.gov
f.root-servers.net 192.5.5.241 pao1a.f.root-servers.org
g.root-servers.net 192.112.36.4 g.root-servers-pac2-2.net
h.root-servers.net 128.63.2.53 H3
i.root-servers.net 192.36.148.17 s1.bnx
j.root-servers.net 192.58.128.30 jluepe1-ellju1
k.root-servers.net 193.0.14.129 k2.linx.k.ripe.net
l.root-servers.net 199.7.83.42 lax12.l.root-servers.org
m.root-servers.net 202.12.27.33 M-NRT-JPIX-1

Direct probing of DNS roots (?): + IPv6 Tests + + – – DNS support for IPv6 (?): OK +Your system does not look up IPv6 addresses by default. Your DNS resolver is not on Google's IPv6 "whitelist", which means that Google does not enable IPv6 access to their services for you.
DNS support for IPv6 (?): OK + IPv4, IPv6, and your web browser (?): No IPv6 support +Your browser was unable to fetch a test image from an IPv6-only server. IPv4 performance to our IPv4-only server did not differ substantially from our IPv4/IPv6 dual-stacked one.
IPv4, IPv6, and your web browser (?): No IPv6 support + IPv6 connectivity (?): No IPv6 support +Your system appears to have no IPv6 connectivity as it was unable to look up the IPv6 address associated with our IPv6 test server.
IPv6 connectivity (?): No IPv6 support + Host Properties + + – – System clock accuracy (?): Warning –Your computer's clock is 6 seconds slow. System clock accuracy (?): Warning +
Browser properties (?): OK +Your web browser sends the following parameters to all web sites you visit:User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.3; .NET4.0C; .NET4.0E)Accept: application/x-ms-application, image/jpeg, application/xaml+xml, image/gif, image/pjpeg, application/x-ms-xbap, */*Accept Language: en-USAccept Encoding: gzip, deflateAccept Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7Java identifies your operating system as Windows 7.
Browser properties (?): OK + Uploaded data (?): OK +The applet uploaded the following additional content: apache_404custom_404plain_404raw_http_contentupnp_0_descrupnp_0_details
Uploaded data (?): OK

interestor

join:2013-01-17
update: Thought I'd tether the cellphone to the computer. Dramatic increase in speed. Couldn't run speedtest, but downloads went up to 1.5mbps. What is that, 10,000 faster?

Then I thought I'd reset the cable modem. Unplugged it for several minutes. Downloads were faster than before, though slower than the phone. Speedtest says 1.5Mbps down 4Mbps up.


hobgoblin
Sortof Agoblin
Premium
join:2001-11-25
Orchard Park, NY
kudos:11
I really cant read all that.

Hob

scififan68

join:2010-10-02
Fremont, NE

2 edits
reply to interestor
You have issues, I did tracert to your ip and the ping spiked up to 1.5-2 seconds, so obviously TWC may be having an issue in your area.

10 70 ms 79 ms 59 ms ae-5-1.cr0.chi30.tbone.rr.com [66.109.6.112]
11 211 ms 214 ms 206 ms ae-0-0.cr0.chi10.tbone.rr.com [66.109.6.20]
12 154 ms 181 ms 124 ms 107.14.19.35
13 85 ms 74 ms 62 ms 107.14.17.172
14 129 ms 230 ms 244 ms 66.109.6.79
15 246 ms 279 ms 201 ms bun6-nycmnytg-rtr001.nyc.rr.com
16 83 ms 80 ms 93 ms bun116.nycmnys-rtr02.nyc.rr.com
17 2427 ms 2180 ms 1516 ms tenge18-10-nycmnys-c401a.nyc.rr.com ----- 2 seconds.
18 272 ms 228 ms 195 ms cpe-24-XXX-XXX-XX.nyc.res.rr.com

EDIT:
As of 4:51am EST:

10 30 ms 31 ms 33 ms ae-5-1.cr0.chi30.tbone.rr.com [66.109.6.112]
11 64 ms 63 ms 63 ms ae-0-0.cr0.chi10.tbone.rr.com [66.109.6.20]
12 64 ms 63 ms 63 ms 107.14.19.35
13 62 ms 63 ms 63 ms 107.14.17.172
14 59 ms 63 ms 63 ms 66.109.6.79
15 64 ms 60 ms 63 ms bun6-nycmnytg-rtr001.nyc.rr.com
16 57 ms 56 ms 60 ms bun116.nycmnys-rtr02.nyc.rr.com
17 62 ms 79 ms 89 ms tenge18-10-nycmnys-c401a.nyc.rr.com
18 68 ms 68 ms 69 ms cpe-24-XXX-XXX-XX.nyc.res.rr.com

interestor

join:2013-01-17
Thanks for looking into it scififan, I appreciate that.

Hmmm, where should I look to see if others in the area, or even this same building, are having a similar slowdown? What can be done about this?

nephipower

join:2012-02-20
San Antonio, TX
said by interestor:

Thanks for looking into it scififan, I appreciate that.

Hmmm, where should I look to see if others in the area, or even this same building, are having a similar slowdown? What can be done about this?

Have you tried calling TWC tech support? Really what you need is to have a tech come out and that isn't going to happen unless you call them.

megaghost86

join:2009-04-24
San Francisco, CA
reply to interestor
I'm in Bushwick and use TWC and have the same problem and same exact DL/UL speeds. Must be an area thing.


fatal

join:2000-12-29
Brooklyn, NY
all good in 11220


HFCNUT82

join:2007-12-13
reply to interestor
I agree with scififan68 on this one.

Looking at the trace scififan68 provided shows the issue is more than likely not on the coax distribution side of their network (Field issue). The hop that spikes to almost 2 seconds appears to be referring tot he Tengig port on the CMTS chassis.

17 2427 ms 2180 ms 1516 ms tenge18-10-nycmnys-c401a.nyc.rr.com ----- 2 seconds.
18 272 ms 228 ms 195 ms cpe-24-XXX-XXX-XX.nyc.res.rr.com

The hop after that is your PC/CPE and since the there is no further layer 3 devices between the CMTS and you then it is more than likely an issue with that port based on the response times. It could be utilization at peak hours or a faulty connection but if it increases, then you would need to call them and explain to them where on your trace you are seeing the spikes. If you notice latency, run a trace just to verify since the trace done by scififan68 is him coming into the local network there and you want to prove that this is showing up on outbound traces as well.

Good luck

interestor

join:2013-01-17
reply to interestor
Thanks for the detail there.

And, you can't really call twc... But I did email the social media reps and a technician is coming over tomorrow (sunday).

I'll post what is found, for other brooklanders. I am 11218 btw.

tymoney321

join:2007-04-08
Flushing, NY
reply to interestor
tenge18-10-nycmnyk-c404.nyc.rr.com & the cpe one have been giving me trouble for months. They just keep wasting my time with local techs.