Start.ca → Re: 50% Packet loss for toronto.voip.ms

I would try something like 1000 (or more) pings to your router (192.168.1.1) first and see that 100% get a reply, as Rocca mentioned once you have one "bad" hop the rest of the results (following that hop) are meaningless, so you really want to rule out the router first. If you are using WiFi keep in mind that you are susceptible to interference.

+1

Getting one good trace that only hit the first hop 3 times isn't a good indication of where the problem is, particularly as an earlier one showed that you did have a problem at hop 1. Do a "ping -n 1000 192.168.1.1" ...if you lose a single packet out of that then you have a problem between your computer and router, or you have a problem with the router.

Are you connected wired or wireless to your router?

Can you also download »winmtr.net/download-winmtr/ and let it run for at least 10 minutes, then post the results? (or preferably email the html file to me since it's hard to read the textized version.

What we're trying to determine is really where the first hop with loss is. The traceroutes and pings show conflicting information so we need something more complete to get an accurate idea.

Please make sure you are not running any other downloads or other computers through that router at the time. What we really need for testing is to go direct to the modem, but we'll skip that for now.

Thanks.

Hi rocca,

For the last several days at least, connections are always wired to the router. I just finished the WinMTR test on toronto2. I had to quit at 500 packets, can't wait until 1000 as I had to do something else. Attached is the text results. I will email the HTML file to you via Start support.

Thanks, as an attachment here is good.

That shows zero loss (ie no problem at this time), when you're experiencing the problem please run it again and post the results.

As others have mentioned, you may also want to try one of their other servers too as toronto.voip.ms seems to have frequent issues.

i can say i been having issues with toronto.voip.ms and toronto2.voip.ms

i have a open ticket with them trying to resolve the issue.

Just an FYI, this may not be the issue, but the voip toronto servers are terrible, I'd switch to something else and see if you continue to see the problem

i have switched, but i figured i would tell them but they told me.

they had no other reports and everything looks fine on there end.

only thing i can think of is maybe and issue with the data centers link to Hurricane Electric.
if the guys at voip.ms don't pass through HE then they wouldn't see the problem.

just a thought.

traceroute to toronto.voip.ms (199.21.149.36), 30 hops max, 60 byte packets
1 64.140.114.1 (64.140.114.1) 0.280 ms 0.323 ms 0.417 ms
2 v514.core1.tor1.he.net (216.66.0.53) 3.808 ms 3.855 ms 3.954 ms
3 yesup-ecommerce-solutions-inc.10gigabitethernet1-1.core1.tor1.he.net (216.66.70.14) 1.454 ms 1.456 ms 1.457 ms
4 C3R2.YesUP.com (166.48.160.12) 1.456 ms 1.456 ms 1.456 ms
5 199.21.149.36 (199.21.149.36) 1.543 ms 1.546 ms 1.546 ms

...path looks pretty good, if yesup.com (their ISP) peers at TorIX then even better but I don't think it's related to HE since it looks like a local hand-off.

im using montreal.voip.ms now and it has been fine ..also i did notice that it passes through HE to, so i guess HE is fine then