Community History:502 bad gateway
From Blaseball Wiki
During the early days of the Discipline Era, the Blaseball website would frequently fail under heavy traffic. When this occured, the Nginx proxy that served as a front-end would report a 502 bad gateway error. Afterwards, the umpires or Commissioner would frequently call for a "siesta", pausing gameplay until the site recovered. An extended siesta took place following Season 3 during which the servers were upgraded[1], which brought an end to the regular appearance of the error.
Legacy
The gateway in front of the arch leading to Blaseball 2 is named the Bad Gateway.[2]
