All Systems Operational
Merchant Control Center   ? Operational
Portal Cloud   ? Operational
Direct Merchant eCommerce   ? Operational
Reseller eCommerce   ? Operational
UPS Shipping - Third Party API   Operational
FedEx Shipping - Third Party API   Operational
Avalara CertCapture   Operational
Avalara Tax Calculation Service   Operational
Salesforce NA10   ? Operational
Salesforce NA17   ? Operational
Salesforce NA30   ? Operational
Salesforce NA11   Operational
Salesforce NA12   Operational
Salesforce NA14   Operational
Salesforce NA15   Operational
Salesforce NA16   Operational
Salesforce NA22   Operational
Salesforce NA23   Operational
Salesforce NA24   Operational
Salesforce NA34   Operational
Win32   Operational
POS Portal Central Office Network   Operational
Louisville Warehouse Network   Operational
Sacramento Warehouse Network   Operational
Call Distribution Center   ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
Schedule Maintenance Jul 22, 21:30-23:30 PDT
There will be scheduled maintenance during this time. Some systems may be unresponsive during the maintenance window.
Posted on Jul 20, 16:49 PDT
POS Portal was acquired by ScanSource in June of 2017. As part of that acquisition, we have started to integrate the POS Portal network with ScanSource. This is scheduled to complete on September 10, 2018. The following items will be changing as part of this transition:

• Domains – after the transition, all communication will use @scansource email addresses. The @posportal.com domain will remain a valid domain after the transition.
• IP Addresses – The IP addresses used by POS Portal will be changing.

The following items will not be changing as part of the integration:
• Phone numbers
• Fax numbers

Action items you should be prepared to take in advance of September 10th:
• Update whitelists to include the ScanSource.com domain and the new IP addresses.
• Update firewall rules to include the ScanSource.com domain and the new IP addresses
• Test connectivity

A testing environment will be made available for you to validate connectivity. More details on this testing environment will be published in July.

Please provide us with the contact to provide the new IP addresses that need to be whitelisted. You can email the contact information to scansource-integration@posportal.com.

We are available for discussion during the process or to review any details of the transition your team may have. Please submit any questions to scansource-integration@posportal.com. Using this email will ensure all communication receives a timely response.
Posted on Jun 4, 07:35 PDT
Past Incidents
Jul 20, 2018

No incidents reported today.

Jul 19, 2018

No incidents reported.

Jul 18, 2018

No incidents reported.

Jul 17, 2018
Resolved - The changes implemented last night have addressed the issue with the transaction throughput.
Jul 17, 05:55 PDT
Monitoring - A solution has been implemented to address the performance issue with the application. This will be monitored for 24 hours to validate ensure the issue has been addressed. The next update will be no later than 8 AM PST on 7/17/2018.
Jul 16, 21:31 PDT
Investigating - We are investigating slow response times with API and Portal Access services.
Jul 16, 14:40 PDT
Jul 15, 2018

No incidents reported.

Jul 14, 2018

No incidents reported.

Jul 13, 2018

No incidents reported.

Jul 12, 2018

No incidents reported.

Jul 11, 2018

No incidents reported.

Jul 10, 2018

No incidents reported.

Jul 9, 2018

No incidents reported.

Jul 8, 2018

No incidents reported.

Jul 7, 2018

No incidents reported.

Jul 6, 2018
Postmortem - Read details
Jul 8, 11:56 PDT
Resolved - This incident is now closed. The RFO will be posted within 24 hours.
Jul 6, 17:19 PDT
Update - The issues has been addressed. We will continue to monitor to ensure there are no further issues.
Jul 6, 07:42 PDT
Monitoring - A fix has been implemented and we are monitoring the results.
Jul 6, 07:40 PDT
Identified - We are experiencing an issue with system connectivity. The issue has been identified and we are working to resolve.
Jul 6, 07:15 PDT