status.idexx.com
Active Incident
If you are currently experiencing an issue that is not displayed on this page, please contact the Help Desk at x6HELP for assistance.

Scheduled Maintenance

PLANNED MAINTENANCE: STRAPI CMSPlanned Maintenance

Schedule

June 17, 2024 4:00PM - 6:00PM EDT

Components

Strapi CMS

Description

Subject: PLANNED MAINTENANCE: STRAPI CMS Incident Statement: Strapi CMS and OS Maintenance June 17, 2024 4:00PM - 6:00PM ET. Strapi application will not be available for a few minutes during the window as the OS updates are applied. Application(s) Impacted: Strapi CMS and CMS Publishing Group(s) Impacted: Marketing Region(s) Impacted: Global Maintenance Team(s): CX Billing and Self-Service Business Impact: Strapi CMS and CMS Publishing unavailable
OUTAGE NOTIFICATION - Altamonte Springs FloridaNetwork Outage

Incident Status

Network Outage

Components

Network/WiFi/Power


June 14, 2024 8:29AM EDT
[Investigating] OUTAGE NOTIFICATION - Altamonte Springs Florida Incident Statement: network is currently offline Groups impacted: Altamonte Springs Florida Resolution Team: Network Operations ETA for resolution: Unknown
OUTAGE NOTIFICATION - Vienna Austria LabNetwork Outage

Incident Status

Network Outage

Components

Network/WiFi/Power


June 13, 2024 2:32PM EDT
[Investigating] Incident: The Vienna Austria lab network is currently offline Incident Statement: The lab network is currently offline due to what may be a power related issue. Impact: IDEXX employees at the lab will not have access to IDEXX resources or the internet until the issue is resolved. Groups impacted: Vienna Austria Lab employees Resolution Team: Network Operations ETA for resolution: Unknown
North American Transportation OperationsPerformance Degradation

Incident Status

Performance Degradation

Components

Courier/Transportation System (VCR)


June 14, 2024 7:23PM EDT
[Monitoring] Update #3 - Systems are responding favorably to work being done. IVR call handling volumes are improving and the route reconciliation dashboard has seen consistent behavior throughout the day. Courier vendor traffic and customer pickup data is becoming more consistent and timely. Continuing to prioritize adding capacity to the infrastructure, increasing stability and resiliency. Work and monitoring expecting to continue throughout the weekend. Any changes to performance through the weekend will be reported out via status.idexxi.com. Otherwise, expect additional updates on Monday. Update #2 - Vendor has applied a hot-fix to the environment and teams continue to monitor the system, which has stabilized, and performance is returning to normal. However, we are still receiving sporadic reports of vendors unable to connect to our system, and we are investigating. Additionally, the teams are working on updates to add capacity to the infrastructure, increasing stability and resiliency. Incident Statement: System resources appear to be stabilizing and activity showing positive results. May expect some minor residual symptoms today, but with few interruptions. Reloading the dashboard should work in the event you get a 502 Gateway timeout error. We are continuing to troubleshoot and monitor throughout the week. Group and Region Impacted: North America Transportation Operations Impacted Applications: VCR API – Dashboards Business Impact: May anticipate some small system resource constraints as the systems and data continue to catch up. There may be some intermittent timeout issues on the IVR , the API and the dashboard. Reloading the dashboard should work to solve the inability to load or reconcile a route. We are continuing to troubleshoot and monitor. Resolution Team: Product Manager, InfiniGIS Development Team, Core Platform Services   ETA for Resolution: Unknown   Next Update: Monday, June 24, 2024, 10:00 a.m. EDT

June 14, 2024 1:05PM EDT
[Monitoring] Update #2 - Vendor has applied a hot-fix to the environment and teams continue to monitor the system, which has stabilized, and performance is returning to normal. However, we are still receiving sporadic reports of vendors unable to connect to our system, and we are investigating. Additionally, the teams are working on updates to add capacity to the infrastructure, increasing stability and resiliency. Incident Statement: System resources appear to be stabilizing and activity showing positive results. May expect some minor residual symptoms today, but with few interruptions. Reloading the dashboard should work in the event you get a 502 Gateway timeout error. We are continuing to troubleshoot and monitor throughout the week. Group and Region Impacted: North America Transportation Operations Impacted Applications: VCR API – Dashboards Business Impact: May anticipate some small system resource constraints as the systems and data continue to catch up. There may be some intermittent timeout issues on the IVR , the API and the dashboard. Reloading the dashboard should work to solve the inability to load or reconcile a route. We are continuing to troubleshoot and monitor. Resolution Team: Product Manager, InfiniGIS Development Team, Core Platform Services   ETA for Resolution: Unknown   Next Update: Friday, June 14, 2024, End of Day

June 14, 2024 12:59PM EDT
[Monitoring] Update #2 - Vendor has applied a hot-fix to the environment and teams continue to monitor the system, which has stabilized, and performance is returning to normal. The teams are working on updates to add capacity to the infrastructure, increasing stability and resiliency. Incident Statement: System resources appear to be stabilizing and activity showing positive results. May expect some minor residual symptoms today, but with few interruptions. Reloading the dashboard should work in the event you get a 502 Gateway timeout error. We are continuing to troubleshoot and monitor throughout the week. Group and Region Impacted: North America Transportation Operations Impacted Applications: VCR API – Dashboards Business Impact: May anticipate some small system resource constraints as the systems and data continue to catch up. There may be some intermittent timeout issues on the IVR , the API and the dashboard. Reloading the dashboard should work to solve the inability to load or reconcile a route. We are continuing to troubleshoot and monitor. Resolution Team: Product Manager, InfiniGIS Development Team, Core Platform Services   ETA for Resolution: Unknown   Next Update: Friday, June 14, 2024, End of Day

June 12, 2024 2:56PM EDT
[Investigating] PERFORMANCE DEGREDATION 4-Low: Critical system is available without risk; Users still able to work. Non-Critical system is partially degraded and/or users are still able to accomplish some but not all of their day to day tasks. Incident Statement: System resources appear to be stabilizing and activity showing positive results. May expect some minor residual symptoms today, but with few interruptions. Reloading the dashboard should work in the event you get a 502 Gateway timeout error. We are continuing to troubleshoot and monitor throughout the week. Group(s) Impacted: North America Transportation Operations Region(s) Impacted: North America Transportation Operations Impacted Applications: VCR API – Dashboards Business Impact: May anticipate some small system resource constraints as the systems and data continue to catch up. There may be some intermittent timeout issues on the IVR , the API and the dashboard. Reloading the dashboard should work to solve the inability to load or reconcile a route. We are continuing to troubleshoot and monitor. Resolution Team(s): Product Manager and InfiniGIS Development Team   ETA for Resolution: Unknown   Next Update: End of Day Additional Comments:

June 11, 2024 2:11PM EDT
[Investigating] 2-High: Critical system is partially degraded and/or users are still able to accomplish some tasks but not all of their day to day tasks. Incident Statement: Continued system resource constraints causing intermittent timeout issues on the IVR , the API and the dashboard. Reloading the dashboard should work to solve the inability to load or reconcile a route. We are continuing to troubleshoot and monitor. Group(s) Impacted: North America Transportation Operations Region(s) Impacted: North America Transportation Operations Impacted Applications: VCR API – Dashboards Business Impact: Continued system resource constraints causing intermittent timeout issues on the IVR , the API and the dashboard. Reloading the dashboard should work to solve the inability to load or reconcile a route. We are continuing to troubleshoot and monitor. Resolution Team(s): Product Manager and InfiniGIS Development Team ETA for Resolution: Unknown Next Update: End of Day

June 10, 2024 8:35PM EDT
[Investigating] PERFORMANCE DEGREDATION 4-Low: Critical system is available without risk; Users still able to work. Non-Critical system is partially degraded and/or users are still able to accomplish some but not all of their day to day tasks. Incident Statement: Some vendors having issues sending stop data due to a backup in sending/ receiving data. As a result, the transportation TMS system and the Route Reconciliation dashboard are not maintaining synced data with the status of the routes that includes arrival, departure, and bag count. Labs are receiving routes before the system has caught up, causing the labs to have to blind reconcile. Working as quickly as possible to resolve this issue. Group(s) Impacted: North America Transportation Operations Region(s) Impacted: North America Transportation Operations Impacted Applications: VCR API – Dashboards Business Impact: Transportation is experiencing significant delays in receiving some courier route data. The result at times can be vendors repeatedly attempting to send data that our system is rejecting, which is causing their queue to stack up and not be able to send us validated data. I am currently working with vendors to troubleshoot their issues and catch up these routes. Resolution Team(s): Product Manager and InfiniGIS Development Team   ETA for Resolution: Unknown   Next Update: End of Day
PERFORMANCE DEGRADATION - LYNXXOperational

Incident Status

Operational

Components

LYNXX


May 29, 2024 5:51PM EDT
[Monitoring] Update #6 - Development activities continue, with a target date of June 13, 2024 for production implementation. IT Lab Ops continues to check daily for stuck accessions; none found since Thursday, May 23. These updates will be paused until the maintenance is complete on June 13, unless new information or issues arise. Update #5 - Development activities still on track and expected to be ready for production late next week. IT Lab Ops continues to check daily for orders stuck in LYNXX. No accessions have been found since Thursday, May 23. Update #4: Items continue on track. IT Lab Ops will continue to perform the manual process to check for orders stuck in LYNXX. This process will be performed 5:00 – 6:00 p.m. EDT, over the weekend/US holiday. Update #3: The manual procedure to check for orders stuck in LYNXX and re-release them, remains in place. A monitoring process for accessions released in LYNXX but partial/unreleased in VC+ is still under assessment. These continue to be escalated to Customer Service and Lab Liaisons. IT Teams are making progress on a permanent fix for these issues. Update #2: IT Teams continue to evaluate options for a monitoring process to identify accessions that are released in LYNXX but are partial/unreleased in VC+. Progress on permanent solutions for these issues continue. Update #1: For Orders stuck in LYNXX and partial in VC+: IT is running a manual procedure to check for accessions and re-release them. This process will continue to be ran at 5:00 – 6:00 p.m. EDT and 7:00 – 8:00 a.m. EDT, for the rest of the week and then once a day over the weekend/US holiday. For Orders released in LYNXX and partial/unreleased in VC+: IT is working on a monitoring process to identify these accessions, in the meantime, these will continue to be escalated to Customer Service and Lab Liaisons. Teams are currently working on a permanent fix for these issues. Severity: Medium Incident Start Date and Time: May 17th 9:30 am ET (estimated) Incident Statement: This is a continuation of the IT Notification issued and resolved last week. We are still seeing a spike in escalations to Customer Support and the Lab Liaisons to re-release accessions which are not syncing properly from LYNXX to VC+. Two issues have been identified and being worked on by teams. Orders are showing as stuck in LYNXX and partial/unreleased in VC+. IT has instituted a manual process to check for these accessions and re-release them two times each day. Run times are 5:00 – 6:00 p.m. EDT and 7:00 – 8:00 a.m. EDT. This will continue daily until a permanent fix is in place. Orders are showing as expected in LYNXX and partial/unreleased in VC+. Currently there is not a way to identify these as they show completely resulted in LYNXX, so these will continue to be escalated to Customer Service and Lab Liaisons. Groups and Regions Impacted: US and Canada Customer Support Application Impacted: LYNXX Business Impact: Some results are not fully releasing through our ecosystem, causing increased customer calls that require manual re-rereleasing. Resolution Teams: LYNXX Developers, LYNXX SRE, RDE Developers, Enterprise Architecture, Middleware, VC+ Team, Enterprise IT Lab Ops. Next Update: Thursday, June 13, 2024 upon maintenance completion.

May 28, 2024 4:17PM EDT
[Monitoring] Update #5 - Development activities still on track and expected to be ready for production late next week. IT Lab Ops continues to check daily for orders stuck in LYNXX. No accessions have been found since Thursday, May 23. Update #4: Items continue on track. IT Lab Ops will continue to perform the manual process to check for orders stuck in LYNXX. This process will be performed 5:00 – 6:00 p.m. EDT, over the weekend/US holiday. Update #3: The manual procedure to check for orders stuck in LYNXX and re-release them, remains in place. A monitoring process for accessions released in LYNXX but partial/unreleased in VC+ is still under assessment. These continue to be escalated to Customer Service and Lab Liaisons. IT Teams are making progress on a permanent fix for these issues. Update #2: IT Teams continue to evaluate options for a monitoring process to identify accessions that are released in LYNXX but are partial/unreleased in VC+. Progress on permanent solutions for these issues continue. Update #1: For Orders stuck in LYNXX and partial in VC+: IT is running a manual procedure to check for accessions and re-release them. This process will continue to be ran at 5:00 – 6:00 p.m. EDT and 7:00 – 8:00 a.m. EDT, for the rest of the week and then once a day over the weekend/US holiday. For Orders released in LYNXX and partial/unreleased in VC+: IT is working on a monitoring process to identify these accessions, in the meantime, these will continue to be escalated to Customer Service and Lab Liaisons. Teams are currently working on a permanent fix for these issues. Severity: Medium Incident Start Date and Time: May 17th 9:30 am ET (estimated) Incident Statement: This is a continuation of the IT Notification issued and resolved last week. We are still seeing a spike in escalations to Customer Support and the Lab Liaisons to re-release accessions which are not syncing properly from LYNXX to VC+. Two issues have been identified and being worked on by teams. Orders are showing as stuck in LYNXX and partial/unreleased in VC+. IT has instituted a manual process to check for these accessions and re-release them two times each day. Run times are 5:00 – 6:00 p.m. EDT and 7:00 – 8:00 a.m. EDT. This will continue daily until a permanent fix is in place. Orders are showing as expected in LYNXX and partial/unreleased in VC+. Currently there is not a way to identify these as they show completely resulted in LYNXX, so these will continue to be escalated to Customer Service and Lab Liaisons. Groups and Regions Impacted: US and Canada Customer Support Application Impacted: LYNXX Business Impact: Some results are not fully releasing through our ecosystem, causing increased customer calls that require manual re-rereleasing. Resolution Teams: LYNXX Developers, LYNXX SRE, RDE Developers, Enterprise Architecture, Middleware, VC+ Team, Enterprise IT Lab Ops. Next Update: Wednesday, May 29, 4:00 p.m. EDT

May 24, 2024 8:03PM EDT
[Identified] Update #4: Items continue on track. IT Lab Ops will continue to perform the manual process to check for orders stuck in LYNXX. This process will be performed 5:00 – 6:00 p.m. EDT, over the weekend/US holiday. Update #3: The manual procedure to check for orders stuck in LYNXX and re-release them, remain in place. A monitoring process for accessions released in LYNXX but partial/unreleased in VC+ is still under assessment. These continue to be escalated to Customer Service and Lab Liaisons. IT Teams are making progress on a permanent fix for these issues. Update #2: IT Teams continue to evaluate options for a monitoring process to identify accessions that are released in LYNXX but are partial/unreleased in VC+. Progress on permanent solutions for these issues continue. Update #1: For Orders stuck in LYNXX and partial in VC+: IT is running a manual procedure to check for accessions and re-release them. This process will continue to be ran at 5:00 – 6:00 p.m. EDT and 7:00 – 8:00 a.m. EDT, for the rest of the week and then once a day over the weekend/US holiday. For Orders released in LYNXX and partial/unreleased in VC+: IT is working on a monitoring process to identify these accessions, in the meantime, these will continue to be escalated to Customer Service and Lab Liaisons. Teams are currently working on a permanent fix for these issues. Severity: Medium Incident Start Date and Time: May 17th 9:30 am ET (estimated) Incident Statement: This is a continuation of the IT Notification issued and resolved last week. We are still seeing a spike in escalations to Customer Support and the Lab Liaisons to re-release accessions which are not syncing properly from LYNXX to VC+. Two issues have been identified and being worked on by teams. Orders are showing as stuck in LYNXX and partial/unreleased in VC+. IT has instituted a manual process to check for these accessions and re-release them two times each day. Run times are 5:00 – 6:00 p.m. EDT and 7:00 – 8:00 a.m. EDT. This will continue daily until a permanent fix is in place. Orders are showing as expected in LYNXX and partial/unreleased in VC+. Currently there is not a way to identify these as they show completely resulted in LYNXX, so these will continue to be escalated to Customer Service and Lab Liaisons. Groups and Regions Impacted: US and Canada Customer Support Application Impacted: LYNXX Business Impact: Some results are not fully releasing through our ecosystem, causing increased customer calls that require manual re-rereleasing. Resolution Teams: LYNXX Developers, LYNXX SRE, RDE Developers, Enterprise Architecture, Middleware, VC+ Team, Enterprise IT Lab Ops. Next Update: Tuesday, May 28, 10:00 a.m. EDT

May 24, 2024 12:35PM EDT
[Identified] Update #3: The manual procedure to check for orders stuck in LYNXX and re-release them, remain in place. A monitoring process for accessions released in LYNXX but partial/unreleased in VC+ is still under assessment. These continue to be escalated to Customer Service and Lab Liaisons. IT Teams are making progress on a permanent fix for these issues. Update #2: IT Teams continue to evaluate options for a monitoring process to identify accessions that are released in LYNXX but are partial/unreleased in VC+. Progress on permanent solutions for these issues continue. Update #1: For Orders stuck in LYNXX and partial in VC+: IT is running a manual procedure to check for accessions and re-release them. This process will continue to be ran at 5:00 – 6:00 p.m. EDT and 7:00 – 8:00 a.m. EDT, for the rest of the week and then once a day over the weekend/US holiday. For Orders released in LYNXX and partial/unreleased in VC+: IT is working on a monitoring process to identify these accessions, in the meantime, these will continue to be escalated to Customer Service and Lab Liaisons. Teams are currently working on a permanent fix for these issues. Severity: Medium Incident Start Date and Time: May 17th 9:30 am ET (estimated) Incident Statement: This is a continuation of the IT Notification issued and resolved last week. We are still seeing a spike in escalations to Customer Support and the Lab Liaisons to re-release accessions which are not syncing properly from LYNXX to VC+. Two issues have been identified and being worked on by teams. Orders are showing as stuck in LYNXX and partial/unreleased in VC+. IT has instituted a manual process to check for these accessions and re-release them two times each day. Run times are 5:00 – 6:00 p.m. EDT and 7:00 – 8:00 a.m. EDT. This will continue daily until a permanent fix is in place. Orders are showing as expected in LYNXX and partial/unreleased in VC+. Currently there is not a way to identify these as they show completely resulted in LYNXX, so these will continue to be escalated to Customer Service and Lab Liaisons. Groups and Regions Impacted: US and Canada Customer Support Application Impacted: LYNXX Business Impact: Some results are not fully releasing through our ecosystem, causing increased customer calls that require manual re-rereleasing. Resolution Teams: LYNXX Developers, LYNXX SRE, RDE Developers, Enterprise Architecture, Middleware, VC+ Team, Enterprise IT Lab Ops. Next Update: Friday, May 24, 4:00 p.m. EDT

May 23, 2024 4:12PM EDT
[Identified] Update #2: IT Teams continue to evaluate options for a monitoring process to identify accessions that are released in LYNXX but are partial/unreleased in VC+. Progress on permanent solutions for these issues continue. Update #1: For Orders stuck in LYNXX and partial in VC+: IT is running a manual procedure to check for accessions and re-release them. This process will continue to be ran at 5:00 – 6:00 p.m. EDT and 7:00 – 8:00 a.m. EDT, for the rest of the week and then once a day over the weekend/US holiday. For Orders released in LYNXX and partial/unreleased in VC+: IT is working on a monitoring process to identify these accessions, in the meantime, these will continue to be escalated to Customer Service and Lab Liaisons. Teams are currently working on a permanent fix for these issues. Severity: Medium Incident Start Date and Time: May 17th 9:30 am ET (estimated) Incident Statement: This is a continuation of the IT Notification issued and resolved last week. We are still seeing a spike in escalations to Customer Support and the Lab Liaisons to re-release accessions which are not syncing properly from LYNXX to VC+. Two issues have been identified and being worked on by teams. Orders are showing as stuck in LYNXX and partial/unreleased in VC+. IT has instituted a manual process to check for these accessions and re-release them two times each day. Run times are 5:00 – 6:00 p.m. EDT and 7:00 – 8:00 a.m. EDT. This will continue daily until a permanent fix is in place. Orders are showing as expected in LYNXX and partial/unreleased in VC+. Currently there is not a way to identify these as they show completely resulted in LYNXX, so these will continue to be escalated to Customer Service and Lab Liaisons. Groups and Regions Impacted: US and Canada Customer Support Application Impacted: LYNXX Business Impact: Some results are not fully releasing through our ecosystem, causing increased customer calls that require manual re-rereleasing. Resolution Teams: LYNXX Developers, LYNXX SRE, RDE Developers, Enterprise Architecture, Middleware, VC+ Team, Enterprise IT Lab Ops. Next Update: Friday, May 24, 4:00 p.m. EDT

May 23, 2024 10:02AM EDT
[Identified] Update #1: For Orders stuck in LYNXX and partial in VC+: IT is running a manual procedure to check for accessions and re-release them. This process will continue to be ran at 5:00 – 6:00 p.m. EDT and 7:00 – 8:00 a.m. EDT, for the rest of the week and then once a day over the weekend/US holiday. For Orders released in LYNXX and partial/unreleased in VC+: IT is working on a monitoring process to identify these accessions, in the meantime, these will continue to be escalated to Customer Service and Lab Liaisons. Teams are currently working on a permanent fix for these issues. Severity: Medium Incident Start Date and Time: May 17th 9:30 am ET (estimated) Incident Statement: This is a continuation of the IT Notification issued and resolved last week. We are still seeing a spike in escalations to Customer Support and the Lab Liaisons to re-release accessions which are not syncing properly from LYNXX to VC+. Two issues have been identified and being worked on by teams. Orders are showing as stuck in LYNXX and partial/unreleased in VC+. IT has instituted a manual process to check for these accessions and re-release them two times each day. Run times are 5:00 – 6:00 p.m. EDT and 7:00 – 8:00 a.m. EDT. This will continue daily until a permanent fix is in place. Orders are showing as expected in LYNXX and partial/unreleased in VC+. Currently there is not a way to identify these as they show completely resulted in LYNXX, so these will continue to be escalated to Customer Service and Lab Liaisons. Groups and Regions Impacted: US and Canada Customer Support Application Impacted: LYNXX Business Impact: Some results are not fully releasing through our ecosystem, causing increased customer calls that require manual re-rereleasing. Resolution Teams: LYNXX Developers, LYNXX SRE, RDE Developers, Enterprise Architecture, Middleware, VC+ Team, Enterprise IT Lab Ops. Next Update: Thursday, May 23, 4:00 p.m. EDT

May 22, 2024 4:29PM EDT
[Identified] Severity: Medium Incident Start Date and Time: May 17th 9:30 am ET (estimated) Incident Statement: This is a continuation of the IT Notification issued and resolved last week. We are still seeing a spike in escalations to Customer Support and the Lab Liaisons to re-release accessions which are not syncing properly from LYNXX to VC+. Two issues have been identified and being worked on by teams. Orders are showing as stuck in LYNXX and partial/unreleased in VC+. IT has instituted a manual process to check for these accessions and re-release them two times each day. Run times are 5:00 – 6:00 p.m. EDT and 7:00 – 8:00 a.m. EDT. This will continue daily until a permanent fix is in place. Orders are showing as expected in LYNXX and partial/unreleased in VC+. Currently there is not a way to identify these as they show completely resulted in LYNXX, so these will continue to be escalated to Customer Service and Lab Liaisons. Groups and Regions Impacted: US and Canada Customer Support Application Impacted: LYNXX Business Impact: Some results are not fully releasing through our ecosystem, causing increased customer calls that require manual re-rereleasing. Resolution Teams: LYNXX Developers, LYNXX SRE, RDE Developers, Enterprise Architecture, Middleware, VC+ Team, Enterprise IT Lab Ops. Next Update: Thursday, May 23, 10:00 a.m. EDT

ADP

Operational

AirWatch

Operational

Alteryx

Operational

Anaplan

Operational

Avaya Telephone Software

Operational

AWS Large Scale Events

Operational

Beacon

Operational

Benevity Spark

Operational

Billtrust

Operational

BioRad

Operational

Birst

Operational

Bovine Reference Lab

Operational

Box

Operational

Bugzilla

Operational

Business Objects

Operational

Cameleon

Operational

CBS

Operational

Cellavision

Operational

Cellular Services (AT&T/Verizon)

Operational

CLAB

Operational

Clarity

Operational

Clouded Leopard

Performance Degradation

Concur Travel & Expenses

Operational

Content Server

Operational

Courier/Transportation System (VCR)

Performance Degradation

Datadog

Operational

Data Integration Hub (DIH)

Operational

Data Warehouse

Operational

DataPoint

Operational

Diavet

Operational

Digital Cytology

Operational

Docusign

Operational

Einsender

Operational

Enrollment Platform

Operational

Enterprise Alert

Operational

Faxing

Operational

File Shares

Operational

Firstwave

Operational

Genesys Cloud

Operational

GetPaid

Operational

GDOS

Operational

GRIP (Global Results Integration Platform)

Operational

Holon (Voice Picking)

Operational

Horizon (VDI and Applications)

Operational

Humanity

Operational

Idexx.com

Operational

IDEXX Online Orders

Operational

Instrument Manager

Operational

Interactive Intelligence (Genesys Connect)

Operational

Interflex

Operational

Intradexx/Sharepoint

Operational

ISL

Operational

Japan LIMS

Operational

Jira

Operational

KnowBe4

Operational

LabCAT: Griffon

Operational

Labs Instruments

Operational

LDE (Labs Data Exchange)

Operational

LogicManager

Operational

LYNXX

Operational

Managed File Transfer

Operational

MDOS

Operational

Microsoft Office 365

Operational

myIDEXX

Operational

Network/WiFi/Power

Network Outage

NICE Workforce Management

Operational

Novopath

Operational

NuLAB

Operational

OMDM

Operational

PatentSafe

Operational

Pathpixx

Operational

PCR Application Suite (PAS)

Operational

Philips IMS

Operational

Philips IMS - ANZ

Operational

Phocas

Operational

Powerscribe

Operational

Practice Intelligence

Operational

Proofpoint (Security Education Platform)

Operational

PubWeb

Operational

Q-Pulse

Operational

Q-Pulse - ANZ

Operational

Rally

Operational

RDE

Operational

Salesforce

Operational

SAP

Operational

SAS

Operational

SecureLink

Operational

ServiceNow

Operational

Smart Service

Operational

Snowflake

Operational

Solutions Builder

Operational

Splunk

Operational

SpringCM

Operational

StarLIMS - ANZ

Operational

STARLIMS - Brazil

Operational

Strapi CMS

Operational

Synopsys Polaris

Operational

Tableau

Operational

Taxware

Operational

ThanXX (Achievers)

Operational

Unity Connect

Operational

Unity Realtime

Operational

VetMedStat

Operational

VPN

Operational

WebEx

Operational

WebPACS

Operational

Winshuttle

Operational

Workday

Operational

Workflow - ANZ

Operational

XiPay

Operational

Zendesk

Operational