Announcements
You Could WIN A Year Of Wireless Service – Learn More!

Tutor

 • 

6 Messages

Thu, Jun 22, 2017 6:31 PM

AT&T is BLOCKING my site hosted by GoDaddy.com

AT&T is BLOCKING my site hosted by GoDaddy.com

My website is hosted through godaddy and I have not been able to access it from any computer at my house where I have AT&T cable service. 

Can AT&T block certain websites arbitrarily, is this an example of censorship like what they have in China?


Our sites have been blocked since last night since around 9pm. (Same Dedicated Server)

 

lopestatus.com

gofoto.it

riggedit.com

machineheads.ca
felicekinnear.com

 

All att wireless and att u-verse users are affected.

 

(1) the site works for all non-att users, in the US or world wide

(2) site block at home using att u-verse

(3) site NOT blocked at home using VPN /Proxy into another network.

 

Should not there be a due process for appealing the block? Is this a freedom of speech issue?

 

Can someone kindly point to to whom I should ask a review of the blocking? Thank you.

Responses

Tutor

 • 

6 Messages

3 years ago

Here is where TraceRt Failed:

 

C:\Users\loper>ping lopestatus.com

Pinging lopestatus.com [184.168.187.1] with 32 bytes of data:
Reply from 184.168.187.1: bytes=32 time=34ms TTL=49
Reply from 184.168.187.1: bytes=32 time=33ms TTL=49
Reply from 184.168.187.1: bytes=32 time=33ms TTL=49
Reply from 184.168.187.1: bytes=32 time=33ms TTL=49

Ping statistics for 184.168.187.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 34ms, Average = 33ms

C:\Users\loper>traceroute lopestatus.com

C:\Users\loper>tracert lopestatus.com

Tracing route to lopestatus.com [184.168.187.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms homeportal [192.168.1.254]
2 20 ms 18 ms 70 ms 76-217-128-1.lightspeed.sndgca.sbcglobal.net [76
.217.128.1]
3 19 ms 18 ms 20 ms 71.157.16.57
4 19 ms 19 ms 18 ms 75.20.78.142
5 21 ms 19 ms 19 ms 75.20.78.129
6 20 ms 18 ms 20 ms 12.83.70.149
7 25 ms 23 ms 22 ms ggr2.la2ca.ip.att.net [12.122.129.105]
8 24 ms 24 ms 36 ms 192.205.37.146
9 * * * Request timed out.
10 34 ms 34 ms 34 ms 4.16.137.146
11 35 ms 37 ms 35 ms be39.trmc0215-01.ars.mgmt.phx3.gdg [184.168.0.73
]
12 34 ms 35 ms 36 ms be39.trmc0215-01.ars.mgmt.phx3.gdg [184.168.0.73
]
13 34 ms 33 ms 34 ms ip-97-74-255-129.ip.secureserver.net [97.74.255.
129]
14 33 ms 34 ms 33 ms p3nlhg212c1212.shr.prod.phx3.secureserver.net [1
84.168.187.1]

Trace complete.


So it fails here:
http://192.205.37.146/
According to : http://ipaddress.is/192.205.37.146#.WUwTs-vyvmh
Which is your router or switch; 

NetRange: 192.205.0.0 - 192.205.255.255
CIDR: 192.205.0.0/16
OriginAS:
NetName: NETBLK-ATT
NetHandle: NET-192-205-0-0-1
Parent: NET-192-0-0-0-0
NetType: Direct Allocation
RegDate: 1992-08-03
Updated: 2012-04-02
Ref: http://whois.arin.net/rest/net/NET-192-205-0-0-1

OrgName: AT&T Services, Inc.
OrgId: ATTSE-Z
Address: Enterprise IP Group
Address: c/o John M Nelson
Address: 240 N Meridian Street
Address: Room 280
City: Indianapolis
StateProv: IN
PostalCode: 46204
Country: US
RegDate: 2009-01-30
Updated: 2009-02-04
Comment: http://www.att.com
Ref: http://whois.arin.net/rest/org/ATTSE-Z

OrgTechHandle: SBCDN-ARIN
OrgTechName: SBCDNS
OrgTechPhone: +1-317-265-2859
OrgTechRef: http://whois.arin.net/rest/poc/SBCDN-ARIN

OrgAbuseHandle: ABUSE7-ARIN
OrgAbuseName: abuse
OrgAbusePhone: +1-919-319-8167
OrgAbuseRef: http://whois.arin.net/rest/poc/ABUSE7-ARIN

 

..and I'm sure you're working to resolve it as fast as possible; as I cannot be the only one with this issue?

Please update me with the status.  Cheers!

Tutor

 • 

6 Messages

3 years ago

After 2 hours on the phone with Customer Support;

The nice lady let me read back to her that the IP address http://192.205.37.146/ was failing.
She Confirmed.

When I then said the location of the issue; as note by a quick google search: https://db-ip.com/192.205.37.146
being ATT hardware in INDIANA; she got flustered and put me on hold.

Came back and said,

"No it is THIS IP that times out:"

184.168.0.73 
That is a Godaddy server. 
But according to Godaddy...This is a security protocol; and they saw no issues on their end.
ALSO; if you did a traceroute from my modem, how do you get a magic IP address that I cannot?

So did this lady just punt me?  She seemed so much happier to give me the IP address of Godaddy because she knew I would go away.
How is that acceptable in 2017?  

I guess I'll just FAX the Datacenter in Indiana...Oh wait...THE LINE IS BUSY FOR HOURS.  Maybe I'm not the only one affected?

At a loss here; I guess you can't just tell me "We are aware of the issue and are working to resolve it as soon as possible?" 
You train people not let me escalate until 2 hours of my time is wasted ("DID YOU TRY UNPLUGGING IT?")
....so the supervisor can just lie to my face? 

Contributor

 • 

1 Message

3 years ago

Yeah. I had a DNS horror story from AT&T today.

 

Simple issue, their DNS servers recognized a domain name I was tryting to reach  -- SoldiersofFortune-deepwood.enjinvoice.com  -- but had no IP address attached to it. This worked fine a couple days ago.  When I talked to a tech, I tried to show them the NSLOOKUP information on it.  The tech didn't even know what the NSLOOKUP command was, or did, so I showed him a bad entry and a good entry.  He immediately transfered me to someone else and I showed them what was happening and they tried to tell me it was a third party issue and they'd help me if I SUBSCRIBED to some extended coverage service.  When I told them I shouldn't have to pay extra for an issue that's clearly on an issue on their servers.  She told me it couldn't be an issues with AT&T because if it were, I wouldn't be able to access the internet at all, refuse any help, and then proceeded to try and sell me the extended coverage service again.  Really crappy service on their part.  I feel like they're trying to hold me ransom with an approach of... we'll fix it, but you gotta pay us more...  I'm looking at other services now.

Tutor

 • 

6 Messages

3 years ago

So this is still an issue.