LinkedIn Outage History
5 incidents recorded over the last 365 days, 5 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 LinkedIn Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 15, 2026 | Linkedin.com - IssueThis has now been resolved and we’re back up and running. Apologies for any inconvenience caused and thanks for your patience! | 3h 46m | Resolved |
| Aug 14, 2026 | LinkedIn.com IssueSome members may have experienced trouble accessing LinkedIn. This has now been resolved. | -1097 min | Resolved |
| May 21, 2026 | Notification IssueSome members may have experienced an issue with content notifications sent in error on LinkedIn.com. This has now been resolved. Apologies for any inconvenience caused and thanks for your patience! | -172 min | Resolved |
| Mar 28, 2026 | LinkedIn.com-IssueThis has now been resolved and we’re back up and running. Apologies for any inconvenience caused and thanks for your patience! | 123h 15m | Resolved |
| Oct 28, 2025 | Linkedin.com - IssueThis has now been resolved and we’re back up and running. Apologies for any inconvenience caused and thanks for your patience! | 28 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 LinkedIn 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 LinkedIn 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 LinkedIn 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 LinkedIn outage in this window ran 5d 3h, against a mean recovery of 1d 18h. If you depend on LinkedIn 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.