Nexus Repository Outage History
1 incident recorded over the last 365 days, 1 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 Nexus Repository Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 29, 2025 | Data Services IncidentThis incident has been resolved. | 19 min | Resolved |
How to Read This Nexus Repository 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 Nexus Repository 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 Nexus Repository outage in this window ran 19 min, against a mean recovery of 19 min. If you depend on Nexus Repository 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.