Ghost Status: How to Check If Ghost Is Down Right Now (2026)
Where to find the Ghost(Pro) status page, what each component means, and how to diagnose Ghost outages differently depending on whether you use Ghost(Pro) managed hosting or self-hosted Ghost.
Is Ghost Down Right Now?
For Ghost(Pro) users: check status.ghost.org. For self-hosted Ghost: status.ghost.org does not apply — your server is your infrastructure.
Ghost(Pro) vs Self-Hosted: The Critical Distinction
Ghost has two completely different deployment models with entirely different troubleshooting paths. Knowing which one you use determines where to look when something breaks.
Ghost(Pro) — Managed Hosting
- Hosted at ghost.io — Ghost Foundation runs the servers
- Your site URL ends in .ghost.io (or custom domain)
- Ghost handles updates, backups, email delivery, CDN
- Status page: status.ghost.org
- If Ghost(Pro) is down, it's their problem to fix
Self-Hosted Ghost
- Runs on your own VPS, Docker, or cloud server
- You manage Node.js, Nginx, MySQL, and SSL
- Email via Mailgun, Postmark, or SMTP you configure
- status.ghost.org does NOT apply to your setup
- If your site is down, check
ghost statuson your server
your-site.com/ghost. If the URL shows a ghost.io billing badge or the Ghost Foundation manages your account, you're on Ghost(Pro). If you set it up yourself on DigitalOcean, Railway, or a VPS, you're self-hosted.Ghost(Pro) Official Status Page
The official Ghost(Pro) status page at status.ghost.org is maintained by Ghost Foundation and covers all managed hosting components:
Monitor your Ghost site independently
Better Stack monitors your Ghost site every 30 seconds from multiple locations — Ghost(Pro) or self-hosted. Know about outages before your subscribers do.
Try Better Stack Free →Self-Hosted Ghost: Troubleshooting Checklist
If you run Ghost on your own server, outages are your responsibility. Here's the systematic check order:
Check the Ghost process
Ghost runs as a Node.js process managed by Ghost-CLI or PM2. A crashed process brings down the site.
ghost status
# or: pm2 statusCheck Nginx / reverse proxy
Ghost typically runs on port 2368 behind Nginx. Nginx issues cause 502 errors even when Ghost is running.
sudo systemctl status nginx
sudo nginx -tCheck Ghost logs
Ghost logs capture startup errors, database failures, and email issues.
ghost log
# or: tail -f /var/www/ghost/content/logs/ghost.logCheck database connectivity
Ghost uses MySQL (production) or SQLite (development). A database connection failure prevents Ghost from starting.
mysql -u ghost -p ghost -e "SELECT 1"Check server resources
Insufficient memory is a common cause of Ghost process crashes on small VPS instances.
free -m
topGhost Newsletter Issues
Ghost newsletters are one of the most common pain points. Here's how to diagnose email delivery failures:
| Symptom | Likely Cause | Where to Check |
|---|---|---|
| Emails not sending (Ghost Pro) | Ghost(Pro) email incident | status.ghost.org → Email |
| Emails not sending (self-hosted) | Mailgun API key or domain invalid | Ghost Admin → Settings → Email |
| Emails landing in spam | Missing DKIM/SPF/DMARC records | DNS records for your sending domain |
| Subscriber count stuck | Portal or membership incident | status.ghost.org → Memberships |
| Paid subscriptions not processing | Stripe integration issue | Ghost Admin → Members → Stripe dashboard |
| Test email works, bulk fails | Email provider rate limit | Mailgun/Postmark send limits on your plan |
| Newsletter sent but no clicks | Tracking or link issue (not an outage) | Ghost Admin → Posts → Email performance |
What to Do When Ghost Is Down
Ghost(Pro) Users
- Check status.ghost.org for incident confirmation
- Subscribe to incident email updates on status page
- Contact Ghost(Pro) support with your site URL
- Notify subscribers if a newsletter was delayed
- Wait — Ghost(Pro) outages are typically resolved quickly
Self-Hosted Ghost Users
- Run
ghost restartif the process is stopped - Check Nginx errors in
/var/log/nginx/error.log - Free memory if the VPS is resource-constrained
- Check Ghost Forum for known version-specific bugs
- Set up monitoring to catch future outages early
Monitor your Ghost site availability independently
Better Stack monitors your Ghost site every 30 seconds, independent of whether you use Ghost(Pro) or self-host. Alerts via Slack, email, or PagerDuty.
Try Better Stack Free →Frequently Asked Questions
Where is the official Ghost status page?
Ghost(Pro)'s official status page is at status.ghost.org. It shows real-time status for Ghost(Pro) managed hosting including the dashboard, site hosting, API, email/newsletter delivery, and CDN. If you run self-hosted Ghost, status.ghost.org does NOT apply — your issues come from your own server, VPS, or container. For independent third-party monitoring of your Ghost site, use apistatuscheck.com.
Why is my Ghost site down but the admin panel works?
Ghost separates the admin panel (your-site.com/ghost) from public site delivery. On Ghost(Pro), a CDN or hosting outage can affect public visitors while the admin panel remains accessible. For self-hosted Ghost, this usually indicates a Nginx/reverse proxy issue rather than Ghost itself — Ghost's Node.js process may be running fine while Nginx is misconfigured or down. Check status.ghost.org for Ghost(Pro) users; for self-hosted, check your reverse proxy configuration.
Why are Ghost newsletters not sending?
Ghost newsletter delivery failures have two common root causes: (1) Ghost(Pro) email delivery incident — check status.ghost.org for the Email component, (2) Self-hosted Ghost email configuration — Ghost uses Mailgun by default, check your Mailgun dashboard for bounces, verify your Mailgun API key and domain in Ghost settings, check DKIM/SPF/DMARC DNS records. Ghost(Pro) handles email delivery infrastructure for you; self-hosted Ghost requires you to manage the email provider integration separately.
What is the difference between Ghost(Pro) down and self-hosted Ghost down?
Ghost(Pro) is Ghost's managed hosting service — Ghost Foundation runs the servers, updates, backups, and CDN for you. If Ghost(Pro) is down, status.ghost.org will reflect it. Self-hosted Ghost runs on your own server (DigitalOcean, AWS, Hetzner, etc.) — if it's down, it's your infrastructure issue, not Ghost's. Most 'is Ghost down?' searches are from Ghost(Pro) users. Self-hosted users should check their server status, Nginx logs, Node.js process (pm2 status), and database connection.
Why is the Ghost admin panel not loading?
Ghost admin panel loading failures are caused by: (1) Ghost(Pro) dashboard incident — check status.ghost.org, (2) Self-hosted: Ghost Node.js process crashed — run 'ghost status' or 'pm2 status' on your server, (3) Database connection issue — Ghost uses MySQL/SQLite, check database logs, (4) Browser cache or extension interference — try incognito, (5) Server resource exhaustion — check CPU/memory on your VPS. For Ghost(Pro), this is rare and usually resolves quickly; for self-hosted, crashed processes are the most common cause.
Alert Pro
14-day free trialStop checking — get alerted instantly
Next time Ghost goes down, you'll know in under 60 seconds — not when your users start complaining.
- Email alerts for Ghost + 9 more APIs
- $0 due today for trial
- Cancel anytime — $9/mo after trial