Error 37

(noun) The infamous error message displayed in the game Diablo 3 whenever a player is unable to login. The error is a result of Blizzard's servers being overloaded, resulting in a server crash. Blizzard, in their infinite wisdom, decided to require people who spent $60 on their video game (should have only been $50, considering there are no licensing fees on pc) to be online even when they simply wanted to play the single player campaign.

Nerd 1: ERROR 37!!! WTF!!! I WAITED TEN YEARS TO PLAY THIS FUCKING GAME AND NOW I CAN'T BECAUSE YOU STUPID FUCKERS AT BLIZZARD MADE IT SO I CAN'T EVEN PLAY THE FUCKING GAME WITHOUT BEING CONNECTED TO YOUR STUPID FUCKING SERVERS THAT YOU HAD TO KNOW WHERE GONNA CRASH, BECAUSE THEY FUCKING CRASHED WHEN YOU DID THE FUCKING BETA!!! WTF!!!

Nerd 2: Yeah man, that sucks. That's why I bought Max Payne 3.

by cfisher2833 October 26, 2012

Error 37

Absolute rejection in the face of overwhelming loyalty and love.

Alternative meanings:

- not complying to a request
- an excuse by Blizzard to not have adequate servers for Diablo

I asked my girlfriend if she wanted to marry me but she responded with an Error 37.

by demoneyes905 November 9, 2012

Error 37

The complete and utter despair that fills your soul right as the moment of pure bliss is about to be reached but then fails.

I bought a single player game I waited 12 years for, then couldn't play it because of error 37

by Gindy389 October 24, 2012

Error 37

Error 37 is the result of Activision thinking they know how to make the sequel to Blizzard's #1 game and failing at server maintenance.

EX1: "Hey man, have you played Diablo 3 yet?"

"Fuck no, I get that retarded Error 37."

EX2: "Hey, can you look something up for me real quick?"

"Nope, Error 37."

by Axis1337 October 24, 2012

Error 37'd

To be Error 37'd is to be playing Diablo 3, then being cut off because the server isn't up-to-par.

Person 1: What's up with you, bro?

Person 2: I got Error 37'd, man.

Person 1: Ouch.

by JustNineLetters October 27, 2012

Error 37

The infamous error associated with the catastrophic launch of Diablo 3 in 2012.

"This is a message to the people that work for Blizzard Entertainment, specifically the Diablo 3 crew. I wasn't going to make a video today because I didn't think anybody would see it. I thought everybody would be out playing Diablo 3, and I thought I would be playing Diablo 3, you'd be playing Diablo 3, but NOBODY'S FUCKING PLAYING DIABLO 3! Because you gotta see the servers down, the servers are down! And every time I try to log in, all I get is fucking Error 37! Error 37! I keep trying to log in and I get Error 37! ERROR 37! Why the fuck is it 37?! What the fuck are the other 36?! Shouldn't this be error number 1?! Error number 1, I can't log the FUCK IN!? Holy SHIT! WHAT THE FUCK IS NUMBER 35?! SOMEONE SHOT SOMEBODY RUNNING THE SERVERS?! DID ONE OF THE FUCKING HAMSTERS GET LOOSE?! I SPENT ALL FUCKING NIGHT TRYING TO GET THIS GODDAMN COLLECTOR'S EDITION! I STOOD LINE AT FUCKING WALMART! I CAN BARELY STAND UP! I FUCKING STOOD IN LINE AND JUST CAN'T EVEN PLAY THE FUCKING GAME! And oh, okay, I finally- okay, I finally get in, I'm- I finally get past Error 37! What do I get?! Error 3006! Can't even load the character screen! Error 3006! HOW MANY FUCKING ERRORS DID YOU GUYS COUNT TO?! Fucking what do I expect the next error... 9999? HOLY SHIT, IT'S OVER 9000! FUCK you, Blizzard! FUCKING... WORK YOUR GAMING YOU AIN'T WORK! THIS IS BULLSHIT! THIS IS BULLSHIT! I PAID MONEY, CASH MONEY, DOLLARS MONEY, CASH MONEY! FUUUUUUUUUUUUUUUUUUUUU-"

by FB3Network February 14, 2026