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.
Cloud services
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
Мониторинг доступности сервиса GitHub, пользовательских сигналов и технических проверок 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 | 571 ms | 1 137 ms | 0 | 0 |
| 2026-11-14 00:00:00 | 23 | 553 ms | 836 ms | 0 | 0 |
| 2026-11-14 03:00:00 | 22 | 550 ms | 1 126 ms | 0 | 0 |
| 2026-11-14 06:00:00 | 23 | 578 ms | 1 467 ms | 0 | 0 |
| 2026-11-14 09:00:00 | 22 | 530 ms | 569 ms | 0 | 0 |
| 2026-11-14 12:00:00 | 23 | 556 ms | 728 ms | 0 | 0 |
| 2026-11-14 15:00:00 | 22 | 587 ms | 1 546 ms | 0 | 0 |
| 2026-11-14 18:00:00 | 23 | 597 ms | 1 710 ms | 0 | 0 |
| 2026-11-14 21:00:00 | 22 | 580 ms | 1 031 ms | 0 | 0 |
| 2026-11-15 00:00:00 | 23 | 569 ms | 1 279 ms | 0 | 0 |
| 2026-11-15 03:00:00 | 22 | 571 ms | 939 ms | 0 | 0 |
| 2026-11-15 06:00:00 | 22 | 621 ms | 1 206 ms | 0 | 0 |
| 2026-11-15 09:00:00 | 23 | 634 ms | 1 528 ms | 0 | 0 |
| 2026-11-15 12:00:00 | 22 | 623 ms | 1 696 ms | 0 | 0 |
| 2026-11-15 15:00:00 | 23 | 704 ms | 2 001 ms | 0 | 0 |
| 2026-11-15 18:00:00 | 22 | 934 ms | 8 002 ms | 0 | 0 |
| 2026-11-15 21:00:00 | 23 | 679 ms | 1 880 ms | 0 | 0 |
| 2026-11-16 00:00:00 | 22 | 586 ms | 1 228 ms | 0 | 0 |
| 2026-11-16 03:00:00 | 23 | 663 ms | 1 974 ms | 0 | 0 |
| 2026-11-16 06:00:00 | 22 | 611 ms | 1 213 ms | 0 | 0 |
| 2026-11-16 09:00:00 | 23 | 651 ms | 1 335 ms | 0 | 0 |
| 2026-11-16 12:00:00 | 23 | 657 ms | 1 252 ms | 0 | 0 |
| 2026-11-16 15:00:00 | 22 | 629 ms | 1 732 ms | 0 | 0 |
| 2026-11-16 18:00:00 | 23 | 593 ms | 1 245 ms | 0 | 0 |
| 2026-11-16 21:00:00 | 23 | 561 ms | 1 114 ms | 0 | 0 |
| 2026-11-17 00:00:00 | 22 | 538 ms | 755 ms | 0 | 0 |
| 2026-11-17 03:00:00 | 23 | 508 ms | 588 ms | 0 | 0 |
| 2026-11-17 06:00:00 | 23 | 544 ms | 1 234 ms | 0 | 0 |
| 2026-11-17 09:00:00 | 23 | 796 ms | 5 004 ms | 0 | 0 |
| 2026-11-17 12:00:00 | 23 | 523 ms | 552 ms | 0 | 0 |
| 2026-11-17 15:00:00 | 22 | 519 ms | 594 ms | 0 | 0 |
| 2026-11-17 18:00:00 | 22 | 1 478 ms | 8 002 ms | 0 | 0 |
| 2026-11-17 21:00:00 | 23 | 936 ms | 7 245 ms | 0 | 0 |
| 2026-11-18 00:00:00 | 22 | 523 ms | 567 ms | 0 | 0 |
| 2026-11-18 03:00:00 | 23 | 510 ms | 571 ms | 0 | 0 |
| 2026-11-18 06:00:00 | 23 | 531 ms | 569 ms | 0 | 0 |
| 2026-11-18 09:00:00 | 23 | 541 ms | 613 ms | 0 | 0 |
| 2026-11-18 12:00:00 | 22 | 579 ms | 1 533 ms | 0 | 0 |
| 2026-11-18 15:00:00 | 23 | 1 157 ms | 8 003 ms | 0 | 0 |
| 2026-11-18 18:00:00 | 14 | 1 278 ms | 8 003 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 GitHub, 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 GitHub 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.