All Systems Operational
PAR POS on Admin25
Operational
UAT Server
Operational
Customer Support Telephone Services
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Oct 25, 2026
No incidents reported today.
Oct 24, 2026
No incidents reported.
Oct 23, 2026
No incidents reported.
Oct 22, 2026
Completed -
The scheduled maintenance has been completed.
Oct 22, 00:30 PDT
Oct 22, 00:30 PDT
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 21, 22:30 PDT
Oct 21, 22:30 PDT
Scheduled -
Admin25 5.16r5 upgrade has been scheduled on 10/21 at 10:30 PM Pacific.
For full system requirements and supported operating systems, please review the PAR POS System Requirements documentation:
https://product-docs.partech.com/docs/par-pos/system-requirements/PAR-POS-Network-Connectivity-Requirements
Oct 20, 13:25 PDT
For full system requirements and supported operating systems, please review the PAR POS System Requirements documentation:
https://product-docs.partech.com/docs/par-pos/system-requirements/PAR-POS-Network-Connectivity-Requirements
Oct 20, 13:25 PDT
Oct 21, 2026
Oct 20, 2026
No incidents reported.
Oct 19, 2026
No incidents reported.
Oct 18, 2026
No incidents reported.
Oct 17, 2026
No incidents reported.
Oct 16, 2026
No incidents reported.
Oct 15, 2026
No incidents reported.
Oct 14, 2026
Completed -
The scheduled maintenance has been completed.
Oct 14, 23:30 PDT
Oct 14, 23:30 PDT
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 14, 22:30 PDT
Oct 14, 22:30 PDT
Scheduled -
PAR has scheduled maintenance on the server hosting the PAR POS instance on 10/14 at 10:30 pm Pacific.
During the maintenance window, customers may experience brief periods of increased latency when accessing the Admin Portal or API endpoints. No prolonged service interruption is expected. We will provide an update once maintenance is complete.
Important Notice for Integrators and Partners:
As part of this maintenance, PAR is implementing updates to our SSL certificate configuration. These updates introduce additional trusted Certificate Authorities (CAs) and result in a change to the certificate chain and trust path used across PAR POS platforms. While existing documentation focuses primarily on in‑store POS environments, these SSL certificate changes also apply to API integrations. Integrations that currently function may encounter connectivity issues if the appropriate root and intermediate certificates are not trusted within partner applications or infrastructure.
PAR platforms utilize a combination of Certificate Authorities, including:
- AWS Certificate Authority
- ssl.com
- Cloudflare Certificate Authorities (including ssl.com–issued certs via Cloudflare)
Required Integrator Action (Strongly Recommended):
All integrators are strongly recommended to validate SSL/TLS connectivity prior to the maintenance window by testing against PAR’s APIINT (integration test) endpoints. These endpoints represent PAR’s two primary certificate authority paths and will help confirm compatibility with the updated trust chain. Successful testing indicates that your integration should continue to function as expected following maintenance.
- https://api-apiint.parpos.com/Sales.svc
- https://api-apiint.brinkpos.net/Sales.svc
In addition, check for the following:
Certificate pinning - If your integration pins to a specific certificate or thumbprint, it will break as once Cloudflare is in front, the certificate presented to the client changes. Confirm that the code either does not pin a certificate, or is updated to pin to the new Cloudflare-issued certificate.
TLS version and SNI - Cloudflare requires TLS 1.2 or higher, and requires SNI (Server Name Indication) in the handshake. If the client is on an older TLS version or an old library that skips SNI, the connection will fail.
Reference Documentation:
- SSL Certificate Validation Document:
- https://cdn.parpos.com/docs/SSLCertificateValidation.pdf
Network Connectivity Requirements:
https://cdn.parpos.com/en/docs/PAR_POS_Network_Connectivity_Requirements_All_In_One.pdf
Support:
If you encounter issues during testing or require additional technical details, please contact your PAR representative or email support.PARPOSsoftware@partech.com.
We appreciate your partnership and proactive validation to ensure uninterrupted service.
Oct 8, 17:51 PDT
During the maintenance window, customers may experience brief periods of increased latency when accessing the Admin Portal or API endpoints. No prolonged service interruption is expected. We will provide an update once maintenance is complete.
Important Notice for Integrators and Partners:
As part of this maintenance, PAR is implementing updates to our SSL certificate configuration. These updates introduce additional trusted Certificate Authorities (CAs) and result in a change to the certificate chain and trust path used across PAR POS platforms. While existing documentation focuses primarily on in‑store POS environments, these SSL certificate changes also apply to API integrations. Integrations that currently function may encounter connectivity issues if the appropriate root and intermediate certificates are not trusted within partner applications or infrastructure.
PAR platforms utilize a combination of Certificate Authorities, including:
- AWS Certificate Authority
- ssl.com
- Cloudflare Certificate Authorities (including ssl.com–issued certs via Cloudflare)
Required Integrator Action (Strongly Recommended):
All integrators are strongly recommended to validate SSL/TLS connectivity prior to the maintenance window by testing against PAR’s APIINT (integration test) endpoints. These endpoints represent PAR’s two primary certificate authority paths and will help confirm compatibility with the updated trust chain. Successful testing indicates that your integration should continue to function as expected following maintenance.
- https://api-apiint.parpos.com/Sales.svc
- https://api-apiint.brinkpos.net/Sales.svc
In addition, check for the following:
Certificate pinning - If your integration pins to a specific certificate or thumbprint, it will break as once Cloudflare is in front, the certificate presented to the client changes. Confirm that the code either does not pin a certificate, or is updated to pin to the new Cloudflare-issued certificate.
TLS version and SNI - Cloudflare requires TLS 1.2 or higher, and requires SNI (Server Name Indication) in the handshake. If the client is on an older TLS version or an old library that skips SNI, the connection will fail.
Reference Documentation:
- SSL Certificate Validation Document:
- https://cdn.parpos.com/docs/SSLCertificateValidation.pdf
Network Connectivity Requirements:
https://cdn.parpos.com/en/docs/PAR_POS_Network_Connectivity_Requirements_All_In_One.pdf
Support:
If you encounter issues during testing or require additional technical details, please contact your PAR representative or email support.PARPOSsoftware@partech.com.
We appreciate your partnership and proactive validation to ensure uninterrupted service.
Oct 8, 17:51 PDT
Oct 13, 2026
No incidents reported.
Oct 12, 2026
No incidents reported.
Oct 11, 2026
No incidents reported.