You may want to add the [url=https://www.gog.com/forum/general/a_new_my_account_d5f25/post1019]issue to the list.

You sure about that? http://gog.com properly redirects me.

Your link just times out for me. (See attached.)

I typically type gog.com to access gog. And this morning, it isn't working. I resorted to direct forum bookmarks, and they worked. Then, out of curiosity, I clicked the gog logo, which links to www.gog.com. And that worked. But no, gog.com alone doesn't work for me at present.

Perhaps I'm unique. I haven't updated anything that should have caused this, though.

Ping gog.com and see if you get a reply. If you do, then your browser doesn't handle redirects properly. If you don't, then your DNS is playing tricks on you, or my DNS is still cached.
Interesting thing is that gog.com and www.gog.com produce different results when pinged for me.

You're not unique.

I just tried chrome and IE, and they seem to work. But, it appears that chrome is adding www BEFORE sending the request. That is, chrome is matching gog.com to www.gog.com immediately. IE is less transparent, so I'm unsure what's happening there. Ping doesn't work:

C:\Users\Molasses>ping gog.com

Pinging gog.com [209.177.157.167] with 32 bytes of data:
Reply from 129.250.204.154: Destination host unreachable.
Reply from 129.250.204.154: Destination host unreachable.
Reply from 129.250.204.154: Destination host unreachable.
Reply from 129.250.204.154: Destination host unreachable.

Ping statistics for 209.177.157.167:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

C:\Users\Molasses>ping www.gog.com

Pinging e11072.g.akamaiedge.net [23.33.60.243] with 32 bytes of data:
Reply from 23.33.60.243: bytes=32 time=46ms TTL=56
Reply from 23.33.60.243: bytes=32 time=46ms TTL=56
Reply from 23.33.60.243: bytes=32 time=50ms TTL=56
Reply from 23.33.60.243: bytes=32 time=46ms TTL=56

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

edit:
Thanks for confirming, Vanished. Now I can stop looking for problems on my end.

Do a traceroute on each address. Seems like a server in the middle of the route is off.
Does Chrome add the www even if you type http://gog.com? I know if you only type gog.com it will add the www. part, though unsure if it does that only if it can find it in history.
And do a traceroute as well, you also seem to get a server hiccup midway.

Yes, chrome adds the www even when I type that directly. It's matching and selecting from an existing list.

Did the tracert. The difference seems to be that www.gog.com immediately resolves to an akamai address, but gog.com does not (as seen in the two pings).

The two pings shows that gog.com is never reached, since the "Destination host unreachable" is from an different address. VanishedOne's tracerout shows the problem to be in a virtual host on hso-group, and it is possible that it's an older hosting for said site which is being phased out.
Either way, as you said, it's something not on your end :)

Thanks for the suggestions, JMich. I sent a follow-up message to support pointing them here.

Having same problem - gog.com doesn't bring up the website while www.gog.com does. 'Not just me' according to the 'Down Or Just Me' website (ref attached).

I was wandering why a random guy was insisting in sending a friend request when i was refusing every single time and now i know why. Good old gog...

The forum for Favourited topics is displaying the number of posts as the number of pages. It appears to only be for favourited topics (see attached pic)