I’m creating this topic to report planned maintenance breaks or unexpected hiccups on Postcrossing’s servers that might cause the website to be unavailable for a bit.
These downtimes usually don’t last very long, so if you bump into one, please be patient, take a little break while we work on things and try again later! 
Is everything okay today?
I searched the forum for an announcement about maintenance but I didn’t find anything.
It’s back up on my end!
Everything is ok and the site should be back now! Just a quick upgrade to a bigger server, ahead of the World Postcard Day spike.
And in a few minutes we’re going to downgrade the server, now that the World Postcard Day peak is behind us. Should be just a few minutes of downtime!
…aaaaaand we’re back! Carry on!
There’s a security update to the database server on the to-do list for today — the website should be down for less than 5 minutes.
And we’re back — all good!
So lucky to witness the few-minute long update - my first time!
Thanks a lot for maintaining such a wonderful website!
Thank you. I’m facing this issue when I am registering my postcards… But it’s returned to normal finally.
It’s been a bit of a wild ride with the database server today 
but hopefully things have quieted down now.
Just letting everyone know we’re going to be updating the forum software in a little bit — please expect some downtime (though hopefully not too long).
Well, the good news is that the downtime was short! But on the other hand, some images seem to be missing… we’re working on it!
I was trying to upload some to a pm and wondering what on earth I was doing wrong. Now I understand!
Quick maintenance break on the main site today — we’ll be back in a minute, if all goes well!
…aaaaand done, all systems good. Carry on!
Just a quick heads up that the website will be down soon for about 5 minutes or so, while we reboot to make some security updates on the database server.
…and back! All good. 
Thanks for all your hard work to keep things running smoothly! 
Sorry for all the hiccups today! 
Paulo was trying to address one issue and ended up causing another… Things should be back to normal now that the misbehaving bit of code has been found.
