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-17 04:00:00 | 7 | 471 ms | 571 ms | 0 | 0 |
| 2026-11-17 05:00:00 | 8 | 487 ms | 672 ms | 0 | 0 |
| 2026-11-17 06:00:00 | 7 | 445 ms | 586 ms | 0 | 0 |
| 2026-11-17 07:00:00 | 8 | 516 ms | 637 ms | 0 | 0 |
| 2026-11-17 08:00:00 | 8 | 613 ms | 1 034 ms | 0 | 0 |
| 2026-11-17 09:00:00 | 8 | 451 ms | 585 ms | 0 | 0 |
| 2026-11-17 10:00:00 | 8 | 550 ms | 640 ms | 0 | 0 |
| 2026-11-17 11:00:00 | 7 | 566 ms | 701 ms | 0 | 0 |
| 2026-11-17 12:00:00 | 8 | 1 185 ms | 5 005 ms | 0 | 0 |
| 2026-11-17 13:00:00 | 7 | 500 ms | 538 ms | 0 | 0 |
| 2026-11-17 14:00:00 | 8 | 569 ms | 711 ms | 0 | 0 |
| 2026-11-17 15:00:00 | 7 | 604 ms | 909 ms | 0 | 0 |
| 2026-11-17 16:00:00 | 8 | 684 ms | 1 042 ms | 0 | 0 |
| 2026-11-17 17:00:00 | 7 | 541 ms | 706 ms | 0 | 0 |
| 2026-11-17 18:00:00 | 8 | 532 ms | 743 ms | 0 | 0 |
| 2026-11-17 19:00:00 | 7 | 545 ms | 766 ms | 0 | 0 |
| 2026-11-17 20:00:00 | 7 | 528 ms | 757 ms | 0 | 0 |
| 2026-11-17 21:00:00 | 8 | 591 ms | 790 ms | 0 | 0 |
| 2026-11-17 22:00:00 | 7 | 463 ms | 504 ms | 0 | 0 |
| 2026-11-17 23:00:00 | 8 | 483 ms | 583 ms | 0 | 0 |
| 2026-11-18 00:00:00 | 7 | 420 ms | 524 ms | 0 | 0 |
| 2026-11-18 01:00:00 | 8 | 504 ms | 620 ms | 0 | 0 |
| 2026-11-18 02:00:00 | 7 | 496 ms | 636 ms | 0 | 0 |
| 2026-11-18 03:00:00 | 8 | 1 037 ms | 5 005 ms | 0 | 0 |
| 2026-11-18 04:00:00 | 7 | 1 189 ms | 5 005 ms | 0 | 0 |
| 2026-11-18 05:00:00 | 8 | 477 ms | 635 ms | 0 | 0 |
| 2026-11-18 06:00:00 | 8 | 439 ms | 597 ms | 0 | 0 |
| 2026-11-18 07:00:00 | 7 | 475 ms | 616 ms | 0 | 0 |
| 2026-11-18 08:00:00 | 8 | 512 ms | 680 ms | 0 | 0 |
| 2026-11-18 09:00:00 | 8 | 512 ms | 639 ms | 0 | 0 |
| 2026-11-18 10:00:00 | 7 | 528 ms | 811 ms | 0 | 0 |
| 2026-11-18 11:00:00 | 8 | 553 ms | 742 ms | 0 | 0 |
| 2026-11-18 12:00:00 | 7 | 597 ms | 772 ms | 0 | 0 |
| 2026-11-18 13:00:00 | 8 | 601 ms | 868 ms | 0 | 0 |
| 2026-11-18 14:00:00 | 7 | 555 ms | 745 ms | 0 | 0 |
| 2026-11-18 15:00:00 | 8 | 600 ms | 779 ms | 0 | 0 |
| 2026-11-18 16:00:00 | 7 | 524 ms | 696 ms | 0 | 0 |
| 2026-11-18 17:00:00 | 8 | 560 ms | 698 ms | 0 | 0 |
| 2026-11-18 18:00:00 | 7 | 540 ms | 760 ms | 0 | 0 |
| 2026-11-18 19:00:00 | 7 | 559 ms | 711 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.