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-16 07:00:00 | 8 | 292 ms | 322 ms | 0 | 0 |
| 2026-11-16 08:00:00 | 7 | 759 ms | 3 508 ms | 0 | 0 |
| 2026-11-16 09:00:00 | 8 | 291 ms | 339 ms | 0 | 0 |
| 2026-11-16 10:00:00 | 7 | 309 ms | 336 ms | 0 | 0 |
| 2026-11-16 11:00:00 | 8 | 297 ms | 339 ms | 0 | 0 |
| 2026-11-16 12:00:00 | 7 | 290 ms | 298 ms | 0 | 0 |
| 2026-11-16 13:00:00 | 8 | 377 ms | 525 ms | 0 | 0 |
| 2026-11-16 14:00:00 | 7 | 299 ms | 315 ms | 0 | 0 |
| 2026-11-16 15:00:00 | 8 | 312 ms | 386 ms | 0 | 0 |
| 2026-11-16 16:00:00 | 7 | 332 ms | 480 ms | 0 | 0 |
| 2026-11-16 17:00:00 | 8 | 693 ms | 2 419 ms | 0 | 0 |
| 2026-11-16 18:00:00 | 8 | 389 ms | 977 ms | 0 | 0 |
| 2026-11-16 19:00:00 | 7 | 297 ms | 316 ms | 0 | 0 |
| 2026-11-16 20:00:00 | 8 | 293 ms | 337 ms | 0 | 0 |
| 2026-11-16 21:00:00 | 7 | 308 ms | 338 ms | 0 | 0 |
| 2026-11-16 22:00:00 | 8 | 322 ms | 439 ms | 0 | 0 |
| 2026-11-16 23:00:00 | 7 | 287 ms | 324 ms | 0 | 0 |
| 2026-11-17 00:00:00 | 8 | 280 ms | 300 ms | 0 | 0 |
| 2026-11-17 01:00:00 | 8 | 319 ms | 480 ms | 0 | 0 |
| 2026-11-17 02:00:00 | 7 | 285 ms | 316 ms | 0 | 0 |
| 2026-11-17 03:00:00 | 8 | 316 ms | 468 ms | 0 | 0 |
| 2026-11-17 04:00:00 | 7 | 291 ms | 331 ms | 0 | 0 |
| 2026-11-17 05:00:00 | 7 | 297 ms | 330 ms | 0 | 0 |
| 2026-11-17 06:00:00 | 8 | 288 ms | 326 ms | 0 | 0 |
| 2026-11-17 07:00:00 | 8 | 281 ms | 312 ms | 0 | 0 |
| 2026-11-17 08:00:00 | 8 | 422 ms | 1 365 ms | 0 | 0 |
| 2026-11-17 09:00:00 | 8 | 355 ms | 714 ms | 0 | 0 |
| 2026-11-17 10:00:00 | 7 | 310 ms | 351 ms | 0 | 0 |
| 2026-11-17 11:00:00 | 8 | 316 ms | 372 ms | 0 | 0 |
| 2026-11-17 12:00:00 | 8 | 299 ms | 343 ms | 0 | 0 |
| 2026-11-17 13:00:00 | 7 | 331 ms | 457 ms | 0 | 0 |
| 2026-11-17 14:00:00 | 8 | 296 ms | 314 ms | 0 | 0 |
| 2026-11-17 15:00:00 | 7 | 302 ms | 334 ms | 0 | 0 |
| 2026-11-17 16:00:00 | 8 | 324 ms | 398 ms | 0 | 0 |
| 2026-11-17 17:00:00 | 7 | 295 ms | 320 ms | 0 | 0 |
| 2026-11-17 18:00:00 | 7 | 332 ms | 598 ms | 0 | 0 |
| 2026-11-17 19:00:00 | 8 | 373 ms | 801 ms | 0 | 0 |
| 2026-11-17 20:00:00 | 7 | 324 ms | 349 ms | 0 | 0 |
| 2026-11-17 21:00:00 | 8 | 437 ms | 1 258 ms | 0 | 0 |
| 2026-11-17 22:00:00 | 7 | 325 ms | 352 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.