- Detected by Pingoru
- Sep 02, 2026, 10:22 PM UTC
- Resolved
- Sep 02, 2026, 10:54 PM UTC
- Duration
- 32m
Affected: Reporting (Reporting)
Timeline · 2 updates
-
investigating Sep 02, 2026, 10:22 PM UTC
We are aware of issues affecting HL7 and are actively investigating. We will provide updates as more information becomes available.
-
resolved Sep 02, 2026, 10:54 PM UTC
Our engineers have identified and fixed the issue and will continue to monitor.
Read the full incident report →
- Detected by Pingoru
- Aug 12, 2026, 02:09 AM UTC
- Resolved
- Aug 12, 2026, 03:51 AM UTC
- Duration
- 1h 42m
Affected: Reporting (Reporting)
Timeline · 2 updates
-
investigating Aug 12, 2026, 02:09 AM UTC
Some customers may be experiencing a degraded service on Reporting. Our Engineering Team is working on the issue and will provide updates as more information is available.
-
resolved Aug 12, 2026, 03:51 AM UTC
The issue has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 24, 2026, 12:10 PM UTC
- Resolved
- Jul 24, 2026, 01:12 PM UTC
- Duration
- 1h 2m
Affected: Omni Impressions (Omni Impressions)Reporting (Reporting)Nexus (Nexus)Continuity (Continuity)
Timeline · 2 updates
-
investigating Jul 24, 2026, 12:10 PM UTC
We are aware of issues affecting Rad AI services due to an outage in our primary cloud provider. Our team is actively investigating and working to resolve the situation. We will provide updates as more information becomes available.
-
resolved Jul 24, 2026, 01:12 PM UTC
Our cloud provider has fixed their outage and connectivity has been restored to all RadAI products.
Read the full incident report →
- Detected by Pingoru
- May 27, 2026, 02:11 PM UTC
- Resolved
- May 27, 2026, 02:11 PM UTC
- Duration
- –
Affected: Reporting (Reporting)
Timeline · 1 update
-
resolved May 27, 2026, 02:11 PM UTC
We are investigating an issue where selecting an observation from the list may cause the Reporting application to close the report for some users. If you have any questions, please reach out to [email protected].
Read the full incident report →
- Detected by Pingoru
- May 06, 2026, 04:03 PM UTC
- Resolved
- May 06, 2026, 04:41 PM UTC
- Duration
- 37m
Affected: Reporting (Reporting)
Timeline · 2 updates
-
investigating May 06, 2026, 04:03 PM UTC
We are investigating an issue affecting OmniReport. Users may experience degraded performance. Updates will be provided as we learn more.
-
resolved May 06, 2026, 04:41 PM UTC
We have identified the root cause of the Omni Report outage. All services should now be restored to normal operations, but we are continuing to monitor closely.
Read the full incident report →
- Detected by Pingoru
- Apr 14, 2026, 01:42 PM UTC
- Resolved
- Apr 14, 2026, 02:00 PM UTC
- Duration
- 17m
Affected: Reporting (Reporting)
Timeline · 2 updates
-
investigating Apr 14, 2026, 01:42 PM UTC
Users of Reporting EAP may be experiencing issues with logging in. Our teams have identified the issue and are working on a resolution.
-
resolved Apr 14, 2026, 02:00 PM UTC
EAP is now available for everyone
Read the full incident report →
- Detected by Pingoru
- Apr 02, 2026, 11:04 PM UTC
- Resolved
- Apr 02, 2026, 11:04 PM UTC
- Duration
- –
Affected: Reporting (Reporting)
Timeline · 1 update
-
resolved Apr 02, 2026, 11:04 PM UTC
We are currently investigating an issue with the Advanced Speech engine for Reporting. Advanced Speech engine users should switch to the Standard Speech model. We will provide an update by 7:40 EST.
Read the full incident report →
- Detected by Pingoru
- Apr 02, 2026, 02:10 PM UTC
- Resolved
- Apr 02, 2026, 02:10 PM UTC
- Duration
- –
Affected: Reporting (Reporting)
Timeline · 1 update
-
resolved Apr 02, 2026, 02:10 PM UTC
Some users are reporting issues with Reporting with login failures or spinning.
Read the full incident report →
- Detected by Pingoru
- Mar 26, 2026, 04:53 PM UTC
- Resolved
- Mar 26, 2026, 05:30 PM UTC
- Duration
- 37m
Affected: Reporting (Reporting)
Timeline · 2 updates
-
investigating Mar 26, 2026, 04:53 PM UTC
We are currently investigating feedback due to the degraded speech service.
-
resolved Mar 26, 2026, 05:30 PM UTC
The speech service is now back to normal.
Read the full incident report →
- Detected by Pingoru
- Mar 19, 2026, 12:08 AM UTC
- Resolved
- Mar 19, 2026, 12:35 AM UTC
- Duration
- 27m
Affected: Reporting (Reporting)
Timeline · 2 updates
-
investigating Mar 19, 2026, 12:08 AM UTC
Rad AI is currently down due to an ongoing issue. Our team is actively working on a fix and will provide updates shortly.
-
resolved Mar 19, 2026, 12:35 AM UTC
Services to the Reporting Client have been fully restored.
Read the full incident report →
- Detected by Pingoru
- Mar 05, 2026, 03:56 PM UTC
- Resolved
- Mar 05, 2026, 06:50 PM UTC
- Duration
- 2h 54m
Affected: Omni Impressions (Omni Impressions)
Timeline · 2 updates
-
investigating Mar 05, 2026, 03:56 PM UTC
We are seeing an increased number of timeouts for the Impressions service. Our teams are investigating.
-
resolved Mar 05, 2026, 06:50 PM UTC
We have identified the root cause of the Omni Impression generation problem, and the issue is now resolved. Impressions should now be functioning as intended. Thank you!
Read the full incident report →
- Detected by Pingoru
- Mar 03, 2026, 05:38 PM UTC
- Resolved
- Mar 03, 2026, 07:32 PM UTC
- Duration
- 1h 54m
Affected: Omni Impressions (Omni Impressions)
Timeline · 2 updates
-
investigating Mar 03, 2026, 05:38 PM UTC
We are seeing an increase in timeouts for the recommendation within the Impression service. Our teams are investigating.
-
resolved Mar 03, 2026, 07:32 PM UTC
Our recommendation service is now stable. Thank you for your patience!
Read the full incident report →
- Detected by Pingoru
- Feb 24, 2026, 02:56 PM UTC
- Resolved
- Feb 24, 2026, 05:08 PM UTC
- Duration
- 2h 12m
Affected: Reporting (Reporting)
Timeline · 2 updates
-
investigating Feb 24, 2026, 02:56 PM UTC
We are actively investigating a latency issue that may impact user login and report signing.
-
resolved Feb 24, 2026, 05:08 PM UTC
The latency issue with Login and Report signing is resolved. FHIR connection has returned to normal, and we will continue to monitor.
Read the full incident report →
- Detected by Pingoru
- Jan 16, 2026, 06:18 PM UTC
- Resolved
- Jan 16, 2026, 06:18 PM UTC
- Duration
- –
Affected: Reporting (Reporting)
Timeline · 1 update
-
resolved Jan 16, 2026, 06:18 PM UTC
Latency has returned to normal on the Reporting platform, and we will continue to monitor.
Read the full incident report →
- Detected by Pingoru
- Dec 24, 2025, 09:37 PM UTC
- Resolved
- Dec 24, 2025, 09:37 PM UTC
- Duration
- –
Affected: Reporting (Reporting)
Timeline · 1 update
-
resolved Dec 24, 2025, 09:37 PM UTC
We are currently investigating reports of increased latency and intermittent service outages. Our team is actively working to identify the root cause and will provide updates as more information becomes available.
Read the full incident report →
- Detected by Pingoru
- Dec 24, 2025, 09:36 PM UTC
- Resolved
- Dec 24, 2025, 09:36 PM UTC
- Duration
- –
Affected: Reporting (Reporting)
Timeline · 1 update
-
resolved Dec 24, 2025, 09:36 PM UTC
We are currently investigating latency issues with Omni and Omnibox.
Read the full incident report →
- Detected by Pingoru
- Dec 16, 2025, 04:37 PM UTC
- Resolved
- Dec 16, 2025, 05:03 PM UTC
- Duration
- 26m
Affected: Omni Impressions (Omni Impressions)
Timeline · 2 updates
-
investigating Dec 16, 2025, 04:37 PM UTC
We are currently experiencing latency and intermittent outages affecting the Omni Impression application. Users may notice delays in impression generation or periods where the application is unavailable. Our engineering team is actively investigating and working to restore normal performance.
-
resolved Dec 16, 2025, 05:03 PM UTC
The issue causing latency and intermittent outages in Omni Impression has been resolved. All services are now operating normally.
Read the full incident report →
- Detected by Pingoru
- Dec 04, 2025, 09:59 PM UTC
- Resolved
- Dec 04, 2025, 11:10 PM UTC
- Duration
- 1h 11m
Affected: Reporting (Reporting)
Timeline · 2 updates
-
investigating Dec 04, 2025, 09:59 PM UTC
We are currently working on resolving the crashing and error issues affecting Reporting.
-
resolved Dec 04, 2025, 11:10 PM UTC
We have reverted the Reporting app to the previous release.
Read the full incident report →
- Detected by Pingoru
- Nov 24, 2025, 04:59 PM UTC
- Resolved
- Nov 24, 2025, 07:47 PM UTC
- Duration
- 2h 48m
Affected: Omni Impressions (Omni Impressions)
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 02:43 PM UTC
- Resolved
- Nov 18, 2025, 02:43 PM UTC
- Duration
- –
Affected: Reporting (Reporting)
Timeline · 1 update
-
resolved Nov 18, 2025, 02:43 PM UTC
Update 1: Cloudfare has reported the issue is resolved and all internal testing is successful with the Rad AI applications. Cloudfare currently has a global network outage. We are closely monitoring the situation and will update impacts to Rad AI as soon as our teams complete initial investigation. https://www.cloudflarestatus.com/
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 06:00 PM UTC
- Resolved
- Oct 20, 2025, 10:28 PM UTC
- Duration
- 4h 28m
Affected: Reporting (Reporting)Continuity (Continuity)
Timeline · 2 updates
-
investigating Oct 20, 2025, 06:00 PM UTC
Some Reporting and Continuity customers maybe experiencing degradation due to the AWS outage (https://health.aws.amazon.com/health/status). We are currently monitoring the situation and will update as we have additional information.
-
resolved Oct 20, 2025, 10:28 PM UTC
We are stabilized now. We are monitoring closely but message processing is back to normal throughput with no elevated error rates. Latest AWS Update (Oct 20 2:48 PM PDT): "We have restored EC2 instance launch throttles to pre-event levels and EC2 launch failures have recovered across all Availability Zones in the US-EAST-1 Regions. AWS services which rely on EC2 instance launches such as Redshift are working through their backlog of EC2 instance launches successfully and we anticipate full recovery of the backlog over the next two hours. We can confirm that Connect is handling new voice and chat sessions normally. There is a backlog of analytics and reporting data that we must process and anticipate that we will have worked through the backlog over the next two hours. We will provide an update by 3:30 PM PDT."
Read the full incident report →
- Detected by Pingoru
- May 22, 2025, 03:36 PM UTC
- Resolved
- May 22, 2025, 04:06 PM UTC
- Duration
- 30m
Affected: Reporting (Reporting)
Timeline · 2 updates
-
investigating May 22, 2025, 03:36 PM UTC
Certain functions of Reporting are inaccessible for some users. Our team is currently investigating.
-
resolved May 22, 2025, 04:06 PM UTC
All services are back up.
Read the full incident report →
- Detected by Pingoru
- Apr 09, 2025, 02:30 PM UTC
- Resolved
- Apr 09, 2025, 06:42 PM UTC
- Duration
- 4h 12m
Affected: Reporting (Reporting)
Timeline · 2 updates
-
investigating Apr 09, 2025, 02:30 PM UTC
Some users report having trouble using the Omni Report functionality in Rad AI Reporting this morning. We are investigating this issue and will provide an update once normal service is restored.
-
resolved Apr 09, 2025, 06:42 PM UTC
The earlier issue with Omni Report has been resolved and should be functioning normally now. Please contact Support if you experience any further issues.
Read the full incident report →