Why Is My Discord Bot Offline? How to Keep a Bot Online 24/7
A Discord bot goes offline when the program running it stops, so to keep a bot online 24/7 you need it hosted on a machine that never sleeps. Either pay for a real always-on host and manage it yourself, or use a hosted bot like PeakBot that runs on its own infrastructure and stays online by default with nothing for you to maintain.
If your bot keeps showing up grey in the member list, you are not alone. "Why is my Discord bot offline?" is one of the most common questions server owners ask, and the answer is almost always the same: the thing that runs your bot stopped running. This guide explains exactly why that happens, what "always on" really requires, and the two real paths to a bot that never drops.
Why your Discord bot keeps going offline
A Discord bot is just a program. It logs into Discord, holds an open connection, and listens for events. The moment that program stops running, your bot disconnects and goes grey. Discord itself is fine. Your bot's host is the problem.
Here are the usual reasons a self-run bot drops:
- The host went to sleep. Free hosting platforms put inactive projects to sleep after a few minutes. When the project sleeps, the bot disconnects.
- The process crashed. An unhandled error, a memory spike, or a bad bit of code can kill the process. With nothing to restart it, the bot stays offline until you notice.
- Your computer was running it. If you started the bot on your own PC, it dies the moment you close the terminal, sleep the laptop, or lose internet.
- The token was reset or the bot was rate-limited. A regenerated token or too many failed requests can lock the bot out.
- The hosting free tier ran out of hours. Many free plans cap monthly runtime. Hit the cap and everything shuts off.
If your bot is online but acting dead instead, that is a different issue covered in our guide to why your Discord bot is not working and how to fix it. For pure offline problems, read on.
The problem with free hosts (Replit, Glitch, UptimeRobot pings)
A lot of tutorials tell you to host a bot on a free platform and "keep it awake" by pinging it every few minutes. This works until it doesn't, and it is the single biggest reason hobby bots flicker on and off.
Here is the honest breakdown:
- Replit is great for learning and quick prototypes. But on the free tier, repls sleep when idle. People work around this by adding a tiny web server and pinging it with an external service, which is a hack, not a fix. Repls still get recycled, and your bot still drops.
- Glitch had the same model and the same sleeping behavior, with project hour limits on top.
- UptimeRobot pings are an external service hitting your bot's web endpoint on a schedule to fake activity. The catch: pinging keeps a web page awake, but it does nothing for a crashed bot process, a depleted hour quota, or a platform that has decided to recycle your container anyway.
The deeper issue is that none of these were designed to run a persistent Discord connection forever. They are designed for code you visit, edit, and walk away from. You can fight that with hacks, but you will spend more time babysitting uptime than building your community.
There is nothing wrong with free hosting to learn. The mistake is trusting it to keep a live community's bot online around the clock.
What 'always on' actually requires
Before you pick a path, know what genuine 24/7 uptime needs. A bot that truly never drops requires all four of these:
- A machine that never sleeps. A server or container that runs continuously, not one that idles out.
- Automatic restarts. When the process crashes (and eventually it will), something must bring it back instantly without you touching it.
- A stable network connection. Reliable bandwidth to Discord's gateway, not your home Wi-Fi.
- Monitoring and alerts. Someone or something watching, so a multi-hour outage doesn't go unnoticed.
Miss any one of these and you get flicker. Pings fake the first one badly and ignore the other three, which is why the ping trick disappoints. Now here are the two real ways to get all four.
Option 1: Self-host and manage uptime yourself
If you wrote your own bot or run a custom one, self-hosting on proper infrastructure is the path that gives you full control. It costs money and time, but it works.
Step 1: Pick real always-on hosting
Use a paid host built to run processes continuously: a small VPS (virtual private server), a container platform with a paid always-on tier, or a dedicated bot-hosting service. The key word is "paid and always-on." If a plan mentions sleeping after inactivity, it is not what you want for production.
Step 2: Run the bot under a process manager
Do not run node bot.js in a terminal and hope. Use a process manager such as PM2, systemd, or a Docker restart policy so that when the process dies, it restarts on its own within seconds. This single step eliminates most "my bot went offline overnight" reports.
Step 3: Add health checks and alerts
Set up basic monitoring that tells you when the bot disconnects, by email, SMS, or a message to a private channel. You want to learn about downtime from an alert, not from an angry member.
Step 4: Keep the token safe and handle reconnects
Store your bot token in an environment variable, never in code you might share. Make sure your code handles Discord gateway reconnects gracefully so a brief network blip doesn't require a full restart.
Self-hosting is the right answer when you have a genuinely custom bot and the willingness to maintain it. For most server owners, though, that maintenance is the whole problem they wanted to avoid, which leads to option 2.
Option 2: Use a hosted bot that's online by default
The simplest way to never think about uptime again is to not run the bot yourself at all. A hosted bot runs on the provider's infrastructure. You invite it, configure it through a dashboard, and it stays online because keeping it online is the provider's job, not yours.
PeakBot is built exactly this way. It is a free, AI-powered Discord bot that runs on its own always-on infrastructure, so there is no host to rent, no process manager to configure, and no ping hack to maintain. You add it once and it stays online. It currently powers 500+ Discord communities, and it replaces MEE6, Carl-bot, Dyno, and TidyCord with a single bot, which also means one fewer thing that can drop offline.
What you get on the free tier, with no time limit and no trial, includes:
- Context-aware AI moderation that reads message intent per channel instead of matching a fixed blocklist
- XP and leveling across messages and voice, with leaderboards and role rewards
- A ticket system with categories and transcripts
- Welcome messages with embeds, DMs, and auto-role
- Unlimited reaction roles, giveaways, polls, and a starboard
- Anti-raid and anti-nuke protection, full logging, and invite tracking
- Twitch and YouTube integrations and custom commands
Pro is $8.25/month (or $69/year, which works out to $5.75/month billed yearly) per server, and it unlocks the AI Server Builder that builds a complete server, including channels, roles, categories, permissions, and automations, from a plain-English description in under 60 seconds.
For comparison and honesty: MEE6 premium is $11.95/mo, Carl-bot premium is $7.99/mo, Dyno premium is $4.99/mo, and Arcane is about $7 per server per month. Each of those is a capable bot with real strengths. The point here is not that they go offline, they are hosted too, but that PeakBot gives you the widest free feature set on always-on hosting without a separate per-feature host to manage. If you are just deciding which bot to invite, the easiest Discord bot to set up walks through that choice.
How to check if your bot is really online 24/7
"Looks online right now" is not the same as "online 24/7." Here is how to actually verify uptime:
- Check the member list color. A bot with a green, idle, or DND dot is connected. Grey means offline. This is the quick glance, not the proof.
- Watch it over time. Note the bot's status at a few different hours, including overnight. A bot that is reliably green at 3 a.m. and 3 p.m. is a good sign.
- Test a command after quiet periods. Run a simple command first thing in the morning. If it responds instantly after hours of no activity, the host is not sleeping it.
- Use the bot's own dashboard if it has one. A hosted bot like PeakBot shows status and recent activity in its analytics dashboard, so you are not guessing from a colored dot.
- Set up an uptime monitor for self-hosted bots. If you run your own, a monitoring service that alerts you on disconnect is the real test.
Troubleshooting: bot shows online but isn't responding
Sometimes the dot is green but commands do nothing. The bot is connected to Discord but not reacting. Work through these in order:
- Permissions. The bot needs permission in the specific channel and the right server-level permissions. Missing permissions silently break commands. Roles are a common culprit, covered in why your Discord bot won't assign roles.
- Role hierarchy. A bot can only manage roles and members below its own highest role. Drag the bot's role up in Server Settings, Roles.
- Slash commands not registered. Newer bots use slash commands that can take time to appear or need a re-invite with the right scope. Re-adding the bot often fixes this, as shown in how to add a Discord bot step by step.
- Gateway intents. Self-hosted bots need the correct intents enabled in the developer portal to receive message and member events.
- The bot is rate-limited. Too many actions too fast can throttle responses temporarily. Give it a minute.
- It is connected but the process is stuck. For self-hosted bots, a frozen process can stay "online" while doing nothing. A restart clears it, another reason a process manager matters.
The simplest path to a bot that never drops
If you want full control over custom code and you enjoy infrastructure, self-host on a paid always-on platform, run under a process manager, and add alerts. That gets you genuine 24/7.
If you just want a bot that is online whenever your members are, without renting servers or fighting sleep timers, use a hosted bot that runs on its own always-on infrastructure. PeakBot is free, AI-powered, and online by default, so uptime stops being your problem. You can see everything it does on the features page or compare it side by side on the comparison page.
Frequently asked questions
Why does my Discord bot keep going offline?
Your bot goes offline whenever the program running it stops, usually because a free host put it to sleep, the process crashed with nothing to restart it, or it was running on a computer that got turned off. Hosting it on an always-on platform, or using a hosted bot, fixes this.
Does pinging my bot with UptimeRobot keep it online 24/7?
Not reliably. Pinging keeps a web endpoint awake, but it does nothing for a crashed bot process, an exhausted free-tier hour limit, or a platform that recycles your container. It is a workaround for free hosts, not a real uptime solution.
How do I host a Discord bot for free without it going offline?
True free 24/7 hosting of a self-written bot is hard, because free tiers sleep or cap runtime. The reliable free path is to use a hosted bot that runs on the provider's always-on infrastructure, like PeakBot, which stays online without you hosting anything.
Is PeakBot online 24/7?
Yes. PeakBot runs on its own always-on infrastructure, so it stays online by default with nothing for you to host, ping, or restart. It currently powers 500+ Discord communities.
My bot shows online but won't respond to commands. What's wrong?
That is usually a permissions, role hierarchy, or slash-command registration issue rather than an uptime problem. Check the bot's channel permissions, make sure its role sits above the roles it manages, and try re-inviting it with the correct scopes.
