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-18 14:35:00 | 1 | 527 ms | 527 ms | 0 | 0 |
| 2026-11-18 14:40:00 | 1 | 443 ms | 443 ms | 0 | 0 |
| 2026-11-18 14:50:00 | 1 | 500 ms | 500 ms | 0 | 0 |
| 2026-11-18 15:00:00 | 1 | 377 ms | 377 ms | 0 | 0 |
| 2026-11-18 15:05:00 | 1 | 628 ms | 628 ms | 0 | 0 |
| 2026-11-18 15:15:00 | 1 | 744 ms | 744 ms | 0 | 0 |
| 2026-11-18 15:20:00 | 1 | 779 ms | 779 ms | 0 | 0 |
| 2026-11-18 15:30:00 | 1 | 539 ms | 539 ms | 0 | 0 |
| 2026-11-18 15:40:00 | 1 | 621 ms | 621 ms | 0 | 0 |
| 2026-11-18 15:45:00 | 1 | 635 ms | 635 ms | 0 | 0 |
| 2026-11-18 15:55:00 | 1 | 473 ms | 473 ms | 0 | 0 |
| 2026-11-18 16:00:00 | 1 | 445 ms | 445 ms | 0 | 0 |
| 2026-11-18 16:10:00 | 1 | 489 ms | 489 ms | 0 | 0 |
| 2026-11-18 16:20:00 | 1 | 542 ms | 542 ms | 0 | 0 |
| 2026-11-18 16:25:00 | 1 | 696 ms | 696 ms | 0 | 0 |
| 2026-11-18 16:35:00 | 1 | 515 ms | 515 ms | 0 | 0 |
| 2026-11-18 16:40:00 | 1 | 442 ms | 442 ms | 0 | 0 |
| 2026-11-18 16:50:00 | 1 | 537 ms | 537 ms | 0 | 0 |
| 2026-11-18 17:00:00 | 1 | 566 ms | 566 ms | 0 | 0 |
| 2026-11-18 17:05:00 | 1 | 605 ms | 605 ms | 0 | 0 |
| 2026-11-18 17:15:00 | 1 | 531 ms | 531 ms | 0 | 0 |
| 2026-11-18 17:20:00 | 1 | 462 ms | 462 ms | 0 | 0 |
| 2026-11-18 17:30:00 | 1 | 679 ms | 679 ms | 0 | 0 |
| 2026-11-18 17:40:00 | 1 | 698 ms | 698 ms | 0 | 0 |
| 2026-11-18 17:45:00 | 1 | 507 ms | 507 ms | 0 | 0 |
| 2026-11-18 17:55:00 | 1 | 433 ms | 433 ms | 0 | 0 |
| 2026-11-18 18:00:00 | 1 | 481 ms | 481 ms | 0 | 0 |
| 2026-11-18 18:10:00 | 1 | 492 ms | 492 ms | 0 | 0 |
| 2026-11-18 18:20:00 | 1 | 673 ms | 673 ms | 0 | 0 |
| 2026-11-18 18:25:00 | 1 | 430 ms | 430 ms | 0 | 0 |
| 2026-11-18 18:35:00 | 1 | 760 ms | 760 ms | 0 | 0 |
| 2026-11-18 18:40:00 | 1 | 537 ms | 537 ms | 0 | 0 |
| 2026-11-18 18:50:00 | 1 | 404 ms | 404 ms | 0 | 0 |
| 2026-11-18 19:00:00 | 1 | 457 ms | 457 ms | 0 | 0 |
| 2026-11-18 19:05:00 | 1 | 577 ms | 577 ms | 0 | 0 |
| 2026-11-18 19:15:00 | 1 | 625 ms | 625 ms | 0 | 0 |
| 2026-11-18 19:20:00 | 1 | 487 ms | 487 ms | 0 | 0 |
| 2026-11-18 19:30:00 | 1 | 711 ms | 711 ms | 0 | 0 |
| 2026-11-18 19:40:00 | 1 | 527 ms | 527 ms | 0 | 0 |
| 2026-11-18 19:45:00 | 1 | 529 ms | 529 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.