I'm no expert, but that could be due to one of many things.  Were you able to load other websites while this was happening (was it only mgoblog doing this?) 

I haven't encountered any problems recently with mgoblog.

It happened to me once, but I reloaded the page after that and had no issues. It took a little longer than usual but loaded up just fine.

I've also been getting that periodically today (probably about five times total), and only at MGoBlog. I'm on Firefox, if that matters.

I got that and was hoping the site was overloaded due to Derrick Green committing

Lol I thought people went crazy about the uniforms.

I got that just now when I tried to access the board, and again trying to reach the homepage.  I had to refresh a few times but I eventually got back in.

as I was having trouble with 503's from mgoblog, I got a 504 from umhoops. Does Brian host for umhoops?

I usually see this when the site is overloaded with traffic, usually due to a commitment.

So, to see that Derrick Green has not committed is very disappointing.

The server couldn't handle traffic for whatever reason, so you can't make it to the site. It's the hosting company, not Brian or your computer.

Everytime I get that it seems there is either a new post or an edit to an existing one that pops up as soon as I finally get the page to load.

I usually see this when the site is overloaded with traffic, usually due to a commitment.

So, to see that Derrick Green has not committed is very disappointing.

Everytime I get that it seems there is either a new post or an edit to an existing one that pops up as soon as I finally get the page to load.

Everytime I get that it seems there is either a new post or an edit to an existing one that pops up as soon as I finally get the page to load.

Edit: double post due to 504 error in middle of submitting post. Hah

It happens to me every now and then, and usually when it happens I cannot access the site for a good hour or so.  I had assumed there was some kind of maintenance being done on the site, or that there was a very brief, acute landslide of hits to the site for no particular reason (although I know that warning is a different one so it seems unlikely).

So many people were getting the 503 error that I managed to get the 504 error a little while ago, which is "Gateway Timeout". All it means that I was apparently late to the party of hits (or other items) slowing down the server and the proxy was saying, "No more, no more...". That being said, sometimes I will get the 503 error when significant front page content is loading as well - I reloaded and Brian's take on the uniforms was suddenly there. 

It means run.  Don't look back just run as fast as you can.

Sometimes he is meditating:

Sometimes MGoBlog loads way slower than any other site I am browsing that day. Not sure if it is just traffic related or what, but those days usually coincide with the ones where I get the 503. 

I got that too and upon visiting the site, saw an RR *and* a Uniformz thread, either of which on their own always means lots of rabble rabble and thus more traffic than usual.  But both at the same time I'm guessing was more than the site could handle.

When the site is riding the struggle bus, the odds of double posting are increased. Exhibit A:

i have no idea what any of you are talking about, that's just the basic error message husband's get when requesting sex.

You sir, found the end of the Internet. Go back.

It's everyone "studying" for finals, right?