What does reachable from NexIP mean?
The monitored web endpoint returned a successful HTTP response from the NexIP location. This does not guarantee that messaging, calls, login or other features work for every user or region.
Social networks
HTTP-проверка из точки NexIP успешна. Доступность из всех регионов не подтверждена.
The monitored web endpoint returned a successful HTTP response from the NexIP location. This does not guarantee that messaging, calls, login or other features work for every user or region.
Reports over 24 hours, signals over 15 minutes and the outage index measure different periods and conditions. Their values may differ without being contradictory.
Service monitoring
Мониторинг доступности сервиса LinkedIn, пользовательских сигналов и технических проверок NexIP.
Reports submitted to NexIP. One report does not prove a widespread outage.
No reports during this period.
30-minute intervals · Moscow time · actual dataLast 7 days
Observation points
Observation history
Actual NexIP primary probe measurements, not user reports
| Time (server) | Checks | Average | Peak | Down | Blocked |
|---|---|---|---|---|---|
| 2026-11-13 21:00:00 | 22 | 586 ms | 959 ms | 0 | 0 |
| 2026-11-14 00:00:00 | 23 | 525 ms | 661 ms | 0 | 0 |
| 2026-11-14 03:00:00 | 22 | 479 ms | 616 ms | 0 | 0 |
| 2026-11-14 06:00:00 | 23 | 439 ms | 638 ms | 0 | 0 |
| 2026-11-14 09:00:00 | 22 | 750 ms | 5 005 ms | 0 | 0 |
| 2026-11-14 12:00:00 | 23 | 545 ms | 959 ms | 0 | 0 |
| 2026-11-14 15:00:00 | 22 | 642 ms | 3 019 ms | 0 | 0 |
| 2026-11-14 18:00:00 | 23 | 602 ms | 1 003 ms | 0 | 0 |
| 2026-11-14 21:00:00 | 22 | 524 ms | 744 ms | 0 | 0 |
| 2026-11-15 00:00:00 | 23 | 473 ms | 884 ms | 0 | 0 |
| 2026-11-15 03:00:00 | 22 | 666 ms | 5 004 ms | 0 | 0 |
| 2026-11-15 06:00:00 | 22 | 445 ms | 585 ms | 0 | 0 |
| 2026-11-15 09:00:00 | 23 | 488 ms | 752 ms | 0 | 0 |
| 2026-11-15 12:00:00 | 22 | 558 ms | 873 ms | 0 | 0 |
| 2026-11-15 15:00:00 | 23 | 558 ms | 838 ms | 0 | 0 |
| 2026-11-15 18:00:00 | 22 | 490 ms | 662 ms | 0 | 0 |
| 2026-11-15 21:00:00 | 23 | 485 ms | 710 ms | 0 | 0 |
| 2026-11-16 00:00:00 | 22 | 662 ms | 5 005 ms | 0 | 0 |
| 2026-11-16 03:00:00 | 23 | 455 ms | 564 ms | 0 | 0 |
| 2026-11-16 06:00:00 | 22 | 464 ms | 621 ms | 0 | 0 |
| 2026-11-16 09:00:00 | 23 | 480 ms | 682 ms | 0 | 0 |
| 2026-11-16 12:00:00 | 23 | 550 ms | 764 ms | 0 | 0 |
| 2026-11-16 15:00:00 | 22 | 549 ms | 793 ms | 0 | 0 |
| 2026-11-16 18:00:00 | 23 | 795 ms | 5 006 ms | 0 | 0 |
| 2026-11-16 21:00:00 | 23 | 534 ms | 726 ms | 0 | 0 |
| 2026-11-17 00:00:00 | 22 | 711 ms | 5 005 ms | 0 | 0 |
| 2026-11-17 03:00:00 | 23 | 468 ms | 672 ms | 0 | 0 |
| 2026-11-17 06:00:00 | 23 | 528 ms | 1 034 ms | 0 | 0 |
| 2026-11-17 09:00:00 | 23 | 521 ms | 701 ms | 0 | 0 |
| 2026-11-17 12:00:00 | 23 | 762 ms | 5 005 ms | 0 | 0 |
| 2026-11-17 15:00:00 | 22 | 613 ms | 1 042 ms | 0 | 0 |
| 2026-11-17 18:00:00 | 22 | 535 ms | 766 ms | 0 | 0 |
| 2026-11-17 21:00:00 | 23 | 515 ms | 790 ms | 0 | 0 |
| 2026-11-18 00:00:00 | 22 | 475 ms | 636 ms | 0 | 0 |
| 2026-11-18 03:00:00 | 23 | 889 ms | 5 005 ms | 0 | 0 |
| 2026-11-18 06:00:00 | 23 | 475 ms | 680 ms | 0 | 0 |
| 2026-11-18 09:00:00 | 23 | 531 ms | 811 ms | 0 | 0 |
| 2026-11-18 12:00:00 | 22 | 585 ms | 868 ms | 0 | 0 |
| 2026-11-18 15:00:00 | 23 | 563 ms | 779 ms | 0 | 0 |
| 2026-11-18 18:00:00 | 14 | 549 ms | 760 ms | 0 | 0 |
Success is up or degraded among recorded primary probe checks. This is not a public uptime SLA. Available history can be shorter than the selected range.
Your signal
Tell us. Registration is not required. The same signal will not be counted repeatedly within a short period.
User opinions are separate from the technical outage status.
No ratings yet
No comments yet.
This page tracks the current observed status of LinkedIn, recent incidents, automated availability checks and available user reports. NexIP does not treat a single failed check as proof of a global outage.
Ping · Website availability · Website monitoring · All service outages
NexIP shows the current observed status of LinkedIn using automated checks, incident data and available user signals. A local connection problem may differ from a large-scale outage.
Availability can differ by provider, region, DNS, routing, application version or service component. NexIP therefore separates observed signals from confirmed large-scale incidents.
Check the host with Ping, website availability and your own connection. Comparing several independent checks helps distinguish a local problem from a wider outage.