Copied!
Sign In
Access your IPWhois.net account
No account? Create one

Is It Down? linkedin.com

Favicon linkedin.com
https://linkedin.com · UP · DownDetector

Host: linkedin.com Server: Frankfurt, DE Timezone: America/New_York History: 20 / 20 checks Site is UP
Live monitoring · last checked 20:53:49
60
sec until next refresh
UP
Current
200
HTTP Code
533
Response ms
100%
Uptime (20)
4
Outages

Response Time Last 20 Checks

UP    DOWN

Recent Checks (Last 20 Pings)

Time (America/New_York) Status HTTP Code Response (ms)
20:53:49 · 12.05.2026 UP 200 533
20:40:05 · 12.05.2026 UP 200 492
20:20:07 · 12.05.2026 UP 200 495
20:00:07 · 12.05.2026 UP 200 413
19:40:05 · 12.05.2026 UP 200 567
19:20:06 · 12.05.2026 UP 200 467
19:00:06 · 12.05.2026 UP 200 405
18:40:06 · 12.05.2026 UP 200 466
18:20:07 · 12.05.2026 UP 200 415
18:00:07 · 12.05.2026 UP 200 428
17:40:06 · 12.05.2026 UP 200 491
17:20:07 · 12.05.2026 UP 200 428
17:00:07 · 12.05.2026 UP 200 470
16:40:06 · 12.05.2026 UP 200 473
16:20:07 · 12.05.2026 UP 200 483
16:00:07 · 12.05.2026 UP 200 432
15:40:06 · 12.05.2026 UP 200 484
15:20:06 · 12.05.2026 UP 200 446
15:00:10 · 12.05.2026 UP 200 453
14:40:06 · 12.05.2026 UP 200 446
20:53:49
12.05.2026
UP  HTTP 200  · 533ms
20:40:05
12.05.2026
UP  HTTP 200  · 492ms
20:20:07
12.05.2026
UP  HTTP 200  · 495ms
20:00:07
12.05.2026
UP  HTTP 200  · 413ms
19:40:05
12.05.2026
UP  HTTP 200  · 567ms
19:20:06
12.05.2026
UP  HTTP 200  · 467ms
19:00:06
12.05.2026
UP  HTTP 200  · 405ms
18:40:06
12.05.2026
UP  HTTP 200  · 466ms
18:20:07
12.05.2026
UP  HTTP 200  · 415ms
18:00:07
12.05.2026
UP  HTTP 200  · 428ms
17:40:06
12.05.2026
UP  HTTP 200  · 491ms
17:20:07
12.05.2026
UP  HTTP 200  · 428ms
17:00:07
12.05.2026
UP  HTTP 200  · 470ms
16:40:06
12.05.2026
UP  HTTP 200  · 473ms
16:20:07
12.05.2026
UP  HTTP 200  · 483ms
16:00:07
12.05.2026
UP  HTTP 200  · 432ms
15:40:06
12.05.2026
UP  HTTP 200  · 484ms
15:20:06
12.05.2026
UP  HTTP 200  · 446ms
15:00:10
12.05.2026
UP  HTTP 200  · 453ms
14:40:06
12.05.2026
UP  HTTP 200  · 446ms

Last Detected Downtime

Detected at 2026-05-07 06:40:06  ·  HTTP 429  ·  281ms

All Recorded Outages

Time (America/New_York)HTTPResponse (ms)Error
2026-05-07 06:40:06 429 281
2026-05-04 17:00:06 429 566
2026-04-15 18:00:08 429 439
2026-04-10 05:20:06 429 1101
06:40:06
07.05.2026
DOWN  HTTP 429  · 281ms
17:00:06
04.05.2026
DOWN  HTTP 429  · 566ms
18:00:08
15.04.2026
DOWN  HTTP 429  · 439ms
05:20:06
10.04.2026
DOWN  HTTP 429  · 1101ms

Recently Checked Sites

WebsiteStatusHTTPResponseUptime
DOWN 6001 ms
0%
DOWN 42 ms
0%
UP 200 602 ms
87.5%
UP 200 60 ms
100%
DOWN 406 461 ms
0%
UP 200 4487 ms
100%
UP 200 46 ms
100%
UP 200 145 ms
100%
UP 200 332 ms
15%
UP 200 85 ms
100%
6001ms
DOWN  HTTP · 0%
42ms
DOWN  HTTP · 0%
602ms
UP  HTTP 200 · 87.5%
60ms
UP  HTTP 200 · 100%
461ms
DOWN  HTTP 406 · 0%
4487ms
UP  HTTP 200 · 100%
46ms
UP  HTTP 200 · 100%
145ms
UP  HTTP 200 · 100%
332ms
UP  HTTP 200 · 15%
85ms
UP  HTTP 200 · 100%

About This Check

We send an HTTP HEAD request from our Frankfurt, Germany server to linkedin.com. A response of HTTP 200–399 within 10 seconds = UP. Any timeout, DNS failure, or error code = DOWN. A rolling history of the last 20 checks is stored and displayed above.

If the site shows UP here but you can't access it, the issue is local flush your DNS cache (ipconfig /flushdns on Windows / sudo dscacheutil -flushcache on macOS) or try a different network.

For community-reported outage data and user comments, check DownDetector linkedin.com.