TSG Global Outage History

TSG Global is up right now

TSG Global had 2 outages in the last 2 years totaling 7h 21m of downtime — averaging 0.1 incidents per month.

There were 2 TSG Global outages since October 8, 2025 totaling 7h 21m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.tsgglobal.com

Notice October 15, 2025

Inbound SMS Delivery Delays (HTTP Webhooks)

Detected by Pingoru
Oct 15, 2025, 07:10 PM UTC
Resolved
Oct 15, 2025, 08:24 PM UTC
Duration
1h 13m
Affected: Local Inbound/Outbound SMSToll-Free Inbound/Outbound SMSLocal Inbound/Outbound MMSToll-Free Inbound/Outbound MMS
Timeline · 2 updates
  1. identified Oct 15, 2025, 07:10 PM UTC

    Status: Identified - Fix in Progress Impact: Inbound SMS messages to HTTP webhooks may experience delays. SMPP customers are not affected. Affected Services: Long Code (10DLC) inbound HTTP webhooks Toll-Free inbound HTTP webhooks Short Code inbound HTTP webhooks Not Affected: SMPP customers (all message types) Outbound messaging (all types) Current Actions: Our engineering team has identified the issue and is implementing a fix. We will update this incident as soon as inbound HTTP webhook delivery is restored to normal.

  2. resolved Oct 15, 2025, 08:24 PM UTC

    Our engineering team identified and resolved the issue. Inbound HTTP webhook delivery has been restored to normal operation.

Read the full incident report →

Notice October 8, 2025

Messaging delivery delays and failures for some users

Detected by Pingoru
Oct 08, 2025, 10:16 AM UTC
Resolved
Oct 08, 2025, 04:24 PM UTC
Duration
6h 8m
Affected: SMPPLocal Inbound/Outbound SMSToll-Free Inbound/Outbound SMSLocal Inbound/Outbound MMSToll-Free Inbound/Outbound MMS
Timeline · 5 updates
  1. investigating Oct 08, 2025, 10:16 AM UTC

    We are currently investigating an outage impacting our messaging stack. The issue originated from an unexpected failure on one of our infrastructure nodes, which is affecting message processing and queueing. Our engineering team is actively restoring service and implementing additional stability measures to prevent recurrence. Updates will be posted here as they become available.

  2. identified Oct 08, 2025, 10:39 AM UTC

    Our team identified that one of our backend nodes failed, affecting message queue handling. We are working at restoring functionality and will provide additional updates as they become available.

  3. monitoring Oct 08, 2025, 12:14 PM UTC

    Most Services have been restored, and we are monitoring the environment to ensure full stability

  4. monitoring Oct 08, 2025, 02:45 PM UTC

    All services are fully operational, we continue to monitor.

  5. resolved Oct 08, 2025, 04:24 PM UTC

    This incident has been resolved. Messaging operations are functioning normally.

Read the full incident report →