Visit Outage History
23 incidents recorded over the last 365 days. 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 Visit Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 25, 2026 | Release 6.0The scheduled maintenance has been completed. | 5 min | Scheduled |
| Oct 9, 2026 | Release 5.68The scheduled maintenance has been completed. | 45 min | Scheduled |
| Sep 20, 2026 | Release 5.67The scheduled maintenance has been completed. | 5 min | Scheduled |
| Sep 6, 2026 | Release 5.66The scheduled maintenance has been completed. | 5 min | Scheduled |
| Sep 4, 2026 | Release 5.66We will be undergoing scheduled maintenance during this time. | 5 min | Scheduled |
| Aug 23, 2026 | Release 5.65The scheduled maintenance has been completed. | 5 min | Scheduled |
| Aug 9, 2026 | Release 5.64The scheduled maintenance has been completed. | 5 min | Scheduled |
| Jul 12, 2026 | Release 5.63The scheduled maintenance has been completed. | 5 min | Scheduled |
| Jun 28, 2026 | Release 5.62The scheduled maintenance has been completed. | 5 min | Scheduled |
| Jun 14, 2026 | Release 5.61The scheduled maintenance has been completed. | 5 min | Scheduled |
| May 31, 2026 | Release 5.60The scheduled maintenance has been completed. | 5 min | Scheduled |
| May 17, 2026 | Release 5.59The scheduled maintenance has been completed. | 5 min | Scheduled |
| May 3, 2026 | Release 5.58The scheduled maintenance has been completed. | 5 min | Scheduled |
| Apr 19, 2026 | Release 5.57The scheduled maintenance has been completed. | 5 min | Scheduled |
| Apr 5, 2026 | Release 5.56The scheduled maintenance has been completed. | 5 min | Scheduled |
| Mar 22, 2026 | Release 5.55The scheduled maintenance has been completed. | 5 min | Scheduled |
| Mar 8, 2026 | Release 5.54The scheduled maintenance has been completed. | 5 min | Scheduled |
| Feb 22, 2026 | Release 5.53The scheduled maintenance has been completed. | 5 min | Scheduled |
| Feb 8, 2026 | Release 5.52The scheduled maintenance has been completed. | 5 min | Scheduled |
| Jan 25, 2026 | Release 5.51The scheduled maintenance has been completed. | 5 min | Scheduled |
| Dec 14, 2025 | Release 5.50The scheduled maintenance has been completed. | 5 min | Scheduled |
| Nov 30, 2025 | Release 5.49The scheduled maintenance has been completed. | 5 min | Scheduled |
| Nov 16, 2025 | Release 5.48The scheduled maintenance has been completed. | 5 min | Scheduled |
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 Visit 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 Visit 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 Visit 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 Visit outage in this window ran 45 min, against a mean recovery of 7 min. If you depend on Visit 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.