ATT Routing issue to open source software website hosted in France

I've tried to attach the ping and traceroute results (plain text) but there is a 403 error. How best to include that information?

Will try an image to see if that works.

<update> found that i can include log as a code block

$ traceroute godotengine.org
traceroute to godotengine.org (212.85.158.4), 64 hops max, 52 byte packets
 1  dsldevice.attlocal.net (192.168.1.254)  2.855 ms  2.119 ms  1.701 ms
 2  104-182-52-1.lightspeed.rlghnc.sbcglobal.net (104.182.52.1)  4.206 ms  3.837 ms  2.991 ms
 3  99.173.77.16 (99.173.77.16)  3.116 ms  4.182 ms  3.919 ms
 4  12.123.138.230 (12.123.138.230)  17.093 ms  12.797 ms  15.834 ms
 5  wswdc21crs.ip.att.net (12.122.2.190)  10.985 ms  12.360 ms  10.718 ms
 6  wswdc401igs.ip.att.net (12.122.113.37)  13.190 ms  11.737 ms  12.154 ms
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * *^C

$ ping godotengine.org
PING godotengine.org (212.85.158.4): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
Request timeout for icmp_seq 9

Hi, magiclantern, let us see what we can do to help you access this website.

There are two possibilities that come to mind: the site is blocking your IP, or the site is being detected as harmful.

After looking over your traceroute, we see that the timeout is happening outside of the AT&T network. Hop 6 is the last one before you're connected to the website, and since it's working, it's likely that the website itself may be blocking your IP.

Software like AT&T's Mobile Security, and other 3rd party security services, can prevent websites from loading. This is because there is a vulnerability that was detected by the service indicating that the website has been rated harmful. To determine if this is the case, visit https://mxtoolbox.com.

1. Enter the website
2. Wait for the results
3. Green checks are what you want to see
4. If you see red, contact your WebHost to help resolve the codes

To resolve the vulnerabilities, you will need to contact the WebHost or your web developer. AT&T is unable to assist with items of this nature.

Let us know what you found and if you need further assistance.

Aminah, AT&T Community Specialist

In working with support yesterday I disabled all ATT security that could be disabled. No change.

Looks like only 1 green check - yellow and red stuff too.

What does this mean?

Thank you for the update, magiclantern.

The results should show green checks across the board. This coupled with the fact that the site appears to be working on the AT&T network, tells us that you'll need to contact the webhost for the site you're trying to reach, as mentioned earlier

We appreciate you for contacting the AT&T Community Forums team. If you need help again in the future, we'll be here.

Aminah, AT&T Community Specialist

After a little reading on DMARC. Seems that is for email message authentication.

Why should my web browser accessing a https website be impacted or care about message authentication?

Noticed that @ATTHelp posted information related to "AT&T's Mobile Security."

This issue is occurring on my ATT fiber internet.

Also, not sure how you are able to state "... the fact that the site appears to be working on the AT&T network..." as I'm on the ATT network and the site is not accessible.

On other networks (my work non-ATT network, my non-ATT cellular provider) I am able to access the site.

I am having the same issue with godotengine.org on att fiber. Godotengine.org is an opensource game development website.

ATT replaced my modem and it had no effect.

@nyfiberuser - I reached out to some of the folks that use Godot and they recommended using a VPN. Turns out there are some free options that I have been able to verify work (Proton).

Although open source game engine software should be considered safe to most people, for some reason it is blocked on at least parts of ATT's fiber network.

I tried calling ATT customer service twice before posting here, but they seemed to be clueless about this type of filtering.

I am having the same issue using ATT. It seems somewhat intermittent. I can DNS resolve godotengine.org, but most of the time a connection cannot be established. At other times (trying on different days), the response will slowly trickle in. It even seems that after some time of inactivity godotengine.org will respond, until it eventually stops.

This results in a very negative user and developer experience. The Godot Engine QA section is impacted, so googling any kind of issue around Godot is incredibly frustrating, because that content is inaccessible, including the Godot Asset Library.

As a workaround I'm re-routing all requests to godotengine.org (212.85.158.4) to go through a VPN in my pfsense router, which isn't really a solution for most users.

I came across this thread by googling "att cannot reach godotengine.org".

As a previous user mentioned, the godotengine.org website is properly accessible via all other means; other ISPs, mobile networks, hotspots. But not when trying to access it directly through ATT's fiber network.

The OP was in the Raleigh NC area.  By any chance are you in that area too?  I seem to recall other weird routing issues coming out of Raleigh in recent months.

I'm on the West Coast and have no issue loading that website, quite quickly in fact.  My tracert ends successfully at web.tuxfamily.net [212.85.158.4].

@tonydi Yes, I am in Raleigh. The traceroute looks similar to OP's.

$ traceroute godotengine.org --resolve-hostnames
traceroute to godotengine.org (212.85.158.4), 64 hops max
  1   172.24.128.1 (battlestation.mshome.net)  0.144ms  0.153ms  0.135ms
  2   10.10.1.1 (firewall.home)  0.374ms  0.346ms  0.315ms
  3   192.168.2.254 (attbox.home)  1.218ms  1.191ms  1.017ms
  4   107.197.152.1 (107-197-152-1.lightspeed.rlghnc.sbcglobal.net)  2.119ms  1.488ms  2.042ms
  5   99.173.76.198 (99.173.76.198)  2.219ms  2.200ms  1.990ms
  6   12.123.138.18 (rlgnc22crs.ip.att.net)  13.340ms  11.187ms  16.291ms
  7   12.122.2.190 (wswdc21crs.ip.att.net)  11.713ms  9.747ms  15.939ms
  8   12.122.113.37 (wswdc401igs.ip.att.net)  10.639ms  11.374ms  13.439ms
  9   *  *  *
 10   *  *  *
 11   *  *  *
 12   *  *  *
 13   *  *  *
 14   *  *  *
^C

Interesting!  The problem is we don't know who owns the servers after that last AT&T hop.  After my trace leaves the AT&T network it heads to twelve99 servers for most of the rest of the journey.

Of course even if we could pinpoint the problem, there's really not a whole lot we can do.  None of the ATTHelp people have access to the NOC engineers who could look at the routing and those engineers never interface with any member of the public. 

Just had a thought.  On other issues like email and website blocklists, where ATTHelp is helpless, people have had success in posting on the AT&T Business Community forums.  Those AT&T people seem to have better connections to the people who push the buttons and pull the levers that run the network.  Maybe that's worth a shot?

https://bizcommunity.att.com

All - thanks for the comments and posts. Since before April 26, 2022 I have been unable to access the open source software website https://godotengine.org from my AT&T fiber home internet in the Raleigh NC area.

With the recent comments, I decided to try again and found that as of June 27, 2022, I am now able to access https://godotengine.org !

Also, I ran another traceroute got the below - now shows getting to site 212.85.158.4 - though continues after that for some reason I don't understand.

$ traceroute godotengine.org
traceroute to godotengine.org (212.85.158.4), 64 hops max, 52 byte packets
 1  dsldevice.attlocal.net (192.168.1.254)  2.589 ms  2.112 ms  1.878 ms
 2  104-182-52-1.lightspeed.rlghnc.sbcglobal.net (104.182.52.1)  2.954 ms  2.615 ms  2.987 ms
 3  99.173.77.14 (99.173.77.14)  4.140 ms  5.046 ms  4.074 ms
 4  * * *
 5  * * *
 6  32.130.16.197 (32.130.16.197)  16.938 ms  18.117 ms  19.961 ms
 7  4.68.62.225 (4.68.62.225)  17.835 ms * *
 8  * * *
 9  212.3.235.154 (212.3.235.154)  95.645 ms  96.757 ms  97.189 ms
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
31  * * *
32  * * *
33  *^C

Ping does work now:

$ ping godotengine.org
PING godotengine.org (212.85.158.4): 56 data bytes
64 bytes from 212.85.158.4: icmp_seq=0 ttl=47 time=112.325 ms
64 bytes from 212.85.158.4: icmp_seq=1 ttl=47 time=110.778 ms
64 bytes from 212.85.158.4: icmp_seq=2 ttl=47 time=110.727 ms
64 bytes from 212.85.158.4: icmp_seq=3 ttl=47 time=111.818 ms
64 bytes from 212.85.158.4: icmp_seq=4 ttl=47 time=110.998 ms
64 bytes from 212.85.158.4: icmp_seq=5 ttl=47 time=110.883 ms
64 bytes from 212.85.158.4: icmp_seq=6 ttl=47 time=111.579 ms
^C
--- godotengine.org ping statistics ---
7 packets transmitted, 7 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 110.727/111.301/112.325/0.569 ms