TL;DR at the very bottom. I woke up today at around noon to an email from my host.


My host has temporarily decided to block port 443 (so https won’t work). I’m trying to get them to take it off right now. Until then the whole site will still work through http://catbox.moe/
Sorry.
Update 2/15/2017 1:40 PM
I’ll be writing a blog post later about this. The block should be removed shortly.
catbox.moe
files.catbox.moe
qt.catbox.moe
nofun.catbox.moe
catbox.moe
files.catbox.moe
qt.catbox.moe
nofun.catbox.moe
sorry for the late stats post. hope you all have a great new year~
While accessing some older files, you might meet a black page with Lain on it before being redirected to your file. Don’t worry! It’s a part of my new space saving project hereafter called Project Lain. Skip to the last paragraph for a tl;dr
Currently, Catbox doesn’t cost that much to host. But if I were to keep growing at this exponential rate, it’d cost me more money. And I don’t like spending more money than I have to. So I’ve been looking into alternatives, and my decided solution is to offload files that haven’t been accessed for more than 5 months to AWS S3.
What does this mean exactly? What happens to your files when nobody has accessed them after 5 months? Not a lot really. Your file is moved from Catbox’s server to my AWS S3 instance, and a flag is set in my database that says “hey, this file doesn’t exist on the main server anymore”. If someone were to then access the file after it’s been moved, they’ll be greeted by the intermission page with Lain. During this time, the file is grabbed from my AWS S3 instance and put back on the main server. After a few seconds, the page will refresh to check if the file has been downloaded yet, and if not, will continue to show the intermission page (repeat). The file will then be kept on Catbox for another 5 months, provided nobody accesses it.
So, what does this mean for you, the end user? That really depends on if you’re registered. Currently, registered users’ files are excluded from the 5 month no access move policy. That means that only anonymously uploaded files will be moved to S3. However, this does not impact the reliability of your files being hosted on Catbox. Anonymously uploaded files will still be served after 5 months of no access. They’re just on another server.
catbox.moe
files.catbox.moe
qt.catbox.moe
nofun.catbox.moe
Oh gosh 2 million hits, and nearly 6 TB of bandwidth!

I love you guys~
catbox.moe
files.catbox.moe
qt.catbox.moe
nofun.catbox.moe
catbox.moe
files.catbox.moe
qt.catbox.moe
nofun.catbox.moe
And as always, thanks for using Catbox~
I swear I’ve been working!
A lot of the updates have been on the back-end: segregating my API so it’s more manageable, moving resources into folders where I can better edit them. But the biggest change I’ve been working on is albums!
Just like Imgur, but better because no ads and it’s moe. It took me about a month and a half of on and off writing to finish it to the point where I’d be happy deploying it, but even now there’s some smaller style points that I want to fine tune (if you saw Catbox in it’s infancy, you’d know styling isn’t my forte). I’m also looking for your input! If there’s anything you’d do differently, tell me about it. I’m (usually) pretty good at looking over criticism, and might even implement some of your ideas! Hit me up here
catbox.moe
files.catbox.moe
qt.catbox.moe
nofun.catbox.moe
oh god so much traffic.