← HonkWatch.com

Is Ncrvoyix down in Fr. S. Antarctic Lands?

Planned maintenance at Ncrvoyix

People in Fr. S. Antarctic Lands: 0 reports in the last hour Official page: Planned maintenance, checked 8 min ago Our checks: loads from 26 of 35 places
Ncrvoyix has planned maintenance. Maintenance on Voyix Pay / Settlement & Funding-NAMER. Updated 7 Nov, 20:25 UTC, 8 min ago · Official status page
Report a problem
Change country

Known issues (from NCR Voyix's status page)

Maintenance

  • Voyix Pay Scheduled Maintenance - Phase 2 (under way) 7 Nov, 18:00 UTC to 7 Nov, 22:00 UTC. Affects Settlement & Funding-NAMER · Details Latest update (7 Nov, 18:00 UTC): Scheduled maintenance is currently in progress. We will provide updates as necessary.
  • 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 Latest update (3 Nov, 16:31 UTC): We are performing a regular server-side update, transactions might be delayed during this time. This maintenance will include Pulse real-time and Pulse real-time API.
  • 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 Latest update (3 Nov, 23:11 UTC): We will be performing maintenance with a general release of 20.2.0.1013.
Show 7 more maintenance windows
  • 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 Latest update (30 Oct, 20:32 UTC): We will be performing maintenance on the following components during this window. During this time, NCR Voyix will fail all traffic to alternate data centers to not impact transactions. WebClient Reporting will be unavailable during the maintenance window, with potential intermittent impact after th
  • 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 Latest update (3 Nov, 23:12 UTC): We will be performing a general release of CFC version 20.2.0.1013.
  • 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 Latest update (30 Oct, 16:41 UTC): We will be performing maintenance on the following components during this window. During this time, NCR Voyix will fail all traffic to alternate data centers to not impact transactions. WebClient Reporting will be unavailable during the maintenance window, with potential intermittent impact after th
  • Command Center update to CMC Console - EMEA (planned) 11 Nov, 23:00 UTC to 12 Nov, 03:00 UTC. Affects Command Center-EMEA · Details Latest update (6 Nov, 09:25 UTC): Dear Valued Customer, On November 11, 2026, between 23:00 UTC and November 12, 2026 3:00 UTC during the scheduled maintenance window, NCR Voyix will update CMC Console component to improve Machine Detail Reporting in CMC Client. During this activity, you may experience a minimal interruption. At NCR
  • Command Center update to CMC Console - NAMER (planned) 12 Nov, 05:00 UTC to 12 Nov, 09:00 UTC. Affects Command Center-NAMER · Details Latest update (6 Nov, 09:24 UTC): Dear Valued Customer, On November 12, 2026, between 5:00 UTC and 9:00 UTC during the scheduled maintenance window, NCR Voyix will update CMC Console component to improve Machine Detail Reporting in CMC Client. During this activity, you may experience a minimal interruption. At NCR Voyix, your satisf
  • Command Center update to CMC Console - APAC (planned) 12 Nov, 16:00 UTC to 12 Nov, 20:00 UTC. Affects Command Center-APAC · Details Latest update (6 Nov, 09:25 UTC): Dear Valued Customer, On November 12, 2026, between 16:00 UTC and 20:00 UTC during the scheduled maintenance window, NCR Voyix will update CMC Console component to improve Machine Detail Reporting in CMC Client. During this activity, you may experience a minimal interruption. At NCR Voyix, your sati
  • CFC Server Maintenance EMEA Region (planned) 13 Nov, 02:00 UTC to 13 Nov, 08:00 UTC. Affects Configuration Center-EMEA · Details Latest update (6 Nov, 14:36 UTC): We will be undergoing scheduled maintenance during this time.

We keep the first 10 of 13 maintenance windows; the rest are on NCR Voyix's status page.

In NCR Voyix's own words, as we read them every 15 minutes, last 8 min ago. Read NCR Voyix's status page

Reports from people in Fr. S. Antarctic Lands

Last 24 hours · Fr. S. Antarctic Lands · times in UTC

0 reports

No community reports in the last 24 hours from Fr. S. Antarctic Lands. Having trouble? Add your report.

Status page: maintenance, 6 Nov, 18:15 to 22:11 UTCStatus page: maintenance, 15:33 to 16:04 UTCStatus page: maintenance, 18:10 to now 024 00:0006:0012:0018:00 20:45-20:50 UTC: 9 of 10 places loaded it, typical 1074 ms20:50-21:00 UTC: 11 of 11 places loaded it, typical 807 to 870 ms21:00-21:05 UTC: 2 of 2 places loaded it21:05-21:10 UTC: 10 of 10 places loaded it, typical 920 ms21:10-21:15 UTC: 9 of 10 places loaded it, typical 734 ms21:15-21:20 UTC: 6 of 7 places loaded it, typical 1141 ms21:20-21:25 UTC: 11 of 11 places loaded it, typical 801 ms21:25-21:30 UTC: 4 of 5 places loaded it, typical 1198 ms21:30-21:35 UTC: 8 of 10 places loaded it, typical 683 ms21:35-21:45 UTC: 11 of 11 places loaded it, typical 1374 to 1426 ms21:45-21:50 UTC: 5 of 5 places loaded it, typical 890 ms21:50-21:55 UTC: 9 of 9 places loaded it, typical 1619 ms21:55-22:05 UTC: 11 of 11 places loaded it, typical 755 to 789 ms22:05-22:10 UTC: 7 of 7 places loaded it, typical 1592 ms22:10-22:25 UTC: 11 of 11 places loaded it, typical 748 to 842 ms22:25-22:30 UTC: 8 of 8 places loaded it, typical 1021 ms22:30-22:35 UTC: 10 of 11 places loaded it, typical 1070 ms22:35-23:10 UTC: 11 of 11 places loaded it, typical 764 to 1495 ms23:10-23:15 UTC: 10 of 11 places loaded it, typical 740 ms23:15-00:10 UTC: 11 of 11 places loaded it, typical 749 to 1502 ms00:10-00:15 UTC: 10 of 11 places loaded it, typical 1123 ms00:15-00:25 UTC: 11 of 11 places loaded it, typical 900 to 1040 ms00:25-00:30 UTC: 9 of 11 places loaded it, typical 739 ms00:30-00:35 UTC: 11 of 11 places loaded it, typical 719 ms00:35-00:40 UTC: 10 of 11 places loaded it, typical 1477 ms00:40-00:45 UTC: 11 of 11 places loaded it, typical 743 ms00:45-00:50 UTC: 10 of 11 places loaded it, typical 701 ms00:50-01:15 UTC: 11 of 11 places loaded it, typical 737 to 1388 ms01:15-01:20 UTC: 10 of 11 places loaded it, typical 773 ms01:20-01:45 UTC: 11 of 11 places loaded it, typical 695 to 1257 ms01:45-01:55 UTC: 10 of 11 places loaded it, typical 1029 to 1124 ms01:55-02:15 UTC: 11 of 11 places loaded it, typical 727 to 837 ms02:15-02:45 UTC: 10 of 11 places loaded it, typical 735 to 1145 ms02:45-02:50 UTC: 11 of 11 places loaded it, typical 760 ms02:50-02:55 UTC: 10 of 11 places loaded it, typical 1117 ms02:55-03:05 UTC: 11 of 11 places loaded it, typical 656 to 710 ms03:05-03:15 UTC: 10 of 11 places loaded it, typical 740 to 1137 ms03:15-03:25 UTC: 11 of 11 places loaded it, typical 845 to 887 ms03:25-03:30 UTC: 10 of 11 places loaded it, typical 730 ms03:30-03:40 UTC: 11 of 11 places loaded it, typical 738 to 1490 ms03:40-03:45 UTC: 10 of 11 places loaded it, typical 1556 ms03:45-04:10 UTC: 11 of 11 places loaded it, typical 707 to 1481 ms04:10-04:15 UTC: 10 of 11 places loaded it, typical 1075 ms04:15-04:45 UTC: 11 of 11 places loaded it, typical 717 to 878 ms04:45-04:50 UTC: 9 of 11 places loaded it, typical 1408 ms04:50-05:00 UTC: 11 of 11 places loaded it, typical 729 to 803 ms05:00-05:10 UTC: 10 of 11 places loaded it, typical 711 to 996 ms05:10-06:00 UTC: 11 of 11 places loaded it, typical 672 to 1478 ms06:00-06:15 UTC: 10 of 11 places loaded it, typical 764 to 1111 ms06:15-06:50 UTC: 11 of 11 places loaded it, typical 734 to 1030 ms06:50-06:55 UTC: 10 of 11 places loaded it, typical 808 ms06:55-07:00 UTC: 11 of 11 places loaded it, typical 1453 ms07:00-07:05 UTC: 10 of 10 places loaded it, typical 1287 ms07:05-07:25 UTC: 11 of 11 places loaded it, typical 708 to 796 ms07:25-07:30 UTC: 10 of 11 places loaded it, typical 704 ms07:30-07:40 UTC: 11 of 11 places loaded it, typical 720 to 1421 ms07:40-07:45 UTC: 9 of 11 places loaded it, typical 705 ms07:45-08:15 UTC: 11 of 11 places loaded it, typical 760 to 1505 ms08:15-08:20 UTC: 10 of 11 places loaded it, typical 747 ms08:20-08:35 UTC: 11 of 11 places loaded it, typical 736 to 1335 ms08:35-08:40 UTC: 10 of 11 places loaded it, typical 1079 ms08:40-09:05 UTC: 11 of 11 places loaded it, typical 684 to 1241 ms09:05-09:10 UTC: 10 of 11 places loaded it, typical 785 ms09:10-09:15 UTC: 11 of 11 places loaded it, typical 794 ms09:15-09:20 UTC: 9 of 10 places loaded it, typical 756 ms09:20-09:25 UTC: 11 of 11 places loaded it, typical 808 ms09:25-09:30 UTC: 9 of 11 places loaded it, typical 1423 ms09:30-09:40 UTC: 11 of 11 places loaded it, typical 723 to 884 ms09:40-09:45 UTC: 10 of 11 places loaded it, typical 690 ms09:45-09:50 UTC: 11 of 11 places loaded it, typical 788 ms09:50-10:05 UTC: 10 of 11 places loaded it, typical 661 to 718 ms10:05-10:15 UTC: 11 of 11 places loaded it, typical 752 to 783 ms10:15-10:20 UTC: 5 of 5 places loaded it, typical 854 ms10:20-10:25 UTC: 10 of 11 places loaded it, typical 1108 ms10:25-10:55 UTC: 11 of 11 places loaded it, typical 716 to 1445 ms10:55-11:00 UTC: 10 of 11 places loaded it, typical 749 ms11:00-11:15 UTC: 11 of 11 places loaded it, typical 778 to 864 ms11:15-11:20 UTC: 10 of 11 places loaded it, typical 803 ms11:20-11:35 UTC: 11 of 11 places loaded it, typical 769 to 1555 ms11:35-11:40 UTC: 5 of 5 places loaded it, typical 750 ms11:40-12:15 UTC: 11 of 11 places loaded it, typical 749 to 958 ms12:15-12:20 UTC: 10 of 11 places loaded it, typical 872 ms12:20-13:05 UTC: 11 of 11 places loaded it, typical 746 to 1460 ms13:05-13:10 UTC: 10 of 11 places loaded it, typical 883 ms13:10-13:15 UTC: 9 of 11 places loaded it, typical 784 ms13:15-13:20 UTC: 10 of 11 places loaded it, typical 721 ms13:20-14:00 UTC: 11 of 11 places loaded it, typical 737 to 1451 ms14:00-14:05 UTC: 10 of 11 places loaded it, typical 715 ms14:05-14:50 UTC: 11 of 11 places loaded it, typical 716 to 1590 ms14:50-14:55 UTC: 10 of 11 places loaded it, typical 890 ms14:55-15:05 UTC: 11 of 11 places loaded it, typical 743 to 879 ms15:05-15:10 UTC: 10 of 11 places loaded it, typical 754 ms15:10-15:35 UTC: 11 of 11 places loaded it, typical 765 to 1482 ms15:35-15:40 UTC: 10 of 11 places loaded it, typical 851 ms15:40-16:05 UTC: 11 of 11 places loaded it, typical 756 to 1480 ms16:05-16:15 UTC: 10 of 11 places loaded it, typical 725 to 813 ms16:15-16:45 UTC: 11 of 11 places loaded it, typical 739 to 859 ms16:45-16:50 UTC: 10 of 11 places loaded it, typical 1091 ms16:50-17:30 UTC: 11 of 11 places loaded it, typical 742 to 1556 ms17:30-17:35 UTC: 10 of 11 places loaded it, typical 735 ms17:35-18:05 UTC: 11 of 11 places loaded it, typical 756 to 1349 ms18:05-18:15 UTC: 10 of 11 places loaded it, typical 1063 to 1219 ms18:15-18:20 UTC: 11 of 11 places loaded it, typical 778 ms18:20-18:30 UTC: 10 of 11 places loaded it, typical 779 to 1011 ms18:30-18:35 UTC: 11 of 11 places loaded it, typical 962 ms18:35-18:40 UTC: 10 of 11 places loaded it, typical 1607 ms18:40-19:25 UTC: 11 of 11 places loaded it, typical 662 to 1515 ms19:25-19:30 UTC: 10 of 11 places loaded it, typical 731 ms19:30-19:40 UTC: 11 of 11 places loaded it, typical 748 to 793 ms19:40-19:45 UTC: 10 of 11 places loaded it, typical 768 ms19:45-19:55 UTC: 11 of 11 places loaded it, typical 749 to 802 ms19:55-20:00 UTC: 10 of 11 places loaded it, typical 756 ms20:00-20:30 UTC: 11 of 11 places loaded it, typical 732 to 1306 ms20:30-20:35 UTC: 4 of 4 places loaded it, typical 541 ms Typical response time of the places that loaded it, at most 1619 ms

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

Tinted columns: when Ncrvoyix's status page showed a partial outage, a major outage or maintenance, as we read it every 15 minutes; the times are when we saw it, not when the provider posted it. Strip under the bars: how many places loaded ncrvoyix.com in each 5 minutes, of those that checked, and the line under it their typical response time. Any answer from the website counts as loaded, even an error page; 24 places that usually can't load it are left out. Website checks don't test sign-in, payments or every feature. Tinted columns and our checks are worldwide; the bars count reports from Fr. S. Antarctic Lands only.

Latest checks, 20:30-20:35 UTC: 4 of 4 places loaded it, typical 541 ms.

Report totals as of 7 Nov, 20:33 UTC

Report a problem with Ncrvoyix

Choose where you are, then tap what isn't working. Tapping a problem sends your report; no account needed.

What isn't working? Tap one to send

Anonymous · one report per service per hour. This adds your experience to the chart; the provider is not contacted.

Compare worldwide reports · Other services in Fr. S. Antarctic Lands

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 Fr. S. Antarctic Lands. The report chart above is filtered to Fr. S. Antarctic Lands.

Our own checks of ncrvoyix.com

Every 5 minutes, from our probes

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

Doha: loaded in 965 ms Hong Kong: loaded in 1258 ms Madrid: loaded in 687 ms New Jersey: loaded in 229 ms Singapore: loaded in 1712 ms Tokyo: loaded in 1163 ms Delhi: loaded in 1718 ms Atlanta: loaded in 425 ms Warsaw: loaded in 780 ms Portsmouth: loaded in 787 ms Toronto: loaded in 295 ms New York: loaded in 216 ms Hamina: loaded in 759 ms Seattle: loaded in 517 ms St. Louis: loaded in 329 ms Mumbai: loaded in 1586 ms São Paulo: loaded in 692 ms Jakarta: loaded in 1108 ms Dallas: loaded in 440 ms Melbourne: loaded in 1318 ms Cape Town: loaded in 1541 ms Los Angeles: loaded in 585 ms Sydney: loaded in 1392 ms Port Louis: loaded in 2181 ms Lauterbourg: loaded in 785 ms Bangalore: loaded in 1893 ms Seoul: 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) Frankfurt: could not load it (Unresolvable: Cannot resolve ncrvoyix.com: No address associ) Amsterdam: 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) Santiago: 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) Johannesburg: 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)
  • DohaReachable965 ms, just now
  • Hong KongReachable1258 ms, just now
  • SeoulName does not resolve13 ms, just now
  • LondonName does not resolve2 ms, just now
  • FrankfurtName does not resolve1 ms, just now
  • AmsterdamName does not resolve2 ms, just now
  • MadridReachable687 ms, just now
  • New JerseyReachable229 ms, just now
  • OsakaName does not resolve2 ms, just now
  • SantiagoName does not resolve1 ms, just now
  • QuerétaroName does not resolve1 ms, just now
  • JohannesburgName does not resolve11 ms, just now
  • SingaporeReachable1712 ms, just now
  • Tel AvivName does not resolve13 ms, just now
  • TokyoReachable1163 ms, just now
  • DelhiReachable1718 ms, just now
  • AtlantaReachable425 ms, just now
  • WarsawReachable780 ms, just now
  • PortsmouthReachable787 ms, just now
  • TorontoReachable295 ms, just now
  • New YorkReachable216 ms, just now
  • HaminaReachable759 ms, 4 min ago
  • SeattleReachable517 ms, 4 min ago
  • St. LouisReachable329 ms, 4 min ago
  • MumbaiReachable1586 ms, 4 min ago
  • São PauloReachable692 ms, 4 min ago
  • JakartaReachable1108 ms, 4 min ago
  • DallasReachable440 ms, 4 min ago
  • MelbourneReachable1318 ms, 4 min ago
  • Cape TownReachable1541 ms, 4 min ago
  • Los AngelesReachable585 ms, 4 min ago
  • SydneyReachable1392 ms, 4 min ago
  • Port LouisReachable2181 ms, 4 min ago
  • LauterbourgReachable785 ms, 5 min ago
  • BangaloreReachable1893 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

Voyix Pay

  • Settlement & Funding-NAMERMaintenance

296 other parts are working.

Incidents and maintenance

Maintenance

  • Voyix Pay Scheduled Maintenance - Phase 2 (now) 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

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

Of the last 90 days, 2 had a partial or major outage, 3 had maintenance only and 85 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

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 Fr. S. Antarctic Lands 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?

Ncrvoyix is doing planned maintenance, so some parts may not work right now. It is probably not just you.

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.

Other services in Payments and shops

Each card shows that service's own status, not Ncrvoyix's. A problem listed here does not mean Ncrvoyix has one.

See the live outage feed for Fr. S. Antarctic Lands · Find another service