Is LinkedIn down?
Vendor reports no incidentWhat LinkedIn reports
LinkedIn reports no incident on its status page.
As of the last successful poll, 2026-10-22 19:40 UTC.
Our regional reading
This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.
Checks passingchecked 1 minute ago
Our checks of LinkedIn pass from all 10 regions we check.
As of Oct 22, 2026, 7:47 PM UTC, RealUptime's checks of LinkedIn passed in all 10 regions that returned a reading.
Email me when LinkedIn reports an incident on its status page, and again when it reports it resolved.
LinkedIn reports: All systems operational (“All Systems Operational”)
LinkedIn's own component breakdown, as they publish it
- LinkedIn Campaign ManagerOperational
- LinkedIn LearningOperational
- LinkedIn RecruiterOperational
- LinkedIn.comOperational
- LinkedIn AdsOperational
- LinkedIn JobsOperational
- LinkedIn Sales InsightsOperational
- LinkedIn PagesOperational
- LinkedIn Talent HubOperational
- LinkedIn Sales NavigatorOperational
- Linkedin Talent InsightsOperational
These are LinkedIn's components, named and scored by LinkedIn. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.
This is LinkedIn's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.
LinkedIn response time, by region
Check your own site while you wait on LinkedIn
Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not LinkedIn. It cannot diagnose LinkedIn's own systems.
What our checks show, and what people reported
- North AmericaChecks passingUS-East, US-West, US-Central, Canada
- US-EastChecks passinglatency: 1245msstatus code: 200checked: Oct 22, 2026, 7:44 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach LinkedIn normally. We do not have enough reports from US-East to say anything about what people there are seeing.
- US-WestChecks passinglatency: 1040msstatus code: 200checked: Oct 22, 2026, 7:47 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach LinkedIn normally. We do not have enough reports from US-West to say anything about what people there are seeing.
- US-CentralChecks passinglatency: 986msstatus code: 200checked: Oct 22, 2026, 7:39 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach LinkedIn normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
- CanadaChecks passinglatency: 608msstatus code: 200checked: Oct 22, 2026, 7:43 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach LinkedIn normally. We do not have enough reports from Canada to say anything about what people there are seeing.
- South AmericaChecks passinglatency: 2176msstatus code: 200checked: Oct 22, 2026, 7:39 PM UTC0 people in the last 5 minutesNot enough reports to sayOur South America probes reach LinkedIn normally. We do not have enough reports from South America to say anything about what people there are seeing.
- EuropeChecks passingEurope, UK
- EuropeChecks passinglatency: 655msstatus code: 200checked: Oct 22, 2026, 7:42 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach LinkedIn normally. We do not have enough reports from Europe to say anything about what people there are seeing.
- UKChecks passinglatency: 860msstatus code: 200checked: Oct 22, 2026, 7:38 PM UTC0 people in the last 5 minutesNot enough reports to sayOur UK probes reach LinkedIn normally. We do not have enough reports from UK to say anything about what people there are seeing.
- Asia PacificChecks passingAsia-Pacific, Southeast Asia, Australia
- Asia-PacificChecks passinglatency: 1869msstatus code: 200checked: Oct 22, 2026, 7:44 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach LinkedIn normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
- Southeast AsiaChecks passinglatency: 2458msstatus code: 200checked: Oct 22, 2026, 7:43 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach LinkedIn normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
- AustraliaChecks passinglatency: 2429msstatus code: 200checked: Oct 22, 2026, 7:46 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach LinkedIn normally. We do not have enough reports from Australia to say anything about what people there are seeing.
Somewhere else or not sure: 0 people in the last 5 minutes
These are unverified reports from people using LinkedIn, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for LinkedIn yet, which is not evidence that nothing is wrong.
Recent probe events
check entries are our own probes' readings; declared entries are the vendor's. How this check works
We have been measuring LinkedIn since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.
Need this in writing? Generate an SLA evidence report for LinkedIn covering any window you pick, with our check readings and LinkedIn's own claim at the time, side by side.
Full check history for LinkedIn: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.
Put this badge in your README
Live, from this page's own readings.[](https://realuptime.io/outages/linkedin)<a href="https://realuptime.io/outages/linkedin"><img src="https://realuptime.io/outages/linkedin/badge.svg?days=30" alt="LinkedIn uptime by RealUptime's checks" height="20"></a>The badge shows the share of our checks that passed over the last 30 days. The window is printed on it, so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.
To cite this page: RealUptime, "Is LinkedIn down?", https://realuptime.io/outages/linkedin. The readings change with every check, so give the date you read them.
Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.
What we check
What our check can and cannot see
A pass means the service's public web page loaded and answered normally. It does not show that the product, the API or sign-in behind it works; a page can load from a cache while the product is down.
Host checked: www.linkedin.com