RebelMouse logo

Is RebelMouse Down?

SaaSLive status, outages, and incident history

No. RebelMouse is up right now.

Every monitored RebelMouse system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 3m agoLive · 60s while moving

Know the moment RebelMouse breaks

RebelMouse is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

Official RebelMouse status page
How we know: the official RebelMouse status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

RebelMouse Component Status

The main RebelMouse systems on this page. All 37 are operational right now.

37operational
AWS DocumentDB
Operational
AWS ec2-us-east-1
Operational
AWS elb-us-east-1
Operational

34 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking AWS RDS, AWS route53, AWS s3-us-standard, AWS ses-us-east-1, Braintree API, Braintree PayPal Processing, CDN, Celery, Content Delivery API, Discovery, EKS Cluster, ElastiCache, and 22 more.

See all of them free

Component statuses may change independently during partial outages.

Recent RebelMouse Outages & Incidents

Incident history from the official RebelMouse status page, including resolution updates.

Image Resize Service Performance DegradationResolved Aug 25, 2026 · 0 minResolved

## Summary Between 14:14 and 14:30 UTC, the Image Resize service was unable to keep up with incoming demand, causing a portion of asset requests to fail with HTTP 503 responses. The service was saturated by a sharp, sustained increase in crawler traffic that pushed request volume well beyond the capacity provisioned for normal baseline load. The incident was mitigated by significantly increasing the resources and capacity available to the service. Error rates began falling within minutes of the capacity change and returned to baseline by 14:30 UTC. No data loss occurred, and no customer content was affected — failures were limited to transient delivery errors on individual asset requests. ## Impact * **Failed requests:** 38,248 asset 503 responses during 14:14-14:30 UTC timeframe. * **Total requests served:** approximately 1.31 million asset requests in the same interval. * **Aggregate error rate**: approximately 2.91%. Roughly 97% of asset requests continued to succeed throughout the incident, and users retrying a failed image load would frequently have received it successfully. ## Timeline * 14:14 Elevated 503 error rates began on asset requests. * 14:20 Peak impact: 5.65% of asset requests failing. * 14:25 Additional capacity took effect; error rates began declining. * 14:30 Incident is resolved. ## Root cause The Image Resize service experienced a large increase in load driven by crawler traffic. Crawlers requesting image assets generated a volume of resize work substantially higher than typical baseline demand, and heavily weighted toward uncached variants, which meant a large share of that traffic had to be served by origin resize workers rather than from cache. ## Mitigation and resolution Once the resize tier was identified as the saturation point, available resources and capacity for the service were increased significantly. Error rates began declining at 14:25, fell steadily over the following four minutes, and returned to baseline by 14:30. Normal behavior was confirmed from 14:30 UTC onward. The expanded capacity was left in place after recovery pending a review of steady-state sizing. ## Action items Review and permanently raise baseline capacity for the resize tier to restore adequate burst headroom. --- [2026-08-26T08:08:17.997-04:00] (resolved) We are currently investigating this issue.

EKS Cluster UpgradeScheduled for Aug 21, 2026 · 6h 0mScheduled

The scheduled maintenance has been completed. --- [2026-08-21T02:00:12.076-04:00] (in_progress) Scheduled maintenance is currently in progress. We will provide updates as necessary. --- [2026-08-21T01:00:17.948-04:00] (scheduled) Maintenance will begin as scheduled in 60 minutes. --- [2026-08-20T10:39:52.942-04:00] (scheduled) We’re going to upgrade our production EKS cluster. We have tested the entire system in the staging environment and do not expect any disruptions to service during the upgrade.

DocumentDB MaintenanceScheduled for Jul 18, 2026 · 1h 0mScheduled

The scheduled maintenance has been completed. --- [2026-07-18T04:00:07.708-04:00] (in_progress) Scheduled maintenance is currently in progress. We will provide updates as necessary. --- [2026-07-18T03:00:07.312-04:00] (scheduled) Maintenance will begin as scheduled in 60 minutes. --- [2026-07-17T10:04:59.320-04:00] (scheduled) We are going to perform maintenance on our SQS and DocumentDB infrastructure. During the maintenance window: The Broken Links service will be stopped. Automations (webhooks) will be stopped. AI Search will be unavailable. Post visibility may be temporarily affected. No data will be lost. Any events delayed during the maintenance window will be processed automatically once the maintenance is complete.

RebelMouse Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a RebelMouse incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 8100.00% average · 5 days with incidentsSep 25

Live RebelMouse Outage Reports

Problems reported by engineers using RebelMouse. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No RebelMouse problems reported yet.

Something wrong with RebelMouse on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About RebelMouse

Is RebelMouse down? RebelMouse reports live availability for 37 components at status.rebelmouse.com, among them AWS ec2-us-east-1, AWS route53 and AWS ses-us-east-1. Track RebelMouse outages, degradations and past incidents here, with uptime history and alerts across your SaaS stack.

Over the past 30 days, PulsAPI has measured RebelMouse uptime at 99.99%. Response times, incident history, and SLA tracking for RebelMouse are available on the PulsAPI dashboard.

RebelMouse Status FAQ

Is RebelMouse down right now?

The verdict at the top of this page comes from the latest poll of the official RebelMouse status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if RebelMouse is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until RebelMouse recovers.

How do I check RebelMouse uptime history?

PulsAPI tracks RebelMouse uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 99.99%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever RebelMouse changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect RebelMouse outages?

PulsAPI reads the official RebelMouse status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual RebelMouse components?

Yes. PulsAPI monitors 37 individual RebelMouse components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when RebelMouse goes down?

Yes. Create a free account and subscribe to RebelMouse: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with RebelMouse to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot RebelMouse problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor RebelMouse?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so RebelMouse plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track RebelMouse with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services