🚧ℹ️ Transfers are looking like they'll be done on time, but converting lemmy from kubernetes to docker took longer than expected. Pawb.social is online and we're moving on to furry.engineer and pawb.fun now!

Sorry for the delay, as it looks like we'll probably be ~1 hr late bringing up the last of mastodon.

🚧ℹ️ A few small restarts of the routing middleware may cause momentary blips while we get furry.engineer and pawb.fun online. Those shouldn't last more than a minute or so.

🚧ℹ️ furry.engineer is back online!

🚧ℹ️ pawb.fun is back online!

This concludes the downtime-required portion of our maintenance and switchover!

You'll probably notice that some media for remote users (avatars, banners, attachments) may not be loading -- This is expected!

We're currently migrating the cached data from the old server to the new one in the background as that makes up the bulk of our stored media.

We expect that to continue to transfer overnight and will check back in tomorrow to see how far it's got, and let everyone know once all the transfers are complete.

If you have any issues or feedback on the performance of the services, please let us know on Lemmy at https://pawb.social/c/pawbsocial_feedback, by the hashtag #pawbsocial on furry.engineer or pawb.fun, or by email to network@pawb.social.

Thank you for your patience, and again, a special thank you to our Ko-fi donators that made this possible 💙

ℹ️ We'll be briefly restarting our application router to show a better error message than "404 not found" when the routes go offline (usually due to a restart). Shouldn't last longer than 30 seconds as it's a rolling restart.

ℹ️ Okay! All done!

Now, instead of seeing the generic "404 page not found" error when we restart our services, this page will be displayed explaining the issue more accurately and clearly.

This will typically show up when we restart the services or when a container running a service becomes unavailable, but these conditions should only last at most a minute or two.

You'll still see a differently worded error page served directly by Cloudflare if / when our router goes completely offline.

Finally, we've also added references to https://status.pawb.social in addition to this Telegram channel. Going forward, we'll be ensuring the status site is updated with any maintenance or outages in the same manner as we do here.

ℹ️ Mastodon Update - Nov 6, 2025

We'll be upgrading our Mastodon instances (furry.engineer and pawb.fun) to v4.5.0 at 4 PM US Mountain Time.

We expect this upgrade to take no longer than 30 minutes to perform, and will be performing this upgrade in a rolling manner (beginning with furry.engineer).

✅ Maintenance has concluded! furry.engineer and pawb.fun have been updated to Mastodon v4.5.0!

⚠️☁️ We're aware of ongoing issues with Cloudflare that are causing intermittent connection outages for all Pawb Social services.

If you experience an error page (Cloudflare's "Internal server error", or our "service interruption" page), please wait a few minutes then attempt again. According to Cloudflare, most issues should be resolved, but we're still seeing some blips on our monitoring application and aren't sure how representative that is for our users.

Cloudflare's Status Updates can be found at https://www.cloudflarestatus.com/.

⚠️ We’ve had a power spike and our equipment turned off for safety. Currently bringing things back online.

✅ Service has been restored. Apologies for the interruption.

Additional load we believed to be surge only (not UPS backed) was in fact using the UPS backup power causing the load to exceed the unit's max rating unexpectedly. We're reworking this to prevent this happening again, and apologize for the inconvenience.

⚠️ We’re restarting Lemmy to triage sporadic 502 errors. Hopefully shouldn’t be long.

🚧 Mastodon Update - Dec 8, 2025

We’ll be performing a rolling upgrade of our Mastodon instances, furry.engineer and pawb.fun.

There may be a brief interruption in service while the deployment propagates, but it shouldn’t be longer than 10-15 minutes.

We’ll be starting the maintenance window at 3 PM US Mountain Time, and we expect to be finished by 3:30 PM US Mountain Time.

🎉️️️️️️ That's a wrap! (...21 days early)

Since Crash is likely to forget and a lot of services seem to be running their yearly recaps around this time, we've gone ahead and run Wrapstodon for 2025 on furry.engineer and pawb.fun!

#Wrapstodon is a yearly recap of your activity on Mastodon, your most popular posts and hashtags, and where you might theoretically sit compared to other users of Pawb Social services.

If you're eligible to receive a #Wrapstodon, you'll see the notification on the web client (apps don't show this yet, sorry) saying "Your 2025 #Wrapstodon awaits!"

Here's Crash's as an example of what you may find!

ℹ️ Boom, those just went out to everyone who has been active this year!

The shared Ruby code snippet to manually run Wrapstodon for some reason would exclude anyone that didn't use hashtags.. so.. Yeah, now it goes out to everyone that's posted!

If you didn't see your #Wrapstodon before, it should be in your notifications now. :3

🚧️️️️️️ The UPS breaker tripped while doing cabling and is resetting; We should be back shortly-- Apologies for the interruption!

✅️️️️️️️ All online again! :3

ℹ️ We’ve updated our Terms of Service / Code of Conduct!

Other than the introduction of the existing terms into the new ToS system in Mastodon, we’ve added a jurisdiction clause limiting legal matters to the laws of the State of Colorado, and the state / district courts located therein.

We’re doing this to limit Pawb Social’s potential impact from the upcoming state-based age verification laws, and ensuring that the venue of choice is located where Pawb Social is based.

If there’s any questions or concerns, please reach out to network@pawb.social.

(In plain English: If you want to take Pawb Social to court, you need to do it in Colorado, subject to Colorado law and applicable US Federal law)