Skip to main content
RebelMouse logo

Is RebelMouse Down?

No — RebelMouse is up

Reachable from all 8 checked regions

Average response time: 213ms

Last checked · checks run every 6 hours

Official status page: https://status.rebelmouse.com

RebelMouse uptime

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

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

30-day history

32-day clean streak
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, 32 checks
Sep 22: 100.00% uptime, 32 checks
Sep 23: 100.00% uptime, 32 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, 31 checks
Sep 30: 100.00% uptime, 28 checks
Oct 1: 100.00% uptime, 31 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
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Sep 14 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.

ams
255ms
DNS 74ms TCP 2ms TLS 6ms TTFB 246ms
arn
330ms
DNS 90ms TCP 10ms TLS 24ms TTFB 293ms
nrt
153ms
DNS 137ms TCP 1ms TLS 4ms TTFB 147ms
ord
51ms
DNS 28ms TCP 1ms TLS 6ms TTFB 45ms
sin
459ms
DNS 180ms TCP 1ms TLS 3ms TTFB 454ms
sjc
121ms
DNS 35ms TCP 1ms TLS 5ms TTFB 114ms
syd
204ms
DNS 189ms TCP 0ms TLS 3ms TTFB 197ms
yyz
137ms
DNS 121ms TCP 0ms TLS 4ms TTFB 131ms

What RebelMouse does

RebelMouse is a managed publishing platform that hosts websites for media companies and brands, handling the CMS, the front end, content distribution and traffic analytics as one service. Publishers use it instead of running their own WordPress or custom stack. Sites built on it are served through RebelMouse's infrastructure, so the platform is the hosting layer as well as the editor.

What an outage looks like

Published sites serve slowly or fail to load for readers in some regions while others are unaffected, because RebelMouse serves through several CDN locations. Editors cannot publish or save, or the editor loads while media uploads fail. Analytics stop updating, so traffic appears to collapse when it has not. Logged-in reader features fail while anonymous page views work normally.

What to do about it

Read status.rebelmouse.com, which is unusually explicit: alongside its own Full Platform, Media, Discovery, Stats and Content Delivery API rows it reports the upstream services it depends on, including AWS us-east-1 components, six Fastly CDN locations, Braintree, MongoDB, Redis and RabbitMQ. Check whether an upstream row is the one failing, because a Fastly or AWS us-east-1 incident explains the symptom and sets the timeline.

Is it down for everyone, or just you?

If this page says RebelMouse 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

AWS
AWS
Fastly
Fastly
Contentful
Contentful
Ghost
Ghost

RebelMouse outage FAQ

Readers in one country cannot load my site but I can. Is RebelMouse down?
Possibly only in part. RebelMouse reports six Fastly CDN locations separately, covering London, New York, Los Angeles, Amsterdam, Hong Kong and Sydney, so an edge problem in one region leaves readers elsewhere unaffected and gives you no symptom at all from your own location. Check the CDN rows for the region your readers are in rather than testing from your desk.
Why does RebelMouse list AWS and Fastly on its status page?
Because those are its dependencies, and naming them tells you where a problem actually is. RebelMouse's status page reports AWS us-east-1 services including EC2, RDS, S3, Route 53 and SES, plus six Fastly locations, alongside its own platform components. When an upstream row is the one failing, the cause and the likely timeline belong to that provider, and RebelMouse recovers when it does.
My traffic numbers dropped to zero. Did I lose readers?
Check the Stats row before believing the number. RebelMouse lists Stats as a component separate from the platform and from content delivery, so analytics can stop collecting while pages serve normally to every reader. A reporting outage looks identical to a traffic collapse on a dashboard, and the difference matters if anyone is about to act on it. Compare against a second analytics source if you have one.
Can readers still reach articles while the editor is down?
Often yes. RebelMouse reports the platform, media, content delivery and the CDN as separate components, so already-published pages can continue serving from the edge while the editing interface is unavailable. What stops is publishing new work and changing existing pages. If the CDN rows are healthy and only the platform is affected, your site stays up for readers.
Will a post I was editing be lost?
Anything saved before the failure is stored on RebelMouse's side and returns with the service. Unsaved edits are a different matter, and RebelMouse publishes no guarantee covering work in progress in the editor, so copy the text somewhere local before reloading the page. A reload is the action that most often discards edits that were never sent to the server.

How we measure this

  • We request RebelMouse'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 RebelMouse 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 RebelMouse 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