dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
1320
htothem
join:2013-08-27
Montreal, QC

htothem

Member

Ping/Jitter increase drasticly after 6 pm ACN

Hello everyone,
I am currently experiencing some really big changes in ping speed and quality depending on the time of the day. I play shooters and sports games, so ping is pretty important for me. My connection is FTTN 7/1 with ACN Canada.

I do a lot of testing using pingtest.net and ping -t in cmd. I also use tracert command.

So, when I get home mid-afternoon, my ping is really good. Below 30-35 with 1-2ms jitter to NY, below 40 and 1-2ms jitter to Chicago and so on. Everything works perfectly.

Later, every evenings, the ping go up and doesn't go back until late night/early morning.

This is some exemple of evening pingtest.net :
New York http://www.pingtest.net/result/85579515.png
Chicago http://www.pingtest.net/result/85579599.png
Toronto http://www.pingtest.net/result/85579661.png

And speedtest.net :

http://www.speedtest.net/my-result/2926150890
http://www.speedtest.net/my-result/2926152666
http://www.speedtest.net/my-result/2926153949

Ping -t on google.ca (my Windows is in french)

C:\Windows\system32>ping -t www.google.ca

Envoi d'une requête 'ping' sur www.google.ca [74.125.131.94] avec 32 octets de d
onnées :
Réponse de 74.125.131.94 : octets=32 temps=93 ms TTL=46
Réponse de 74.125.131.94 : octets=32 temps=97 ms TTL=46
Réponse de 74.125.131.94 : octets=32 temps=99 ms TTL=46
Réponse de 74.125.131.94 : octets=32 temps=99 ms TTL=46
Réponse de 74.125.131.94 : octets=32 temps=98 ms TTL=46
Réponse de 74.125.131.94 : octets=32 temps=93 ms TTL=46
Réponse de 74.125.131.94 : octets=32 temps=93 ms TTL=46
Réponse de 74.125.131.94 : octets=32 temps=73 ms TTL=46
Réponse de 74.125.131.94 : octets=32 temps=154 ms TTL=46
Réponse de 74.125.131.94 : octets=32 temps=147 ms TTL=46
Réponse de 74.125.131.94 : octets=32 temps=152 ms TTL=46
Réponse de 74.125.131.94 : octets=32 temps=143 ms TTL=46
Réponse de 74.125.131.94 : octets=32 temps=155 ms TTL=46
Réponse de 74.125.131.94 : octets=32 temps=151 ms TTL=46
Réponse de 74.125.131.94 : octets=32 temps=152 ms TTL=46
Réponse de 74.125.131.94 : octets=32 temps=148 ms TTL=46
Réponse de 74.125.131.94 : octets=32 temps=157 ms TTL=46
Réponse de 74.125.131.94 : octets=32 temps=144 ms TTL=46
Réponse de 74.125.131.94 : octets=32 temps=78 ms TTL=46
Réponse de 74.125.131.94 : octets=32 temps=87 ms TTL=46
Réponse de 74.125.131.94 : octets=32 temps=79 ms TTL=46
Réponse de 74.125.131.94 : octets=32 temps=97 ms TTL=46
Réponse de 74.125.131.94 : octets=32 temps=107 ms TTL=46
Délai d'attente de la demande dépassé.

Statistiques Ping pour 74.125.131.94:
Paquets : envoyés = 24, reçus = 23, perdus = 1 (perte 4%),
Durée approximative des boucles en millisecondes :
Minimum = 73ms, Maximum = 157ms, Moyenne = 117ms

Tracert to google.ca
C:\Windows\system32>tracert www.google.ca

Détermination de l'itinéraire vers www.google.ca [74.125.131.94]
avec un maximum de 30 sauts :

1 tracert www.yahoo.com

Détermination de l'itinéraire vers ds-any-fp3-real.wa1.b.yahoo.com [98.139.180.1
49]
avec un maximum de 30 sauts :

1 1 ms 1 ms 1 ms homeportal [192.168.1.254]
2 74 ms 78 ms 77 ms 64.111.81.15
3 73 ms 81 ms 75 ms 64.111.83.109
4 66 ms * 67 ms ae1-303.cr1.mtl1.ca.nlayer.net [69.31.142.21]
5 77 ms 74 ms 76 ms xe-10-1-0.cr1.nyc2.us.nlayer.net [69.22.142.109]

6 80 ms 81 ms * vlan-78.ar2.ewr1.us.nlayer.net [69.31.34.127]
7 145 ms 133 ms * equinixexchange-nyc.yahoo.com [206.223.131.16]
8 87 ms 91 ms 95 ms ae-2.pat1.bfz.yahoo.com [216.115.100.26]
9 91 ms * 92 ms ae-4.msr2.bf1.yahoo.com [216.115.100.73]
10 89 ms 154 ms * xe-2-0-0.clr2-a-gdc.bf1.yahoo.com [98.139.232.97
]
11 78 ms 84 ms 84 ms et17-1.fab7-1-sat.bf1.yahoo.com [98.139.128.89]

12 * 77 ms 75 ms po-10.bas2-7-prd.bf1.yahoo.com [98.139.129.163]

13 * 78 ms 80 ms ir1.fp.vip.bf1.yahoo.com [98.139.180.149]

Itinéraire déterminé.

Additional information :

Early July, I upgraded from 5/1 to 7/1 cause they told me it could help my problem. When I did, they had to send a new modem, so the one I'm using is less than 2 month old.

Mid-August they sent us a Bell technician to check the line and he made a "card" change in the poll of something like that. He told us he saw errors on the card. He also said the signal from the poll to our home is excellent. After that, it was a little bit better but nothing reasonably good.

All and all, my roommate and I have called their support at least 15 times in the last two months. They are very unhelpful and always seems to get angry when we want their help. They have lied a couple time on opening tickets, calling us back, etc.(Probably the worst customer service experience I have ever had). Changing ISP is not really an option.

Sorry for my english, hope someone can help me out.
Thanks.

Guspaz
Guspaz
MVM
join:2001-11-05
Montreal, QC

2 recommendations

Guspaz

MVM

ACN is a pyramid scheme... you really ought to avoid them.

creed3020
Premium Member
join:2006-04-26
Kitchener, ON

creed3020 to htothem

Premium Member

to htothem
I really hate to see how ACN changes people. It makes them think of friends and family of a network for their virus to spread further, all for personal gain. It's awful those that have been deceived by this scheme.

Furthermore if you have this many issues with their support lying to you then it's time to switch and watch the pyramid collapse.

Fraoch
join:2003-08-01
Cambridge, ON
SmartRG SR808ac
TP-Link EAP225
Grandstream HT502

Fraoch to htothem

Member

to htothem
Wow, I never knew...!

Just went to their website and came away with that sick feeling I got when I was a teenager looking for a job and attended a sales pitch/brainwashing session on selling Cutco knives...

Also this should be a great disincentive to anyone interested:

ACN has a reputation for success, success that’s really synonymous with the Trump name and other successful names, and you can be a part of it. - Donald J. Trump

Yeah...any endorsement from him is really a reverse endorsement in my book.

To the OP: really only ACN can help you, and based on their philosophy they'd probably say you're not selling enough. Drop them like a disease.
htothem
join:2013-08-27
Montreal, QC

htothem

Member

Thanks for your answers.

I know how terrible of a company ACN is. I'm not part of the pyramid. Actually, when I move here on July 1st, I "negotiated" the internet with the owner without knowing it was ACN. So it's included in my rent and I don't want to pay double for Internet.

Does the number posted in OP gives you guys any information on the source of the problem?

Fraoch
join:2003-08-01
Cambridge, ON
SmartRG SR808ac
TP-Link EAP225
Grandstream HT502

Fraoch

Member

said by htothem:

I know how terrible of a company ACN is. I'm not part of the pyramid. Actually, when I move here on July 1st, I "negotiated" the internet with the owner without knowing it was ACN. So it's included in my rent and I don't want to pay double for Internet.

Gotchya. Bad situation to be in for sure.

74 ms to the first hop is indicative of line problems. Unfortunately there's nothing you can do about this. Bell needs to address this and if ACN lies to you, gets mad at you and won't submit a ticket to Bell then you're unlikely to see a change.

Wish I could tell you different, but there's nothing you can do - this is a technical issue you don't really have any control over.
htothem
join:2013-08-27
Montreal, QC

htothem

Member

After trying a trace route this afternoon, it seems the first 3 hops (after my network) are a lot worst at night than during the day.

Microsoft Windows [version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Tous droits réservés.

C:\Windows\system32>ping -t www.google.ca

Envoi d'une requête 'ping' sur www.google.ca [74.125.131.94] avec 32 octets de d
onnées :
Réponse de 74.125.131.94 : octets=32 temps=40 ms TTL=46
Réponse de 74.125.131.94 : octets=32 temps=39 ms TTL=46
Réponse de 74.125.131.94 : octets=32 temps=39 ms TTL=46
Réponse de 74.125.131.94 : octets=32 temps=40 ms TTL=46
Réponse de 74.125.131.94 : octets=32 temps=39 ms TTL=46
Réponse de 74.125.131.94 : octets=32 temps=39 ms TTL=46
Réponse de 74.125.131.94 : octets=32 temps=40 ms TTL=46
Réponse de 74.125.131.94 : octets=32 temps=40 ms TTL=46
Réponse de 74.125.131.94 : octets=32 temps=39 ms TTL=46
Réponse de 74.125.131.94 : octets=32 temps=40 ms TTL=46
Réponse de 74.125.131.94 : octets=32 temps=40 ms TTL=46
Réponse de 74.125.131.94 : octets=32 temps=40 ms TTL=46
Réponse de 74.125.131.94 : octets=32 temps=40 ms TTL=46
Réponse de 74.125.131.94 : octets=32 temps=39 ms TTL=46

Statistiques Ping pour 74.125.131.94:
Paquets : envoyés = 14, reçus = 14, perdus = 0 (perte 0%),
Durée approximative des boucles en millisecondes :
Minimum = 39ms, Maximum = 40ms, Moyenne = 39ms

C:\Windows\system32>tracert www.google.ca

Détermination de l'itinéraire vers www.google.ca [74.125.131.94]
avec un maximum de 30 sauts :

1 1 ms 1 ms 1 ms homeportal [192.168.1.254]
2 13 ms 12 ms 14 ms 64.111.81.15
3 12 ms 13 ms 12 ms 64.111.83.109
4 24 ms 23 ms 23 ms 67.69.211.161
5 * * * Délai d'attente de la demande dépassé.
6 * * * Délai d'attente de la demande dépassé.
7 * * * Délai d'attente de la demande dépassé.
8 * * * Délai d'attente de la demande dépassé.
9 22 ms 23 ms 23 ms 72.14.221.241
10 22 ms 23 ms 23 ms 209.85.248.180
11 25 ms 24 ms 24 ms 72.14.236.206
12 34 ms 29 ms 30 ms 209.85.249.11
13 42 ms 40 ms 42 ms 209.85.241.222
14 41 ms 41 ms 40 ms 216.239.48.103
15 * * * Délai d'attente de la demande dépassé.
16 40 ms 40 ms 40 ms vc-in-f94.1e100.net [74.125.131.94]

Itinéraire déterminé.
htothem

htothem to Fraoch

Member

to Fraoch
Thanks. What sucks is that we had a Bell technician here and he told us he repaired the problem.

Also, I'm wondering if it is normal the 1st hop after my network is in Toronto, even tho I live downtown Montreal.

Fraoch
join:2003-08-01
Cambridge, ON
SmartRG SR808ac
TP-Link EAP225
Grandstream HT502

Fraoch to htothem

Member

to htothem
said by htothem:

After trying a trace route this afternoon, it seems the first 3 hops (after my network) are a lot worst at night than during the day.

Indicative of local area congestion perhaps, but this is DSL and shouldn't be subject to such a degree of congestion versus cable.

If that's the case, there is hope - if Bell customers are also experiencing the same issues Bell may actually get around to fixing it. Do you know anyone in the area with Bell DSL? Are they having similar issues?
Fraoch

Fraoch to htothem

Member

to htothem
said by htothem:

Also, I'm wondering if it is normal the 1st hop after my network is in Toronto, even tho I live downtown Montreal.

Toronto? I'm not even getting that:

whois 64.111.81.15
 
NetRange:       64.111.80.0 - 64.111.95.255
CIDR:           64.111.80.0/20
OriginAS:       AS19397
NetName:        ACN-NET-1
NetHandle:      NET-64-111-80-0-1
Parent:         NET-64-0-0-0-0
NetType:        Direct Allocation
RegDate:        2007-11-19
Updated:        2012-03-02
Ref:            http://whois.arin.net/rest/net/NET-64-111-80-0-1
 
OrgName:        ACN
OrgId:          ACNCO
Address:        1000 Progress Place
City:           Concord
StateProv:      NC
PostalCode:     28092
Country:        US
RegDate:        2008-10-09
Updated:        2009-09-01
Ref:            http://whois.arin.net/rest/org/ACNCO
 

I'm not a WHOIS expert, but it's safe to say that just because it's allocated to a certain company in a certain geographical location doesn't mean it's actually located there.

Your second hop is in the same range too. I wouldn't worry about it too much.

Guspaz
Guspaz
MVM
join:2001-11-05
Montreal, QC

Guspaz to htothem

MVM

to htothem
On Bell's GAS network, wherever your ISP's PoP is located is where your first hop will be. This is the case with me, for example, since I'm in downtown Montreal, but TekSavvy's PoP is in Toronto.
htothem
join:2013-08-27
Montreal, QC

htothem

Member

Thanks for the info, good to know.
Does that means that if you go on »www.theweathernetwork.com/ for exemple, your default city is Toronto ?

Guspaz
Guspaz
MVM
join:2001-11-05
Montreal, QC

Guspaz to htothem

MVM

to htothem
Yes. It's extremely annoying, but it's The Weather Network's fault for relying solely on IP-based geolocation. There are browser APIs to query the user's pre-defined location (most mobile sites use them), but The Weather Network doesn't use them.
htothem
join:2013-08-27
Montreal, QC

htothem

Member

I talked again to an ACN technical support and he told me that the street light may cause interference from my home to the FTTN. Seems far fetch but could be real. I googled a little bit and some people may have the same problem. It fits with the hours i'm experiencing the trouble. We'll see...