- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Solved! Go to Correct Answer
Correct answers
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@oldtraveler wrote:I would be glad to report my (your) findings to Verizon. Who should I contact?
My best suggestion would be to report the issue to the Verizon Direct forum over at DSLReports. There are some pretty good employees in there which monitor the forums and answer threads.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
404-Not Found to that JPG file
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Just remove the dot at the end: http://philsden.com/tracert.jpg
What you're seeing is likely due to congestion during the evening hours. In general, it's hard to say right now who needs to get on the ball and add more bandwidth, whether it's Cogent or Verizon, but try running the traceroute in the early morning hours to see if things are improved. Speeds should be better, too. Since you're going from California to Boston, expect the latency to be around 80-100ms.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That tracert was done at about 6:30am pst. I just ran another one and got very similar results with one cogentco server timed out.
Isn't there someway to route this diffferently?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
A potential way to change your routing is to get your IP address changed. It was discovered by a pretty performance hungry customer in the LA area, that the routing can change depending on whether or not you have an even ending or an odd ending IP address. If you have an even number at the end of the final octet, try leaving your router powered off for a few hours overnight, and then power it back up to see if you get a different address.
If that isn't an option, I'd at least let Verizon support know if you haven't already. It's possible that if Cogent is having problems even at 6AM, and it isn't due to congestion, it's possibly a bad route all together. Verizon should be able to drop the route until it's fixed. Convincing someone that this can be done is going to take a bit of work, though.
Let's also not forget the return path, though. If you're able to, see if you can get a traceroute from the web server back to your connection. This will help show a potetial problem with perhaps, another transit provider that could be making Cogent look like the bad route.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you Smith 6612.
Today, so far, your suggestion that I turn off the router for a few hours has worked. Tracert has twice shown to server timeouts and the ftp client is working as it should. Hoping that this is a permanent fix.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Tracert has shown NO timeouts.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Glad to hear. Sounds like there's just a bad circuit somewhere in the backbone that needs attention. It wouldn't hurt to report your findings to Verizon, along with the solution so they can escalate the request to the people responsible for the backbone.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I would be glad to report my (your) findings to Verizon. Who should I contact?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@oldtraveler wrote:I would be glad to report my (your) findings to Verizon. Who should I contact?
My best suggestion would be to report the issue to the Verizon Direct forum over at DSLReports. There are some pretty good employees in there which monitor the forums and answer threads.