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.

Sep 4, 2026

Xponent Communications Control PROD Multiparser service endpoint update
Completed - The scheduled maintenance has been completed.
Sep 4, 00:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 3, 21:30 UTC
Scheduled - Planned Date:
Start: 09-03-2026 21:30 UTC
End: 09-03-2026 24:30 UTC

Summary:
We will be deploying updates to Xponent Commuications Control to update our Multiparser service endpoint responsible for Template Preview within XCC.

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.
Sep 3, 21:22 UTC

Sep 3, 2026

Xponent Communications Control PROD Release 26.3.2 – US & EU
Completed - The scheduled maintenance has been completed.
Sep 3, 15:04 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 2, 01:00 UTC
Scheduled - Planned Date:
Start: 09/02/2026 1:00:00 PM UTC
End: 09/02/2026 10:00:00 PM UTC

Summary:
We will be deploying updates to Xponent Communications Control as part of the 26.3.2 release rollout. This update introduces various feature enhancements and bug fixes to the AWS application.

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.
Aug 31, 14:36 UTC

Sep 2, 2026

Sep 1, 2026

No incidents reported.

Aug 31, 2026

No incidents reported.

Aug 30, 2026

No incidents reported.

Aug 29, 2026

No incidents reported.

Aug 28, 2026

No incidents reported.

Aug 27, 2026

Xponent Core Platform – Aurora MySQL Upgrade (v3.08.2 → v3.10.3) – CSG US East (N. Virginia) [2 of 2]
Completed - The scheduled maintenance has been completed.
Aug 27, 07:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 27, 05:00 UTC
Scheduled - 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.
Aug 21, 21:54 UTC

Aug 26, 2026

Xponent Voice & Messaging - OD2 - Network services Maintenance
Completed - The scheduled maintenance has been completed.
Aug 26, 11:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 26, 05:00 UTC
Scheduled - 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.
Aug 14, 12:48 UTC
Batch Communication Engine PROD Release 26.3.4
Completed - The scheduled maintenance has been completed.
Aug 26, 07:52 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 26, 03:30 UTC
Scheduled - We will be deploying updates to Batch Communication Engine as part of the 26.3.4 rollout. This update introduces various application bug fixes.
Aug 25, 10:57 UTC
Xponent Core Platform – Aurora MySQL Upgrade (v3.08.2 → v3.10.3) – CSG US East (N. Virginia) [1 of 2]
Completed - The scheduled maintenance has been completed.
Aug 26, 07:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 26, 05:01 UTC
Scheduled - 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.
Aug 21, 21:53 UTC

Aug 25, 2026

Xponent Core Platform – Aurora MySQL Upgrade (v3.08.2 → v3.10.3) – Kitewheel US West (Oregon)
Completed - The scheduled maintenance has been completed.
Aug 25, 07:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 25, 05:00 UTC
Scheduled - 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.
Aug 21, 21:52 UTC

Aug 24, 2026

Xponent Core Platform – Aurora MySQL Upgrade (v3.08.2 → v3.10.3) – Kitewheel US East (N. Virginia)
Completed - The scheduled maintenance has been completed.
Aug 24, 08:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 24, 05:00 UTC
Scheduled - 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.
Aug 21, 21:51 UTC

Aug 23, 2026

No incidents reported.

Aug 22, 2026

No incidents reported.

Aug 21, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage