Gemcutter

Hey 1440 followers, there's updates and more about what's going on today at rubygems.org at @rubygems_status. See ya there.

Hey folks, we're about to deploy some infrastructure changes. Check out @rubygems_status for more info (for now on too!)

@aefaradien this feed is basically it! I guess we could set up a redirector to redirect here.

Back up again for now...keeping an eye on the server. Having memory issues.

Maintenance mode is online, so gem serving should be working again while we investigate this.

@aefaradien we can put an entry on help.rubygems.org about it, maybe the google juice will work then

And apparently we're down...again.

Now showing our months/years worth of uptime data: uptime.rubygems.org/

Going to sign off for now, more detailed uptime reports on: stats.pingdom.com/0sxq7d9s3p… We'll get that on a .rubygems.org subdomain soon!

Huge thanks to @evanphx for putting out the fire this morning. 6:45 for @qrush in Chicago, much earlier for him!

And we're back up! HAPPY MONDAY!

@rdvdijk cocaine-infused yodeling is the best way to deal with downtime.

Redis is almost ready! Our AOF is *HUUUGE*. Maintenance page is up and gem serving is working, so bundler/gem install should be working.

Found this neat site for our uptime. We'll toss it on a .rubygems.org subdomain after this incident: stats.pingdom.com/0sxq7d9s3p…

@RainuxLuo we also actually have 99% uptime most months! stats.pingdom.com/0sxq7d9s3p…

@RainuxLuo sorry for the hassle. see stackoverflow.com/questions/… for a workaround.