Comcast XFINITY → Re: Transition Blues -- Deja vu all over again?

First of all, Comcast is already using the AT&T backbone for our connection (as opposed to Sprint with @Home), so the basic infrastructure is already merged. I would think one of the benefits we would get would be unlimited newsgroups (since AT&T already has this). I don't know how good AT&T's customer service is, but I would think we would most likely go with AT&T's, since they have more experience with customer service management. I don't forsee any speed changes (AT&T has the same limits Comcast has), however, I think the cost for AT&T/Comcast would be much cheaper since they would own their own infrastructure. Mail & web limits would probably be the same as well.

said by mbernste:

---

I would think one of the benefits we would get would be unlimited newsgroups (since AT&T already has this).

---

This assumes that cable internet after the merger would follow the AT&T Broadband model versus the Comcast High Speed Internet model. It may be premature to speculate that there will be a net gain in feature availability for current Comcast High Speed Internet customers.

said by mbernste:

---

First of all, Comcast is already using the AT&T backbone for our connection (as opposed to Sprint with @Home)...

---

Really? (said with appropriate wide-eyed awe)

Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:

1 11 ms 11 ms 9 ms 10.XXX.XXX.XXX
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 10 ms 11 ms 15 ms 68.XXX.XXX.XXX
6 17 ms 18 ms 22 ms sl-gw22-chi-6-3.sprintlink.net [144.228.151.177]
7 18 ms 17 ms 18 ms 144.232.10.13
8 35 ms 38 ms 34 ms sl-bb21-spr-13-1.sprintlink.net [144.232.19.206]
9 37 ms 37 ms 37 ms sl-bb21-pen-10-3.sprintlink.net [144.232.8.161]
10 38 ms 39 ms 37 ms sl-bb20-pen-15-0.sprintlink.net [144.232.16.33]
11 38 ms 38 ms 39 ms sl-gw4-pen-9-0.sprintlink.net [144.232.5.18]
12 40 ms 39 ms 41 ms sl-cogentcomm-5-0.sprintlink.net [160.81.202.18]
13 42 ms 41 ms 41 ms p5-0.core02.jfk02.atlas.cogentco.com [66.28.4.1]
14 41 ms 41 ms 42 ms p6-0.core01.jfk01.atlas.cogentco.com [66.28.4.12.2]
15 45 ms 40 ms 41 ms g49.ba01.b001362-1.jfk01.atlas.cogentco.com [66..28.66.42]
16 41 ms 41 ms 42 ms Net-Access-Corporation.demarc.cogentco.com [66.2.8.28.74]
17 42 ms 41 ms 42 ms vlan23.msfc1.nyc.nac.net [209.123.37.29]
18 44 ms 45 ms 49 ms a9-0-1165.msfc1.oct.nac.net [209.123.11.10]
19 54 ms 51 ms 48 ms www.dslreports.com [209.123.109.175]

Trace complete.

"Ridin' on the City of New Orleans,
Illinois Central, Monday morning rail..." (A.G.)

Hey jackie, looks like you got competition for your job, boyo.

John

said by jmadams:

---

said by mbernste:

---

First of all, Comcast is already using the AT&T backbone for our connection (as opposed to Sprint with @Home)...

---

Really? (said with appropriate wide-eyed awe)

Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:

1 11 ms 11 ms 9 ms 10.XXX.XXX.XXX
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 10 ms 11 ms 15 ms 68.XXX.XXX.XXX
6 17 ms 18 ms 22 ms sl-gw22-chi-6-3.sprintlink.net [144.228.151.177]

---

all that says is that the other end of the pipe is on a sprintlink own router..

the physical line.. most cases an OC-3, is provisioned and owned by AT&T. The IP service goes through sprintlink for the most parts tho some areas may use other providers.

kinda like DSL in a way.. my dsl line is owned and provisioned by Verizon, the dsl signal is provided via Covad equipment, and the IP service is through mindspring - talk about a nightmare getting someone to take ownership of a line problem.