ATT Routing issue to open source software website hosted in France

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

@metaversedev - I am now able to get to the Godot Engine website. Does it work now for you as well?

@magiclantern It works for me as well right now. But this has happened before, and it was intermittent. Couple of weeks ago, I fired up Godot, grabbed something from the asset library and it worked. Later that day it threw errors again. So I'm hoping this holds.

Yeah, same broke/fix cycle we've seen with other routing issues in these forums.  They eventually resolve but may come and go a couple three times before they seem to stick.

Well, let's keep this open and see if the problem comes back.

If it does come back, I (or someone else) can try posting the issue also to the https://bizcommunity.att.com forums mentioned by @tonydi to see if we can get someone with the ability to resolve the issue.