RapidSOS Outage History

Started Oct 23, 2026, 03:15 AM UTC· resolved Oct 23, 2026, 05:30 AM UTC

1. investigating Oct 23, 2026, 03:15 AM UTC

   Our engineers have discovered an issue with the RapidSOS components flagged below. We have escalated to the appropriate teams and are working to identify and resolve the issue as quickly as possible. We will provide updates here as information becomes available. Please reach out to [email protected] with any questions.

2. monitoring Oct 23, 2026, 04:56 AM UTC

   The fix has been implemented and we are monitoring the results for time being.

3. resolved Oct 23, 2026, 05:30 AM UTC

   The earlier issue with the RapidSOS components flagged below has been resolved and all systems are fully operational. We take these issues seriously and apologize for the impact on your operations. Please reach out to [email protected] with any questions. Thank you for your patience, RapidSOS Engineering Team

Read the full incident report →

Started Oct 20, 2026, 12:28 PM UTC· resolved Oct 20, 2026, 12:45 PM UTC

1. resolved Oct 20, 2026, 12:45 PM UTC

   Our engineers identified an issue today between 9:22 am and 9:41 am and took immediate steps for remediation. During this window there was a Partial Outage of Monitoring Services, Live Agent Voice and IVR Verification Telephony Components. The incident has since been resolved, all systems are fully operational, and connection stability has been restored. We take these issues seriously and apologize for the impact on your operations. Please reach out to [email protected] with any questions. Thank you for your patience, RapidSOS Engineering Team

Read the full incident report →

Started Oct 15, 2026, 06:20 AM UTC· resolved Oct 15, 2026, 03:22 PM UTC

1. identified Oct 15, 2026, 06:20 AM UTC

   One of our upstream providers has identified an issue which is affecting the RapidSOS components flagged below. Our provider is working to remedy a fix as quickly as possible. We will provide updates here as information becomes available. Thank you for your patience, RapidSOS Engineering Team

2. resolved Oct 15, 2026, 03:22 PM UTC

   The earlier issue with the RapidSOS components flagged below has been resolved and all systems are fully operational. We take these issues seriously and apologize for the impact on your operations. Please reach out to [email protected] with any questions. Thank you for your patience, RapidSOS Engineering Team

Read the full incident report →

Started Oct 09, 2026, 10:11 PM UTC· resolved Oct 10, 2026, 12:44 AM UTC

1. investigating Oct 09, 2026, 10:11 PM UTC

   Our engineers have discovered an issue with the RapidSOS components flagged below. We have escalated to the appropriate teams and are working to identify and resolve the issue as quickly as possible. We will provide updates here as information becomes available. Please reach out to [email protected] with any questions. Thank you for your patience, RapidSOS Engineering Team

2. monitoring Oct 09, 2026, 11:42 PM UTC

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

3. resolved Oct 10, 2026, 12:44 AM UTC

   The incident has been resolved.

Read the full incident report →

Started Sep 15, 2026, 04:55 PM UTC· resolved Sep 15, 2026, 07:40 PM UTC

1. resolved Sep 15, 2026, 07:40 PM UTC

   Our engineers identified an issue today between 12:55 pm and 15:40 pm and took immediate steps for remediation. During this window there was a Major Outage for the Transcription Component. The incident has since been resolved, all systems are fully operational, and connection stability has been restored. We take these issues seriously and apologize for the impact on your operations. Please reach out to [email protected] with any questions. Thank you for your patience, RapidSOS Engineering Team

Read the full incident report →

Started Sep 02, 2026, 09:06 PM UTC· resolved Sep 03, 2026, 01:56 AM UTC

1. identified Sep 02, 2026, 09:06 PM UTC

   One of our upstream providers has identified an issue which is affecting the RapidSOS components flagged below. Our provider is working to remedy a fix as quickly as possible. We will provide updates here as information becomes available. Thank you for your patience, RapidSOS Engineering Team

2. identified Sep 02, 2026, 11:45 PM UTC

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

3. monitoring Sep 03, 2026, 12:14 AM UTC

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

4. resolved Sep 03, 2026, 01:56 AM UTC

   The incident has been resolved.

Read the full incident report →

Started Aug 18, 2026, 02:22 PM UTC· resolved Aug 18, 2026, 02:41 PM UTC

1. resolved Aug 18, 2026, 02:41 PM UTC

   Our engineers identified an issue today between 10:22 am and 10:41 am and took immediate steps for remediation. During this window there was a Partial Outage of Data Connect and IVR Verification Telephony Components. The incident has since been resolved, all systems are fully operational, and connection stability has been restored. We take these issues seriously and apologize for the impact on your operations. Please reach out to [email protected] with any questions. Thank you for your patience, RapidSOS Engineering Team

Read the full incident report →

Started Aug 13, 2026, 06:56 PM UTC· resolved Aug 13, 2026, 08:10 PM UTC

1. identified Aug 13, 2026, 06:56 PM UTC

   Our engineers have identified the issue with the RapidSOS components flagged below. We are working to remedy a fix as quickly as possible. We will provide updates here as information becomes available. Please reach out to [email protected] with any questions. Thank you for your patience, RapidSOS Engineering Team

2. monitoring Aug 13, 2026, 07:30 PM UTC

   Our engineers have implemented a fix for the issue with the RapidSOS components flagged below. All RapidSOS Services are operational, and we are observing this closely and will provide updates as information becomes available. Please reach out to [email protected] with any questions. Thank you for your patience, RapidSOS Engineering Team

3. resolved Aug 13, 2026, 08:10 PM UTC

   The earlier issue with the RapidSOS components flagged below has been resolved and all systems are fully operational. We take these issues seriously and apologize for the impact on your operations. Please reach out to [email protected] with any questions. Thank you for your patience, RapidSOS Engineering Team

Read the full incident report →

Started Jul 23, 2026, 02:57 PM UTC· resolved Jul 23, 2026, 08:11 PM UTC

1. identified Jul 23, 2026, 02:57 PM UTC

   One of our upstream providers has identified an issue which is affecting the RapidSOS components flagged below. Our provider is working to remedy a fix as quickly as possible. We will provide updates here as information becomes available. Thank you for your patience, RapidSOS Engineering Team

2. investigating Jul 23, 2026, 03:17 PM UTC

   Investigating — Android ELS (Device‑Based Location) data delivery We are investigating a report of an elevated error rate on the Android ELS SMS data path. Our ingest endpoints are responding normally, and we are working with our upstream partners to determine the source of the reported errors. Scope: This affects only the non‑US Android ELS SMS data path (Integration › Location APIs and UNITE › Device‑Based Locations). US services are not impacted.

3. resolved Jul 23, 2026, 08:11 PM UTC

   The incident has been resolved.

Read the full incident report →

Started Jun 24, 2026, 01:52 PM UTC· resolved Jun 24, 2026, 02:53 PM UTC

1. resolved Jun 24, 2026, 02:53 PM UTC

   Our engineers identified an issue today between 09:52 AM EST and 10:53:00 AM EST and took immediate steps for remediation. During this window there was a degradation of Monitoring Service . The incident has since been resolved, all systems are fully operational, and connection stability has been restored. We take these issues seriously and apologize for the impact on your operations. Please reach out to [email protected] with any questions. Thank you for your patience, RapidSOS Engineering Team

Read the full incident report →

Started Jun 17, 2026, 08:17 PM UTC· resolved Jun 18, 2026, 04:32 PM UTC

1. identified Jun 17, 2026, 08:17 PM UTC

   One of our upstream providers has identified an issue which is affecting the RapidSOS components flagged below. Our provider is working to remedy a fix as quickly as possible. We will provide updates here as information becomes available. Thank you for your patience, RapidSOS Engineering Team

2. resolved Jun 18, 2026, 04:32 PM UTC

   The incident has been resolved.

Read the full incident report →

Started Jun 11, 2026, 04:58 PM UTC· resolved Jun 12, 2026, 01:33 AM UTC

1. resolved Jun 12, 2026, 01:33 AM UTC

   Our engineers identified an issue today between 12:58PM ET and 21:33PM ET and took immediate steps for remediation. During this window there was a degradation of Multimedia to 911 . The incident has since been resolved, all systems are fully operational, and connection stability has been restored. We take these issues seriously and apologize for the impact on your operations. Please reach out to [email protected] with any questions. Thank you for your patience, RapidSOS Engineering Team

Read the full incident report →

Started Jun 10, 2026, 06:30 PM UTC· resolved Jun 10, 2026, 08:40 PM UTC

1. identified Jun 10, 2026, 06:30 PM UTC

   Our engineers have identified the issue with the RapidSOS component Map Layers flagged below. We are continuing to work towards remediation as quickly as possible. We will provide updates here as information becomes available. Please reach out to [email protected] with any questions. Thank you for your patience, RapidSOS Engineering Team

2. resolved Jun 10, 2026, 08:40 PM UTC

   The earlier issue with the RapidSOS component Map Layers flagged below has been resolved and all systems are fully operational. We take these issues seriously and apologize for the impact on your operations. Please reach out to [email protected] with any questions. Thank you for your patience, RapidSOS Engineering Team

Read the full incident report →

Started Jun 04, 2026, 02:10 PM UTC· resolved Jun 04, 2026, 03:00 PM UTC

1. identified Jun 04, 2026, 02:10 PM UTC

   One of our upstream providers is still experiencing an issue which is affecting the RapidSOS component Monitoring Services flagged below. We are continuing to communicate with our provider and will resolve this incident once we have received confirmation that the issue has been resolved. Thank you for your patience, RapidSOS Engineering Team

2. resolved Jun 04, 2026, 03:00 PM UTC

   Our upstream provider has confirmed that the issue is resolved and all systems are now fully operational and stable. We take these issues seriously and apologize for the impact on your operations. Please reach out to [email protected] with any questions. Thank you for your patience, RapidSOS Engineering Team

Read the full incident report →

Started May 29, 2026, 05:15 AM UTC· resolved May 29, 2026, 12:00 PM UTC

1. identified May 29, 2026, 05:15 AM UTC

   One of our upstream providers is still experiencing an issue which is affecting the RapidSOS component SMS Verification. We are continuing to communicate with our provider and will resolve this incident once we have received confirmation that the issue has been resolved. Thank you for your patience, RapidSOS Engineering Team

2. resolved May 29, 2026, 12:00 PM UTC

   Our upstream provider has confirmed that the issue is resolved and all systems are now fully operational and stable. We take these issues seriously and apologize for the impact on your operations. Please reach out to [email protected] with any questions. Thank you for your patience, RapidSOS Engineering Team

Read the full incident report →

Started May 28, 2026, 02:10 PM UTC· resolved May 28, 2026, 03:53 PM UTC

1. investigating May 28, 2026, 02:10 PM UTC

   Our engineers have discovered an issue with the RapidSOS components flagged below. We have escalated to the appropriate teams and are working to identify and resolve the issue as quickly as possible. We will provide updates here as information becomes available. Please reach out to [email protected] with any questions. Thank you for your patience, RapidSOS Engineering Team

2. resolved May 28, 2026, 03:53 PM UTC

   Our upstream provider has confirmed that the issue is resolved and all systems are now fully operational and stable. We take these issues seriously and apologize for the impact on your operations. Please reach out to [email protected] with any questions. Thank you for your patience, RapidSOS Engineering Team

Read the full incident report →

Started May 26, 2026, 02:52 PM UTC· resolved May 26, 2026, 06:32 PM UTC

1. investigating May 26, 2026, 02:52 PM UTC

   Our engineers have discovered an issue with the RapidSOS components flagged below. We have escalated to the appropriate teams and are working to identify and resolve the issue as quickly as possible. We will provide updates here as information becomes available. Please reach out to [email protected] with any questions. Thank you for your patience, RapidSOS Engineering Team

2. resolved May 26, 2026, 06:32 PM UTC

   The earlier issue with the RapidSOS components flagged below has been resolved and all systems are fully operational. We take these issues seriously and apologize for the impact on your operations. Please reach out to [email protected] with any questions. Thank you for your patience, RapidSOS Engineering Team

Read the full incident report →

Started May 22, 2026, 10:02 PM UTC· resolved May 22, 2026, 10:04 PM UTC

1. resolved May 22, 2026, 10:04 PM UTC

   Our engineers identified an issue today between 18:02 EST and 18:04 EST and took immediate steps for remediation. During this window there was a degradation of UNITE components. The incident has since been resolved, all systems are fully operational, and connection stability has been restored. We take these issues seriously and apologize for the impact on your operations. Please reach out to [email protected] with any questions. Thank you for your patience, RapidSOS Engineering Team

Read the full incident report →

Started May 21, 2026, 03:42 PM UTC· resolved May 21, 2026, 05:26 PM UTC

1. resolved May 21, 2026, 05:26 PM UTC

   Our engineers identified an issue today between: 11:42 am - 11:50 am, 12:08 pm - 12:10 pm, and 1:24 pm - 1:26 pm, and took immediate steps for remediation. During these windows there was a degradation of Connect - US components. The incident has since been resolved, all systems are fully operational, and connection stability has been restored. We take these issues seriously and apologize for the impact on your operations. Please reach out to [email protected] with any questions. Thank you for your patience, RapidSOS Engineering Team

Read the full incident report →

Started May 12, 2026, 05:55 PM UTC· resolved May 12, 2026, 06:36 PM UTC

1. resolved May 12, 2026, 06:36 PM UTC

   Between 13:55 PM EST and 14:36 PM EST, an issue with an upstream provider caused partial outage. The upstream provider has since restored normal operations, and our services are now functioning as expected. We apologize for any inconvenience and are following up with the provider to help prevent recurrence. Please reach out to [email protected] with any questions. Thank you for your patience, RapidSOS Engineering Team

Read the full incident report →

Started May 08, 2026, 12:18 AM UTC· resolved May 08, 2026, 12:40 AM UTC

1. resolved May 08, 2026, 12:40 AM UTC

   Our engineers identified an issue today between 20:18 ET and 20:40 ET and took immediate steps for remediation. During this window there was a degradation of IVR Verification. The incident has since been resolved, all systems are fully operational, and connection stability has been restored. We take these issues seriously and apologize for the impact on your operations. Please reach out to [email protected] with any questions. Thank you for your patience, RapidSOS Engineering Team

Read the full incident report →

Started May 07, 2026, 01:09 AM UTC· resolved May 07, 2026, 03:05 AM UTC

1. investigating May 07, 2026, 01:09 AM UTC

   Our engineers have discovered an issue with the RapidSOS components flagged below. We have escalated to the appropriate teams and are working to identify and resolve the issue as quickly as possible. We will provide updates here as information becomes available. Please reach out to [email protected] with any questions. Thank you for your patience, RapidSOS Engineering Team

2. monitoring May 07, 2026, 01:20 AM UTC

   Our engineers have implemented a fix for the issue with the RapidSOS components flagged below. All RapidSOS Services are operational, and we are observing this closely and will provide updates as information becomes available. Please reach out to [email protected] with any questions. Thank you for your patience, RapidSOS Engineering Team

3. resolved May 07, 2026, 03:05 AM UTC

   The earlier issue with the RapidSOS components flagged below has been resolved and all systems are fully operational. We take these issues seriously and apologize for the impact on your operations. Please reach out to [email protected] with any questions. Thank you for your patience, RapidSOS Engineering Team

Read the full incident report →

Started Apr 30, 2026, 07:03 PM UTC· resolved Apr 30, 2026, 07:19 PM UTC

1. resolved Apr 30, 2026, 07:19 PM UTC

   Our engineers identified an issue today between 3:03 pm and 3:19 pm and took immediate steps for remediation. During this window there was a degradation of Third-Party Monitoring Services. The incident has since been resolved, all systems are fully operational, and connection stability has been restored. We take these issues seriously and apologize for the impact on your operations. Please reach out to [email protected] with any questions. Thank you for your patience, RapidSOS Engineering Team

Read the full incident report →

Started Apr 29, 2026, 08:40 PM UTC· resolved Apr 29, 2026, 10:45 PM UTC

1. resolved Apr 29, 2026, 10:45 PM UTC

   Our engineers identified an issue today between 4:40 pm and 6:45 pm and took immediate steps for remediation. During this window there was a degradation of Telephony Transcription Service . The incident has since been resolved, all systems are fully operational, and connection stability has been restored. We take these issues seriously and apologize for the impact on your operations. Please reach out to [email protected] with any questions. Thank you for your patience, RapidSOS Engineering Team

Read the full incident report →

Started Apr 27, 2026, 08:47 PM UTC· resolved Apr 27, 2026, 10:45 PM UTC

1. resolved Apr 27, 2026, 10:45 PM UTC

   Our engineers identified an issue today between 4:47 PM ET and 6:45 PM ET and took immediate steps for remediation. During this window there was a partial outage of Live Agent Voice . The incident has since been resolved, all systems are fully operational, and connection stability has been restored. We take these issues seriously and apologize for the impact on your operations. Please reach out to [email protected] with any questions. Thank you for your patience, RapidSOS Engineering Team

Read the full incident report →