All Systems Operational
DATA IN
Operational
CSG S1 01 - Europe (Frankfurt)
Operational
CSG S1 02 - Europe (Frankfurt)
Operational
CSG S2 - Europe (Frankfurt)
Operational
CSG S1 - US East (N. Virginia)
Operational
CSG S2 - US East (N. Virginia)
Operational
CSG S3 - US East (N. Virginia)
Operational
CSG S4 - US East (N. Virginia)
Operational
KW S1 - US East (N. Virginia)
Operational
KW S2 - US East (N. Virginia)
Operational
KW S3 - US East (N. Virginia)
Operational
KW S4 - US East (N. Virginia)
Operational
KW S5 - US East (N. Virginia)
Operational
KW S1 - US West (Oregon)
Operational
PROFILING
Operational
CSG S1 01 - Europe (Frankfurt)
Operational
CSG S1 02 - Europe (Frankfurt)
Operational
CSG S2 - Europe (Frankfurt)
Operational
CSG S1 - US East (N. Virginia)
Operational
CSG S2 - US East (N. Virginia)
Operational
CSG S3 - US East (N. Virginia)
Operational
CSG S4 - US East (N. Virginia)
Operational
KW S1 - US East (N. Virginia)
Operational
KW S2 - US East (N. Virginia)
Operational
KW S3 - US East (N. Virginia)
Operational
KW S4 - US East (N. Virginia)
Operational
KW S5 - US East (N. Virginia)
Operational
KW S1 - US West (Oregon)
Operational
JOURNEY ORCHESTRATION
Operational
CSG S1 01 - Europe (Frankfurt)
Operational
CSG S1 02 - Europe (Frankfurt)
Operational
CSG S2 - Europe (Frankfurt)
Operational
CSG S1 - US East (N. Virginia)
Operational
CSG S2 - US East (N. Virginia)
Operational
CSG S3 - US East (N. Virginia)
Operational
CSG S4 - US East (N. Virginia)
Operational
KW S1 - US East (N. Virginia)
Operational
KW S2 - US East (N. Virginia)
Operational
KW S3 - US East (N. Virginia)
Operational
KW S4 - US East (N. Virginia)
Operational
KW S5 - US East (N. Virginia)
Operational
KW S1 - US West (Oregon)
Operational
COMMUNICATIONS
Operational
CX Channels - SMS - Omaha Data Center 1
Operational
CX Channels - SMS - Omaha Data Center 2
Operational
CX Channels - SMS - Azure East US
Operational
CX Channels - SMS - Azure West US
Operational
CX Channels - MMS - Omaha Data Center 1
Operational
CX Channels - MMS - Omaha Data Center 2
Operational
CX Channels - MMS - Azure East US
Operational
CX Channels - MMS - Azure West US
Operational
CX Channels - Voice - Omaha Data Center 1
Operational
CX Channels - Voice - Omaha Data Center 2
Operational
CX Channels - Voice - Azure East US
Operational
CX Channels - Voice - Azure West US
Operational
CX Channels - RCS - Omaha Data Center 1
Operational
CX Channels - RCS - Omaha Data Center 2
Operational
CX Channels - RCS - Azure East US
Operational
CX Channels - RCS - Azure West US
Operational
CX Channels - Email - AWS US East (N. Virginia)
Operational
CX Channels - Email - AWS EU Central (Frankfurt)
Operational
CX Channels - Email - Omaha Data Center 1
Operational
ANALYTICS
Operational
CSG S1 01 - Europe (Frankfurt)
Operational
CSG S1 02 - Europe (Frankfurt)
Operational
CSG S2 - Europe (Frankfurt)
Operational
CSG S1 - US East (N. Virginia)
Operational
CSG S2 - US East (N. Virginia)
Operational
CSG S3 - US East (N. Virginia)
Operational
CSG S4 - US East (N. Virginia)
Operational
KW S1 - US East (N. Virginia)
Operational
KW S2 - US East (N. Virginia)
Operational
KW S3 - US East (N. Virginia)
Operational
KW S4 - US East (N. Virginia)
Operational
KW S5 - US East (N. Virginia)
Operational
KW S1 - US West (Oregon)
Operational
DATA OUT
Operational
CSG S1 01 - Europe (Frankfurt)
Operational
CSG S1 02 - Europe (Frankfurt)
Operational
CSG S2 - Europe (Frankfurt)
Operational
CSG S1 - US East (N. Virginia)
Operational
CSG S2 - US East (N. Virginia)
Operational
CSG S3 - US East (N. Virginia)
Operational
CSG S4 - US East (N. Virginia)
Operational
KW S1 - US East (N. Virginia)
Operational
KW S2 - US East (N. Virginia)
Operational
KW S3 - US East (N. Virginia)
Operational
KW S4 - US East (N. Virginia)
Operational
KW S5 - US East (N. Virginia)
Operational
KW S1 - US West (Oregon)
Operational
PREMIUM EXPERIENCE APPLICATIONS
Operational
Batch Commuincations Engine - US East (N. Virginia)
Operational
Bill Explainer Microsite API - US East (N. Virginia)
Operational
Bill Explainer Studio - US East (N. Virginia)
Operational
Payment Reminder Microsite API - US East (N. Virginia)
Operational
Payment Reminder Studio - US East (N. Virginia)
Operational
Xponent Communications Control - US East (N. Virginia)
Operational
Xponent Communications Control - AWS EU Central (Frankfurt)
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Scheduled Maintenance
Xponent Voice & Messaging - BigIP Upgrade Jul 31, 2026 05:00-07:00 UTC
Planned Date:
Start: 07/31/2026 5:00:00 AM UTC
End: 07/31/2026 7:00:00 AM UTC
Summary:
CSG Xponent Voice and Messaging applications will undergo scheduled maintenance, which will impact components "Voice/PRE".
Next Steps:
As we make progress during the maintenance window, we will provide updates. Once the upgrade is complete, all affected components will be marked as complete.
If you notice any unexpected behavior, please contact CSG’s Global Service Desk team via the MyCSG Support portal here: https://www.csgi.com/mycsgcustomer-support/ or call the phone number listed at the bottom of the page for your region.
Posted on Jul 24, 2026 - 12:31 UTC
Start: 07/31/2026 5:00:00 AM UTC
End: 07/31/2026 7:00:00 AM UTC
Summary:
CSG Xponent Voice and Messaging applications will undergo scheduled maintenance, which will impact components "Voice/PRE".
Next Steps:
As we make progress during the maintenance window, we will provide updates. Once the upgrade is complete, all affected components will be marked as complete.
If you notice any unexpected behavior, please contact CSG’s Global Service Desk team via the MyCSG Support portal here: https://www.csgi.com/mycsgcustomer-support/ or call the phone number listed at the bottom of the page for your region.
Posted on Jul 24, 2026 - 12:31 UTC
Batch Communication Engine PROD Release 26.3.2 Jul 31, 2026 10:07-16:07 UTC
We will be deploying updates to Batch Communication Engine as part of the 26.3.2 rollout. This update introduces various application bug fixes.
Posted on Jul 28, 2026 - 10:08 UTC
Posted on Jul 28, 2026 - 10:08 UTC
Xponent Core Upgrade to 26.2.5 – CSG Europe (Frankfurt) Region [1 of 2] Aug 3, 2026 17:00-21:00 UTC
Update -
We will be undergoing scheduled maintenance during this time.
Jul 27, 2026 - 22:14 UTC
Jul 27, 2026 - 22:14 UTC
Scheduled -
Planned Date:
Start: August 03, 2026, 17:00 UTC
End: August 03, 2026, 21:00 UTC
Summary:
Xponent will undergo planned maintenance to upgrade the Xponent Core to version 26.2.5 in the Europe (Frankfurt) region. This release includes enhancements, performance improvements, and bug fixes to improve overall stability and reliability of our Journey Orchestration and Analytics services.
All upgrades will be performed on a rolling basis starting on August 3 and ending on August 6.
There will be no downtime, and all services will remain fully operational during this maintenance window. Customers may notice minor interruption while individual stacks restart. No action is required.
Email Node Template Changes
With this release, Email Nodes will use "Approved" templates instead of "Active" templates. If you have graphs using the Xponent Email node, you will need to complete a post-release check to confirm the expected template, template version, and parameter mappings are still selected correctly.
- Open the graph and review the Xponent Email node configuration.
- Open the template selector and confirm the intended template is available and selected from the Approved templates list.
- Confirm the intended template version is selected.
- Review the parameter mappings and confirm they are still correct.
- If the expected template or version is not selected, update the configuration and redeploy the graph.
Email & Messaging Node Data Persistence
As part of this release, Email and Messaging nodes will start persisting communication data on profile, enabling future profile-based capabilities such as segmentation and reporting. Before invoking an Email or Messaging node, ensure an identifier is mapped in the graph. Identifier mapping is now mandatory for these nodes as communication activity will be persisted on profile.
Full release notes will be available soon at:
https://xponent-knowledge-base.document360.io/docs/xponent-journey-hub-release-notes
Next Steps:
As we make progress during the maintenance window, we will provide updates. Once the upgrade is complete, all affected components will be marked as complete.
If you notice any unexpected behavior, please contact CSG's Global Service Desk team via the MyCSG Support portal here: https://www.csgi.com/mycsgcustomer-support/ or call the phone number listed at the bottom of the page for your region.
Jul 27, 2026 - 21:55 UTC
Start: August 03, 2026, 17:00 UTC
End: August 03, 2026, 21:00 UTC
Summary:
Xponent will undergo planned maintenance to upgrade the Xponent Core to version 26.2.5 in the Europe (Frankfurt) region. This release includes enhancements, performance improvements, and bug fixes to improve overall stability and reliability of our Journey Orchestration and Analytics services.
All upgrades will be performed on a rolling basis starting on August 3 and ending on August 6.
There will be no downtime, and all services will remain fully operational during this maintenance window. Customers may notice minor interruption while individual stacks restart. No action is required.
Email Node Template Changes
With this release, Email Nodes will use "Approved" templates instead of "Active" templates. If you have graphs using the Xponent Email node, you will need to complete a post-release check to confirm the expected template, template version, and parameter mappings are still selected correctly.
- Open the graph and review the Xponent Email node configuration.
- Open the template selector and confirm the intended template is available and selected from the Approved templates list.
- Confirm the intended template version is selected.
- Review the parameter mappings and confirm they are still correct.
- If the expected template or version is not selected, update the configuration and redeploy the graph.
Email & Messaging Node Data Persistence
As part of this release, Email and Messaging nodes will start persisting communication data on profile, enabling future profile-based capabilities such as segmentation and reporting. Before invoking an Email or Messaging node, ensure an identifier is mapped in the graph. Identifier mapping is now mandatory for these nodes as communication activity will be persisted on profile.
Full release notes will be available soon at:
https://xponent-knowledge-base.document360.io/docs/xponent-journey-hub-release-notes
Next Steps:
As we make progress during the maintenance window, we will provide updates. Once the upgrade is complete, all affected components will be marked as complete.
If you notice any unexpected behavior, please contact CSG's Global Service Desk team via the MyCSG Support portal here: https://www.csgi.com/mycsgcustomer-support/ or call the phone number listed at the bottom of the page for your region.
Jul 27, 2026 - 21:55 UTC
Xponent Core Upgrade to 26.2.5 – Kitewheel US East (N. Virginia) Region Aug 4, 2026 05:30-08:30 UTC
Planned Date:
Start: August 04, 2026, 05:30 UTC
End: August 04, 2026, 08:30 UTC
Summary:
Xponent will undergo planned maintenance to upgrade the Xponent Core to version 26.2.5 in the US East (N. Virginia) region. This release includes enhancements, performance improvements, and bug fixes to improve overall stability and reliability of our Journey Orchestration and Analytics services.
All upgrades will be performed on a rolling basis starting on August 3 and ending on August 6.
There will be no downtime, and all services will remain fully operational during this maintenance window. Customers may notice minor interruption while individual stacks restart. No action is required.
Email Node Template Changes
With this release, Email Nodes will use "Approved" templates instead of "Active" templates. If you have graphs using the Xponent Email node, you will need to complete a post-release check to confirm the expected template, template version, and parameter mappings are still selected correctly.
- Open the graph and review the Xponent Email node configuration.
- Open the template selector and confirm the intended template is available and selected from the Approved templates list.
- Confirm the intended template version is selected.
- Review the parameter mappings and confirm they are still correct.
- If the expected template or version is not selected, update the configuration and redeploy the graph.
Email & Messaging Node Data Persistence
As part of this release, Email and Messaging nodes will start persisting communication data on profile, enabling future profile-based capabilities such as segmentation and reporting. Before invoking an Email or Messaging node, ensure an identifier is mapped in the graph. Identifier mapping is now mandatory for these nodes as communication activity will be persisted on profile.
Full release notes will be available soon at:
https://xponent-knowledge-base.document360.io/docs/xponent-journey-hub-release-notes
Next Steps:
As we make progress during the maintenance window, we will provide updates. Once the upgrade is complete, all affected components will be marked as complete.
If you notice any unexpected behavior, please contact CSG's Global Service Desk team via the MyCSG Support portal here: https://www.csgi.com/mycsgcustomer-support/ or call the phone number listed at the bottom of the page for your region.
Posted on Jul 27, 2026 - 22:11 UTC
Start: August 04, 2026, 05:30 UTC
End: August 04, 2026, 08:30 UTC
Summary:
Xponent will undergo planned maintenance to upgrade the Xponent Core to version 26.2.5 in the US East (N. Virginia) region. This release includes enhancements, performance improvements, and bug fixes to improve overall stability and reliability of our Journey Orchestration and Analytics services.
All upgrades will be performed on a rolling basis starting on August 3 and ending on August 6.
There will be no downtime, and all services will remain fully operational during this maintenance window. Customers may notice minor interruption while individual stacks restart. No action is required.
Email Node Template Changes
With this release, Email Nodes will use "Approved" templates instead of "Active" templates. If you have graphs using the Xponent Email node, you will need to complete a post-release check to confirm the expected template, template version, and parameter mappings are still selected correctly.
- Open the graph and review the Xponent Email node configuration.
- Open the template selector and confirm the intended template is available and selected from the Approved templates list.
- Confirm the intended template version is selected.
- Review the parameter mappings and confirm they are still correct.
- If the expected template or version is not selected, update the configuration and redeploy the graph.
Email & Messaging Node Data Persistence
As part of this release, Email and Messaging nodes will start persisting communication data on profile, enabling future profile-based capabilities such as segmentation and reporting. Before invoking an Email or Messaging node, ensure an identifier is mapped in the graph. Identifier mapping is now mandatory for these nodes as communication activity will be persisted on profile.
Full release notes will be available soon at:
https://xponent-knowledge-base.document360.io/docs/xponent-journey-hub-release-notes
Next Steps:
As we make progress during the maintenance window, we will provide updates. Once the upgrade is complete, all affected components will be marked as complete.
If you notice any unexpected behavior, please contact CSG's Global Service Desk team via the MyCSG Support portal here: https://www.csgi.com/mycsgcustomer-support/ or call the phone number listed at the bottom of the page for your region.
Posted on Jul 27, 2026 - 22:11 UTC
Xponent Core Upgrade to 26.2.5 – Kitewheel US West (Oregon) Region Aug 4, 2026 05:30-09:30 UTC
Planned Date:
Start: August 04, 2026, 05:30 UTC
End: August 04, 2026, 08:30 UTC
Summary:
Xponent will undergo planned maintenance to upgrade the Xponent Core to version 26.2.5 in the US West (Oregon) region. This release includes enhancements, performance improvements, and bug fixes to improve overall stability and reliability of our Journey Orchestration and Analytics services.
All upgrades will be performed on a rolling basis starting on August 3 and ending on August 6.
There will be no downtime, and all services will remain fully operational during this maintenance window. Customers may notice minor interruption while individual stacks restart. No action is required.
Email Node Template Changes
With this release, Email Nodes will use "Approved" templates instead of "Active" templates. If you have graphs using the Xponent Email node, you will need to complete a post-release check to confirm the expected template, template version, and parameter mappings are still selected correctly.
- Open the graph and review the Xponent Email node configuration.
- Open the template selector and confirm the intended template is available and selected from the Approved templates list.
- Confirm the intended template version is selected.
- Review the parameter mappings and confirm they are still correct.
- If the expected template or version is not selected, update the configuration and redeploy the graph.
Email & Messaging Node Data Persistence
As part of this release, Email and Messaging nodes will start persisting communication data on profile, enabling future profile-based capabilities such as segmentation and reporting. Before invoking an Email or Messaging node, ensure an identifier is mapped in the graph. Identifier mapping is now mandatory for these nodes as communication activity will be persisted on profile.
Full release notes will be available soon at:
https://xponent-knowledge-base.document360.io/docs/xponent-journey-hub-release-notes
Next Steps:
As we make progress during the maintenance window, we will provide updates. Once the upgrade is complete, all affected components will be marked as complete.
If you notice any unexpected behavior, please contact CSG's Global Service Desk team via the MyCSG Support portal here: https://www.csgi.com/mycsgcustomer-support/ or call the phone number listed at the bottom of the page for your region.
Posted on Jul 27, 2026 - 22:13 UTC
Start: August 04, 2026, 05:30 UTC
End: August 04, 2026, 08:30 UTC
Summary:
Xponent will undergo planned maintenance to upgrade the Xponent Core to version 26.2.5 in the US West (Oregon) region. This release includes enhancements, performance improvements, and bug fixes to improve overall stability and reliability of our Journey Orchestration and Analytics services.
All upgrades will be performed on a rolling basis starting on August 3 and ending on August 6.
There will be no downtime, and all services will remain fully operational during this maintenance window. Customers may notice minor interruption while individual stacks restart. No action is required.
Email Node Template Changes
With this release, Email Nodes will use "Approved" templates instead of "Active" templates. If you have graphs using the Xponent Email node, you will need to complete a post-release check to confirm the expected template, template version, and parameter mappings are still selected correctly.
- Open the graph and review the Xponent Email node configuration.
- Open the template selector and confirm the intended template is available and selected from the Approved templates list.
- Confirm the intended template version is selected.
- Review the parameter mappings and confirm they are still correct.
- If the expected template or version is not selected, update the configuration and redeploy the graph.
Email & Messaging Node Data Persistence
As part of this release, Email and Messaging nodes will start persisting communication data on profile, enabling future profile-based capabilities such as segmentation and reporting. Before invoking an Email or Messaging node, ensure an identifier is mapped in the graph. Identifier mapping is now mandatory for these nodes as communication activity will be persisted on profile.
Full release notes will be available soon at:
https://xponent-knowledge-base.document360.io/docs/xponent-journey-hub-release-notes
Next Steps:
As we make progress during the maintenance window, we will provide updates. Once the upgrade is complete, all affected components will be marked as complete.
If you notice any unexpected behavior, please contact CSG's Global Service Desk team via the MyCSG Support portal here: https://www.csgi.com/mycsgcustomer-support/ or call the phone number listed at the bottom of the page for your region.
Posted on Jul 27, 2026 - 22:13 UTC
Xponent Core Upgrade to 26.2.5 – CSG US East (N. Virginia) Region Aug 5, 2026 05:30-08:30 UTC
Planned Date:
Start: August 05, 2026, 05:30 UTC
End: August 05, 2026, 08:30 UTC
Summary:
Xponent will undergo planned maintenance to upgrade the Xponent Core to version 26.2.5 in the US East (N. Virginia) region. This release includes enhancements, performance improvements, and bug fixes to improve overall stability and reliability of our Journey Orchestration and Analytics services.
All upgrades will be performed on a rolling basis starting on August 3 and ending on August 6.
There will be no downtime, and all services will remain fully operational during this maintenance window. Customers may notice minor interruption while individual stacks restart. No action is required.
Email Node Template Changes
With this release, Email Nodes will use "Approved" templates instead of "Active" templates. If you have graphs using the Xponent Email node, you will need to complete a post-release check to confirm the expected template, template version, and parameter mappings are still selected correctly.
- Open the graph and review the Xponent Email node configuration.
- Open the template selector and confirm the intended template is available and selected from the Approved templates list.
- Confirm the intended template version is selected.
- Review the parameter mappings and confirm they are still correct.
- If the expected template or version is not selected, update the configuration and redeploy the graph.
Email & Messaging Node Data Persistence
As part of this release, Email and Messaging nodes will start persisting communication data on profile, enabling future profile-based capabilities such as segmentation and reporting. Before invoking an Email or Messaging node, ensure an identifier is mapped in the graph. Identifier mapping is now mandatory for these nodes as communication activity will be persisted on profile.
Full release notes will be available soon at:
https://xponent-knowledge-base.document360.io/docs/xponent-journey-hub-release-notes
Next Steps:
As we make progress during the maintenance window, we will provide updates. Once the upgrade is complete, all affected components will be marked as complete.
If you notice any unexpected behavior, please contact CSG's Global Service Desk team via the MyCSG Support portal here: https://www.csgi.com/mycsgcustomer-support/ or call the phone number listed at the bottom of the page for your region.
Posted on Jul 27, 2026 - 22:16 UTC
Start: August 05, 2026, 05:30 UTC
End: August 05, 2026, 08:30 UTC
Summary:
Xponent will undergo planned maintenance to upgrade the Xponent Core to version 26.2.5 in the US East (N. Virginia) region. This release includes enhancements, performance improvements, and bug fixes to improve overall stability and reliability of our Journey Orchestration and Analytics services.
All upgrades will be performed on a rolling basis starting on August 3 and ending on August 6.
There will be no downtime, and all services will remain fully operational during this maintenance window. Customers may notice minor interruption while individual stacks restart. No action is required.
Email Node Template Changes
With this release, Email Nodes will use "Approved" templates instead of "Active" templates. If you have graphs using the Xponent Email node, you will need to complete a post-release check to confirm the expected template, template version, and parameter mappings are still selected correctly.
- Open the graph and review the Xponent Email node configuration.
- Open the template selector and confirm the intended template is available and selected from the Approved templates list.
- Confirm the intended template version is selected.
- Review the parameter mappings and confirm they are still correct.
- If the expected template or version is not selected, update the configuration and redeploy the graph.
Email & Messaging Node Data Persistence
As part of this release, Email and Messaging nodes will start persisting communication data on profile, enabling future profile-based capabilities such as segmentation and reporting. Before invoking an Email or Messaging node, ensure an identifier is mapped in the graph. Identifier mapping is now mandatory for these nodes as communication activity will be persisted on profile.
Full release notes will be available soon at:
https://xponent-knowledge-base.document360.io/docs/xponent-journey-hub-release-notes
Next Steps:
As we make progress during the maintenance window, we will provide updates. Once the upgrade is complete, all affected components will be marked as complete.
If you notice any unexpected behavior, please contact CSG's Global Service Desk team via the MyCSG Support portal here: https://www.csgi.com/mycsgcustomer-support/ or call the phone number listed at the bottom of the page for your region.
Posted on Jul 27, 2026 - 22:16 UTC
Xponent Core Upgrade to 26.2.5 – CSG Europe (Frankfurt) Region [2 of 2] Aug 6, 2026 09:00-12:00 UTC
Planned Date:
Start: August 06, 2026, 09:00 UTC
End: August 06, 2026, 12:00 UTC
Summary:
Xponent will undergo planned maintenance to upgrade the Xponent Core to version 26.2.5 in the Europe (Frankfurt) region. This release includes enhancements, performance improvements, and bug fixes to improve overall stability and reliability of our Journey Orchestration and Analytics services.
All upgrades will be performed on a rolling basis starting on August 3 and ending on August 6.
There will be no downtime, and all services will remain fully operational during this maintenance window. Customers may notice minor interruption while individual stacks restart. No action is required.
Email Node Template Changes
With this release, Email Nodes will use "Approved" templates instead of "Active" templates. If you have graphs using the Xponent Email node, you will need to complete a post-release check to confirm the expected template, template version, and parameter mappings are still selected correctly.
- Open the graph and review the Xponent Email node configuration.
- Open the template selector and confirm the intended template is available and selected from the Approved templates list.
- Confirm the intended template version is selected.
- Review the parameter mappings and confirm they are still correct.
- If the expected template or version is not selected, update the configuration and redeploy the graph.
Email & Messaging Node Data Persistence
As part of this release, Email and Messaging nodes will start persisting communication data on profile, enabling future profile-based capabilities such as segmentation and reporting. Before invoking an Email or Messaging node, ensure an identifier is mapped in the graph. Identifier mapping is now mandatory for these nodes as communication activity will be persisted on profile.
Full release notes will be available soon at:
https://xponent-knowledge-base.document360.io/docs/xponent-journey-hub-release-notes
Next Steps:
As we make progress during the maintenance window, we will provide updates. Once the upgrade is complete, all affected components will be marked as complete.
If you notice any unexpected behavior, please contact CSG's Global Service Desk team via the MyCSG Support portal here: https://www.csgi.com/mycsgcustomer-support/ or call the phone number listed at the bottom of the page for your region.
Posted on Jul 27, 2026 - 22:18 UTC
Start: August 06, 2026, 09:00 UTC
End: August 06, 2026, 12:00 UTC
Summary:
Xponent will undergo planned maintenance to upgrade the Xponent Core to version 26.2.5 in the Europe (Frankfurt) region. This release includes enhancements, performance improvements, and bug fixes to improve overall stability and reliability of our Journey Orchestration and Analytics services.
All upgrades will be performed on a rolling basis starting on August 3 and ending on August 6.
There will be no downtime, and all services will remain fully operational during this maintenance window. Customers may notice minor interruption while individual stacks restart. No action is required.
Email Node Template Changes
With this release, Email Nodes will use "Approved" templates instead of "Active" templates. If you have graphs using the Xponent Email node, you will need to complete a post-release check to confirm the expected template, template version, and parameter mappings are still selected correctly.
- Open the graph and review the Xponent Email node configuration.
- Open the template selector and confirm the intended template is available and selected from the Approved templates list.
- Confirm the intended template version is selected.
- Review the parameter mappings and confirm they are still correct.
- If the expected template or version is not selected, update the configuration and redeploy the graph.
Email & Messaging Node Data Persistence
As part of this release, Email and Messaging nodes will start persisting communication data on profile, enabling future profile-based capabilities such as segmentation and reporting. Before invoking an Email or Messaging node, ensure an identifier is mapped in the graph. Identifier mapping is now mandatory for these nodes as communication activity will be persisted on profile.
Full release notes will be available soon at:
https://xponent-knowledge-base.document360.io/docs/xponent-journey-hub-release-notes
Next Steps:
As we make progress during the maintenance window, we will provide updates. Once the upgrade is complete, all affected components will be marked as complete.
If you notice any unexpected behavior, please contact CSG's Global Service Desk team via the MyCSG Support portal here: https://www.csgi.com/mycsgcustomer-support/ or call the phone number listed at the bottom of the page for your region.
Posted on Jul 27, 2026 - 22:18 UTC