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 03:00:00 | 4 | 275 ms | 299 ms | 0 | 4 |
| 2026-11-17 03:30:00 | 4 | 268 ms | 290 ms | 0 | 4 |
| 2026-11-17 04:00:00 | 3 | 266 ms | 279 ms | 0 | 3 |
| 2026-11-17 04:30:00 | 4 | 277 ms | 330 ms | 0 | 4 |
| 2026-11-17 05:00:00 | 4 | 322 ms | 463 ms | 0 | 4 |
| 2026-11-17 05:30:00 | 4 | 272 ms | 280 ms | 0 | 4 |
| 2026-11-17 06:00:00 | 3 | 265 ms | 282 ms | 0 | 3 |
| 2026-11-17 06:30:00 | 4 | 266 ms | 284 ms | 0 | 4 |
| 2026-11-17 07:00:00 | 4 | 277 ms | 278 ms | 0 | 4 |
| 2026-11-17 07:30:00 | 4 | 307 ms | 415 ms | 0 | 4 |
| 2026-11-17 08:00:00 | 4 | 278 ms | 344 ms | 0 | 4 |
| 2026-11-17 08:30:00 | 4 | 278 ms | 302 ms | 0 | 4 |
| 2026-11-17 09:00:00 | 4 | 270 ms | 281 ms | 0 | 4 |
| 2026-11-17 09:30:00 | 4 | 274 ms | 278 ms | 0 | 4 |
| 2026-11-17 10:00:00 | 4 | 267 ms | 275 ms | 0 | 4 |
| 2026-11-17 10:30:00 | 4 | 276 ms | 300 ms | 0 | 4 |
| 2026-11-17 11:00:00 | 3 | 260 ms | 268 ms | 0 | 3 |
| 2026-11-17 11:30:00 | 4 | 272 ms | 281 ms | 0 | 4 |
| 2026-11-17 12:00:00 | 4 | 267 ms | 274 ms | 0 | 4 |
| 2026-11-17 12:30:00 | 4 | 268 ms | 276 ms | 0 | 4 |
| 2026-11-17 13:00:00 | 4 | 284 ms | 325 ms | 0 | 4 |
| 2026-11-17 13:30:00 | 3 | 273 ms | 278 ms | 0 | 3 |
| 2026-11-17 14:00:00 | 4 | 264 ms | 270 ms | 0 | 4 |
| 2026-11-17 14:30:00 | 4 | 282 ms | 303 ms | 0 | 4 |
| 2026-11-17 15:00:00 | 4 | 271 ms | 287 ms | 0 | 4 |
| 2026-11-17 15:30:00 | 3 | 267 ms | 276 ms | 0 | 3 |
| 2026-11-17 16:00:00 | 4 | 274 ms | 278 ms | 0 | 4 |
| 2026-11-17 16:30:00 | 4 | 272 ms | 280 ms | 0 | 4 |
| 2026-11-17 17:00:00 | 4 | 274 ms | 290 ms | 0 | 4 |
| 2026-11-17 17:30:00 | 3 | 294 ms | 311 ms | 0 | 3 |
| 2026-11-17 18:00:00 | 4 | 285 ms | 310 ms | 0 | 4 |
| 2026-11-17 18:30:00 | 4 | 306 ms | 396 ms | 0 | 4 |
| 2026-11-17 19:00:00 | 3 | 283 ms | 312 ms | 0 | 3 |
| 2026-11-17 19:30:00 | 4 | 299 ms | 391 ms | 0 | 4 |
| 2026-11-17 20:00:00 | 4 | 305 ms | 375 ms | 0 | 4 |
| 2026-11-17 20:30:00 | 3 | 293 ms | 314 ms | 0 | 3 |
| 2026-11-17 21:00:00 | 4 | 396 ms | 505 ms | 0 | 4 |
| 2026-11-17 21:30:00 | 4 | 304 ms | 354 ms | 0 | 4 |
| 2026-11-17 22:00:00 | 3 | 278 ms | 279 ms | 0 | 3 |
| 2026-11-17 22:30:00 | 4 | 287 ms | 312 ms | 0 | 4 |
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.