For the past hour (it's now 12:30 CET), the site has been really slow to load, whenever I change forums or threads. A couple of times, the connection was lost completely, and one time I just got a blank white page, but with the new (I guess) favicon.
I wonder if Update 2 is being rolled out right now?

I've been on and off for the last hour trawling through forums. Noticed nothing different here.
Update 2 and it's supposed green goodness is meant to be released soon though according to twitter :)

I've had no troubles with it which is odd since I'm usually the first to get weird issues with tech

Well, maybe it's just a glitchy router between here and GOG's server, then. But I'm still experiencing it, even now.

Meh, I'm fine here. No difference.

What are your ping times to gog.com? Mine are in the 450-500ms range
Real circuitous routing too, 22 hops

stable 110ms ping, no problems there

Most of the time, it just times out. Here's one that didn't (completely):
Pinging gog.com [70.38.122.71] with 32 bytes of data:
Request timed out.
Reply from 70.38.122.71: bytes=32 time=104ms TTL=56
Request timed out.
Request timed out.
Ping statistics for 70.38.122.71:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 104ms, Maximum = 104ms, Average = 104ms
I'll post my traceroute in a minute, but that keeps timing out too.
This is pretty indicative of what I'm up against:
5 9 ms 10 ms 13 ms ge-2-0-0.alb2nxu5.dk.ip.tdc.net [83.88.26.98]
6 108 ms 104 ms 100 ms te0-1-4-0.alb2nqh2.dk.ip.tdc.net [83.88.13.49]
7 102 ms 97 ms 114 ms pos7-0-0.nyk2nxg1.us.ip.tdc.net [83.88.26.94]
8 97 ms 96 ms 94 ms ge2-0-0.nyk2nxg2.us.ip.tdc.net [83.88.23.118]
9 98 ms 94 ms 95 ms xe-1-0-0.paix.nyc-telx-dis-1.peer1.net [198.32.118.146]
10 * * * Request timed out.
11 * * * Request timed out.
12 104 ms 107 ms 105 ms g9-8.hd-core02.peer1.mtl.iweb.com [216.187.90.134]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * 103 ms * ip-70-38-122-71.static.privatedns.com [70.38.122.71]
17 * * * Request timed out.
18 * * * Request timed out.
19 * 103 ms * ip-70-38-122-71.static.privatedns.com [70.38.122.71]
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * 106 ms ip-70-38-122-71.static.privatedns.com [70.38.122.71]
Trace complete.
Damn, no code tags. Well, you get the idea.

Over the last ten minutes, most are are around the 380ms mark. I don't have the tools right now to say much else from a simple ping command.

Yup, theres a dead router somewhere along that line, maybe the hamster has died and they're holding a memorial.
On an unrelated note, I was surprised to see GOG running on a class A address

Well, it can't be completely dead (but it's definitely been kneecapped), or I wouldn't get through at all. I don't suppose there's any way I can route around it?

Haven't had any time outs, but I have noticed that the number of topics counter appears to randomly fluctuate for this board.

Curiously, my route to Gamespot.com is also broken. Not merely slowed, but completely broken. And it's a completely different route:
Tracing route to gamespot.com [216.239.113.172]
over a maximum of 30 hops:
5 24 ms 24 ms 29 ms ge-2-0-0.alb2nxu5.dk.ip.tdc.net [83.88.26.98]
6 110 ms 103 ms 99 ms te0-1-4-0.alb2nqh2.dk.ip.tdc.net [83.88.13.49]
7 98 ms 102 ms 120 ms pos7-0-0.nyk2nxg1.us.ip.tdc.net [83.88.26.94]
8 737 ms 167 ms 471 ms TenGigabitEthernet2-3.ar4.NYC1.gblx.net [146.82.
35.201]
9 105 ms 112 ms 96 ms te3-1-10g.ar5.NYC1.gblx.net [67.17.108.246]
10 96 ms 106 ms 102 ms 64.212.107.98
11 182 ms 188 ms 168 ms cr1.n54ny.ip.att.net [12.122.131.46]
12 172 ms 171 ms 178 ms cr2.cgcil.ip.att.net [12.122.1.2]
13 188 ms 170 ms 175 ms cr1.cgcil.ip.att.net [12.122.2.53]
14 171 ms 171 ms 170 ms cr1.sffca.ip.att.net [12.122.4.121]
15 172 ms 177 ms 178 ms gar5.sffca.ip.att.net [12.122.137.9]
16 * * * Request timed out.
Past that point it's nothing but timeouts. Anyone else have the same problem?

Nah it can be dead, the last router to reply to a ping would just be trying all the alternate pathways it knows or broadcasting it to ask if any other routers in the same network can pass the packet on. Most likely most of those other routers its asking say "Yeah I know the way" and immediately sends it to the dead router again.
There's no practical way for an end user to route around a broken link, you can do it but its a pain in the arse and would probably take longer than waiting for the problem to be fixed. Best off ringing your ISP & asking if they have problems. ask if they can get to www.gog.com and they'll load it, see the games and buy something. Doesn't help YOU but it helps build the glorious GOG empire