- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Download starts with full speed. then few seconds later it drops down to 50kb/s
If I connect to a VPN service and then download the same file the speed remains high and stable.
?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
there TOS says they don't, but that doesn't mean it's not a bad path, or a congested peering point.
you'd need a traceroute to upload.to and also from upload.to back to you to find out where.
If you can access your router, do the following, and you'll hopefully be working in 5 minutes.
Actiontec MI424-WR - RELEASE DHCP
Click on MY NETWORK icon at the top.
Select NETWORK CONNECTIONS from the menu on the left.
Select BROADBAND CONNECTION (coax or ethernet) depending on your connection to the ONT.
Click SETTINGS
Click RELEASE
Click APPLY
Disconnect the router immediately to prevent it from re-requesting a DHCP lease ---- wait 5 minutes, and turn it all back on and try again
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Also from my experience, those sites down't have a great upload speed to begin with, so double check their support forums for the max upload speeds to their servers and also check what their subscription rate is. If everyone is sending 50 mb uploads, there's a certain point where upload.to won't be able to accomodate everyone doing that. they may (likely) don't have the capacity at certain times of the day
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am actaully having a premium account with uploaded.to and never experienced this issue with my previous provider.
I just moved to verizon 2 weeks ago and since then I see this behaviour.
I have no download or upload limit to uploadet.to
I mean it`s odd to see that, but if I use a VPN service all is fine? Clearly Verizon is artificially slowing the speed towards their servers?
Tracert looks fine, it times out only on the 5th hops, everything is below 80ms.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Assuming the OP correctly notated his transfer rate as 50 kbps, this is only 0.05 Mbps which I doubt would overload any server or connection.
Also strange that using a VPN would make faster because the overhead of a VPN connection normally slows a connection by 10% - 50%.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That would only be clear if you had a reverse trace from upload.to, without that it's an inference
If you get that we can look at the trace's. might be a bad asymetric path, or bad load balancing.
Have you tried rebooting the ONT and or getting a new IP route via the method above?
It would actually be interesting seeing a trace with and without the vpn.
Comparing those two you could probably see where the issue is, what hop/router is being bypassed etc.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, I rebooted the ONT yesterday and released the DHCP / renew IPs 3 times since yesterday.
tracert without VPN
Tracing route to uploaded.to [81.171.123.200] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.5] 2 7 ms 7 ms 7 ms l100.nwrknj-vfttp-163.verizon-gni.net [108.35.14 .1] 3 10 ms 7 ms 10 ms g1-3-0-0.nwrknj-lcr-22.verizon-gni.net [130.81.2 23.174] 4 8 ms 9 ms 9 ms ae4-0.nwrk-bb-rtr2.verizon-gni.net [130.81.199.1 94] 5 * * * Request timed out. 6 8 ms 9 ms 9 ms 0.ae2.br2.nyc4.alter.net [140.222.229.93] 7 48 ms 35 ms 46 ms 204.255.168.174 8 52 ms 52 ms 52 ms 63.243.128.70 9 * * * Request timed out. 10 * * 51 ms if-3-2.tcore2.aeq-ashburn.as6453.net [216.6.87.9 ] 11 51 ms 52 ms 52 ms if-2-2.tcore1.aeq-ashburn.as6453.net [216.6.87.2 ] 12 51 ms 50 ms 50 ms 66.198.154.186 13 53 ms 53 ms 53 ms unknown.prolexic.com [209.200.144.159] 14 50 ms 48 ms 48 ms unknown.prolexic.com [209.200.144.111] 15 48 ms 47 ms 47 ms unknown.prolexic.com [209.200.144.77] 16 53 ms 53 ms 53 ms unknown.prolexic.com [209.200.144.35] 17 124 ms 126 ms 125 ms 209.200.172.118 18 121 ms 122 ms 121 ms 81.171.123.200 Trace complete.
tracert with VPN
Tracing route to uploaded.to [81.171.123.200] over a maximum of 30 hops: 1 46 ms 46 ms 44 ms speedtest.air [10.4.0.1] 2 * 43 ms 43 ms unknown-client.static.huge-dns.com [198.203.28.4 1] 3 43 ms 41 ms 42 ms core.jax.1.2.12.hugeserver.com [198.205.112.213] 4 43 ms 43 ms 41 ms ve103.e2-13.core-b.jcvnflcq.as19844.net [198.205 .127.13] 5 51 ms 53 ms 50 ms ae5-162.atl11.ip4.gtt.net [173.241.128.137] 6 89 ms 90 ms 93 ms as2914.atl11.ip4.gtt.net [173.241.130.98] 7 * 87 ms 90 ms ae-8.r20.asbnva02.us.bb.gin.ntt.net [129.250.5.2 14] 8 87 ms 86 ms 86 ms ae-1.r06.asbnva02.us.bb.gin.ntt.net [129.250.7.2 5] 9 66 ms 64 ms 67 ms be-30.r04.asbnva02.us.ce.gin.ntt.net [165.254.19 1.118] 10 77 ms 78 ms 78 ms unknown.prolexic.com [209.200.144.159] 11 76 ms 76 ms 74 ms unknown.prolexic.com [209.200.144.111] 12 78 ms 77 ms 79 ms unknown.prolexic.com [209.200.144.77] 13 66 ms 67 ms 68 ms unknown.prolexic.com [209.200.144.35] 14 156 ms 156 ms 842 ms 209.200.172.118 15 173 ms 157 ms * 81.171.123.200 16 157 ms 156 ms 156 ms 81.171.123.200 Trace complete.
dl speed without VPN at the beginning, i am on verizon fios 75/75
towards the end this happens, ALWAYS, it will drop down below 100kbs later on
dl speed with vpn at the beginning
towards the end
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
in the first trace, it's good in vz network but your latency comes at 204.255.168.174 which is verizon, from what I can tell. I did a who is and I get swipper
swipper@verizonbusiness.com and THEN it gets double as bad when it gets to your ISP.
I would email them and see if you get a response. OR try to open a chat or phone ticket. the MS times are so low they might not care, but that's the only indication I See in the tracert. THE PROBLEM with traceroutes, is that it measures round trip latency, but doesn't display round trip paths, it only shows you the forward paths, and that's why it's important to get the reverse traceroute, to see where the real problem is. the reverse trace will show paths that you don't even know exist, and may point to the real problem.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Follow up question, is it ever better one time of the day vs another?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hubrisnxs - what does releasing the DHCP do, and how would it speed up the connection?