said by smbtamu:
Based on this information, is gateway contention still the likely issue or am I back to square one?
I've been looking at the Sharedband site, and trying to sort out how it works. On their "technology"
page, they show multiple routers on the customer premises. Each has a separate WAN connection, which can be a mix of DOCSIS (cable), DSL, and fiberoptic services. It looks like they do load balancing tricks on their servers at step 4. Even with multiple DSL connections from the same provider, as you have, packets traveling between the CPE and the Sharedband aggregation servers may take different routes.
can probably explain the AT&T transit better than I, but you have four DSL modems on four lines. They ride ATM from the DSLAMs (could be as many as four; one port on each) to the AT&T aggregation routers. They are switched from ATM to TCP/IP there, and ride AT&T TCP/IP transit to the Sharedband aggregators. Those could easily be four different routes, and even complicated more if Sharedband is not peering directly with AT&T; your packets could be running on Level 3, or XO, or Cogentco between AT&T and Sharedband. I can't begin to guess how many peering choke points could introduce congestion which isn't on a gateway.
I am sorry, this is complicated beyond my expertise.--
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum