Ringotel Outage History

Ringotel is up right now

Ringotel had 11 outages in the last 2 years totaling 511h 14m of downtime, averaging 0.5 incidents per month.

There were 11 Ringotel outages since January 23, 2025 totaling 511h 14m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: ringotelshell.statuspage.io

Notice October 9, 2026

Users are unable to make or receive calls

Detected by Pingoru
Oct 09, 2026, 10:30 PM UTC
Resolved
Oct 12, 2026, 09:50 PM UTC
Duration
2d 23h
Affected: US West
Timeline · 3 updates
  1. investigating Oct 09, 2026, 10:30 PM UTC

    We are receiving complains that the users are unable to make or receive calls. Our team is on and we will report shortly.

  2. investigating Oct 09, 2026, 11:07 PM UTC

    The issue should be resolved now. We will report back with more details after investigation.

  3. resolved Oct 12, 2026, 09:50 PM UTC

    The incident has been fully resolved. Our team has identified the root cause of the problem affecting incoming and outgoing calls. A patch has been applied to prevent future occurrences. We apologise for any inconvenience caused and appreciate your patience and cooperation.

Read the full incident report →

Critical September 28, 2026

Ringotel Incident - Canada

Detected by Pingoru
Sep 28, 2026, 07:52 AM UTC
Resolved
Sep 28, 2026, 08:23 AM UTC
Duration
31m
Affected: Canada (Central)
Timeline · 2 updates
  1. investigating Sep 28, 2026, 07:52 AM UTC

    A new Ringotel incident has been automatically created in the affected region (Canada). Our team has been notified and will review it immediately. If you have any questions, please contact us at [email protected] or use the online chat / create a ticket. We appreciate your patience in the meantime.

  2. resolved Sep 28, 2026, 08:23 AM UTC

    We've installed an urgent update outside of maintenance hours to ensure the service runs smoothly. All systems are operational and there's been no impact on the service. Should you have any questions or concerns, please let us know by creating a ticket or contacting us at [email protected] Thank you, Ringotel Team

Read the full incident report →

Critical September 2, 2026

Ringotel Incident - Cape Town (South Africa)

Detected by Pingoru
Sep 02, 2026, 05:54 AM UTC
Resolved
Sep 03, 2026, 09:36 AM UTC
Duration
1d 3h
Affected: Africa (Cape Town)
Timeline · 4 updates
  1. investigating Sep 02, 2026, 05:54 AM UTC

    A new Ringotel incident has been automatically created in the affected region (Cape Town (South Africa)). Our team has been notified and will review it immediately. If you have any questions, please contact us at [email protected] or use the online chat / create a ticket. We appreciate your patience in the meantime.

  2. investigating Sep 02, 2026, 09:28 AM UTC

    Our team is investigating a brief outage in Cape Town region between 5:55 and 6:13 AM UTC. The server is fully operational and under extended monitoring. This issue is unrelated to the recent outage in other regions. An update will follow soon.

  3. identified Sep 02, 2026, 08:22 PM UTC

    We have identified a situation that causes heap out-of-memory (OOM) error. Our team is working on a solution to ensure that such incidents won't occur in the future. We appreciate your cooperation and apologise for any inconveniences caused by this issue.

  4. resolved Sep 03, 2026, 09:36 AM UTC

    The team has pinpointed the cause of the heap out-of-memory error and implemented a fix to prevent future occurrences. The affected region is now fully operational and no issues have been reported across the platform. Should you have any question or concerns please don't hesitate to reach out to our support team.

Read the full incident report →

Critical August 31, 2026

Ringotel Incident - US West

Detected by Pingoru
Aug 31, 2026, 02:03 PM UTC
Resolved
Sep 01, 2026, 03:23 PM UTC
Duration
1d 1h
Affected: US West
Timeline · 3 updates
  1. investigating Aug 31, 2026, 02:03 PM UTC

    A new Ringotel incident has been automatically created in the affected region (US West). Our team has been notified and will review it immediately. If you have any questions, please contact us at [email protected] or use the online chat / create a ticket. We appreciate your patience in the meantime.

  2. monitoring Sep 01, 2026, 03:20 PM UTC

    We apologise for the delayed communication about this incident. The root cause has been identified and mitigation measures are in place. We’re now completing infrastructure updates across the regions and a post-mortem will follow shortly.

  3. resolved Sep 01, 2026, 03:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical August 26, 2026

Ringotel Incident - India

Detected by Pingoru
Aug 26, 2026, 03:13 PM UTC
Resolved
Aug 26, 2026, 09:40 PM UTC
Duration
6h 27m
Affected: India (Mumbai)
Timeline · 3 updates
  1. investigating Aug 26, 2026, 03:13 PM UTC

    A new Ringotel incident has been automatically created in the affected region (India). Our team has been notified and will review it immediately. If you have any questions, please contact us at [email protected] or use the online chat / create a ticket. We appreciate your patience in the meantime.

  2. monitoring Aug 26, 2026, 04:18 PM UTC

    The incident has been resolved. Our team is monitoring the status and will provide an update shortly.

  3. resolved Aug 26, 2026, 09:40 PM UTC

    This incident has been resolved and connectivity is fully restored. The problem was caused by an increase in error rates within a system component which resulted in a heap out-of-memory (OOM) error. This caused a temporary service interruption for organisations hosted in the India region. Our team is working on a solution to ensure that such incidents won't occur in the future. We appreciate your cooperation and apologise for any inconveniences caused by this issue.

Read the full incident report →

Notice July 10, 2026

The link to get softphone credentials returns an error

Detected by Pingoru
Jul 10, 2026, 09:54 AM UTC
Resolved
Jul 10, 2026, 10:56 AM UTC
Duration
1h 2m
Affected: Provisioning Portal & API Endpoints
Timeline · 2 updates
  1. investigating Jul 10, 2026, 09:54 AM UTC

    Our team is investigating a problem reported by multiple users who can't retrieve their login credentials through the secure link.

  2. resolved Jul 10, 2026, 10:56 AM UTC

    The issue has been resolved. The credentials link works as expected now. We apologise for any inconvenience caused.

Read the full incident report →

Major June 17, 2026

Users lost the ability to text

Detected by Pingoru
Jun 17, 2026, 02:47 PM UTC
Resolved
Jun 18, 2026, 10:35 AM UTC
Duration
19h 47m
Affected: US West
Timeline · 3 updates
  1. investigating Jun 17, 2026, 02:47 PM UTC

    We have multiple reports from users who have lost an ability to send SMS to external numbers. They are missing the text field to write a message. Our team is investigating this now and will provide an update shortly. Thank you for your patience in the meantime.

  2. monitoring Jun 17, 2026, 03:14 PM UTC

    The issue has been resolved. Please advise affected users to log out and log back into the app again. We're continue monitoring the results.

  3. resolved Jun 18, 2026, 10:35 AM UTC

    Our team has completed the investigation. We have concluded that a bug was introduced in the latest backend update, which caused some users to experience the issue where they lose the ability to send text messages, specifically SMS. A review of internal processes will be performed to avoid such issues in the future. We appreciate your patience and cooperation during the investigation. Should you have any questions or concerns, please don't hesitate to contact our support team.

Read the full incident report →

Notice May 24, 2026

Ringotel Incident - Sao Paulo (South America)

Detected by Pingoru
May 24, 2026, 05:00 PM UTC
Resolved
May 27, 2026, 02:25 PM UTC
Duration
2d 21h
Affected: South America (São Paulo)
Timeline · 2 updates
  1. investigating May 24, 2026, 05:00 PM UTC

    A new Ringotel incident has been automatically created in the affected region (Sao Paulo (South America)). Our team has been notified and will review it immediately. If you have any questions, please contact us at [email protected] or use the online chat / create a ticket. We appreciate your patience in the meantime.

  2. resolved May 27, 2026, 02:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical November 14, 2025

Ringotel Incident - US East

Detected by Pingoru
Nov 14, 2025, 07:34 PM UTC
Resolved
Nov 14, 2025, 08:00 PM UTC
Duration
26m
Affected: US East
Timeline · 3 updates
  1. investigating Nov 14, 2025, 07:34 PM UTC

    A new Ringotel incident has been automatically created in the affected region (US East). Our team has been notified and will review it immediately. If you have any questions, please contact us at [email protected] or use the online chat / create a ticket. We appreciate your patience in the meantime.

  2. resolved Nov 14, 2025, 08:00 PM UTC

    The issue has been resolved and the system is back online. We apologies for any inconvenience caused by this issue. Please reach out to [email protected] if you need any further assistance.

  3. postmortem Nov 15, 2025, 09:10 PM UTC

    On November 14, 2025, from 19:34 UTC to 20:00 UTC \(a total of 26 minutes\), services in the US East region experienced a critical outage. Users in the region were not able to use app's main features, such as making or receiving calls, messages, etc. The Ringotel admin panel showed "Too many connections" error. The root cause was a surge in read operations, which exhausted the connection pool of the production database, leading to a cascading failure. The issue was resolved by performing an emergency upgrade of the database infrastructure. Additional monitoring and alert policies have been implemented to ensure early detection of such surges in the future. We apologize for the inconvenience caused by this issue. If you need further assistance, please feel free to contact [[email protected]](mailto:[email protected]) Thank you for your understanding and support.

Read the full incident report →

Notice April 24, 2025

Outage on Australia Region

Detected by Pingoru
Apr 24, 2025, 10:57 PM UTC
Resolved
Apr 25, 2025, 09:49 PM UTC
Duration
22h 51m
Affected: Australia
Timeline · 3 updates
  1. investigating Apr 24, 2025, 10:57 PM UTC

    We are currently experiencing an outage on the Australian region. Our team is working on it. We apologise for any inconvenience caused in the meantime.

  2. monitoring Apr 24, 2025, 11:40 PM UTC

    The normal operation of the service has been restored. Our team continue monitoring to ensure that the issue is resolved completely. We will provide further report soon.

  3. resolved Apr 25, 2025, 09:49 PM UTC

    The incident has been fully resolved. The outage was caused by increased memory consumption resulting from an error in the system logging. We apologies for any inconvenience caused by this outage. Should you need assistance, please contact us at [email protected]

Read the full incident report →