Is Stripo down?

Last checked just now
Current status
Stripo is up

No incidents right now.

Official status page: https://status.stripo.email · Polled every 5 minutes · 33 components tracked

Stripo is operational right now. Last checked just now; the most recent incident resolved 6d ago.

Real-time Stripo status, recent outages, and incident history — pulled directly from Stripo's official status page at https://status.stripo.email every 5 minutes. Pingoru tracks 33 Stripo services and has captured 16 incidents in the last 90 days (99.11% uptime). Get email, Slack, Discord, or webhook alerts the moment Stripo reports a new incident — free for 5 monitors, no credit card.

Users who monitor Stripo also follow these Marketing services: Mailgun Klaviyo Iterable Braze Brevo Customer.io ZoomInfo Optimizely SurveyMonkey Yotpo View all 6,000+ providers
Stripo uptime 99.11% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 56s
    Started Sep 09, 2026, 03:18 PM UTC · Resolved Sep 09, 2026, 03:19 PM UTC
    Modules Service (plugin)
    Timeline · 2 updates
    • investigating · Sep 09, 2026, 03:18 PM UTC

      There might be issues while viewing, changing or creating new modules in the Modules library inside the editor. Time (UTC) : 2026-09-09T15:18:49

    • resolved · Sep 09, 2026, 03:19 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  2. Resolved 1m
    Started Sep 09, 2026, 03:13 PM UTC · Resolved Sep 09, 2026, 03:15 PM UTC
    Modules Service (plugin)
    Timeline · 2 updates
    • investigating · Sep 09, 2026, 03:13 PM UTC

      There might be issues while viewing, changing or creating new modules in the Modules library inside the editor. Time (UTC) : 2026-09-09T15:13:49

    • resolved · Sep 09, 2026, 03:15 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved 28s
    Started Sep 09, 2026, 03:11 PM UTC · Resolved Sep 09, 2026, 03:11 PM UTC
    Modules Service (plugin)
    Timeline · 2 updates
    • investigating · Sep 09, 2026, 03:11 PM UTC

      There might be issues while viewing, changing or creating new modules in the Modules library inside the editor. Time (UTC) : 2026-09-09T15:10:49

    • resolved · Sep 09, 2026, 03:11 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  4. Resolved 1m
    Started Sep 06, 2026, 07:17 AM UTC · Resolved Sep 06, 2026, 07:19 AM UTC
    Stripo Account Backend part
    Timeline · 2 updates
    • investigating · Sep 06, 2026, 07:17 AM UTC

      There might be an issue with access to the customer’s account. Time (UTC) : 2026-09-06T07:17:04

    • resolved · Sep 06, 2026, 07:19 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  5. Resolved 1h 6m
    Started Aug 05, 2026, 01:50 PM UTC · Resolved Aug 05, 2026, 02:57 PM UTC
    API Gateway Service (plugin)
    Timeline · 5 updates
    • investigating · Aug 05, 2026, 01:59 PM UTC

      We are aware of an issue with the Stripo Plugin: the editor may fail to initialize and does not load for end users. Our team has identified the affected service and is working on a fix. We will post an update as soon as we have more information.

    • identified · Aug 05, 2026, 02:00 PM UTC

      The issue has been identified and a fix is being implemented.

    • monitoring · Aug 05, 2026, 02:49 PM UTC

      A fix has been implemented and we are monitoring the results.

    • resolved · Aug 05, 2026, 02:57 PM UTC

      This incident has been resolved.

    • postmortem · Aug 05, 2026, 04:03 PM UTC

      At 13:45 UTC the AWS host running the database and cache for our plugin environment failed. Auto-recovery restarted it by 14:00 UTC, but the cache service and several microservices required manual restarts. Full recovery: ~15:00 UTC. **Impact \(UTC\).** Autosave was unavailable 13:48–13:57, then severely slow \(~86 s per request vs. under 7 s normally\) until ~14:40. Some plugins using external AutoSave callbacks saw saves fail. Co-editing was degraded 14:16–15:00. Editor initialization also failed for some users early on. **Data.** No evidence of loss: crash recovery completed correctly, all patches that reached the database were persisted, and duplicate resubmissions were safely rejected. Contact us with a timestamp if you suspect otherwise. **Cause.** Hardware failure on the underlying AWS host. It escalated because autosave retries external callbacks synchronously inside the request, exhausting the database connection pool; the cache had no auto-start on reboot; and connection pools did not self-heal. No alarm covered host status or cache availability, so detection came from user reports. **Fixes.** Alerting on host status checks and cache availability; cache auto-start with a health check; connection pool recovery; moving external callbacks out of the request path; alerts on pool saturation, error rate and callback latency; a redundancy review for this environment. We apologize for the disruption. If the impact on your users differed from the above, please contact our support team.

    Latest: At 13:45 UTC the AWS host running the database and cache for our plugin environment failed. Auto-recovery restarted it by 14:00 UTC, but the cache service and several microservices…

See the full Stripo outage history

10 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Stripo outage history →

Or sign up free to get alerts when Stripo breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 15 incidents View full outage history →