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.
Cloud 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
Мониторинг доступности сервиса Akamai, пользовательских сигналов и технических проверок 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 | 276 ms | 276 ms | 0 | 1 |
| 2026-11-17 17:45:00 | 1 | 311 ms | 311 ms | 0 | 1 |
| 2026-11-17 17:50:00 | 1 | 296 ms | 296 ms | 0 | 1 |
| 2026-11-17 18:00:00 | 1 | 266 ms | 266 ms | 0 | 1 |
| 2026-11-17 18:05:00 | 1 | 283 ms | 283 ms | 0 | 1 |
| 2026-11-17 18:15:00 | 1 | 280 ms | 280 ms | 0 | 1 |
| 2026-11-17 18:25:00 | 1 | 310 ms | 310 ms | 0 | 1 |
| 2026-11-17 18:30:00 | 1 | 271 ms | 271 ms | 0 | 1 |
| 2026-11-17 18:40:00 | 1 | 278 ms | 278 ms | 0 | 1 |
| 2026-11-17 18:50:00 | 1 | 396 ms | 396 ms | 0 | 1 |
| 2026-11-17 18:55:00 | 1 | 279 ms | 279 ms | 0 | 1 |
| 2026-11-17 19:05:00 | 1 | 280 ms | 280 ms | 0 | 1 |
| 2026-11-17 19:15:00 | 1 | 312 ms | 312 ms | 0 | 1 |
| 2026-11-17 19:20:00 | 1 | 256 ms | 256 ms | 0 | 1 |
| 2026-11-17 19:30:00 | 1 | 266 ms | 266 ms | 0 | 1 |
| 2026-11-17 19:35:00 | 1 | 262 ms | 262 ms | 0 | 1 |
| 2026-11-17 19:45:00 | 1 | 278 ms | 278 ms | 0 | 1 |
| 2026-11-17 19:55:00 | 1 | 391 ms | 391 ms | 0 | 1 |
| 2026-11-17 20:00:00 | 1 | 276 ms | 276 ms | 0 | 1 |
| 2026-11-17 20:10:00 | 1 | 277 ms | 277 ms | 0 | 1 |
| 2026-11-17 20:20:00 | 1 | 291 ms | 291 ms | 0 | 1 |
| 2026-11-17 20:25:00 | 1 | 375 ms | 375 ms | 0 | 1 |
| 2026-11-17 20:35:00 | 1 | 314 ms | 314 ms | 0 | 1 |
| 2026-11-17 20:45:00 | 1 | 276 ms | 276 ms | 0 | 1 |
| 2026-11-17 20:50:00 | 1 | 290 ms | 290 ms | 0 | 1 |
| 2026-11-17 21:00:00 | 1 | 356 ms | 356 ms | 0 | 1 |
| 2026-11-17 21:05:00 | 1 | 325 ms | 325 ms | 0 | 1 |
| 2026-11-17 21:15:00 | 1 | 399 ms | 399 ms | 0 | 1 |
| 2026-11-17 21:25:00 | 1 | 505 ms | 505 ms | 0 | 1 |
| 2026-11-17 21:30:00 | 1 | 281 ms | 281 ms | 0 | 1 |
| 2026-11-17 21:40:00 | 1 | 354 ms | 354 ms | 0 | 1 |
| 2026-11-17 21:45:00 | 1 | 308 ms | 308 ms | 0 | 1 |
| 2026-11-17 21:55:00 | 1 | 274 ms | 274 ms | 0 | 1 |
| 2026-11-17 22:05:00 | 1 | 279 ms | 279 ms | 0 | 1 |
| 2026-11-17 22:10:00 | 1 | 276 ms | 276 ms | 0 | 1 |
| 2026-11-17 22:20:00 | 1 | 278 ms | 278 ms | 0 | 1 |
| 2026-11-17 22:30:00 | 1 | 312 ms | 312 ms | 0 | 1 |
| 2026-11-17 22:35:00 | 1 | 258 ms | 258 ms | 0 | 1 |
| 2026-11-17 22:45:00 | 1 | 294 ms | 294 ms | 0 | 1 |
| 2026-11-17 22:50:00 | 1 | 284 ms | 284 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 Akamai, 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 Akamai 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.