| 4th channel bonded in BK (11204) So...it looks like 4th channel was bonded in my area(11204) last Wed...
my IP & Gateway changed from 24.184.xxx.xxx to 67.84.xxx.xxx.
Since then the link seems actually more temperamental i.e. more congestion at night, variable latency(spikes) and bandwidth tests less consistent than previously, though within range. I was under impression that having more channels bonded would improve conditions not worsen.
Also, all geo-location services miscalculate my location as Freehold, NJ or Marlboro, NJ. I'm not familiar with algorithms used to pin point that, maybe its DNS based as in CDN location calculations but its odd to say the least. I just hope that the routing is proper.
Now, my downstream power levels are not ideal but still within spec range and are the same as with 3 channels previously; the upstream power level is actually marginally better (lower). So, I do not know what to attribute this change in quality of service other than addition of another channel and different routing.
Anyone care to comment? Thanks. |
|
| I noticed the same thing a couple days ago too: IP changed from 24.xx.xx.xx to 174.xx.xx.xx. Cisco Modem now has 5 bonded channels (up from 3). No performance change that I've noticed, though it's early to tell. |
|
|
|
| reply to Akam310
Arris modem and recently moved to 5 bonded in 11237.
Basically I think you'd be less likely to have congestion issues as it dynamically finds the channel. |
|
Reviews:
 ·Optimum Online
| reply to Akam310
My area in Bk 11214 got the 4th bonded channel last Thursday Feb 2 and since then my boost service has run like basic service at night. My new IP has me located in Freehold NJ nearly 50 miles from where I actually am.
Either we got added to already congested nodes making this great move worthless or as I read in another post they just need to tweak everything to get it working right. I'll give them til the end of the week then I'm raising hell on the phone. |
|
| reply to cseeman
hmmm...5th channel? Maybe its time to upgrade to new Arris... And looks like around 9-10pm the bandwidth drops by half...I'm going to monitor this further for a bit and then start making some calls as well. |
|
| I was having all sorts of prime time issues ranging from low speeds to high pings so they targeted doing several things on my node and beyond I believe to combat the congestion. |
|
| reply to Akam310
Just to be clear, the geo-location means nothing except that the IP range was moved from previously being used in that area, and will be updated whenever ARIN gets around to it. Any changes in performance would have to do with the new equipment you were moved to, and the extra bonded channel. |
|
| Ye...that's what I suspected...just wanted to make sure. Thanks. Going to make some complains at the end of the week if the conditions do not change. I just wish, they would make changes for better, not worse. |
|
| said by Akam310:Ye...that's what I suspected...just wanted to make sure. Thanks. Going to make some complains at the end of the week if the conditions do not change. I just wish, they would make changes for better, not worse.
Instability (is your modem rebooting?) after a channel expansion is not a desirable outcome, and may hint to a problem with the added channel. I suggest you call CV to report this now, not next week.
Geo-location data is an artificial property assigned to IP space by third parties that are not CV, and not regional internet registries like ARIN, much like DNSBLs. Neither CV nor ARIN have any input or influence on what the (numerous) geo-location services do, how they operate, or on their "discovery process". Nothing they do is publicly documented (trade secrets), and there are no known IETF standards for them, as what they do is opaque and in a constant state of flux.
Complaining directly to the sites/services that are using geo-location data wrong with your IP address is the best way of getting the issues corrected. May take a couple of weeks/months. |
|
| The connection seems stable at least as far as staying connected...No drops so far. It just seems that the new subnet/vlan range to which I was moved is over saturated as I'm seeing more congestion, lower amount of available bandwidth and higher latency during peak evening hours. And, the reason I wanted to wait was to build up my case better, collect so more stats and make sure it was not a transient issue. And it is ongoing so far.
As far as geo-location...I really don't care about it, nor rely on it much, so its functionality as long as its not related to my connectivity issues is not vital.
I do appreciate your input on the matter though.
I wonder if my issue can be resolved at the plant end or would require a field tech visit.
I'll call the supervisor in the engineering as regular customer service is pretty clueless and just a waste of my time. Thanks.
|
|
| reply to Akam310
Hi,
i just wanted to share my info:
i am in this Zip Code as well (11204) and i only have three channels bonded:
621.00 MHz
615.00 MHz
609.00 MHz
My modem is running the new firmware though ( TS0703123_090611_MODEL_7_8)(MODEL: TM802G)
I've never gotten over 80Mb |
|
