Still here. Was always here since 2008. I'm currently looking after 63,594,737 bins for you. Living in a mostly stable maintenance mode. You can support my continued existence too https://t.co/ZwTiNsEzFn See you in the code 👋

db fire update: all back. No data loss. Just time. Send @rem hugs.

db fire update: pretty disappointed that the AWS EC2 r4.large machine last so little time. It was originally launch on October 11, 2017 at 9:24:56. Today it was "scheduled for retirement".

db fire update: snapshot going slowly… about 1% per minute.

db fire update: New machine provision and running. Currently snapshotting the db volume so new machine can mount it.

Morning. Apparently stuff is on fire. Yay. Will try my best to recover whatever machine is hosed.

Gah, there was a bug in the cookie setting button at the end of the post. It's fixed now, you can try v5 now:

It's been a while, 2 years in fact, but the blog is back with news as to the future of jsbin AND a direct link to try out v5-alpha today:

A long standing bug that meant that users could not upgrade to PRO has now (finally) been fixed 👉 https://t.co/BWzixNtesR Sorry for the delay, and keep tuned in for jsbin version 5 - open alpha testing soon.

Still working on solving the server issues. We don't have an ETA right now. In the mean time you can use our friends at @js_bin

All the data is there (nearly 40 million bins) and available again. There's still core issues with CPU on apps, and I'm still working on v5.

Creating new servers from the original images didn't seem to work. At one point, I had 4 separate db AWS EC2 instances, but none working.

Original service restored. Sorry about the outage. AWS scheduled a same day reboot on the db server, but it never came back. —

Update: https://t.co/SEbJsHFWaZ is live again (for the time being!!!), and database is back, but changes **are not being saved**. /fixing

Okay! Progress is made. Now gotta reconfigure some DNS and fingers crossed, should be back shortly.

Currently reconfiguring the new data server to mount and use the original mysql database. Hitting a few issues, but getting closer.

Update 1pm UK time—still down. Old db server is up, but unreachable (unsure how). New db server is up and I am configuring now.

Sorry folks, jsbin is going to be down for a little longer this evening. Back on it in the morning.

Update: some 12 hours later, new machine is running, drives attached, but _cannot_ access it. Don't know why. My AWS < my JS (╯°□°)╯︵ ┻━┻

The day is getting on, but I've managed to launch a new machine with (hopefully) the original data drive attached. Still working on it.