My Discord Bot Died at 3 AM and Nobody Told Me for 6 Hours

The 3am bot outage every solo developer dreads — and the one-line fix that means it never happens again.

My Discord Bot Died at 3 AM and Nobody Told Me for 6 Hours

It's a specific kind of bad morning. You wake up, check your phone out of habit, and there's a message from someone in your server: "hey is the bot broken?" You check — it's been down for six hours. Nobody restarted it. Nothing in your code even told you it happened. You just... didn't know.

If you've built a Discord or Telegram bot for more than a few weeks, you already know this feeling. Here's why it keeps happening, and the one thing that actually stops it for good.

The problem isn't your code

The first time this happens, you assume you wrote a bug. You go digging through your command handlers looking for an unhandled exception. Sometimes you find one. Most of the time, you don't — because the real problem usually isn't a bug at all. It's that free and cheap hosting platforms expect your bot to behave like a website, and it doesn't.

Your bot connects out to Discord's servers. It never opens a port for anyone to check on it. So the platform hosting it just... assumes something's wrong, and either restarts it into a loop or lets it quietly go idle. Your bot's logic was never broken. The platform just never got the signal it was looking for.

Why you don't find out until someone else does

Here's the part that actually stings: without something watching your bot from the inside, you are the monitoring system. You find out it's down the same way your users do — by noticing. Which means the actual downtime is however long it takes for someone to notice and tell you, plus however long it takes you to see the message and fix it. For a bot running while you sleep, that's easily half a day.

The fix takes one line

This is the part that makes the whole thing frustrating in hindsight — once you know the actual cause, the fix is almost embarrassingly small:

import staypresent

staypresent.run("bot.py")

That's it. That one line gives your hosting platform the heartbeat it's been looking for, and it automatically relaunches your bot if it ever actually does crash — no more waiting for a Discord message to find out something broke.

And now you actually find out first

The newest version goes a step further — instead of finding out from a user, you get a live status page, automatically, with zero setup:

import staypresent

staypresent.run("bot.py")
# your status page is now live at /status — uptime, restarts, incidents

Check it from your phone before your coffee's even done. If something restarted overnight, you'll see it — and by the time you check, it's probably already back up on its own.

Stop being the last to know

Your bot doesn't need a bigger server, a rewrite, or hours of DevOps you don't have time for. It needs one thing standing between "crashed silently for six hours" and "restarted itself in two seconds, nobody even noticed." That's the entire job StayPresent does.