<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>AT&#x26;T Northeast forum - dslreports.com community</title>
<link>http://www.dslreports.com/forum/ilec,snet</link>
<description>AT&#x26;T Northeast forum current topics</description>
<language>en</language>
<copyright>Copyright 2007, dslreports.com</copyright>
<pubDate>Wed, 08 Feb 2012 10:35:06 EDT</pubDate>
<lastBuildDate>Wed, 08 Feb 2012 10:35:06 EDT</lastBuildDate>

<image>
<title>dslreports.com</title>
<url>http://i.dslr.net/bbrdisc1.gif</url>
<link>http://www.dslreports.com</link>
<width>19</width>
<height>18</height>
<description>bbr disc</description>
</image>

<item>
<title>[info] AT&#x26;amp;T Connecticut-Los Angeles routing problem</title>
<link>http://www.dslreports.com/forum/remark,26693618</link>
<description><![CDATA[:mad: There's a routing loop affecting AT&T customers in the 108.93.168.0/19 block to Los Angeles via NTT, in my case, this affects my ability to access my accounts on DreamHost.  Over 6 calls and about 4 hours on the phone they steadfastly refused to look at the traceroutes, instead running an insane numbers of diagnostics on the DSL; they finally moved us to a new subnet rather than fixing the bloody routing loop.  Keeping an eye on the problem, it's now 2 days later and I can still see the routing loop:

 &#012;traceroute to adsl-108-93-171-254.dsl.wlfrct.sbcglobal.net (108.93.171.254), 30 hops max, 60 byte packets&#012; 1  ip-75-119-220-1.dreamhost.com (75.119.220.1)  61.358 ms  61.342 ms  61.333 ms&#012; 2  router-0.hq.newdream.net (66.33.201.1)  41.634 ms  41.638 ms  41.630 ms&#012; 3  ip-66-33-201-213.dreamhost.com (66.33.201.213)  1.203 ms  1.463 ms  1.464 ms&#012; 4  xe-0-6-0-3.r04.lsanca03.us.bb.gin.ntt.net (198.172.90.69)  1.176 ms  1.169 ms  1.424 ms&#012; 5  xe-1.sbc.lsanca03.us.bb.gin.ntt.net (129.250.9.174)  1.138 ms  1.112 ms xe-0.sbc.lsanca03.us.bb.gin.ntt.net (129.250.9.170)  0.841 ms&#012; 6  ppp-151-164-39-101.rcsntx.swbell.net (151.164.39.101)  2.460 ms  2.007 ms  1.751 ms&#012; 7  151.164.98.90 (151.164.98.90)  20.846 ms  20.842 ms  20.833 ms&#012; 8  151.164.98.89 (151.164.98.89)  1.680 ms  1.483 ms  1.471 ms&#012; 9  151.164.98.90 (151.164.98.90)  20.574 ms  24.468 ms  24.016 ms&#012;10  151.164.98.89 (151.164.98.89)  2.004 ms  1.991 ms  1.972 ms&#012;11  151.164.98.90 (151.164.98.90)  23.923 ms  21.859 ms  21.822 ms&#012;12  151.164.98.89 (151.164.98.89)  1.748 ms  1.795 ms  1.836 ms&#012;13  151.164.98.90 (151.164.98.90)  20.084 ms  25.985 ms  25.973 ms&#012;14  151.164.98.89 (151.164.98.89)  2.101 ms  2.097 ms  1.932 ms&#012;15  151.164.98.90 (151.164.98.90)  23.763 ms  21.772 ms  25.776 ms&#012;16  151.164.98.89 (151.164.98.89)  2.334 ms  2.329 ms  2.301 ms&#012;
Everyone makes mistakes, but their refusal to fix this in the face of clear evidence just shows them to be a bunch of twonks.  I know customers are idiots but after an hour or two they could at least LOOK at the traceroutes I was offering.  No. Loser company.
]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,26693618</guid>
<pubDate>2011-12-24 13:54:42</pubDate>
</item>

<item>
<title>Sure is dead around here</title>
<link>http://www.dslreports.com/forum/remark,26846144</link>
<description><![CDATA[Well now...

What a difference in this forum these past several months...

I remember years ago, when this was a pretty hoppin' place. I remember when we were all sharing our thoughts on TCP Window size, CO versus remote terminal, and home runs.

I remember when this used to double as the Connecticut chat forum.

Hell, I remember 'Disconnected' before he was 'Disconnected.'

So I guess everyone just said the hell with it, and has cable now?

I think about switching, now and again. I know my little 5.1 megabit connection is pretty obsolete. It's just enough to get Netflix HD... once it spools up for a bit.

At least it's reliable. I couldn't help but chuckle when we had the hurricane, and *everyone* I knew with cable was out. My POTS and DSL were up the whole time.

And I like the fact that it's an industry standard, and I can use whatever modem and router I damn well please.

But it's been the same for years now.

What is to become of us poor slobs that live on the shoreline, with UVerse to the east, west and north, and a local cable system that is perhaps the second oldest in the state, aside from Groton's?

Will the telco ever have anything new to offer here?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,26846144</guid>
<pubDate>2012-02-02 16:42:33</pubDate>
</item>

</channel>
</rss>

