Skip to content

Outage tracker / LinkedIn

Is LinkedIn down?

I'm having a problem

Operationalchecked 1 minute ago

We reached LinkedIn from all 10 regions we check.

As of Oct 5, 2026, 8:15 PM UTC, LinkedIn answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 46 days we have measured LinkedIn (since Aug 20, 2026).

Email me the next time we see LinkedIn go down

Measured by our own probes from ten regions, not LinkedIn's status page. One email when a measured outage opens and one when it closes, after you confirm the address. No account, no card.

our independent probeslive · checked Oct 5, 2026, 8:15 PM UTC
US-East372 msOperational
US-West424 msOperational
Europe455 msOperational
Asia-Pacific963 msOperational
US-Central353 msOperational
Canada437 msOperational
UK375 msOperational
Southeast Asia946 msOperational
Australia1416 msOperational
South America735 msOperational
their status pagetheir claim, not our reading

LinkedIn publishes no status feed we can read, so the only independent reading here is ours on the left.

LinkedIn response time, by region

US-East
599msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 800ms2026-09-07 UTC: p95 891ms2026-09-08 UTC: p95 815ms2026-09-09 UTC: p95 817ms2026-09-10 UTC: p95 839ms2026-09-11 UTC: p95 844ms2026-09-12 UTC: p95 856ms2026-09-13 UTC: p95 789ms2026-09-14 UTC: p95 683ms2026-09-15 UTC: p95 542ms2026-09-16 UTC: p95 629ms2026-09-17 UTC: p95 627ms2026-09-18 UTC: p95 478ms2026-09-19 UTC: p95 463ms2026-09-20 UTC: p95 713ms2026-09-21 UTC: p95 574ms2026-09-22 UTC: p95 547ms2026-09-23 UTC: p95 983ms2026-09-24 UTC: p95 1.0s2026-09-25 UTC: p95 536ms2026-09-26 UTC: p95 724ms2026-09-27 UTC: p95 418ms2026-09-28 UTC: p95 390ms2026-09-29 UTC: p95 406ms2026-09-30 UTC: p95 521ms2026-10-01 UTC: p95 869ms2026-10-02 UTC: p95 664ms2026-10-03 UTC: p95 578ms2026-10-04 UTC: p95 612ms2026-10-05 UTC: p95 599ms
Sep 6Sep 20Oct 5
US-West
629msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 981ms2026-09-07 UTC: p95 665ms2026-09-08 UTC: p95 767ms2026-09-09 UTC: p95 530ms2026-09-10 UTC: p95 516ms2026-09-11 UTC: p95 530ms2026-09-12 UTC: p95 304ms2026-09-13 UTC: p95 237ms2026-09-14 UTC: p95 281ms2026-09-15 UTC: p95 753ms2026-09-16 UTC: p95 795ms2026-09-17 UTC: p95 803ms2026-09-18 UTC: p95 655ms2026-09-19 UTC: p95 738ms2026-09-20 UTC: p95 713ms2026-09-21 UTC: p95 713ms2026-09-22 UTC: p95 750ms2026-09-23 UTC: p95 603ms2026-09-24 UTC: p95 560ms2026-09-25 UTC: p95 664ms2026-09-26 UTC: p95 686ms2026-09-27 UTC: p95 415ms2026-09-28 UTC: p95 580ms2026-09-29 UTC: p95 568ms2026-09-30 UTC: p95 816ms2026-10-01 UTC: p95 718ms2026-10-02 UTC: p95 655ms2026-10-03 UTC: p95 860ms2026-10-04 UTC: p95 586ms2026-10-05 UTC: p95 629ms
Sep 6Sep 20Oct 5
Europe
641msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 430ms2026-09-07 UTC: p95 416ms2026-09-08 UTC: p95 434ms2026-09-09 UTC: p95 473ms2026-09-10 UTC: p95 402ms2026-09-11 UTC: p95 389ms2026-09-12 UTC: p95 387ms2026-09-13 UTC: p95 394ms2026-09-14 UTC: p95 709ms2026-09-15 UTC: p95 768ms2026-09-16 UTC: p95 555ms2026-09-17 UTC: p95 682ms2026-09-18 UTC: p95 656ms2026-09-19 UTC: p95 623ms2026-09-20 UTC: p95 624ms2026-09-21 UTC: p95 660ms2026-09-22 UTC: p95 593ms2026-09-23 UTC: p95 550ms2026-09-24 UTC: p95 652ms2026-09-25 UTC: p95 688ms2026-09-26 UTC: p95 627ms2026-09-27 UTC: p95 642ms2026-09-28 UTC: p95 580ms2026-09-29 UTC: p95 667ms2026-09-30 UTC: p95 601ms2026-10-01 UTC: p95 813ms2026-10-02 UTC: p95 870ms2026-10-03 UTC: p95 709ms2026-10-04 UTC: p95 694ms2026-10-05 UTC: p95 641ms
Sep 6Sep 20Oct 5
Asia-Pacific
1.2sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 934ms2026-09-07 UTC: p95 996ms2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 1.4s2026-09-10 UTC: p95 1.2s2026-09-11 UTC: p95 1.4s2026-09-12 UTC: p95 1.3s2026-09-13 UTC: p95 701ms2026-09-14 UTC: p95 773ms2026-09-15 UTC: p95 982ms2026-09-16 UTC: p95 966ms2026-09-17 UTC: p95 1.2s2026-09-18 UTC: p95 1.3s2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 959ms2026-09-21 UTC: p95 1.2s2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 1.0s2026-09-24 UTC: p95 1.3s2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 1.4s2026-09-27 UTC: p95 1.5s2026-09-28 UTC: p95 1.5s2026-09-29 UTC: p95 1.4s2026-09-30 UTC: p95 1.5s2026-10-01 UTC: p95 1.5s2026-10-02 UTC: p95 1.5s2026-10-03 UTC: p95 1.4s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.2s
Sep 6Sep 20Oct 5
US-Central
562msp95 · 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-09-06 UTC: p95 726ms2026-09-07 UTC: p95 1.0s2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 900ms2026-09-10 UTC: p95 717ms2026-09-11 UTC: p95 747ms2026-09-12 UTC: p95 565ms2026-09-13 UTC: p95 829ms2026-09-14 UTC: p95 1.1s2026-09-15 UTC: p95 581ms2026-09-16 UTC: p95 435ms2026-09-17 UTC: p95 387ms2026-09-18 UTC: p95 324ms2026-09-19 UTC: p95 685ms2026-09-20 UTC: p95 638ms2026-09-21 UTC: p95 710ms2026-09-22 UTC: p95 617ms2026-09-23 UTC: p95 657ms2026-09-24 UTC: p95 612ms2026-09-25 UTC: p95 521ms2026-09-26 UTC: p95 638ms2026-09-27 UTC: p95 775ms2026-09-28 UTC: p95 654ms2026-09-29 UTC: p95 630ms2026-09-30 UTC: p95 647ms2026-10-01 UTC: p95 740ms2026-10-02 UTC: p95 712ms2026-10-03 UTC: p95 699ms2026-10-04 UTC: p95 739ms2026-10-05 UTC: p95 562ms
Sep 6Sep 20Oct 5
Canada
876msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 627ms2026-09-07 UTC: p95 565ms2026-09-08 UTC: p95 618ms2026-09-09 UTC: p95 674ms2026-09-10 UTC: p95 614ms2026-09-11 UTC: p95 644ms2026-09-12 UTC: p95 551ms2026-09-13 UTC: p95 558ms2026-09-14 UTC: p95 567ms2026-09-15 UTC: p95 679ms2026-09-16 UTC: p95 650ms2026-09-17 UTC: p95 635ms2026-09-18 UTC: p95 566ms2026-09-19 UTC: p95 606ms2026-09-20 UTC: p95 558ms2026-09-21 UTC: p95 615ms2026-09-22 UTC: p95 640ms2026-09-23 UTC: p95 761ms2026-09-24 UTC: p95 975ms2026-09-25 UTC: p95 768ms2026-09-26 UTC: p95 608ms2026-09-27 UTC: p95 679ms2026-09-28 UTC: p95 636ms2026-09-29 UTC: p95 664ms2026-09-30 UTC: p95 647ms2026-10-01 UTC: p95 724ms2026-10-02 UTC: p95 724ms2026-10-03 UTC: p95 778ms2026-10-04 UTC: p95 836ms2026-10-05 UTC: p95 876ms
Sep 6Sep 20Oct 5
UK
610msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 406ms2026-09-07 UTC: p95 438ms2026-09-08 UTC: p95 400ms2026-09-09 UTC: p95 368ms2026-09-10 UTC: p95 331ms2026-09-11 UTC: p95 344ms2026-09-12 UTC: p95 370ms2026-09-13 UTC: p95 479ms2026-09-14 UTC: p95 613ms2026-09-15 UTC: p95 614ms2026-09-16 UTC: p95 672ms2026-09-17 UTC: p95 821ms2026-09-18 UTC: p95 504ms2026-09-19 UTC: p95 521ms2026-09-20 UTC: p95 523ms2026-09-21 UTC: p95 516ms2026-09-22 UTC: p95 595ms2026-09-23 UTC: p95 570ms2026-09-24 UTC: p95 639ms2026-09-25 UTC: p95 636ms2026-09-26 UTC: p95 494ms2026-09-27 UTC: p95 648ms2026-09-28 UTC: p95 621ms2026-09-29 UTC: p95 586ms2026-09-30 UTC: p95 693ms2026-10-01 UTC: p95 542ms2026-10-02 UTC: p95 668ms2026-10-03 UTC: p95 700ms2026-10-04 UTC: p95 822ms2026-10-05 UTC: p95 610ms
Sep 6Sep 20Oct 5
Southeast Asia
1.4sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.6s2026-09-07 UTC: p95 1.7s2026-09-08 UTC: p95 1.4s2026-09-09 UTC: p95 1.4s2026-09-10 UTC: p95 1.6s2026-09-11 UTC: p95 1.3s2026-09-12 UTC: p95 1.4s2026-09-13 UTC: p95 1.6s2026-09-14 UTC: p95 1.5s2026-09-15 UTC: p95 1.4s2026-09-16 UTC: p95 1.6s2026-09-17 UTC: p95 1.5s2026-09-18 UTC: p95 1.7s2026-09-19 UTC: p95 1.6s2026-09-20 UTC: p95 1.6s2026-09-21 UTC: p95 2.1s2026-09-22 UTC: p95 1.9s2026-09-23 UTC: p95 2.2s2026-09-24 UTC: p95 1.7s2026-09-25 UTC: p95 1.9s2026-09-26 UTC: p95 1.9s2026-09-27 UTC: p95 1.5s2026-09-28 UTC: p95 1.4s2026-09-29 UTC: p95 1.5s2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.5s2026-10-03 UTC: p95 1.5s2026-10-04 UTC: p95 1.5s2026-10-05 UTC: p95 1.4s
Sep 6Sep 20Oct 5
Australia
1.9sp95 · 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-09-06 UTC: p95 1.4s2026-09-07 UTC: p95 1.6s2026-09-08 UTC: p95 1.6s2026-09-09 UTC: p95 1.7s2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 1.7s2026-09-12 UTC: p95 1.7s2026-09-13 UTC: p95 1.9s2026-09-14 UTC: p95 1.7s2026-09-15 UTC: p95 1.3s2026-09-16 UTC: p95 1.5s2026-09-17 UTC: p95 1.5s2026-09-18 UTC: p95 1.2s2026-09-19 UTC: p95 1.6s2026-09-20 UTC: p95 1.8s2026-09-21 UTC: p95 1.8s2026-09-22 UTC: p95 1.6s2026-09-23 UTC: p95 1.6s2026-09-24 UTC: p95 1.6s2026-09-25 UTC: p95 1.8s2026-09-26 UTC: p95 1.7s2026-09-27 UTC: p95 1.5s2026-09-28 UTC: p95 1.4s2026-09-29 UTC: p95 1.5s2026-09-30 UTC: p95 1.7s2026-10-01 UTC: p95 2.5s2026-10-02 UTC: p95 2.9s2026-10-03 UTC: p95 1.8s2026-10-04 UTC: p95 2.0s2026-10-05 UTC: p95 1.9s
Sep 6Sep 20Oct 5
South America
1.4sp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.0s2026-09-07 UTC: p95 1.4s2026-09-08 UTC: p95 1.6s2026-09-09 UTC: p95 1.0s2026-09-10 UTC: p95 1.4s2026-09-11 UTC: p95 1.4s2026-09-12 UTC: p95 1.2s2026-09-13 UTC: p95 1.4s2026-09-14 UTC: p95 1.3s2026-09-15 UTC: p95 1.3s2026-09-16 UTC: p95 835ms2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 1.0s2026-09-19 UTC: p95 1.2s2026-09-20 UTC: p95 964ms2026-09-21 UTC: p95 958ms2026-09-22 UTC: p95 881ms2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 1.2s2026-09-27 UTC: p95 1.4s2026-09-28 UTC: p95 1.3s2026-09-29 UTC: p95 1.0s2026-09-30 UTC: p95 1.3s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.3s2026-10-03 UTC: p95 1.7s2026-10-04 UTC: p95 1.5s2026-10-05 UTC: p95 1.4s
Sep 6Sep 20Oct 5

Is it LinkedIn, or is it you?

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 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 we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 372msstatus code: 200checked: Oct 5, 2026, 8:09 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
      Operationallatency: 424msstatus code: 200checked: Oct 5, 2026, 8:08 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
      Operationallatency: 353msstatus code: 200checked: Oct 5, 2026, 8:06 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
      Operationallatency: 437msstatus code: 200checked: Oct 5, 2026, 8:00 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
    Operationallatency: 735msstatus code: 200checked: Oct 5, 2026, 8:06 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 455msstatus code: 200checked: Oct 5, 2026, 8:10 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
      Operationallatency: 375msstatus code: 200checked: Oct 5, 2026, 8:09 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 963msstatus code: 200checked: Oct 5, 2026, 8:15 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
      Operationallatency: 946msstatus code: 200checked: Oct 5, 2026, 7:58 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
      Operationallatency: 1416msstatus code: 200checked: Oct 5, 2026, 7:59 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 outages

No outages on record yet for LinkedIn.

measured 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 measurements and LinkedIn's own claim at the time, side by side.

Full availability history for LinkedIn: 90-day availability by region, month-by-month uptime, and every incident on record.

Put this badge in your README

LinkedIn uptime measured by RealUptimeLive, from this page's own readings.
[![LinkedIn uptime measured by RealUptime](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 measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and 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: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What LinkedIn's SLA implies, from our measurement

At or above your target

We measured none of downtime for LinkedIn over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from LinkedIn's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

secondaryfunctional
https://api.linkedin.com/v2/me
primary
https://www.linkedin.com/
RealUptime is not affiliated with LinkedIn; the name identifies what we measured, 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 clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.