All Systems Operational

Uptime over the past 90 days. View historical uptime.
DATA IN Operational
90 days ago
100.0 % uptime
Today
CSG S1 01 - Europe (Frankfurt) Operational
90 days ago
100.0 % uptime
Today
CSG S1 02 - Europe (Frankfurt) Operational
90 days ago
100.0 % uptime
Today
CSG S2 - Europe (Frankfurt) Operational
90 days ago
100.0 % uptime
Today
CSG S1 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
CSG S2 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
CSG S3 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
CSG S4 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
KW S1 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
KW S2 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
KW S3 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
KW S4 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
KW S5 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
KW S1 - US West (Oregon) Operational
90 days ago
100.0 % uptime
Today
PROFILING Operational
90 days ago
100.0 % uptime
Today
CSG S1 01 - Europe (Frankfurt) Operational
90 days ago
100.0 % uptime
Today
CSG S1 02 - Europe (Frankfurt) Operational
90 days ago
100.0 % uptime
Today
CSG S2 - Europe (Frankfurt) Operational
90 days ago
100.0 % uptime
Today
CSG S1 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
CSG S2 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
CSG S3 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
CSG S4 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
KW S1 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
KW S2 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
KW S3 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
KW S4 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
KW S5 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
KW S1 - US West (Oregon) Operational
90 days ago
100.0 % uptime
Today
JOURNEY ORCHESTRATION Operational
90 days ago
100.0 % uptime
Today
CSG S1 01 - Europe (Frankfurt) Operational
90 days ago
100.0 % uptime
Today
CSG S1 02 - Europe (Frankfurt) Operational
90 days ago
100.0 % uptime
Today
CSG S2 - Europe (Frankfurt) Operational
90 days ago
100.0 % uptime
Today
CSG S1 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
CSG S2 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
CSG S3 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
CSG S4 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
KW S1 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
KW S2 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
KW S3 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
KW S4 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
KW S5 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
KW S1 - US West (Oregon) Operational
90 days ago
100.0 % uptime
Today
COMMUNICATIONS Operational
90 days ago
100.0 % uptime
Today
CX Channels - SMS - Omaha Data Center 1 Operational
90 days ago
100.0 % uptime
Today
CX Channels - SMS - Omaha Data Center 2 Operational
90 days ago
100.0 % uptime
Today
CX Channels - SMS - Azure East US Operational
90 days ago
100.0 % uptime
Today
CX Channels - SMS - Azure West US Operational
90 days ago
100.0 % uptime
Today
CX Channels - MMS - Omaha Data Center 1 Operational
90 days ago
100.0 % uptime
Today
CX Channels - MMS - Omaha Data Center 2 Operational
90 days ago
100.0 % uptime
Today
CX Channels - MMS - Azure East US Operational
90 days ago
100.0 % uptime
Today
CX Channels - MMS - Azure West US Operational
90 days ago
100.0 % uptime
Today
CX Channels - Voice - Omaha Data Center 1 Operational
90 days ago
100.0 % uptime
Today
CX Channels - Voice - Omaha Data Center 2 Operational
90 days ago
100.0 % uptime
Today
CX Channels - Voice - Azure East US Operational
90 days ago
100.0 % uptime
Today
CX Channels - Voice - Azure West US Operational
90 days ago
100.0 % uptime
Today
CX Channels - RCS - Omaha Data Center 1 Operational
90 days ago
100.0 % uptime
Today
CX Channels - RCS - Omaha Data Center 2 Operational
90 days ago
100.0 % uptime
Today
CX Channels - RCS - Azure East US Operational
90 days ago
100.0 % uptime
Today
CX Channels - RCS - Azure West US Operational
90 days ago
100.0 % uptime
Today
CX Channels - Email - AWS US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
CX Channels - Email - AWS EU Central (Frankfurt) Operational
90 days ago
100.0 % uptime
Today
CX Channels - Email - Omaha Data Center 1 Operational
90 days ago
100.0 % uptime
Today
ANALYTICS Operational
90 days ago
100.0 % uptime
Today
CSG S1 01 - Europe (Frankfurt) Operational
90 days ago
100.0 % uptime
Today
CSG S1 02 - Europe (Frankfurt) Operational
90 days ago
100.0 % uptime
Today
CSG S2 - Europe (Frankfurt) Operational
90 days ago
100.0 % uptime
Today
CSG S1 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
CSG S2 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
CSG S3 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
CSG S4 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
KW S1 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
KW S2 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
KW S3 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
KW S4 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
KW S5 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
KW S1 - US West (Oregon) Operational
90 days ago
100.0 % uptime
Today
DATA OUT Operational
90 days ago
100.0 % uptime
Today
CSG S1 01 - Europe (Frankfurt) Operational
90 days ago
100.0 % uptime
Today
CSG S1 02 - Europe (Frankfurt) Operational
90 days ago
100.0 % uptime
Today
CSG S2 - Europe (Frankfurt) Operational
90 days ago
100.0 % uptime
Today
CSG S1 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
CSG S2 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
CSG S3 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
CSG S4 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
KW S1 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
KW S2 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
KW S3 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
KW S4 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
KW S5 - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
KW S1 - US West (Oregon) Operational
90 days ago
100.0 % uptime
Today
PREMIUM EXPERIENCE APPLICATIONS Operational
90 days ago
100.0 % uptime
Today
Batch Commuincations Engine - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
Bill Explainer Microsite API - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
Bill Explainer Studio - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
Payment Reminder Microsite API - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
Payment Reminder Studio - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
Xponent Communications Control - US East (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
Xponent Communications Control - AWS EU Central (Frankfurt) Operational
90 days ago
100.0 % uptime
Today
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.

No incidents or maintenance related to this downtime.

Aug 8, 2026

No incidents reported today.

Aug 7, 2026

Bill Explainer PROD Release 26.3.3 – US East
Completed - The scheduled maintenance has been completed.
Aug 7, 05:01 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 7, 03:30 UTC
Update - We will be undergoing scheduled maintenance during this time.
Aug 6, 04:10 UTC
Update - We will be undergoing scheduled maintenance during this time.
Aug 6, 04:09 UTC
Scheduled - We will be deploying updates to Bill Explainer as part of the 26.3.3 rollout. This update introduces various application bug fixes.
Aug 6, 04:09 UTC

Aug 6, 2026

Xponent Core Upgrade to 26.2.5 – CSG Europe (Frankfurt) Region [2 of 2]
Completed - The scheduled maintenance has been completed.
Aug 6, 12:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 6, 09:00 UTC
Scheduled - 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.
Jul 27, 22:18 UTC

Aug 5, 2026

Xponent Core Upgrade to 26.2.5 – CSG US East (N. Virginia) Region
Completed - The scheduled maintenance has been completed.
Aug 5, 08:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 5, 05:30 UTC
Scheduled - 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.
Jul 27, 22:16 UTC

Aug 4, 2026

Xponent Core Upgrade to 26.2.5 – Kitewheel US West (Oregon) Region
Completed - The scheduled maintenance has been completed.
Aug 4, 09:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 4, 05:31 UTC
Scheduled - 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.
Jul 27, 22:13 UTC
Xponent Core Upgrade to 26.2.5 – Kitewheel US East (N. Virginia) Region
Completed - The scheduled maintenance has been completed.
Aug 4, 08:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 4, 05:30 UTC
Scheduled - 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.
Jul 27, 22:11 UTC

Aug 3, 2026

Xponent Core Upgrade to 26.2.5 – CSG Europe (Frankfurt) Region [1 of 2]
Completed - The scheduled maintenance has been completed.
Aug 3, 21:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 3, 17:00 UTC
Update - We will be undergoing scheduled maintenance during this time.
Jul 27, 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, 21:55 UTC

Aug 2, 2026

No incidents reported.

Aug 1, 2026

No incidents reported.

Jul 31, 2026

Xponent Voice & Messaging - BigIP Upgrade <Pre>
Completed - The scheduled maintenance has been completed.
Jul 31, 07:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 31, 05:00 UTC
Scheduled - 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.
Jul 24, 12:31 UTC

Jul 30, 2026

No incidents reported.

Jul 29, 2026

Xponent Voice & Messaging - Service Processor firmware version upgrade <ODC/OD2>
Completed - The scheduled maintenance has been completed.
Jul 29, 10:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 29, 06:00 UTC
Scheduled - Planned Date:
Start: 07/29/2026 6:00:00 AM UTC
End: 07/29/2026 10:30:00 AM UTC

Summary:
CSG Xponent Voice and Messaging applications will undergo scheduled maintenance, which will impact components "Voice/Prod/ODC/OD2".

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 24, 12:29 UTC

Jul 28, 2026

Xponent Voice & Messaging - Change datatype in database table column (DBA-Distributed-L3) <ODC>
Completed - The scheduled maintenance has been completed.
Jul 28, 10:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 28, 07:30 UTC
Scheduled - Planned Date:
Start: 07/28/2026 7:30:00 AM UTC
End: 07/28/2026 10:30:00 AM UTC

Summary:
CSG Xponent Voice and Messaging applications will undergo scheduled maintenance, which will impact components "Voice/Prod/ODC".

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 24, 12:26 UTC

Jul 27, 2026

No incidents reported.

Jul 26, 2026

No incidents reported.

Jul 25, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage