How long do skool.com outages usually last?

Most resolve in 5–30 minutes. Planned deploys often clear in under 5 minutes. Unplanned incidents are the long tail — anywhere from 15 to 90 minutes once or twice a year. Anything past 2 hours is rare and you would see widespread coverage on Twitter/X. The platform's overall uptime is high, similar to other modern SaaS communities — over 99.9% on a yearly basis.

Is the maintenance page my fault — did I get banned?

Almost certainly not. Bans show a different screen with a specific message, not the generic maintenance page. If you can reach skool.com on a phone hotspot but not your home Wi-Fi, it is your network. If multiple devices show the same screen, it is global. Either way, account suspensions are rare and always communicated by email first, not by a maintenance page.

Should I refund members during a skool.com outage?

For an outage under an hour, no. Send a one-line acknowledgement and move on. For an outage that interrupted a paid live event or a launch deadline, offer an extension, a recording, or a small credit — not a full refund unless they ask. Members value composure more than apology, and overreacting to a 30-minute issue makes the outage feel bigger than it was.

Can I keep working in tools4skool while skool.com is down?

The tools4skool dashboard remains accessible because it runs on your local browser session and your own backend. You can review queued DMs, edit sequences, plan scheduled posts and check the CRM pipeline. Outbound actions to skool.com (sending DMs, publishing a post) pause until skool is reachable again, then resume from where they left off. Nothing is lost.

Where is the official skool.com status page?

Skool does not publish an official public status page at present. To triangulate during an outage, search Twitter/X for `skool down` or `#skoolcom`, check Down Detector for skool.com, ask in another skool community you belong to, or try a third-party uptime checker. If founder-owned, you may also see a tweet from @samovens acknowledging long incidents.

Skool Under Maintenance: What That Page Means and What to Do

On this page

TL;DR
What the maintenance page actually means
How to check if it is global
What to do while you wait
After it is back up
FAQ

TL;DR

When skool.com shows a maintenance or we'll be right back screen, it is almost always platform-wide, not specific to your community or your account. Skool does not publish a public status page, so the fastest way to confirm is to ask in another community or check Twitter/X for the #skool tag. Most outages last 5–30 minutes. There is nothing useful you can do during a true outage other than communicate with paying members on a backup channel — a Telegram broadcast, an email list, or a tweet that pins to your profile. Once it is back up, members do not need a refund for a 30-minute outage; just send a one-line acknowledgement and move on.

Start your own Skool community in 60 seconds.

14-day free trial — no card required. Most community owners decide whether Skool fits within the first week.

Start Skool free trial →

What the maintenance page is signalling

Skool's stack runs on standard cloud infrastructure. A maintenance screen typically appears for one of three reasons:

1. Planned deploy. Skool ships features regularly. A deploy that touches the database or auth layer can flash a maintenance screen for a minute or two. 2. Unplanned incident. A bad deploy, a third-party dependency outage (Cloudflare, Stripe, the email provider), or a sudden traffic spike can take parts of the platform down. These are the longer outages — sometimes 30–60 minutes. 3. Regional issue. Cloudflare or upstream DNS problems can make skool.com look down to people in one country while it works fine elsewhere. This is more common than people think.

The screen is generic on purpose. It does not tell you which of the three you're seeing, and it does not estimate a return time.

How to confirm it is global before you panic

There is no official skool.com status page (as of this writing). To triangulate fast:

Try a different network — phone hotspot vs home Wi-Fi. Same screen on both = not your network.
Search Twitter/X for `skool down` or `#skoolcom` — if it is global, others are tweeting within 2 minutes.
Check Down Detector for skool.com. Spike in reports = real.
Ask in another community you're a member of. If multiple owners report the same screen, it is platform-wide.
Try `https://www.isitdownrightnow.com/skool.com.html` as a sanity check.

If you can reach the marketing site (skool.com) but the app subdomain is dead, that is a backend issue. If both are dead, it is DNS or Cloudflare. Either way, you wait.

What to actually do during the outage

Three useful things you can control:

Communicate on a backup channel. This is the case for keeping an email list of paying members. A one-line message — Skool is having a brief outage, we'll resume the live call as soon as it's back — keeps people calm and signals professionalism. If you don't have an email list, your own X profile and a pinned tweet works.

Note the time and what you saw. Screenshot the maintenance page with a timestamp. If the outage stretches past an hour and affects something paid (a live event, a course launch), you may want it as evidence later.

Don't keep refreshing. It does nothing. Set a 10-minute timer and check once.

This is also a good moment to evaluate whether your retention workflow has any single points of failure. tools4skool runs as a Chrome extension on your local browser session, so the dashboard pages and DM queues are still visible during a skool.com outage — they just can't send until skool is back. The queue resumes automatically.

What to do once it is back up

Send a single short message in your community. Don't apologise for things you didn't cause — just acknowledge and continue. Something like We're back. The live Q&A starts in 5 minutes lands well.

If the outage interrupted a paid event (a live workshop, a launch deadline, a checkout flow), give an extension or a recording. Members rarely ask for refunds over a short outage; they do remember when an owner handles the moment with grace.

For recurring outages, tools4skool logs every queued DM and scheduled post so nothing is lost — sequences resume on the same step they paused on, and the churn saver DM still fires within 60 seconds of a cancellation once the platform is back online. Free plan covers 1 sequence and 20 DMs/day; paid plans start at $29/month.

Stop leaving DMs, churn, and revenue on the table.

tools4skool plugs the holes Skool ships with. Free plan forever, paid tiers from $29/mo.

Book a demo →

30-second form · no credit card · we email when access opens

Frequently asked

Three causes, in order of likelihood: a planned deploy that touched the database or auth layer (1–5 minutes), an unplanned incident from a bad deploy or third-party dependency outage (15–60 minutes), or a regional Cloudflare/DNS problem affecting only some users (variable). The screen is intentionally generic and does not tell you which you are seeing. There is no public status page.

Ready when you are.

Drop your email — we'll loop you in the day access opens.

Book a demo →

30-second form · no credit card · we email when access opens