The story so far
A collection of the verified and close to verified updates on Plastic’s status. For more information, check out the FAQ.
July 15th
“We’ll probably be back up by late Monday. Really.”
Carl posts this update on the 15th, spends most of the weekend in Plastic Chat.
July 7th
Carl pops into #plastic and asks those present to test out a URL.
June 21st
“We now have a working server image; currently testing across various hardware, possibly using virtual devices and drivers; also need to yet make some decisions on RAID. Another day or two is all.”
Plastic Chat returns, with the aforementioned update message.
Early June
Plastic Chat goes offline for a couple of weeks.
May 23rd
As promised, the site goes down again.
May 16
Although the site is back up, it seems the tech issues are still not entirely solved. The following excerpts are reportedly attributed to carl.
“The thing is with these expectations is that I need the slack…”
“I don’t want to say anything until I know what I’m saying. Because if I say the wrong thing, make a bad estimate, then I’m savaged. Pilloried. Crucified.”
“Anyway, we had no machine from which to broadcast said status message…We just went from three to two [locations]. I have to find another sucker.”
“…I’m not done, and the site’s gonna go down again.”
May 13th
Plastic springs back to life.
May 10th
An explanation for the downtime appears on Plastic Chat.
“The old custom kernels from a couple years back are incompatible with the packet inspection that’s now taking place in hardware before it reaches the web application servers. So the web app has to be patched to not rely on the custom environment anymore.”
Sometime around May 1st
Plastic goes down. Initial uncertainty about the reason, talk of a possible DDOS attack on the site.