Nex Outage History
6 incidents recorded over the last 365 days, 6 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Nex Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 3, 2026 | Medical Alerts are not being synced properly | 1h 26m | Resolved |
| Oct 23, 2026 | Investigating Denticon Synchronizer performance issues | 1h 41m | Resolved |
| Oct 9, 2026 | Elevated error rate across the platform | 1h 36m | Resolved |
| Oct 6, 2026 | Investigating eCW Synchronizer performance issues | 69h 31m | Resolved |
| Sep 30, 2026 | Synchronzier communication failures | 5h 20m | Resolved |
| Sep 3, 2026 | Partial Athena outage detected | 45 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Nex incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Nex Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Nex acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Nex outage in this window ran 2d 21h, against a mean recovery of 13h 23m. If you depend on Nex in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.