I found a solution to the lag spike issue that was reported to me and I did some investigation on. In the case of my customer, his lag spikes were caused by his Rogers supplied modem.
Here’s how I figured it out.
The customer was using the modem to serve up Internet access for his home. So I plugged my MacBook Pro into it via Ethernet and pulled up the page that allowed me to see the modem stats page. Then I had him play Team Fortress 2 and I waited. The stats looked good for the most part. But every once in a while they would fall outside the range that is optimal and that is when the issue would manifest. That implied a line issue or a modem issue. I then phoned Rogers and though it took a while because the tech at the other end of the phone was clearly not used to this sort of advanced troubleshooting, the tech finally suggested that we take the modem to a Rogers store to exchange it. We did that and so far he hasn’t had a re-occurrence. Though we continue to monitor the situation.
Now, I have a feeling that this is not the only cause of this issue. Googling this issue shows a variety of causes and a long history of this issue going back years. Clearly Rogers has a long standing problem with lag spikes that they need to address. I say that because a Rogers customer had to hire someone like me to solve their problem. That doesn’t reflect well on Rogers.
As for troubleshooting this issue in my condo, I have put that on the back burner until my MacBook Pro comes back from being repaired. Expect another update when that happens.
Like this:
Like Loading...
Related
This entry was posted on October 18, 2014 at 8:04 pm and is filed under Commentary with tags Rogers. You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.
Another Update To The Rogers Lag Spike Issue
I found a solution to the lag spike issue that was reported to me and I did some investigation on. In the case of my customer, his lag spikes were caused by his Rogers supplied modem.
Here’s how I figured it out.
The customer was using the modem to serve up Internet access for his home. So I plugged my MacBook Pro into it via Ethernet and pulled up the page that allowed me to see the modem stats page. Then I had him play Team Fortress 2 and I waited. The stats looked good for the most part. But every once in a while they would fall outside the range that is optimal and that is when the issue would manifest. That implied a line issue or a modem issue. I then phoned Rogers and though it took a while because the tech at the other end of the phone was clearly not used to this sort of advanced troubleshooting, the tech finally suggested that we take the modem to a Rogers store to exchange it. We did that and so far he hasn’t had a re-occurrence. Though we continue to monitor the situation.
Now, I have a feeling that this is not the only cause of this issue. Googling this issue shows a variety of causes and a long history of this issue going back years. Clearly Rogers has a long standing problem with lag spikes that they need to address. I say that because a Rogers customer had to hire someone like me to solve their problem. That doesn’t reflect well on Rogers.
As for troubleshooting this issue in my condo, I have put that on the back burner until my MacBook Pro comes back from being repaired. Expect another update when that happens.
Share this:
Like this:
Related
This entry was posted on October 18, 2014 at 8:04 pm and is filed under Commentary with tags Rogers. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.