Proof Outage History
8 incidents recorded over the last 365 days, 8 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 Proof Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jul 20, 2026 | Issue adding documents to a transactionThis incident has been resolved. | 6h 1m | Resolved |
| Jul 14, 2026 | Degraded PerformanceNo new occurrences of the issue have been identified during the monitoring period. The issue has been resolved. | 2h 20m | Resolved |
| Apr 8, 2026 | Document completion delays on Proof platformThis incident has been resolved. | 42 min | Resolved |
| Feb 20, 2026 | Proof platform - real estate closing incident due to eVault service outageThis incident has been resolved. | 31 min | Resolved |
| Feb 4, 2026 | Degraded performance with identity verificationThe vendor has resolved the issue. Our service is functioning normally now. | 37 min | Resolved |
| Jan 15, 2026 | Retroactive update: credential analysis errors on Proof platformOn January 15th 2026, between 10:35 and 11:05 am ET, Proof platform experienced elevated error rates when handling credential analysis. This prevented most signers from entering a meeting with a notary. We observed a… | -101 min | Resolved |
| Dec 12, 2025 | Issue with 3rd-party services impacting eNotesThis incident has been resolved. | 1h 5m | Resolved |
| Nov 17, 2025 | Delays in Processing DocumentsThe issue has been resolved. | 2h 32m | 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 Proof 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 Proof 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 Proof 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 Proof outage in this window ran 6h 1m, against a mean recovery of 1h 58m. If you depend on Proof 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.