Rise Up incident

Rise Up platform is unavailable - AWS

Critical Resolved View vendor source →

Rise Up experienced a critical incident on July 16, 2026 affecting Web application and API, lasting 6h 51m. The incident has been resolved; the full update timeline is below.

Started
Jul 16, 2026, 07:57 AM UTC
Resolved
Jul 16, 2026, 02:49 PM UTC
Duration
6h 51m
Detected by Pingoru
Jul 16, 2026, 07:57 AM UTC

Affected components

Web applicationAPI

Update timeline

  1. investigating Jul 16, 2026, 07:57 AM UTC

    The Rise Up platform is currently unavailable. Our engineering team has been alerted and is actively investigating the root cause. We will provide an update as soon as possible.

  2. identified Jul 16, 2026, 08:22 AM UTC

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

  3. identified Jul 16, 2026, 08:34 AM UTC

    We are continuing to work on a fix for this issue.

  4. identified Jul 16, 2026, 08:57 AM UTC

    All platforms ending with .riseup.ai are now accessible again. We are continuing to work on a fix for custom domains.

  5. identified Jul 16, 2026, 10:03 AM UTC

    Mobile and API are available again. We have restored accessibility to 70% of all custom subdomains, and restoration of the remaining ones is in progress.

  6. monitoring Jul 16, 2026, 10:50 AM UTC

    All custom domains are now available. Our cloud provider has confirmed an issue on their side, and we have put a workaround in place to mitigate it. We are waiting for their confirmation that the incident is fully resolved before rolling back our workaround.

  7. monitoring Jul 16, 2026, 12:42 PM UTC

    Our cloud provider has confirmed that the incident on their side is fully resolved. We are now rolling back our temporary workaround. No downtime is expected during this operation, and we will continue to monitor closely.

  8. resolved Jul 16, 2026, 02:49 PM UTC

    The rollback of our workaround is complete and all services are operating normally on their standard configuration. Our cloud provider confirmed the root cause was an internal issue affecting connection routing on their side. This incident is now resolved. We apologize for the inconvenience and thank you for your patience.