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.
Banks
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
Мониторинг доступности сервиса Райффайзен Банк, пользовательских сигналов и технических проверок 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:20:00 | 1 | 285 ms | 285 ms | 0 | 0 |
| 2026-11-17 17:30:00 | 1 | 288 ms | 288 ms | 0 | 0 |
| 2026-11-17 17:35:00 | 1 | 316 ms | 316 ms | 0 | 0 |
| 2026-11-17 17:45:00 | 1 | 288 ms | 288 ms | 0 | 0 |
| 2026-11-17 17:50:00 | 1 | 320 ms | 320 ms | 0 | 0 |
| 2026-11-17 18:00:00 | 1 | 278 ms | 278 ms | 0 | 0 |
| 2026-11-17 18:10:00 | 1 | 598 ms | 598 ms | 0 | 0 |
| 2026-11-17 18:15:00 | 1 | 268 ms | 268 ms | 0 | 0 |
| 2026-11-17 18:25:00 | 1 | 288 ms | 288 ms | 0 | 0 |
| 2026-11-17 18:35:00 | 1 | 319 ms | 319 ms | 0 | 0 |
| 2026-11-17 18:40:00 | 1 | 275 ms | 275 ms | 0 | 0 |
| 2026-11-17 18:50:00 | 1 | 300 ms | 300 ms | 0 | 0 |
| 2026-11-17 19:00:00 | 1 | 339 ms | 339 ms | 0 | 0 |
| 2026-11-17 19:05:00 | 1 | 355 ms | 355 ms | 0 | 0 |
| 2026-11-17 19:15:00 | 1 | 309 ms | 309 ms | 0 | 0 |
| 2026-11-17 19:25:00 | 1 | 272 ms | 272 ms | 0 | 0 |
| 2026-11-17 19:30:00 | 1 | 312 ms | 312 ms | 0 | 0 |
| 2026-11-17 19:40:00 | 1 | 801 ms | 801 ms | 0 | 0 |
| 2026-11-17 19:45:00 | 1 | 300 ms | 300 ms | 0 | 0 |
| 2026-11-17 19:55:00 | 1 | 295 ms | 295 ms | 0 | 0 |
| 2026-11-17 20:05:00 | 1 | 304 ms | 304 ms | 0 | 0 |
| 2026-11-17 20:10:00 | 1 | 313 ms | 313 ms | 0 | 0 |
| 2026-11-17 20:20:00 | 1 | 296 ms | 296 ms | 0 | 0 |
| 2026-11-17 20:30:00 | 1 | 339 ms | 339 ms | 0 | 0 |
| 2026-11-17 20:35:00 | 1 | 321 ms | 321 ms | 0 | 0 |
| 2026-11-17 20:45:00 | 1 | 349 ms | 349 ms | 0 | 0 |
| 2026-11-17 20:50:00 | 1 | 346 ms | 346 ms | 0 | 0 |
| 2026-11-17 21:00:00 | 1 | 297 ms | 297 ms | 0 | 0 |
| 2026-11-17 21:10:00 | 1 | 270 ms | 270 ms | 0 | 0 |
| 2026-11-17 21:15:00 | 1 | 294 ms | 294 ms | 0 | 0 |
| 2026-11-17 21:25:00 | 1 | 305 ms | 305 ms | 0 | 0 |
| 2026-11-17 21:35:00 | 1 | 445 ms | 445 ms | 0 | 0 |
| 2026-11-17 21:40:00 | 1 | 306 ms | 306 ms | 0 | 0 |
| 2026-11-17 21:50:00 | 1 | 318 ms | 318 ms | 0 | 0 |
| 2026-11-17 21:55:00 | 1 | 1 258 ms | 1 258 ms | 0 | 0 |
| 2026-11-17 22:05:00 | 1 | 344 ms | 344 ms | 0 | 0 |
| 2026-11-17 22:15:00 | 1 | 304 ms | 304 ms | 0 | 0 |
| 2026-11-17 22:20:00 | 1 | 352 ms | 352 ms | 0 | 0 |
| 2026-11-17 22:30:00 | 1 | 290 ms | 290 ms | 0 | 0 |
| 2026-11-17 22:35:00 | 1 | 288 ms | 288 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 Райффайзен Банк, 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 Райффайзен Банк 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.