How to interpret the monitoring status
Technical measurements reflect observations from the NexIP monitoring location. A failed or restricted request alone does not confirm a widespread outage.
AI services
Автоматический запрос из точки NexIP ограничен. Массовый сбой не подтверждён.
Technical measurements reflect observations from the NexIP monitoring location. A failed or restricted request alone does not confirm a widespread outage.
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
Мониторинг доступности сервиса ChatGPT, пользовательских сигналов и технических проверок 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 17:35:00 | 1 | 215 ms | 215 ms | 0 | 1 |
| 2026-11-17 17:45:00 | 1 | 219 ms | 219 ms | 0 | 1 |
| 2026-11-17 17:50:00 | 1 | 210 ms | 210 ms | 0 | 1 |
| 2026-11-17 18:00:00 | 1 | 170 ms | 170 ms | 0 | 1 |
| 2026-11-17 18:05:00 | 1 | 145 ms | 145 ms | 0 | 1 |
| 2026-11-17 18:15:00 | 1 | 225 ms | 225 ms | 0 | 1 |
| 2026-11-17 18:25:00 | 1 | 158 ms | 158 ms | 0 | 1 |
| 2026-11-17 18:30:00 | 1 | 223 ms | 223 ms | 0 | 1 |
| 2026-11-17 18:40:00 | 1 | 214 ms | 214 ms | 0 | 1 |
| 2026-11-17 18:50:00 | 1 | 150 ms | 150 ms | 0 | 1 |
| 2026-11-17 18:55:00 | 1 | 178 ms | 178 ms | 0 | 1 |
| 2026-11-17 19:05:00 | 1 | 198 ms | 198 ms | 0 | 1 |
| 2026-11-17 19:15:00 | 1 | 205 ms | 205 ms | 0 | 1 |
| 2026-11-17 19:20:00 | 1 | 215 ms | 215 ms | 0 | 1 |
| 2026-11-17 19:30:00 | 1 | 146 ms | 146 ms | 0 | 1 |
| 2026-11-17 19:35:00 | 1 | 212 ms | 212 ms | 0 | 1 |
| 2026-11-17 19:45:00 | 1 | 153 ms | 153 ms | 0 | 1 |
| 2026-11-17 19:55:00 | 1 | 208 ms | 208 ms | 0 | 1 |
| 2026-11-17 20:00:00 | 1 | 209 ms | 209 ms | 0 | 1 |
| 2026-11-17 20:10:00 | 1 | 147 ms | 147 ms | 0 | 1 |
| 2026-11-17 20:20:00 | 1 | 156 ms | 156 ms | 0 | 1 |
| 2026-11-17 20:25:00 | 1 | 292 ms | 292 ms | 0 | 1 |
| 2026-11-17 20:35:00 | 1 | 186 ms | 186 ms | 0 | 1 |
| 2026-11-17 20:45:00 | 1 | 203 ms | 203 ms | 0 | 1 |
| 2026-11-17 20:50:00 | 1 | 226 ms | 226 ms | 0 | 1 |
| 2026-11-17 21:00:00 | 1 | 228 ms | 228 ms | 0 | 1 |
| 2026-11-17 21:05:00 | 1 | 173 ms | 173 ms | 0 | 1 |
| 2026-11-17 21:15:00 | 1 | 199 ms | 199 ms | 0 | 1 |
| 2026-11-17 21:25:00 | 1 | 222 ms | 222 ms | 0 | 1 |
| 2026-11-17 21:30:00 | 1 | 218 ms | 218 ms | 0 | 1 |
| 2026-11-17 21:40:00 | 1 | 208 ms | 208 ms | 0 | 1 |
| 2026-11-17 21:45:00 | 1 | 259 ms | 259 ms | 0 | 1 |
| 2026-11-17 21:55:00 | 1 | 210 ms | 210 ms | 0 | 1 |
| 2026-11-17 22:05:00 | 1 | 194 ms | 194 ms | 0 | 1 |
| 2026-11-17 22:10:00 | 1 | 221 ms | 221 ms | 0 | 1 |
| 2026-11-17 22:20:00 | 1 | 161 ms | 161 ms | 0 | 1 |
| 2026-11-17 22:30:00 | 1 | 152 ms | 152 ms | 0 | 1 |
| 2026-11-17 22:35:00 | 1 | 216 ms | 216 ms | 0 | 1 |
| 2026-11-17 22:45:00 | 1 | 209 ms | 209 ms | 0 | 1 |
| 2026-11-17 22:50:00 | 1 | 184 ms | 184 ms | 0 | 1 |
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 ChatGPT, 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 ChatGPT 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.