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-17 04:00:00 | 7 | 509 ms | 588 ms | 0 | 0 |
| 2026-11-17 05:00:00 | 8 | 506 ms | 535 ms | 0 | 0 |
| 2026-11-17 06:00:00 | 7 | 613 ms | 1 234 ms | 0 | 0 |
| 2026-11-17 07:00:00 | 8 | 529 ms | 569 ms | 0 | 0 |
| 2026-11-17 08:00:00 | 8 | 499 ms | 545 ms | 0 | 0 |
| 2026-11-17 09:00:00 | 8 | 547 ms | 667 ms | 0 | 0 |
| 2026-11-17 10:00:00 | 8 | 1 152 ms | 5 004 ms | 0 | 0 |
| 2026-11-17 11:00:00 | 7 | 675 ms | 1 574 ms | 0 | 0 |
| 2026-11-17 12:00:00 | 8 | 514 ms | 530 ms | 0 | 0 |
| 2026-11-17 13:00:00 | 7 | 531 ms | 552 ms | 0 | 0 |
| 2026-11-17 14:00:00 | 8 | 526 ms | 550 ms | 0 | 0 |
| 2026-11-17 15:00:00 | 7 | 526 ms | 594 ms | 0 | 0 |
| 2026-11-17 16:00:00 | 8 | 514 ms | 533 ms | 0 | 0 |
| 2026-11-17 17:00:00 | 7 | 516 ms | 553 ms | 0 | 0 |
| 2026-11-17 18:00:00 | 8 | 614 ms | 1 220 ms | 0 | 0 |
| 2026-11-17 19:00:00 | 7 | 2 503 ms | 8 002 ms | 0 | 0 |
| 2026-11-17 20:00:00 | 7 | 1 442 ms | 6 025 ms | 0 | 0 |
| 2026-11-17 21:00:00 | 8 | 1 612 ms | 7 245 ms | 0 | 0 |
| 2026-11-17 22:00:00 | 7 | 644 ms | 925 ms | 0 | 0 |
| 2026-11-17 23:00:00 | 8 | 515 ms | 551 ms | 0 | 0 |
| 2026-11-18 00:00:00 | 7 | 522 ms | 560 ms | 0 | 0 |
| 2026-11-18 01:00:00 | 8 | 517 ms | 567 ms | 0 | 0 |
| 2026-11-18 02:00:00 | 7 | 533 ms | 552 ms | 0 | 0 |
| 2026-11-18 03:00:00 | 8 | 525 ms | 571 ms | 0 | 0 |
| 2026-11-18 04:00:00 | 7 | 502 ms | 519 ms | 0 | 0 |
| 2026-11-18 05:00:00 | 8 | 501 ms | 516 ms | 0 | 0 |
| 2026-11-18 06:00:00 | 8 | 532 ms | 569 ms | 0 | 0 |
| 2026-11-18 07:00:00 | 7 | 540 ms | 563 ms | 0 | 0 |
| 2026-11-18 08:00:00 | 8 | 522 ms | 561 ms | 0 | 0 |
| 2026-11-18 09:00:00 | 8 | 546 ms | 613 ms | 0 | 0 |
| 2026-11-18 10:00:00 | 7 | 533 ms | 563 ms | 0 | 0 |
| 2026-11-18 11:00:00 | 8 | 542 ms | 572 ms | 0 | 0 |
| 2026-11-18 12:00:00 | 7 | 550 ms | 589 ms | 0 | 0 |
| 2026-11-18 13:00:00 | 8 | 654 ms | 1 533 ms | 0 | 0 |
| 2026-11-18 14:00:00 | 7 | 521 ms | 544 ms | 0 | 0 |
| 2026-11-18 15:00:00 | 8 | 527 ms | 548 ms | 0 | 0 |
| 2026-11-18 16:00:00 | 7 | 1 054 ms | 4 077 ms | 0 | 0 |
| 2026-11-18 17:00:00 | 8 | 1 877 ms | 8 003 ms | 0 | 0 |
| 2026-11-18 18:00:00 | 7 | 1 633 ms | 8 003 ms | 0 | 0 |
| 2026-11-18 19:00:00 | 7 | 923 ms | 2 105 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.