3 edits |
[VoIP] Ping élevé avec montreal3.voip.msJ'ai présentement un ping de 30ms avec montreal3.voip.ms. La dernière fois que j'ai vérifié j'avais 11ms.
Avec toronto3.voip.ms c'est 50ms, normalement c'est 18ms.
Il y a présentement un problème, on passe par Los Angeles pour aller à Montréal? |
|
| |
iamhere
Member
2014-Jul-27 11:56 am
HOST: raspbx Loss% Snt Last Avg Best Wrst StDev
1.|-- tomato 0.0% 10 0.8 0.7 0.6 0.9 0.1
2.|-- dsl.e120.electronicbox.net 0.0% 10 8.6 8.8 8.6 9.7 0.3
3.|-- dsl-mx480.electronicbox.net 0.0% 10 27.3 26.7 8.4 43.6 11.4
4.|-- 10ge3-1.core1.ymq1.he.net 0.0% 10 16.3 15.5 8.4 55.5 14.5
5.|-- 10ge14-4.core1.nyc4.he.net 0.0% 10 20.8 23.2 20.0 28.9 3.2
6.|-- 10ge3-1.core1.nyc6.he.net 0.0% 10 49.8 28.4 20.7 49.8 8.6
7.|-- Assigned23.nyiix.net 0.0% 10 25.9 35.5 25.9 76.9 18.6
8.|-- po23.cr4.mtl.iweb.com 0.0% 10 26.9 40.1 26.0 112.4 29.4
9.|-- te9-4.dr5.mtl.iweb.com 0.0% 10 30.1 31.7 26.4 43.1 6.3
10.|-- 72.55.168.18 0.0% 10 26.7 28.6 26.4 41.1 4.5
Possible routing issue? Wonder why it goes to NYC before returning to Montreal. |
|
 Nitra
join:2011-09-15
Montreal |
Nitra
Member
2014-Jul-27 12:04 pm
Some peers are like that, especially if they're not peered at QIX. |
|
| |
Exiled
Member
2014-Jul-27 4:30 pm
latencyThe route to iweb was direct not too long ago. It's only recently that latency went up. |
|
Nitra
join:2011-09-15
Montreal |
Nitra
Member
2014-Jul-27 5:20 pm
It seems iweb was/is connected to QIX, but it's not a full connection which is why the routing change. |
|
| |
to LanAdmin
Re: [VoIP] Ping élevé avec montreal3.voip.msEverything looks fine here on FTTH
**********
C:\Users\>ping montreal3.voip.ms
Pinging montreal3.voip.ms [72.55.168.18] with 32 bytes of data:
Reply from 72.55.168.18: bytes=32 time=3ms TTL=52
Reply from 72.55.168.18: bytes=32 time=4ms TTL=52
Reply from 72.55.168.18: bytes=32 time=4ms TTL=52
Reply from 72.55.168.18: bytes=32 time=4ms TTL=52
Ping statistics for 72.55.168.18:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 4ms, Average = 3ms
***************
C:\Users\>tracert montreal3.voip.ms
Tracing route to montreal3.voip.ms [72.55.168.18]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms router.asus.com [192.168.1.1]
2 28 ms 12 ms 2 ms 10.11.16.137
3 * 2 ms 2 ms 10.178.206.136
4 2 ms 3 ms 2 ms 10.178.206.137
5 5 ms 4 ms 3 ms tcore3-montreal01_0-0-0-5.net.bell.ca [64.230.36
.112]
6 2 ms 2 ms 2 ms bx4-montrealak_xe2-0-0_0.net.bell.ca [64.230.32.
145]
7 2 ms 2 ms 2 ms ix-0-1-1-0.tcore2.MTT-Montreal.as6453.net [216.6
.114.37]
8 8 ms 10 ms 6 ms if-0-2.tcore1.MTT-Montreal.as6453.net [216.6.115
.89]
9 3 ms 3 ms 6 ms 64.86.31.42
10 3 ms 3 ms 6 ms ae31.cr6.mtl.iweb.com [184.107.1.254]
11 3 ms 3 ms 3 ms po22.cr4.mtl.iweb.com [184.107.1.122]
12 9 ms 8 ms 5 ms te9-4.dr5.mtl.iweb.com [184.107.1.50]
13 4 ms 3 ms 4 ms 72.55.168.18
Trace complete.
Good luck. |
|
| |
You mean FTTN right?
Looks like either you are using a VPN or you aren't on the Ebox network. |
|
| |
no, im not on EBOX. it's FTTH over Bell. just wanted to let you see the difference of TraceRoute |
|
 JEDI
join:2005-04-11
Longueuil |
to LanAdmin
Même problème pour moi, j'ai les mêmes pings que LanAdmin. |
|
|
| |
to demonte21
Well, that's not relevant at all.
When it comes to this sort of thing you need to compare apples to apples, not apples to oranges. |
|
Nitra
join:2011-09-15
Montreal |
to JEDI
Videotron;
Tracing route to 72.55.168.18 over a maximum of 30 hops
1 1 ms 1 ms 1 ms ROUTER [192.168.17.254]
2 * * * Request timed out.
3 12 ms 10 ms 11 ms 216.113.122.9
4 8 ms 7 ms 12 ms 216.113.122.154
5 11 ms 7 ms 8 ms 64.86.31.42
6 10 ms 9 ms 11 ms ae31.cr6.mtl.iweb.com [184.107.1.254]
7 191 ms 20 ms 9 ms po22.cr4.mtl.iweb.com [184.107.1.122]
8 10 ms 8 ms 8 ms te9-4.dr5.mtl.iweb.com [184.107.1.50]
9 8 ms 10 ms 9 ms 72.55.168.18
Trace complete.
OVH
Tracing route to 72.55.168.18 over a maximum of 30 hops
1 1 ms * * 192.95.x.x
2 2 ms 2 ms 2 ms bhs-g2-6k.qc.ca [198.27.73.19]
3 * * * Request timed out.
4 9 ms * 9 ms nyk-5-6k.ny.us [178.32.135.58]
5 9 ms 9 ms 9 ms Assigned23.nyiix.net [198.32.160.23]
6 17 ms 17 ms 17 ms po23.cr4.mtl.iweb.com [67.205.127.117]
7 156 ms 30 ms 18 ms te9-4.dr5.mtl.iweb.com [184.107.1.50]
8 17 ms 17 ms 17 ms 72.55.168.18
Trace complete. |
|
| |
to iamhere
well both oranges and Apple are fruit... Both Bell and ElectronicBox are ISP right? |
|
Nitra
join:2011-09-15
Montreal |
Nitra
Member
2014-Jul-27 8:11 pm
Perhaps you should ask iweb what's up with their peer at QIX. |
|
| |
to demonte21
Brilliant logic.  Someone taking the bus downtown would to take the same route from the south end of the city and the east end of the city? After all, they are going to end up in the same place and they are both taking buses. Has to be the same bus. |
|
| |
Haha, agree |
|
| |
noiiwebqix to Nitra
Anon
2014-Jul-27 11:30 pm
to Nitra
Iweb never turned up their QIX connection at all. If anything their customers should ask that they should. They initially appeared to wish to become members but then were bought by Internap (?) and it never got turned on.
So this ebox issue is unrelated to QIX, but had iWeb peered there like OVH does we would not be having this discussion. IWeb/voip.ms customers: ask iWeb to get their peering up at QIX! |
|
3 edits |
for what it's worth, i've just sent a request for a new feature on voip.ms site, asking that they use QIX for peering their Montreal servers. » www.voip.ms/m/features.php» www.qix.ca/en/members/membershipTeksavvy-> vCable mtr -rw montreal3.voip.ms
Start: Mon Jul 28 08:58:44 2014
HOST: dt Loss% Snt Last Avg Best Wrst StDev
1.|-- pfcable.lan 0.0% 10 0.3 0.4 0.2 0.5 0.0
2.|-- 10.245.179.1 0.0% 10 7.9 8.1 7.1 9.8 0.5
3.|-- 10.170.180.169 0.0% 10 9.2 10.1 8.2 12.7 1.4
4.|-- xe-0-1-1_0-bdr01-mtl.teksavvy.com 0.0% 10 10.1 10.7 8.9 13.6 1.1
5.|-- xe-1-1-0_2210-bdr04-tor.teksavvy.com 0.0% 10 16.1 17.5 15.9 23.1 2.1
6.|-- gw-iweb.torontointernetxchange.net 0.0% 10 18.1 16.5 14.5 18.1 0.9
7.|-- ae21.cr6.mtl.iweb.com 0.0% 10 23.8 24.3 23.4 25.4 0.5
8.|-- po22.cr4.mtl.iweb.com 0.0% 10 24.0 24.9 23.2 31.6 2.4
9.|-- te9-4.dr5.mtl.iweb.com 0.0% 10 26.1 31.5 22.6 81.4 17.8
10.|-- 72.55.168.18 0.0% 10 25.2 24.8 23.3 26.3 0.7
mtr -rw toronto1.voip.ms
Start: Mon Jul 28 09:00:06 2014
HOST: dt Loss% Snt Last Avg Best Wrst StDev
1.|-- pfcable.lan 0.0% 10 0.3 0.4 0.3 0.6 0.0
2.|-- 10.245.179.1 0.0% 10 7.6 8.3 7.0 10.7 1.1
3.|-- 10.170.180.169 0.0% 10 9.3 9.6 8.3 11.1 0.7
4.|-- xe-0-1-0_0-bdr01-mtl.teksavvy.com 0.0% 10 9.9 9.9 8.8 12.7 1.2
5.|-- xe-1-1-0_2210-bdr04-tor.teksavvy.com 0.0% 10 15.2 16.4 14.4 18.3 1.2
6.|-- te0-7-0-22.ccr21.yyz02.atlas.cogentco.com 0.0% 10 16.4 17.3 15.4 19.5 1.2
7.|-- be2373.ccr22.yyz02.atlas.cogentco.com 0.0% 10 20.7 18.6 16.6 20.7 1.2
8.|-- 38.104.251.246 0.0% 10 16.2 17.3 15.1 21.1 1.5
9.|-- 184-75-215-106.amanah.com 0.0% 10 18.3 18.7 16.2 20.9 1.3
|
|
zadigre
Premium Member
join:2006-10-02
Montreal, QC |
zadigre
Premium Member
2014-Jul-28 9:17 am
said by ocnR8qQt:for what it's worth, i've just sent a request for a new feature on voip.ms site, asking that they use QIX for peering their Montreal servers.
»www.voip.ms/m/features.php
Teksavvy-> vCable even if they peer with Qix, it won't change anything for you since you are on Teksavvy... and essentially, you are getting you Internet "feed" through Teksavvy's network in Ontario. |
|
| zadigre |
to LanAdmin
said by LanAdmin:J'ai présentement un ping de 30ms avec montreal3.voip.ms. La dernière fois que j'ai vérifié j'avais 11ms.
Avec toronto3.voip.ms c'est 50ms, normalement c'est 18ms.
Il y a présentement un problème, on passe par Los Angeles pour aller à Montréal? est-ce que tu as le même résultat avec les autres serveurs (montreal, montreal2 à 4)? Je ne suis pas avec EBox... mais sur le fournisseur actuel où je suis (Maskatel à St-Hyacinthe.. qui utilise un feed Vidéotron), les traceroute pour tous les serveurs sont exactement les même. Pas mal le même traceroute que j'ai chez moi avec Vidéotron. Vidéotron à un peering direct avec Iweb... donc ça peut expliquer la situation. Par contre pour EBox, ça risque d'être différent d'un serveur à l'autre. |
|
 hsheriff
join:2012-09-04
Saint-Lambert, QC |
to zadigre
IIRC, teksavvy has recently moved vcable users to their own Montreal Pop and peering with QIX is direct. Its just that they don't buy transit in Montreal. |
|
zadigre
Premium Member
join:2006-10-02
Montreal, QC |
zadigre
Premium Member
2014-Jul-28 10:32 am
said by hsheriff:IIRC, teksavvy has recently moved vcable users to their own Montreal Pop and peering with QIX is direct. Its just that they don't buy transit in Montreal. oh that's good... I didn't know that! |
|
| |
since Teksavvy and OVH also peer at QIX it only takes 12ms instead of 24ms to connect to the OVH Montreal servers, iweb is just a block away from OVH Montreal so i'm expecting the same result when/if they peer at QIX. » www.qix.ca/en/members/membership |
|
| |
noiiwebqix
Anon
2014-Jul-28 11:37 am
IWeb QIX plans I suspect are on hold and possibly forgotten since they were acquired.
If you are a iWeb customer and are with any ISP I suggest you make it known to them that QIX connectivity and local peering is important to you. OVH has understood that and has established a solid footprint at many IXs. Its a shame that iWeb is forcing its customer traffic to go over transit and often to the US and back in a world where privacy/snooping is becoming more of a concern. And of course lower latency and delivery reliability is always very important as well. |
|
| |
As I said, it's a recent EBOX transit problem. It used to be 11ms for Montreal and 18ms for Toronto. It's now 30ms and 50ms. |
|
 diskaceRetired
Premium Member
join:2002-02-21 |
diskace
Premium Member
2014-Jul-28 8:33 pm
We dropped Peer1 late June after Cogeco acquisition, probably the reason but i can't recall what was the path. It would definitely help if Iweb peer at QIX so all their clients would have better latency where Ebox is present. |
|
hsheriff
join:2012-09-04
Saint-Lambert, QC |
Found some older traceroutes where it was going through cogent here: » [DSL] Routing Issues?If my memory serves me it used to go through cogent for me as well until HE was added on. |
|
 ohmer
join:2003-08-06
Quebec, QC |
to LanAdmin
Tu peux réduire ton ping avec voip.ms en utilisant les serveurs de Toronto. J'ai 18ms de ping vers Toronto et 28ms vers Montréal à cause qu'on se paye un aller-retour inutile vers NY.
Je suis surpris que le traceroute depuis Bell ne fasse pas ce même A/R. J'avais l'impression que Bell faisait son peering pratiquement uniquement depuis les USA.
Personnellement, je n'ai pas fait le switch, je ne pense pas que ça vaille la peine de reconfigurer mon ATA et ma boîte vocale pour gagner 10ms. Passer par les USA me bogue un peu, m'enfin.
Je comprends la décision d'affaire de retirer Peer1 étant donné que ça devenait un concurrent direct depuis l’acquisition par Cogeco mais c'est dommage de perdre ce bon peer pour le trafic national. |
|
| |
Mon voisin a vidéotron, j'ai fais le test chez lui, et ca roulait en moyenne entre 30 et 35 ms sur montreal3.... sur FTTH bell fibe j'ai entre 3 et 4 MS. (50/50). toutefois j'utilise seulement montreal.voip.ms... car ca roule entre 2 et 3 ms, mais je ne crois pas que ca ferait une reel différence... |
|
diskaceRetired
Premium Member
join:2002-02-21 |
to ohmer
said by ohmer:Je comprends la décision d'affaire de retirer Peer1 étant donné que ça devenait un concurrent direct depuis l’acquisition par Cogeco mais c'est dommage de perdre ce bon peer pour le trafic national. C'est surtout une question de prix. Ils sont complètement déphasé par rapport au marché du transit IP même si tu achètes des 10 Gig de traffic. |
|
2 edits |
Ebox, vous avez un problème avec vos transits. (Aucun rapport avec le retrait de Peer1.) Après vérification à l'aide du Looking Glass de chacun des transits de Ebox, voici le ping vers montreal3.voip.ms: » www.electronicbox.net/a- ··· s-debox/4ms Tiscali » www.ip.tiscali.net/lg/ (mtl10: Montreal, CA) 9ms Cogent » www.cogentco.com/fr/netw ··· ng-glass (CA-Montreal) 9ms Nlayer » lg.nlayer.net/ (Montreal QC, CA MTL1) 24ms Hurricane Electric » lg.he.net/ (Cologix Montreal/CANIX 3) Le pire transit vers montreal3.voip.ms est Hurricane Electric et c'est le transit choisi par Ebox! |
|
