Roise Outage History

Roise is up right now

Roise had 4 outages in the last 2 years totaling 21h 16m of downtime, averaging 0.2 incidents per month.

There were 4 Roise outages since June 12, 2025 totaling 21h 16m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.heyrosie.com

Critical November 18, 2025

Issues with our CDN (Cloudflare) Connectivity

Detected by Pingoru
Nov 18, 2025, 12:04 PM UTC
Resolved
Nov 18, 2025, 03:45 PM UTC
Duration
3h 40m
Affected: APITelephony
Timeline · 5 updates
  1. identified Nov 18, 2025, 12:04 PM UTC

    Cloudflare is aware of, and investigating an issue which potentially impacts multiple customers. Further detail will be provided as more information becomes available.

  2. monitoring Nov 18, 2025, 12:16 PM UTC

    A fix has been implemented by Cloudflare and we continue monitoring. The services should be restored.

  3. monitoring Nov 18, 2025, 12:24 PM UTC

    We are continuing to monitor for any further issues.

  4. monitoring Nov 18, 2025, 12:25 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Nov 18, 2025, 12:38 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 20, 2025

Upstream Provider Outage Impacting Inbound Calls (AWS outage)

Detected by Pingoru
Oct 20, 2025, 09:00 AM UTC
Resolved
Oct 20, 2025, 08:38 PM UTC
Duration
11h 38m
Affected: APITelephony
Timeline · 4 updates
  1. investigating Oct 20, 2025, 03:19 PM UTC

    We’re currently experiencing disruptions due to upstream network issues affecting AWS, Twilio, and other providers. These outages are impacting inbound call functionality. Our team is actively monitoring the situation and coordinating with vendors to minimize service disruptions.

  2. identified Oct 20, 2025, 03:19 PM UTC

    We are waiting on the upstream provider to apply fixes (AWS).

  3. monitoring Oct 20, 2025, 08:38 PM UTC

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

  4. resolved Oct 20, 2025, 08:38 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical July 26, 2025

Voice Calling Unavailable for New Signups

Detected by Pingoru
Jul 26, 2025, 04:00 AM UTC
Resolved
Jul 26, 2025, 07:37 AM UTC
Duration
3h 36m
Affected: Telephony
Timeline · 4 updates
  1. investigating Jul 26, 2025, 06:22 AM UTC

    We’ve identified an issue where newly signed-up users are unable to make voice calls. This is due to a disruption with one of our upstream telephony providers. Our team is actively working with the provider to resolve this as quickly as possible. Existing users are unaffected. We’ll provide an update as soon as we have more information. Thank you for your patience.

  2. identified Jul 26, 2025, 06:48 AM UTC

    The upstream provider has identified the issue and is actively working on a fix.

  3. monitoring Jul 26, 2025, 07:21 AM UTC

    A fix has been implemented and services have been restored. We are actively monitoring.

  4. resolved Jul 26, 2025, 07:37 AM UTC

    The incident has been resolved. Thank you for your patience.

Read the full incident report →

Critical June 12, 2025

Upstream Provider Outage Impacting Inbound Calls and Phone Number Provisioning

Detected by Pingoru
Jun 12, 2025, 06:49 PM UTC
Resolved
Jun 12, 2025, 09:09 PM UTC
Duration
2h 20m
Affected: API
Timeline · 4 updates
  1. investigating Jun 12, 2025, 06:49 PM UTC

    We’re currently experiencing disruptions due to upstream network issues affecting Twilio, Google Cloud Platform (GCP), Cloudflare, and other providers. These outages are impactin inbound call functionality, as well as phone number provisioning. Our team is actively monitoring the situation and coordinating with vendors to minimize service disruptions.

  2. identified Jun 12, 2025, 08:14 PM UTC

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

  3. monitoring Jun 12, 2025, 08:14 PM UTC

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

  4. resolved Jun 12, 2025, 09:09 PM UTC

    This incident has been resolved.

Read the full incident report →