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.
Messengers
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
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-16 22:30:00 | 1 | 194 ms | 194 ms | 0 | 0 |
| 2026-11-16 22:40:00 | 1 | 199 ms | 199 ms | 0 | 0 |
| 2026-11-16 22:45:00 | 1 | 215 ms | 215 ms | 0 | 0 |
| 2026-11-16 22:55:00 | 1 | 262 ms | 262 ms | 0 | 0 |
| 2026-11-16 23:05:00 | 1 | 269 ms | 269 ms | 0 | 0 |
| 2026-11-16 23:10:00 | 1 | 209 ms | 209 ms | 0 | 0 |
| 2026-11-16 23:20:00 | 1 | 203 ms | 203 ms | 0 | 0 |
| 2026-11-16 23:25:00 | 1 | 182 ms | 182 ms | 0 | 0 |
| 2026-11-16 23:35:00 | 1 | 207 ms | 207 ms | 0 | 0 |
| 2026-11-16 23:40:00 | 1 | 196 ms | 196 ms | 0 | 0 |
| 2026-11-16 23:50:00 | 1 | 188 ms | 188 ms | 0 | 0 |
| 2026-11-16 23:55:00 | 1 | 180 ms | 180 ms | 0 | 0 |
| 2026-11-17 00:05:00 | 1 | 182 ms | 182 ms | 0 | 0 |
| 2026-11-17 00:15:00 | 1 | 179 ms | 179 ms | 0 | 0 |
| 2026-11-17 00:20:00 | 1 | 196 ms | 196 ms | 0 | 0 |
| 2026-11-17 00:30:00 | 1 | 171 ms | 171 ms | 0 | 0 |
| 2026-11-17 00:35:00 | 1 | 194 ms | 194 ms | 0 | 0 |
| 2026-11-17 00:45:00 | 1 | 192 ms | 192 ms | 0 | 0 |
| 2026-11-17 00:50:00 | 1 | 184 ms | 184 ms | 0 | 0 |
| 2026-11-17 01:00:00 | 1 | 185 ms | 185 ms | 0 | 0 |
| 2026-11-17 01:10:00 | 1 | 188 ms | 188 ms | 0 | 0 |
| 2026-11-17 01:15:00 | 1 | 193 ms | 193 ms | 0 | 0 |
| 2026-11-17 01:25:00 | 1 | 168 ms | 168 ms | 0 | 0 |
| 2026-11-17 01:30:00 | 1 | 162 ms | 162 ms | 0 | 0 |
| 2026-11-17 01:40:00 | 1 | 187 ms | 187 ms | 0 | 0 |
| 2026-11-17 01:50:00 | 1 | 185 ms | 185 ms | 0 | 0 |
| 2026-11-17 01:55:00 | 1 | 158 ms | 158 ms | 0 | 0 |
| 2026-11-17 02:05:00 | 1 | 161 ms | 161 ms | 0 | 0 |
| 2026-11-17 02:10:00 | 1 | 163 ms | 163 ms | 0 | 0 |
| 2026-11-17 02:20:00 | 1 | 174 ms | 174 ms | 0 | 0 |
| 2026-11-17 02:30:00 | 1 | 193 ms | 193 ms | 0 | 0 |
| 2026-11-17 02:35:00 | 1 | 181 ms | 181 ms | 0 | 0 |
| 2026-11-17 02:45:00 | 1 | 178 ms | 178 ms | 0 | 0 |
| 2026-11-17 02:50:00 | 1 | 182 ms | 182 ms | 0 | 0 |
| 2026-11-17 03:00:00 | 1 | 190 ms | 190 ms | 0 | 0 |
| 2026-11-17 03:10:00 | 1 | 174 ms | 174 ms | 0 | 0 |
| 2026-11-17 03:15:00 | 1 | 172 ms | 172 ms | 0 | 0 |
| 2026-11-17 03:25:00 | 1 | 165 ms | 165 ms | 0 | 0 |
| 2026-11-17 03:30:00 | 1 | 176 ms | 176 ms | 0 | 0 |
| 2026-11-17 03:40:00 | 1 | 185 ms | 185 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 Discord, 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 Discord 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.