CaryissoVery
msg:1413500 | 3:08 am on Feb 6, 2004 (gmt 0) |
Yes, unable to access server here too.
|
jranes
msg:1413501 | 3:09 am on Feb 6, 2004 (gmt 0) |
I am too.
|
philr
msg:1413502 | 3:10 am on Feb 6, 2004 (gmt 0) |
yes getting it here to in Australia
|
coho75
msg:1413503 | 3:15 am on Feb 6, 2004 (gmt 0) |
Same 502 error here in upstate NY.
|
birdstuff
msg:1413504 | 3:19 am on Feb 6, 2004 (gmt 0) |
Ditto in Virginia.
|
mvander
msg:1413505 | 3:20 am on Feb 6, 2004 (gmt 0) |
502 in Michigan as well.
|
dongjp
msg:1413506 | 3:24 am on Feb 6, 2004 (gmt 0) |
502 going on
|
Polarisman
msg:1413507 | 3:25 am on Feb 6, 2004 (gmt 0) |
G must be allocating some of their processing time to cutting the December checks.
|
Loony
msg:1413508 | 3:32 am on Feb 6, 2004 (gmt 0) |
Heh heh - maybe it's Google putting the fear into us, after that "check's (not?) in the mail" post...
|
MarkHutch
msg:1413509 | 3:32 am on Feb 6, 2004 (gmt 0) |
Well, at least I'm not alone with this problem.
|
CaryissoVery
msg:1413510 | 3:35 am on Feb 6, 2004 (gmt 0) |
Its baaaaaccckkkkkkkk (at least in georgia)
|
MarkHutch
msg:1413511 | 3:36 am on Feb 6, 2004 (gmt 0) |
ditto
|
|
