Skip to content

Outage tracker / LinkedIn

Is LinkedIn down?

I'm having a problem

Vendor reports no incidentWhat LinkedIn reports

LinkedIn reports no incident on its status page.

As of the last successful poll, 2026-11-05 15:31 UTC.

LinkedIn's status page

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 Nov 5, 2026, 3:42 PM UTC, RealUptime's checks of LinkedIn passed in all 10 regions that returned a reading.

Front-door and live API checks

Email me when LinkedIn reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is LinkedIn's own statement from its status page, with our regional reading beside it.

our check readinglive · checked Nov 5, 2026, 3:42 PM UTC
US-East2690 msChecks passing
US-West2530 msChecks passing
Europe2269 msChecks passing
Asia-Pacific3132 msChecks passing
US-Central913 msChecks passing
Canada950 msChecks passing
UK625 msChecks passing
Southeast Asia2227 msChecks passing
Australia2249 msChecks passing
South America2257 msChecks passing
their status pagetheir claim, not our reading

LinkedIn reports: All systems operational (“All Systems Operational”)

from LinkedIn's own status page, checked Nov 5, 2026, 3:33 PM UTC
LinkedIn's own status page shows no incident, and our checks of LinkedIn pass right now.

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

US-East
2.3sp95 · latest
5s2.5s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 851ms2026-10-08 UTC: p95 896ms2026-10-09 UTC: p95 751ms2026-10-10 UTC: p95 730ms2026-10-11 UTC: p95 541ms2026-10-12 UTC: p95 769ms2026-10-13 UTC: p95 894ms2026-10-14 UTC: p95 794ms2026-10-15 UTC: p95 801ms2026-10-16 UTC: p95 856ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.5s2026-10-23 UTC: p95 1.6s2026-10-24 UTC: p95 1.6s2026-10-25 UTC: p95 1.6s2026-10-26 UTC: p95 2.1s2026-10-27 UTC: p95 1.6s2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 1.6s2026-10-30 UTC: p95 1.5s2026-10-31 UTC: p95 1.4s2026-11-01 UTC: p95 1.4s2026-11-02 UTC: p95 1.9s2026-11-03 UTC: p95 2.6s2026-11-04 UTC: p95 2.6s2026-11-05 UTC: p95 2.3s
Oct 7Oct 21Nov 5
US-West
3.2sp95 · latest
5s2.5s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 933ms2026-10-08 UTC: p95 886ms2026-10-09 UTC: p95 900ms2026-10-10 UTC: p95 482ms2026-10-11 UTC: p95 555ms2026-10-12 UTC: p95 534ms2026-10-13 UTC: p95 726ms2026-10-14 UTC: p95 911ms2026-10-15 UTC: p95 844ms2026-10-16 UTC: p95 857ms2026-10-17 UTC: p95 938ms2026-10-18 UTC: p95 1.0s2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.5s2026-10-23 UTC: p95 1.5s2026-10-24 UTC: p95 1.5s2026-10-25 UTC: p95 1.5s2026-10-26 UTC: p95 1.8s2026-10-27 UTC: p95 1.6s2026-10-28 UTC: p95 1.5s2026-10-29 UTC: p95 1.6s2026-10-30 UTC: p95 1.6s2026-10-31 UTC: p95 1.5s2026-11-01 UTC: p95 1.6s2026-11-02 UTC: p95 2.2s2026-11-03 UTC: p95 2.8s2026-11-04 UTC: p95 3.2s2026-11-05 UTC: p95 3.2s
Oct 7Oct 21Nov 5
Europe
2.5sp95 · latest
2.5s1.3s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 723ms2026-10-08 UTC: p95 776ms2026-10-09 UTC: p95 932ms2026-10-10 UTC: p95 803ms2026-10-11 UTC: p95 754ms2026-10-12 UTC: p95 860ms2026-10-13 UTC: p95 637ms2026-10-14 UTC: p95 825ms2026-10-15 UTC: p95 680ms2026-10-16 UTC: p95 613ms2026-10-17 UTC: p95 999ms2026-10-18 UTC: p95 1.0s2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 921ms2026-10-21 UTC: p95 1.0s2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 850ms2026-10-24 UTC: p95 699ms2026-10-25 UTC: p95 806ms2026-10-26 UTC: p95 933ms2026-10-27 UTC: p95 908ms2026-10-28 UTC: p95 799ms2026-10-29 UTC: p95 885ms2026-10-30 UTC: p95 856ms2026-10-31 UTC: p95 943ms2026-11-01 UTC: p95 979ms2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 2.4s2026-11-04 UTC: p95 2.0s2026-11-05 UTC: p95 2.5s
Oct 7Oct 21Nov 5
Asia-Pacific
3.3sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.2s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.5s2026-10-11 UTC: p95 1.4s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 967ms2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.7s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 1.9s2026-10-20 UTC: p95 1.9s2026-10-21 UTC: p95 1.9s2026-10-22 UTC: p95 2.1s2026-10-23 UTC: p95 2.4s2026-10-24 UTC: p95 2.2s2026-10-25 UTC: p95 1.8s2026-10-26 UTC: p95 2.6s2026-10-27 UTC: p95 1.9s2026-10-28 UTC: p95 1.8s2026-10-29 UTC: p95 2.1s2026-10-30 UTC: p95 1.9s2026-10-31 UTC: p95 1.9s2026-11-01 UTC: p95 2.0s2026-11-02 UTC: p95 2.8s2026-11-03 UTC: p95 3.3s2026-11-04 UTC: p95 4.3s2026-11-05 UTC: p95 3.3s
Oct 7Oct 21Nov 5
US-Central
979msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 860ms2026-10-08 UTC: p95 601ms2026-10-09 UTC: p95 684ms2026-10-10 UTC: p95 629ms2026-10-11 UTC: p95 736ms2026-10-12 UTC: p95 720ms2026-10-13 UTC: p95 778ms2026-10-14 UTC: p95 826ms2026-10-15 UTC: p95 630ms2026-10-16 UTC: p95 741ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 1.4s2026-10-24 UTC: p95 1.3s2026-10-25 UTC: p95 1.4s2026-10-26 UTC: p95 1.6s2026-10-27 UTC: p95 1.4s2026-10-28 UTC: p95 1.6s2026-10-29 UTC: p95 1.3s2026-10-30 UTC: p95 1.5s2026-10-31 UTC: p95 1.4s2026-11-01 UTC: p95 1.2s2026-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 1.2s2026-11-04 UTC: p95 1.1s2026-11-05 UTC: p95 979ms
Oct 7Oct 21Nov 5
Canada
1.3sp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 785ms2026-10-08 UTC: p95 832ms2026-10-09 UTC: p95 825ms2026-10-10 UTC: p95 659ms2026-10-11 UTC: p95 730ms2026-10-12 UTC: p95 573ms2026-10-13 UTC: p95 743ms2026-10-14 UTC: p95 827ms2026-10-15 UTC: p95 811ms2026-10-16 UTC: p95 795ms2026-10-17 UTC: p95 734ms2026-10-18 UTC: p95 555ms2026-10-19 UTC: p95 588ms2026-10-20 UTC: p95 502ms2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 965ms2026-10-24 UTC: p95 947ms2026-10-25 UTC: p95 884ms2026-10-26 UTC: p95 1.3s2026-10-27 UTC: p95 1.4s2026-10-28 UTC: p95 1.5s2026-10-29 UTC: p95 1.5s2026-10-30 UTC: p95 1.5s2026-10-31 UTC: p95 1.6s2026-11-01 UTC: p95 1.7s2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 1.6s2026-11-05 UTC: p95 1.3s
Oct 7Oct 21Nov 5
UK
868msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 806ms2026-10-08 UTC: p95 837ms2026-10-09 UTC: p95 934ms2026-10-10 UTC: p95 768ms2026-10-11 UTC: p95 592ms2026-10-12 UTC: p95 685ms2026-10-13 UTC: p95 528ms2026-10-14 UTC: p95 520ms2026-10-15 UTC: p95 556ms2026-10-16 UTC: p95 591ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.4s2026-10-23 UTC: p95 1.4s2026-10-24 UTC: p95 1.3s2026-10-25 UTC: p95 1.5s2026-10-26 UTC: p95 1.4s2026-10-27 UTC: p95 1.4s2026-10-28 UTC: p95 1.3s2026-10-29 UTC: p95 1.4s2026-10-30 UTC: p95 1.4s2026-10-31 UTC: p95 1.4s2026-11-01 UTC: p95 1.4s2026-11-02 UTC: p95 1.2s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 868ms
Oct 7Oct 21Nov 5
Southeast Asia
2.8sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.4s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.9s2026-10-11 UTC: p95 1.6s2026-10-12 UTC: p95 1.7s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 1.4s2026-10-16 UTC: p95 1.3s2026-10-17 UTC: p95 1.7s2026-10-18 UTC: p95 2.2s2026-10-19 UTC: p95 3.0s2026-10-20 UTC: p95 3.2s2026-10-21 UTC: p95 3.0s2026-10-22 UTC: p95 3.9s2026-10-23 UTC: p95 3.1s2026-10-24 UTC: p95 3.0s2026-10-25 UTC: p95 3.2s2026-10-26 UTC: p95 3.5s2026-10-27 UTC: p95 3.1s2026-10-28 UTC: p95 3.0s2026-10-29 UTC: p95 3.2s2026-10-30 UTC: p95 3.3s2026-10-31 UTC: p95 3.2s2026-11-01 UTC: p95 3.5s2026-11-02 UTC: p95 3.8s2026-11-03 UTC: p95 3.7s2026-11-04 UTC: p95 2.4s2026-11-05 UTC: p95 2.8s
Oct 7Oct 21Nov 5
Australia
2.4sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.6s2026-10-08 UTC: p95 1.6s2026-10-09 UTC: p95 1.6s2026-10-10 UTC: p95 1.6s2026-10-11 UTC: p95 1.4s2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 2.5s2026-10-18 UTC: p95 2.6s2026-10-19 UTC: p95 2.8s2026-10-20 UTC: p95 3.2s2026-10-21 UTC: p95 2.6s2026-10-22 UTC: p95 2.8s2026-10-23 UTC: p95 2.7s2026-10-24 UTC: p95 2.8s2026-10-25 UTC: p95 3.0s2026-10-26 UTC: p95 2.6s2026-10-27 UTC: p95 2.7s2026-10-28 UTC: p95 2.8s2026-10-29 UTC: p95 2.7s2026-10-30 UTC: p95 3.0s2026-10-31 UTC: p95 3.1s2026-11-01 UTC: p95 3.0s2026-11-02 UTC: p95 2.9s2026-11-03 UTC: p95 2.5s2026-11-04 UTC: p95 2.4s2026-11-05 UTC: p95 2.4s
Oct 7Oct 21Nov 5
South America
2.7sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.4s2026-10-08 UTC: p95 1.6s2026-10-09 UTC: p95 1.5s2026-10-10 UTC: p95 1.5s2026-10-11 UTC: p95 1.6s2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1.3s2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 1.3s2026-10-17 UTC: p95 1.9s2026-10-18 UTC: p95 2.0s2026-10-19 UTC: p95 1.9s2026-10-20 UTC: p95 2.3s2026-10-21 UTC: p95 2.2s2026-10-22 UTC: p95 2.7s2026-10-23 UTC: p95 9.6s2026-10-24 UTC: p95 3.1s2026-10-25 UTC: p95 3.4s2026-10-26 UTC: p95 3.2s2026-10-27 UTC: p95 3.0s2026-10-28 UTC: p95 2.8s2026-10-29 UTC: p95 3.2s2026-10-30 UTC: p95 3.0s2026-10-31 UTC: p95 2.9s2026-11-01 UTC: p95 2.7s2026-11-02 UTC: p95 2.6s2026-11-03 UTC: p95 2.4s2026-11-04 UTC: p95 2.7s2026-11-05 UTC: p95 2.7s
Oct 7Oct 21Nov 5

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 we measured, function by function

LinkedIn answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the web row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • LinkedIn JobsUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • LinkedIn LearningUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • LinkedIn PagesUS-East: Awaiting dataUS-West: Awaiting dataEurope: Awaiting dataAsia-Pacific: Awaiting dataUS-Central: Awaiting dataCanada: Awaiting dataUK: Awaiting dataSoutheast Asia: Awaiting dataAustralia: Awaiting dataSouth America: Awaiting data
What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 2690msstatus code: 200checked: Nov 5, 2026, 3:42 PM UTC
      0 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-West
      Checks passinglatency: 2530msstatus code: 200checked: Nov 5, 2026, 3:33 PM UTC
      0 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-Central
      Checks passinglatency: 913msstatus code: 200checked: Nov 5, 2026, 3:40 PM UTC
      0 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.
    • Canada
      Checks passinglatency: 950msstatus code: 200checked: Nov 5, 2026, 3:41 PM UTC
      0 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 America
    Checks passinglatency: 2257msstatus code: 200checked: Nov 5, 2026, 3:37 PM UTC
    0 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.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 2269msstatus code: 200checked: Nov 5, 2026, 3:34 PM UTC
      0 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.
    • UK
      Checks passinglatency: 625msstatus code: 200checked: Nov 5, 2026, 3:35 PM UTC
      0 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 Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 3132msstatus code: 200checked: Nov 5, 2026, 3:17 PM UTC
      0 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 Asia
      Checks passinglatency: 2227msstatus code: 200checked: Nov 5, 2026, 3:36 PM UTC
      0 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.
    • Australia
      Checks passinglatency: 2249msstatus code: 200checked: Nov 5, 2026, 3:37 PM UTC
      0 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

Linkedin.com - Issue, 3h 47mdeclared on their status page2026-09-15
LinkedIn.com Issue, 1mdeclared on their status page2026-08-13
Notification Issue, 1mdeclared on their status page2026-05-21
LinkedIn.com-Issue, 123h 16mdeclared on their status page2026-03-28
Linkedin.com - Issue, 29mdeclared on their status page2025-10-28
Linkedin.com - Issue, 2h 14mdeclared on their status page2025-08-25
Linkedin.com Issue, 36h 31mdeclared on their status page2025-07-28
Sales Navigator - Issue, 5h 32mdeclared on their status page2025-07-10

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

LinkedIn uptime by RealUptime's checksLive, from this page's own readings.
[![LinkedIn uptime by RealUptime's checks](https://realuptime.io/outages/linkedin/badge.svg?days=30)](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>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

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.

What we check

secondaryfunctional
https://api.linkedin.com/v2/me
primary
https://www.linkedin.com/
secondary
https://www.linkedin.com/jobs/
secondary
https://www.linkedin.com/learning/
secondary
https://www.linkedin.com/company/linkedin

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

RealUptime is not affiliated with LinkedIn; the name identifies what we checked, and nothing here speaks for LinkedIn's own team. We send a single web request to LinkedIn from 10 regions on our own schedule and time the response. We do not see inside LinkedIn's systems, do not use an account or real transaction, and are not the same signal LinkedIn's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for LinkedIn is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.