Is AdvaPACS down?
Last checked 2m agoNo incidents right now.
AdvaPACS is operational right now. Last checked 2m ago; the most recent incident resolved 3d ago.
Real-time AdvaPACS status, recent outages, and incident history — pulled directly from AdvaPACS's official status page at https://status.advapacs.com every 5 minutes. Pingoru tracks 46 AdvaPACS services and has captured 9 incidents in the last 90 days (99.56% uptime). Get email, Slack, Discord, or webhook alerts the moment AdvaPACS reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Patient Portal
Timeline · 2 updates
- identified · Aug 01, 2026, 01:32 AM UTC
An issue has been found with our email distribution partner. Their team are aware of the issue and investigating the cause.
- resolved · Aug 01, 2026, 02:34 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- RADPAIR
Timeline · 3 updates
- investigating · Jul 29, 2026, 09:33 PM UTC
We are currently investigating this issue.
- identified · Jul 29, 2026, 09:43 PM UTC
RADPAIR has confirmed an issue affecting multiple customers and are investigating the issue.
- resolved · Jul 29, 2026, 09:57 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- eUnity Viewer
Timeline · 2 updates
- investigating · Jul 24, 2026, 12:01 AM UTC
We are currently investigating an issue regarding loading speeds for eUnity in the AUS region.
- resolved · Jul 24, 2026, 12:19 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- AdvaPACS PlatformAdvaPACS PlatformAdvaPACS PlatformAdvaPACS PlatformAdvaPACS PlatformAdvaPACS PlatformAdvaPACS Platform
Timeline · 2 updates
- investigating · Jun 22, 2026, 10:58 PM UTC
We are currently investigating an issue affecting the UI within AdvaPACS.
- resolved · Jun 22, 2026, 10:59 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
-
Timeline · 2 updates
- resolved · Jun 11, 2026, 11:32 PM UTC
AdvaPACS users with tenants located in the Canada (can1) region will have experienced intermittent connection timeouts when trying to access AdvaPACS.
- postmortem · Jun 12, 2026, 08:20 AM UTC
### Summary Between 14:32 UTC and 15:14 UTC, AdvaPACS users in the Canada region experienced intermittent connection timeouts when accessing the platform. During this window, image uploads, downloads, and viewing functionality were unavailable or unreliable. The issue was caused by a failure in a core infrastructure routing component responsible for directing incoming traffic to the appropriate AdvaPACS services. The component exhausted its available memory under heavy concurrent upload load, causing it to crash and restart repeatedly. Service was fully restored at 15:14 UTC and has remained stable since. ### What Happened Due to the routing component being deprecated by the organization that supported it, AdvaPACS has been migrating to a newer and more capable traffic routing layer. This new component had been successfully deployed and validated across multiple smaller regions over several weeks prior to being promoted to larger regions, including Canada. Under the higher volume and concurrency of the Canada region, the routing component's in-memory request buffering exceeded its allocated resources. This caused repeated crashes, during which all in-flight requests were dropped and users experienced connection timeouts. ### Impact * Users in the Canada region were unable to reliably access AdvaPACS for approximately 42 minutes. * Image uploads, downloads, and viewing were affected. * No data loss occurred as a result of this incident. ### Resolution Once the issue was identified, the engineering team determined the root cause was memory exhaustion in the routing layer. Resource allocations were increased to stabilise the component, and service was restored. ### Preventive Measures We have identified the following actions to prevent recurrence: 1. **Enhanced monitoring and alerting** — Dedicated monitoring and automated alerting are being implemented for the routing component to ensure rapid detection and response to any future resource pressure. 2. **Disk-based request buffering** — The routing component is being tuned to offload more request buffering to disk rather than holding entire request bodies in memory. This eliminates the risk of memory exhaustion under heavy upload concurrency. ### Current Status All services in the Canada region are operating normally. The preventive measures listed above are actively being implemented and are expected to be completed shortly.
Latest: ### Summary Between 14:32 UTC and 15:14 UTC, AdvaPACS users in the Canada region experienced intermittent connection timeouts when accessing the platform. During this window, image…
-
See the full AdvaPACS outage history
4 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse AdvaPACS outage history →Or sign up free to get alerts when AdvaPACS breaks · 10 free monitors · No credit card
- Started Aug 01, 2026, 01:32 AM UTC · Resolved Aug 01, 2026, 02:34 AM UTC · 1h 2m
- Started Jul 29, 2026, 09:33 PM UTC · Resolved Jul 29, 2026, 09:57 PM UTC · 24m
- eUnity Service Degradation in AUS ResolvedStarted Jul 24, 2026, 12:01 AM UTC · Resolved Jul 24, 2026, 12:19 AM UTC · 18m
- Service Disruption in All Regions ResolvedStarted Jun 22, 2026, 10:58 PM UTC · Resolved Jun 22, 2026, 10:59 PM UTC · 1m
- Started Jun 11, 2026, 11:32 PM UTC · Resolved Jun 11, 2026, 02:30 PM UTC · —
- Started Jun 09, 2026, 04:43 PM UTC · Resolved Jun 09, 2026, 04:46 PM UTC · 3m
- eUnity unavailable in AUS ResolvedStarted Jun 03, 2026, 04:39 AM UTC · Resolved Jun 03, 2026, 06:02 AM UTC · 1h 23m
- Started Jun 03, 2026, 03:08 AM UTC · Resolved Jun 03, 2026, 06:02 AM UTC · 2h 54m