Rendi Outage History

Rendi is up right now

Pingoru has recorded 5 incidents for Rendi: 3 in the last 12 months and 0 in the last 90 days.

Source: status.rendi.dev

5incidents recorded
3last 12 months
0last 90 days
3 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Rendi in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 526 (0%)

Incidents, newest first

Minor March 30, 2026 Billing is not responsive due to Stripe being down 2h 22m Management Portal

Started Mar 30, 2026, 08:25 AM UTC· resolved Mar 30, 2026, 10:47 AM UTC

  1. investigating Mar 30, 2026, 08:25 AM UTC

    We are monitoring the situation and will update once Stripe is back online.

  2. resolved Mar 30, 2026, 10:47 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 18, 2025 Cloudflare outage 5h 40m API, Management Portal

Started Nov 18, 2025, 12:51 PM UTC· resolved Nov 18, 2025, 06:31 PM UTC

  1. investigating Nov 18, 2025, 12:51 PM UTC

    We are again experiencing service issues due to issues with Cloudflare. System will return to operational as soon as Cloudflare return: https://www.cloudflarestatus.com/

  2. monitoring Nov 18, 2025, 02:44 PM UTC

    A fix has been implemented and we are monitoring the results

  3. resolved Nov 18, 2025, 06:31 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical June 28, 2025 System Down –

Started Jun 28, 2025, 06:00 AM UTC· resolved Jun 28, 2025, 06:00 AM UTC

  1. resolved Jun 28, 2025, 08:09 AM UTC

    System is fully working. API and dashboard rejected inbound traffic due to a firewall configuration problem. Our technical team has resolved this issue within 20 minutes.

Read the full incident report →

Notice June 27, 2025 This is an example incident –

Started Jun 27, 2025, 07:50 AM UTC· resolved Jun 27, 2025, 07:50 AM UTC

  1. investigating Jun 28, 2025, 07:34 AM UTC

    When your product or service isn’t functioning as expected, let your customers know by creating an incident. Communicate early, even if you don’t know exactly what’s going on.

  2. identified Jun 28, 2025, 07:34 AM UTC

    As you continue to work through the incident, update your customers frequently.

  3. monitoring Jun 28, 2025, 07:34 AM UTC

    Let your users know once a fix is in place, and keep communication clear and precise.

  4. resolved Jun 28, 2025, 07:34 AM UTC

    Empathize with those affected and let them know everything is operating as normal.

Read the full incident report →