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 Core Platform – Aurora MySQL Upgrade (v3.08.2 → v3.10.3) – Kitewheel US East (N. Virginia) Aug 24, 2026 05:00-08:00 UTC
Planned Date:
Start: 24 August 2026, 05:00 UTC
End: 24 August 2026, 08:00 UTC
Summary:
Xponent will undergo planned maintenance to upgrade the underlying Aurora MySQL database engine from version 3.08.2 to version 3.10.3 for the Xponent Core (JO) customer databases in the Kitewheel US East (N. Virginia) environment.
AWS is retiring the current Aurora MySQL engine version. Any cluster that remains on this version after 31 August 2026 will be upgraded automatically by AWS according to its schedule, rather than ours. To keep the upgrade under our control, communicate it in advance and remain aligned with supported technology standards, we plan to upgrade all applicable Aurora MySQL clusters by 27 August 2026, ahead of the AWS deadline.
The upgrade will be carried out using an AWS Managed Blue/Green Deployment. A synchronized copy of each database is upgraded in the background and then promoted, which keeps the change controlled and reversible.
What Does This Mean for You?
• This is a zero-downtime upgrade. The Xponent Journey Hub will remain available throughout the maintenance window, and you will be able to log in and make configuration changes as normal.
• Deployed graphs, real-time API listeners, and live integrations will continue to run normally throughout the switchover, with database connections re-established automatically.
• This is a minor version upgrade, so it introduces no backwards-incompatible database changes. Database endpoints do not change, and no connector, integration or configuration updates are required on your side.
• All existing data remains unchanged.
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.
Following the upgrade, we will carry out our standard post-upgrade checks to ensure the platform is operating as expected. As with all Xponent Core (JO) upgrades, appropriate contingency and rollback measures are in place.
No action is required from you at this time.
If you notice any unexpected behaviour, please contact CSG's Global Service Desk via the MyCSG Support portal: https://www.csgi.com/mycsgcustomer-support/ or call the phone number listed at the bottom of the page for your region.
Posted on Aug 21, 2026 - 21:51 UTC
Start: 24 August 2026, 05:00 UTC
End: 24 August 2026, 08:00 UTC
Summary:
Xponent will undergo planned maintenance to upgrade the underlying Aurora MySQL database engine from version 3.08.2 to version 3.10.3 for the Xponent Core (JO) customer databases in the Kitewheel US East (N. Virginia) environment.
AWS is retiring the current Aurora MySQL engine version. Any cluster that remains on this version after 31 August 2026 will be upgraded automatically by AWS according to its schedule, rather than ours. To keep the upgrade under our control, communicate it in advance and remain aligned with supported technology standards, we plan to upgrade all applicable Aurora MySQL clusters by 27 August 2026, ahead of the AWS deadline.
The upgrade will be carried out using an AWS Managed Blue/Green Deployment. A synchronized copy of each database is upgraded in the background and then promoted, which keeps the change controlled and reversible.
What Does This Mean for You?
• This is a zero-downtime upgrade. The Xponent Journey Hub will remain available throughout the maintenance window, and you will be able to log in and make configuration changes as normal.
• Deployed graphs, real-time API listeners, and live integrations will continue to run normally throughout the switchover, with database connections re-established automatically.
• This is a minor version upgrade, so it introduces no backwards-incompatible database changes. Database endpoints do not change, and no connector, integration or configuration updates are required on your side.
• All existing data remains unchanged.
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.
Following the upgrade, we will carry out our standard post-upgrade checks to ensure the platform is operating as expected. As with all Xponent Core (JO) upgrades, appropriate contingency and rollback measures are in place.
No action is required from you at this time.
If you notice any unexpected behaviour, please contact CSG's Global Service Desk via the MyCSG Support portal: https://www.csgi.com/mycsgcustomer-support/ or call the phone number listed at the bottom of the page for your region.
Posted on Aug 21, 2026 - 21:51 UTC
Xponent Core Platform – Aurora MySQL Upgrade (v3.08.2 → v3.10.3) – Kitewheel US West (Oregon) Aug 25, 2026 05:00-07:00 UTC
Planned Date:
Start: 25 August 2026, 05:00 UTC
End: 25 August 2026, 07:00 UTC
Summary:
Xponent will undergo planned maintenance to upgrade the underlying Aurora MySQL database engine from version 3.08.2 to version 3.10.3 for the Xponent Core (JO) customer databases in the Kitewheel US West (Oregon) environment.
AWS is retiring the current Aurora MySQL engine version. Any cluster that remains on this version after 31 August 2026 will be upgraded automatically by AWS according to its schedule, rather than ours. To keep the upgrade under our control, communicate it in advance and remain aligned with supported technology standards, we plan to upgrade all applicable Aurora MySQL clusters by 27 August 2026, ahead of the AWS deadline.
The upgrade will be carried out using an AWS Managed Blue/Green Deployment. A synchronized copy of each database is upgraded in the background and then promoted, which keeps the change controlled and reversible.
What Does This Mean for You?
• This is a zero-downtime upgrade. The Xponent Journey Hub will remain available throughout the maintenance window, and you will be able to log in and make configuration changes as normal.
• Deployed graphs, real-time API listeners, and live integrations will continue to run normally throughout the switchover, with database connections re-established automatically.
• This is a minor version upgrade, so it introduces no backwards-incompatible database changes. Database endpoints do not change, and no connector, integration or configuration updates are required on your side.
• All existing data remains unchanged.
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.
Following the upgrade, we will carry out our standard post-upgrade checks to ensure the platform is operating as expected. As with all Xponent Core (JO) upgrades, appropriate contingency and rollback measures are in place.
No action is required from you at this time.
If you notice any unexpected behaviour, please contact CSG's Global Service Desk via the MyCSG Support portal: https://www.csgi.com/mycsgcustomer-support/ or call the phone number listed at the bottom of the page for your region.
Posted on Aug 21, 2026 - 21:52 UTC
Start: 25 August 2026, 05:00 UTC
End: 25 August 2026, 07:00 UTC
Summary:
Xponent will undergo planned maintenance to upgrade the underlying Aurora MySQL database engine from version 3.08.2 to version 3.10.3 for the Xponent Core (JO) customer databases in the Kitewheel US West (Oregon) environment.
AWS is retiring the current Aurora MySQL engine version. Any cluster that remains on this version after 31 August 2026 will be upgraded automatically by AWS according to its schedule, rather than ours. To keep the upgrade under our control, communicate it in advance and remain aligned with supported technology standards, we plan to upgrade all applicable Aurora MySQL clusters by 27 August 2026, ahead of the AWS deadline.
The upgrade will be carried out using an AWS Managed Blue/Green Deployment. A synchronized copy of each database is upgraded in the background and then promoted, which keeps the change controlled and reversible.
What Does This Mean for You?
• This is a zero-downtime upgrade. The Xponent Journey Hub will remain available throughout the maintenance window, and you will be able to log in and make configuration changes as normal.
• Deployed graphs, real-time API listeners, and live integrations will continue to run normally throughout the switchover, with database connections re-established automatically.
• This is a minor version upgrade, so it introduces no backwards-incompatible database changes. Database endpoints do not change, and no connector, integration or configuration updates are required on your side.
• All existing data remains unchanged.
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.
Following the upgrade, we will carry out our standard post-upgrade checks to ensure the platform is operating as expected. As with all Xponent Core (JO) upgrades, appropriate contingency and rollback measures are in place.
No action is required from you at this time.
If you notice any unexpected behaviour, please contact CSG's Global Service Desk via the MyCSG Support portal: https://www.csgi.com/mycsgcustomer-support/ or call the phone number listed at the bottom of the page for your region.
Posted on Aug 21, 2026 - 21:52 UTC
Xponent Voice & Messaging - OD2 - Network services Maintenance Aug 26, 2026 05:00-11:00 UTC
Planned Date:
Start: 08/26/2026 05:00:00 AM UTC
End: 08/26/2026 11:00:00 AM UTC
Summary:
CSG Xponent Voice and Messaging applications will undergo scheduled maintenance, which will impact components "Voice/Prod/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.
Posted on Aug 14, 2026 - 12:48 UTC
Start: 08/26/2026 05:00:00 AM UTC
End: 08/26/2026 11:00:00 AM UTC
Summary:
CSG Xponent Voice and Messaging applications will undergo scheduled maintenance, which will impact components "Voice/Prod/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.
Posted on Aug 14, 2026 - 12:48 UTC
Xponent Core Platform – Aurora MySQL Upgrade (v3.08.2 → v3.10.3) – CSG US East (N. Virginia) [1 of 2] Aug 26, 2026 05:00-07:00 UTC
Planned Date:
Start: 26 August 2026, 05:00 UTC
End: 26 August 2026, 07:00 UTC
Summary:
Xponent will undergo planned maintenance to upgrade the underlying Aurora MySQL database engine from version 3.08.2 to version 3.10.3 for the Xponent Core (JO) customer databases in the CSG US East (N. Virginia) environment.
AWS is retiring the current Aurora MySQL engine version. Any cluster that remains on this version after 31 August 2026 will be upgraded automatically by AWS according to its schedule, rather than ours. To keep the upgrade under our control, communicate it in advance and remain aligned with supported technology standards, we plan to upgrade all applicable Aurora MySQL clusters by 27 August 2026, ahead of the AWS deadline.
The upgrade will be carried out using an AWS Managed Blue/Green Deployment. A synchronized copy of each database is upgraded in the background and then promoted, which keeps the change controlled and reversible.
What Does This Mean for You?
• This is a zero-downtime upgrade. The Xponent Journey Hub will remain available throughout the maintenance window, and you will be able to log in and make configuration changes as normal.
• Deployed graphs, real-time API listeners, and live integrations will continue to run normally throughout the switchover, with database connections re-established automatically.
• This is a minor version upgrade, so it introduces no backwards-incompatible database changes. Database endpoints do not change, and no connector, integration or configuration updates are required on your side.
• All existing data remains unchanged.
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.
Following the upgrade, we will carry out our standard post-upgrade checks to ensure the platform is operating as expected. As with all Xponent Core (JO) upgrades, appropriate contingency and rollback measures are in place.
No action is required from you at this time.
If you notice any unexpected behaviour, please contact CSG's Global Service Desk via the MyCSG Support portal: https://www.csgi.com/mycsgcustomer-support/ or call the phone number listed at the bottom of the page for your region.
Posted on Aug 21, 2026 - 21:53 UTC
Start: 26 August 2026, 05:00 UTC
End: 26 August 2026, 07:00 UTC
Summary:
Xponent will undergo planned maintenance to upgrade the underlying Aurora MySQL database engine from version 3.08.2 to version 3.10.3 for the Xponent Core (JO) customer databases in the CSG US East (N. Virginia) environment.
AWS is retiring the current Aurora MySQL engine version. Any cluster that remains on this version after 31 August 2026 will be upgraded automatically by AWS according to its schedule, rather than ours. To keep the upgrade under our control, communicate it in advance and remain aligned with supported technology standards, we plan to upgrade all applicable Aurora MySQL clusters by 27 August 2026, ahead of the AWS deadline.
The upgrade will be carried out using an AWS Managed Blue/Green Deployment. A synchronized copy of each database is upgraded in the background and then promoted, which keeps the change controlled and reversible.
What Does This Mean for You?
• This is a zero-downtime upgrade. The Xponent Journey Hub will remain available throughout the maintenance window, and you will be able to log in and make configuration changes as normal.
• Deployed graphs, real-time API listeners, and live integrations will continue to run normally throughout the switchover, with database connections re-established automatically.
• This is a minor version upgrade, so it introduces no backwards-incompatible database changes. Database endpoints do not change, and no connector, integration or configuration updates are required on your side.
• All existing data remains unchanged.
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.
Following the upgrade, we will carry out our standard post-upgrade checks to ensure the platform is operating as expected. As with all Xponent Core (JO) upgrades, appropriate contingency and rollback measures are in place.
No action is required from you at this time.
If you notice any unexpected behaviour, please contact CSG's Global Service Desk via the MyCSG Support portal: https://www.csgi.com/mycsgcustomer-support/ or call the phone number listed at the bottom of the page for your region.
Posted on Aug 21, 2026 - 21:53 UTC
Xponent Core Platform – Aurora MySQL Upgrade (v3.08.2 → v3.10.3) – CSG US East (N. Virginia) [2 of 2] Aug 27, 2026 05:00-07:00 UTC
Planned Date:
Start: 27 August 2026, 05:00 UTC
End: 27 August 2026, 07:00 UTC
Summary:
Xponent will undergo planned maintenance to upgrade the underlying Aurora MySQL database engine from version 3.08.2 to version 3.10.3 for the Xponent Core (JO) customer databases in the CSG US East (N. Virginia) environment.
AWS is retiring the current Aurora MySQL engine version. Any cluster that remains on this version after 31 August 2026 will be upgraded automatically by AWS according to its schedule, rather than ours. To keep the upgrade under our control, communicate it in advance and remain aligned with supported technology standards, we plan to upgrade all applicable Aurora MySQL clusters by 27 August 2026, ahead of the AWS deadline.
The upgrade will be carried out using an AWS Managed Blue/Green Deployment. A synchronized copy of each database is upgraded in the background and then promoted, which keeps the change controlled and reversible.
What Does This Mean for You?
• This is a zero-downtime upgrade. The Xponent Journey Hub will remain available throughout the maintenance window, and you will be able to log in and make configuration changes as normal.
• Deployed graphs, real-time API listeners, and live integrations will continue to run normally throughout the switchover, with database connections re-established automatically.
• This is a minor version upgrade, so it introduces no backwards-incompatible database changes. Database endpoints do not change, and no connector, integration or configuration updates are required on your side.
• All existing data remains unchanged.
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.
Following the upgrade, we will carry out our standard post-upgrade checks to ensure the platform is operating as expected. As with all Xponent Core (JO) upgrades, appropriate contingency and rollback measures are in place.
No action is required from you at this time.
If you notice any unexpected behaviour, please contact CSG's Global Service Desk via the MyCSG Support portal: https://www.csgi.com/mycsgcustomer-support/ or call the phone number listed at the bottom of the page for your region.
Posted on Aug 21, 2026 - 21:54 UTC
Start: 27 August 2026, 05:00 UTC
End: 27 August 2026, 07:00 UTC
Summary:
Xponent will undergo planned maintenance to upgrade the underlying Aurora MySQL database engine from version 3.08.2 to version 3.10.3 for the Xponent Core (JO) customer databases in the CSG US East (N. Virginia) environment.
AWS is retiring the current Aurora MySQL engine version. Any cluster that remains on this version after 31 August 2026 will be upgraded automatically by AWS according to its schedule, rather than ours. To keep the upgrade under our control, communicate it in advance and remain aligned with supported technology standards, we plan to upgrade all applicable Aurora MySQL clusters by 27 August 2026, ahead of the AWS deadline.
The upgrade will be carried out using an AWS Managed Blue/Green Deployment. A synchronized copy of each database is upgraded in the background and then promoted, which keeps the change controlled and reversible.
What Does This Mean for You?
• This is a zero-downtime upgrade. The Xponent Journey Hub will remain available throughout the maintenance window, and you will be able to log in and make configuration changes as normal.
• Deployed graphs, real-time API listeners, and live integrations will continue to run normally throughout the switchover, with database connections re-established automatically.
• This is a minor version upgrade, so it introduces no backwards-incompatible database changes. Database endpoints do not change, and no connector, integration or configuration updates are required on your side.
• All existing data remains unchanged.
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.
Following the upgrade, we will carry out our standard post-upgrade checks to ensure the platform is operating as expected. As with all Xponent Core (JO) upgrades, appropriate contingency and rollback measures are in place.
No action is required from you at this time.
If you notice any unexpected behaviour, please contact CSG's Global Service Desk via the MyCSG Support portal: https://www.csgi.com/mycsgcustomer-support/ or call the phone number listed at the bottom of the page for your region.
Posted on Aug 21, 2026 - 21:54 UTC