Everlaw 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 Everlaw Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Mar 17, 2026 | This is an example incidentEmpathize with those affected and let them know everything is operating as normal. | -1424 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 Everlaw 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 Everlaw 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 Everlaw 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.