Skip to main content
Teachable logo

Is Teachable Down?

No — Teachable is up

Reachable from all 8 checked regions

Average response time: 556ms

Last checked · checks run every 6 hours

Official status page: https://www.teachablestatus.com

Teachable uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
476ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 51 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

51-day clean streak
Sep 10: 100.00% uptime, 32 checks
Sep 11: 100.00% uptime, 32 checks
Sep 12: 100.00% uptime, 32 checks
Sep 13: 100.00% uptime, 32 checks
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: 100.00% uptime, 24 checks
Sep 22: 100.00% uptime, 24 checks
Sep 23: 100.00% uptime, 39 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 40 checks
Sep 30: 100.00% uptime, 32 checks
Oct 1: 100.00% uptime, 32 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks, 1 incident
Oct 9: 100.00% uptime, 24 checks
Sep 10 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

gru
691ms
DNS 178ms TCP 2ms TLS 12ms TTFB 684ms
iad
274ms
DNS 110ms TCP 2ms TLS 13ms TTFB 269ms
jnb
826ms
DNS 285ms TCP 1ms TLS 12ms TTFB 821ms
lax
369ms
DNS 61ms TCP 2ms TLS 14ms TTFB 359ms
lhr
516ms
DNS 91ms TCP 2ms TLS 17ms TTFB 509ms
nrt
708ms
DNS 153ms TCP 1ms TLS 13ms TTFB 704ms
ord
333ms
DNS 128ms TCP 2ms TLS 12ms TTFB 327ms
sin
735ms
DNS 152ms TCP 1ms TLS 18ms TTFB 729ms

What Teachable does

Teachable hosts and sells online courses, coaching programs, memberships and digital downloads for independent creators and small education businesses. Its own site claims more than 150,000 creators and businesses use it. A creator's school runs on a Teachable subdomain or a custom domain, so when Teachable is unavailable the storefront, the checkout and the student video library all go with it.

What an outage looks like

Students cannot log in to a school, or course pages load but video playback stalls. Checkout fails at the payment step, which Teachable tracks separately from the rest of the site. Custom domains may stop resolving to a school while teachable.com itself works normally. Course building and video uploading break for creators while already-published content still plays for students.

What to do about it

teachablestatus.com breaks the platform into Checkout, Video Playback, Content Delivery, Course Building and Custom Domains, so a creator problem separates cleanly from a student one. The same page tracks the upstream services Teachable runs on, including Stripe, Cloudflare, Mailgun and several AWS components, so an incident listed there usually explains the one you are seeing.

Is it down for everyone, or just you?

If this page says Teachable is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Teachable outage FAQ

Is Teachable down or is it just my school?
Open another Teachable school to tell them apart. If a different school loads and yours does not, the problem is more likely your custom domain or your school's settings than the platform. Teachable lists Custom Domains as its own component for exactly this reason, and a domain or certificate fault there looks identical to an outage from a student's side.
Students cannot check out. Is that always Teachable?
Not always. Teachable's status page tracks Checkout separately from its payment gateways, and it also tracks Stripe API, Stripe.js and Stripe Checkout.js as upstream dependencies. A Stripe incident stops payments without touching course delivery, so enrolled students keep watching while new purchases fail. Check both the Checkout component and the Stripe rows before telling buyers to retry.
Will students lose course progress during an outage?
Completions recorded before the outage are already saved. The ones at risk are lessons a student finished while the platform was unreachable, because those clicks never arrived. Ask students to revisit anything they completed during the incident window and confirm it still shows as complete, rather than trusting the tick they saw at the time.
Does the Teachable mobile app work when the website is down?
Sometimes, and the status page treats them separately: iOS Application is its own component alongside teachable.com. The app still needs Teachable's backend, so a core outage takes both. When only the web front end is affected, the app can keep playing lessons. Check the iOS Application row rather than assuming the app mirrors the site.
How do I tell students about an outage if my school is down?
Use a channel that does not run on Teachable: email through your own list, or wherever your community already gathers. Teachable's status page has a subscribe option that sends updates as the incident changes, which gives you something concrete to relay. Posting only inside the school reaches nobody, since the students who need the message cannot get in.

How we measure this

  • We request Teachable's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Teachable publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Teachable goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required