I had posted earlier about verio looking like the are dropping packets… I am still having major major issues and verio is showing about a 5% packet loss. I would think even at 5% I shouldn’t have to retry a page 2, 3, or even 4 times.
Even just maneuvering in the forum or entering this post is taking multiple tries.
Does a 5% loss cause as much havoc as I am getting?
Can’t email reliably, can’t get to the website reliably, just plain miserable.
Thoughts?
5% ploss is not good, but should not be THAT bad either.
We have one server with an issue now, but it is not in any way effecting this server, and I am browsing around fine here.
Yea… I hooked up to my home computer and it uses a different route with NO PROBLEMS at all.
I swear I want to say Jodo has a problem, but my commen sense and IT background says it can’t be when I have it working great on one route, but fails miserably from another route.
The problem is I am on the failing route every single day, day in and day out, and several of my customers are also on that route… so things are not pretty on this end.
I just can’t believe 5% would kill us like this.
How the heck can I get in touch with verio and find out what is going on? Why can they not fix the problem??? Are they really that piss poor that they can’t resolve problems?
I will send internap yet another complaint, that winmtr was very useful last time, can you do that again, and either save a screenshot of it as jpg/bmp or html, then zip it and attach to the forums?
I can send more as I build them… the problem is that simple ping / icmp with 32 or 64 bytes sent at 2 second intervals is NOT the same as loading up web sites loading at full speed.
I am dugin another one with faster requests and a little larger sizes and it is unbelievable. Here is just a quick one. By the way, can I put HTML in here? It would probably help with lining it up.
Here you go:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
no, can’t do HTML.
Why don’t you make a place on your personal site with the DNN blog, then give me the last portion of where to find the html files, I will grab them all there and send over.
They link them well formatted as well, you can also email them to me, where you can use HTML mail, stephen @ jodohost.com
Email on the way.
Let me know when you get it… to make sure it get’s through.
Just sent you another… will post here just in case it doesn’t get through. It’s getting worse:
|[FONT=“Courier New”]------------------------------------------------------------------------------------------|
| WinMTR statistics |
5% would not make browing too bad, but that 70% sure will!
I got the mail and have sent them off already.
I notice the packetloss is starting early, have you tried restarting the local router/modem/dsu?
It starts with a slight loss outside of our immediate control. I have COX doing some checking on their end as well since their last hop starts to looking bad as well.
Greg
Well… we are not having the disconnects or having to retry over and over and over at this point, but we are still seeing packet loss.
However I have a question. Using the WinMTR at 1/2 second intervals of 1024 bytes we get the loss shown below. Between 40 and 60 percent. But when using another program called NeoTrace I am seeing much less with the same data size. I assume the programs must be using a different method. I don’t know if one is using ICMP and the other just using any sort of data packet or why they differ. Anyone with a more detailed explanation on this?
Verio sucks:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
Stephen, I don’t know what to trust now. I have tested 4 tracert/ping programs. Some use ICMP some use UDP and some use a combination.
The WinMTR is the only one showing massive loss… but Visual Trace Route, NeoTrace, and 3d Traceroute are all showing good… with maybe a 1% loss on one hop. And today everything is much smoother.
I wonder why WinMTR would show such a loss and not the other 3. Very strange. Not that I am complaining… having what appears to be a reliable link from a usage standpoint is great. Cox definitely had issues they said and I think Verio did as well. We had another link issue that went through Verizon and they have responded that they had issues as well. That is 3 backbone providers that we happen to go through a lot having issues all at the same time. Arghhh!
I’ve been passing traceroutes to Tanmaya via email the last week or so and for me, in the UK, verio is being rather unreliable. One hop within their network in particular is showing 10% packetloss regularly and quite often even higher. My ISP are being next to useless but Jodohost have been really good and whilst I still have a problem with my routing through verio they are at least working to resolve the issue and keeping me updated 
[QUOTE=Padwah]
I’ve been passing traceroutes to Tanmaya via email the last week or so and for me, in the UK, verio is being rather unreliable. One hop within their network in particular is showing 10% packetloss regularly and quite often even higher. My ISP are being next to useless but Jodohost have been really good and whilst I still have a problem with my routing through verio they are at least working to resolve the issue and keeping me updated 
[/QUOTE]
Yes, jodo has always been helpful in passing along this info to the backbone providers. Unfortunately you are right about the loss of packets with Verio. I personally can’t stand that company, because they have had these issues on and off form months. Usually I experience slow downs verses not being able to connect. Either way… not good.
What are you using for your traceroutes?
Padwah,
Yes, we have one other ticket about Verio issues. (for 3 total + tons of updates)
Greg,
We use WinMTR because it is what the backbones use for their stats, it is the one they ask us for. They actually start getting impressed when we just by default send in MTR charts now, instead of a simple tracert.
MTR uses large amounts of larger packets, and it will indeed show major problems “better” than the others because of that, it is why the backbones like it, they know in short order where the problem lies. However Verio, I have spoken with on the phone, and sent emails to their NOC, I don’t think they care, this is very bad. Today all reports go direct to internap, and I hope if verio does not get their act together they will quit peering with them, as they are causing a major headache.
My opinion… they need to dump Verio if it is within Internap’s control to do so… but then would the grass really be greener on the other side or would it get worse.
Oh well… I know there’s nothing I can do, but hopefully there will be enough complaints in total to make some changes.
Thank you for your efforts.
Oh… is there anything we can do as individuals?
email your complaints (please make sure they include MTR charts or valid traceroutes showing the issue) to [email protected]
Also if cox is not dropping packets this time it will help, as I got a rpely yesterday saying to go to the ISP, it is dropping packets too early(just an excuse)
Cheers stephen,
WHat size packets does WinMTR send? I use ping plotter with it set to use 128 or 256 byte packets, can’t remember off the top of my head what I’ve got it set to.