Skip to content

Outage tracker / LinkedIn

Is LinkedIn down?

I'm having a problem

Operationalchecked 21 minutes ago

We reached LinkedIn from all 4 regions we check.

Functional endpoints verified

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

our independent probeslive · checked Sep 3, 2026, 1:08 AM UTC
US-East656 msOperational
US-West1144 msOperational
Europe192 msOperational
Asia-Pacific1141 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
646msp95 · 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-08-20 UTC: p95 1.1s2026-08-21 UTC: p95 1.0s2026-08-22 UTC: p95 973ms2026-08-23 UTC: p95 997ms2026-08-24 UTC: p95 1.1s2026-08-25 UTC: p95 1.6s2026-08-26 UTC: p95 1.1s2026-08-27 UTC: p95 955ms2026-08-28 UTC: p95 1.1s2026-08-29 UTC: p95 970ms2026-08-30 UTC: p95 943ms2026-08-31 UTC: p95 844ms2026-09-01 UTC: p95 913ms2026-09-02 UTC: p95 819ms2026-09-03 UTC: p95 646ms
Aug 5Aug 19Sep 3
US-West
1.1sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 438ms2026-08-21 UTC: p95 508ms2026-08-22 UTC: p95 412ms2026-08-23 UTC: p95 555ms2026-08-24 UTC: p95 390ms2026-08-25 UTC: p95 369ms2026-08-26 UTC: p95 456ms2026-08-27 UTC: p95 480ms2026-08-28 UTC: p95 465ms2026-08-29 UTC: p95 676ms2026-08-30 UTC: p95 437ms2026-08-31 UTC: p95 677ms2026-09-01 UTC: p95 380ms2026-09-02 UTC: p95 417ms2026-09-03 UTC: p95 1.1s
Aug 5Aug 19Sep 3
Europe
308msp95 · 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-08-20 UTC: p95 426ms2026-08-21 UTC: p95 506ms2026-08-22 UTC: p95 432ms2026-08-23 UTC: p95 637ms2026-08-24 UTC: p95 774ms2026-08-25 UTC: p95 715ms2026-08-26 UTC: p95 594ms2026-08-27 UTC: p95 630ms2026-08-28 UTC: p95 483ms2026-08-29 UTC: p95 474ms2026-08-30 UTC: p95 643ms2026-08-31 UTC: p95 530ms2026-09-01 UTC: p95 550ms2026-09-02 UTC: p95 675ms2026-09-03 UTC: p95 308ms
Aug 5Aug 19Sep 3
Asia-Pacific
1.0sp95 · 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-08-20 UTC: p95 1.0s2026-08-21 UTC: p95 983ms2026-08-22 UTC: p95 824ms2026-08-23 UTC: p95 1.0s2026-08-24 UTC: p95 1.0s2026-08-25 UTC: p95 1.0s2026-08-26 UTC: p95 1.1s2026-08-27 UTC: p95 1.2s2026-08-28 UTC: p95 1.2s2026-08-29 UTC: p95 1.0s2026-08-30 UTC: p95 1.0s2026-08-31 UTC: p95 1.2s2026-09-01 UTC: p95 1.1s2026-09-02 UTC: p95 1.3s2026-09-03 UTC: p95 1.0s
Aug 5Aug 19Sep 3

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

  • US-East
    Operationallatency: 656msstatus code: 401checked: Sep 3, 2026, 1:04 AM 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: 1144msstatus code: 401checked: Sep 3, 2026, 1:03 AM 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.
  • Europe
    Operationallatency: 192msstatus code: 401checked: Sep 3, 2026, 1:08 AM 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.
  • Asia-Pacific
    Operationallatency: 1141msstatus code: 401checked: Sep 3, 2026, 1:01 AM 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.
  • US-Central
    Not monitored from this regionLinkedIn is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Canada
    Not monitored from this regionLinkedIn is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • UK
    Not monitored from this regionLinkedIn is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Southeast Asia
    Not monitored from this regionLinkedIn is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Australia
    Not monitored from this regionLinkedIn is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionLinkedIn is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say

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.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching LinkedIn, and again when they can reach it again. That is our own measurement from ten regions, not LinkedIn's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

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 337h 29m since we started watching it on 2026-08-20, which is 100% uptime by our reading. A 99.9% target allows 20 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

primaryfunctional
https://api.linkedin.com/v2/me
secondary
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 4 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. LinkedIn operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. Read the full methodology.