by HonkWatch

Is Ncrvoyix down in DR Congo?

No problems reported with Ncrvoyix right now

DR Congo No reports in the last hour checked 7 min ago
Ncrvoyix reports no current incident. Updated 6 Nov, 23:46 UTC, 7 min ago · Official status page
Report a problemFollow community reports
Change country

Reports from people in DR Congo

Last 24 hours · DR Congo · times in UTC

0 reports

No community reports in the last 24 hours from DR Congo. Having trouble? Add your report.

024 00:0006:0012:0018:0000:00

Bars: reports every 15 minutes. Reports alone do not confirm an outage; a flat chart does not prove everything works.

Report totals as of 6 Nov, 23:53 UTC

Report a problem with Ncrvoyix

Having trouble? Tap what isn't working. No account needed.

What isn't working?

Anonymous · one report per service per hour. This adds your experience to the chart, without contacting the provider or subscribing you to alerts.

Compare worldwide reports · Other services in DR Congo

Monitor the provider status with HonkWatch

Get monitoring alerts for Ncrvoyix

HonkWatch watches the Ncrvoyix status page for you and alerts you by email, Slack, Discord or Telegram when it reports a problem.

Free account required. Ncrvoyix is selected on the next page. Review the monitor and choose where alerts go. Community reports do not trigger these monitoring alerts.

Start free Log in

Where this status comes from

Provider updates and website checks — Worldwide

The evidence below covers the provider and our available checks. It is not a separate verdict for DR Congo. The report chart above is filtered to DR Congo.

Our own checks of ncrvoyix.com

Every 5 minutes, from our probes

12 of 35 cities can't reach ncrvoyix.com.

Amsterdam: loaded in 873 ms New York: loaded in 624 ms Hamina: loaded in 784 ms Seattle: loaded in 608 ms St. Louis: loaded in 336 ms Mumbai: loaded in 1593 ms Dallas: loaded in 338 ms Jakarta: loaded in 1681 ms Lauterbourg: loaded in 763 ms Sydney: loaded in 1492 ms Port Louis: loaded in 1765 ms Bangalore: loaded in 1888 ms Cape Town: loaded in 1532 ms Doha: loaded in 1076 ms New Jersey: loaded in 211 ms Tokyo: loaded in 1294 ms Singapore: loaded in 1583 ms Delhi: loaded in 1471 ms Frankfurt: loaded in 699 ms Portsmouth: loaded in 872 ms Johannesburg: loaded in 1530 ms Toronto: loaded in 291 ms Los Angeles: loaded in 588 ms Madrid: could not load it (Unresolvable: Cannot resolve ncrvoyix.com: No address associ) Osaka: could not load it (Unresolvable: Cannot resolve ncrvoyix.com: No address associ) London: could not load it (Unresolvable: Cannot resolve ncrvoyix.com: No address associ) Seoul: could not load it (Unresolvable: Cannot resolve ncrvoyix.com: No address associ) Melbourne: could not load it (Unresolvable: Cannot resolve ncrvoyix.com: No address associ) Hong Kong: could not load it (Unresolvable: Cannot resolve ncrvoyix.com: No address associ) Warsaw: could not load it (Unresolvable: Cannot resolve ncrvoyix.com: No address associ) São Paulo: could not load it (Unresolvable: Cannot resolve ncrvoyix.com: No address associ) Santiago: could not load it (Unresolvable: Cannot resolve ncrvoyix.com: No address associ) Atlanta: could not load it (Unresolvable: Cannot resolve ncrvoyix.com: No address associ) Querétaro: could not load it (Unresolvable: Cannot resolve ncrvoyix.com: No address associ) Tel Aviv: could not load it (Unresolvable: Cannot resolve ncrvoyix.com: No address associ)
  • AmsterdamReachable873 ms, just now
  • MadridName does not resolve114 ms, just now
  • OsakaName does not resolve2 ms, just now
  • LondonName does not resolve93 ms, just now
  • SeoulName does not resolve196 ms, just now
  • New YorkReachable624 ms, just now
  • MelbourneName does not resolve9 ms, 3 min ago
  • Hong KongName does not resolve10 ms, 3 min ago
  • WarsawName does not resolve3 ms, 3 min ago
  • São PauloName does not resolve11 ms, 3 min ago
  • SantiagoName does not resolve2 ms, 3 min ago
  • AtlantaName does not resolve2 ms, 3 min ago
  • QuerétaroName does not resolve1 ms, 3 min ago
  • Tel AvivName does not resolve157 ms, 3 min ago
  • HaminaReachable784 ms, 3 min ago
  • SeattleReachable608 ms, 3 min ago
  • St. LouisReachable336 ms, 3 min ago
  • MumbaiReachable1593 ms, 3 min ago
  • DallasReachable338 ms, 4 min ago
  • JakartaReachable1681 ms, 4 min ago
  • LauterbourgReachable763 ms, 4 min ago
  • SydneyReachable1492 ms, 4 min ago
  • Port LouisReachable1765 ms, 4 min ago
  • BangaloreReachable1888 ms, 4 min ago
  • Cape TownReachable1532 ms, 4 min ago
  • DohaReachable1076 ms, 4 min ago
  • New JerseyReachable211 ms, 5 min ago
  • TokyoReachable1294 ms, 5 min ago
  • SingaporeReachable1583 ms, 5 min ago
  • DelhiReachable1471 ms, 5 min ago
  • FrankfurtReachable699 ms, 5 min ago
  • PortsmouthReachable872 ms, 5 min ago
  • JohannesburgReachable1530 ms, 5 min ago
  • TorontoReachable291 ms, 5 min ago
  • Los AngelesReachable588 ms, 5 min ago

This is separate from the status page: we request ncrvoyix.com and note whether it answers. These automated checks do not sign in or use the app's features.

Parts of Ncrvoyix

NCR Voyix Status

All 297 listed parts are working.

Incidents and maintenance

Maintenance

  • Voyix Pay Scheduled Maintenance - Phase 2 (planned) 7 Nov, 18:00 UTC to 7 Nov, 22:00 UTC. Affects Settlement & Funding-NAMER · Details
  • Pulse Server Side Deployment version 20.48.2 (planned) 9 Nov, 10:00 UTC to 9 Nov, 13:00 UTC. Affects Pulse Realtime-NAMER, Pulse Realtime-EMEA, Pulse Realtime-APAC, Pulse Realtime API-NAMER and 2 more · Details
  • Configuration Center (CFC) 22.2.0.1013 General Release (planned) 9 Nov, 17:00 UTC to 9 Nov, 22:00 UTC. Affects Configuration Center-APAC, Configuration Center API-APAC · Details
  • Voyix Connect Maintenance - Common Phase 2 (planned) 10 Nov, 06:00 UTC to 10 Nov, 10:00 UTC. Affects Common Environment Authorizer Service-NAMER, Common Environment Processor Service-NAMER, Online Transaction Processing - Retail-NAMER, Voyix Connect Reporting - Retail-NAMER and 1 more · Details
  • Configuration Center (CFC) 22.2.0.1013 General Release (planned) 10 Nov, 07:00 UTC to 10 Nov, 12:00 UTC. Affects Configuration Center-NAMER, Configuration Center API-NAMER · Details
  • Voyix Connect Maintenance - Hospitality Phase 2 (planned) 10 Nov, 10:30 UTC to 10 Nov, 14:30 UTC. Affects Hospitality Environment Authorizer Service-NAMER, Hospitality Environment Processor Service-NAMER, Online Transaction Processing - Restaurant-NAMER, WebEPS (eCommerce) - Restaurant-NAMER · Details
  • Command Center update to CMC Console - EMEA (planned) 11 Nov, 23:00 UTC to 12 Nov, 03:00 UTC. Affects Command Center-EMEA · Details
  • Command Center update to CMC Console - NAMER (planned) 12 Nov, 05:00 UTC to 12 Nov, 09:00 UTC. Affects Command Center-NAMER · Details
  • Command Center update to CMC Console - APAC (planned) 12 Nov, 16:00 UTC to 12 Nov, 20:00 UTC. Affects Command Center-APAC · Details
  • CFC Server Maintenance EMEA Region (planned) 13 Nov, 02:00 UTC to 13 Nov, 08:00 UTC. Affects Configuration Center-EMEA · Details
Outage history

Last problem: 4 Nov, 11:28 UTC, partial outage for 51 min (Open incident: Pocket Office | MAJOR OUTAGE - NAMER).

Last 9030 days

97.74% of the time without a reported outage, since 3 Nov

Of the last 90 days, 2 had a partial or major outage, 2 had maintenance only and 86 have no data. Recent problems are listed in a table further down.

90 days ago30 days agoToday

No problems Partial outage Major outage Maintenance No data yet

Last 24 hours

Every 15 minutes, hours in UTC

Bars: the share of our own checks of ncrvoyix.com that failed (24,607 checks). Its status page reported no problem in this time. Community reports appear separately above, alongside our checks and provider updates.

0%41%83% 00:0006:0012:0018:0000:00 80% of 393 checks failed73% of 325 checks failed74% of 318 checks failed78% of 349 checks failed78% of 341 checks failed73% of 303 checks failed80% of 367 checks failed80% of 396 checks failed76% of 348 checks failed72% of 291 checks failed75% of 322 checks failed73% of 308 checks failed78% of 374 checks failed77% of 347 checks failed81% of 403 checks failed76% of 335 checks failed78% of 356 checks failed79% of 351 checks failed80% of 384 checks failed78% of 361 checks failed83% of 418 checks failed79% of 362 checks failed81% of 409 checks failed80% of 364 checks failed76% of 333 checks failed82% of 393 checks failed82% of 398 checks failed80% of 385 checks failed75% of 280 checks failed69% of 278 checks failed73% of 271 checks failed73% of 258 checks failed81% of 417 checks failed76% of 341 checks failed74% of 317 checks failed77% of 335 checks failed81% of 351 checks failed77% of 260 checks failed68% of 227 checks failed63% of 169 checks failed71% of 244 checks failed69% of 223 checks failed62% of 208 checks failed72% of 207 checks failed68% of 152 checks failed57% of 127 checks failed65% of 219 checks failed68% of 182 checks failed64% of 198 checks failed71% of 211 checks failed67% of 194 checks failed66% of 119 checks failed66% of 154 checks failed66% of 202 checks failed66% of 175 checks failed63% of 146 checks failed57% of 124 checks failed49% of 116 checks failed58% of 113 checks failed63% of 166 checks failed61% of 145 checks failed56% of 91 checks failed46% of 127 checks failed70% of 134 checks failed48% of 126 checks failed61% of 133 checks failed58% of 113 checks failed59% of 136 checks failed61% of 114 checks failed58% of 124 checks failed69% of 240 checks failed78% of 269 checks failed59% of 143 checks failed66% of 177 checks failed73% of 255 checks failed72% of 184 checks failed52% of 85 checks failed42% of 110 checks failed47% of 119 checks failed60% of 139 checks failed65% of 205 checks failed74% of 300 checks failed72% of 301 checks failed82% of 396 checks failed69% of 157 checks failed75% of 222 checks failed72% of 310 checks failed75% of 242 checks failed73% of 261 checks failed75% of 299 checks failed79% of 365 checks failed76% of 314 checks failed76% of 347 checks failed77% of 376 checks failed78% of 379 checks failed83% of 151 checks failed

Recent problems

4 Nov, 11:28 UTCPartial outage51 minOpen incident: Pocket Office | MAJOR OUTAGE - NAMER
3 Nov, 23:40 UTCPartial outage1 h 6 minOpen incident: BSL APAC | Degraded Performance
What can I try?

Having trouble with Ncrvoyix?

  1. Compare reports from DR Congo and check the latest update above. A quiet chart does not rule out a new or local problem.
  2. Try the service on another device or switch between WiFi and mobile data, if available. If other sites also fail, check your internet provider.
  3. Report a problem with the feature that is failing and the country where you are affected. Submit once; your report appears in the chart.

Reports describe people's experiences. One report alone does not confirm an outage.

Questions about these results

Questions

Is Ncrvoyix down, or is it just me?

The Ncrvoyix status page reports no problem. This does not rule out problems with sign-in, payments, an app or a local network. Check the community reports above and report your experience.

How do we know?

We read the official Ncrvoyix status page and load ncrvoyix.com from our own probes in several cities. People can also report problems here. Their reports appear separately and may reveal issues before a provider update.

How often do we check?

The status page every 15 minutes, day and night, and the website every 5 minutes. We keep 90 days of history: a day we have no reading for shows as "no data yet", never as working.

More in Payments and shops

See the live outage feed for DR Congo · Find another service