Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Telesign Outage History

Every past Telesign outage tracked by IsDown, with detection times, duration, and resolution details.

There were 6868 Telesign outages since April 2020. The 909 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Minor March 27, 2026

March 2026: Operator Alert - Switzerland (CH) - Salt Mobile SA (228/03) - 03/27/2026

Detected Mar 27, 2026 7:08 AM EDT · Resolved Mar 27, 2026 9:20 AM EDT · Duration about 2 hours

Salt Mobile SA in Switzerland experienced network issues that caused delays in SMS message delivery for their end users. The incident began at 04:02 AM PDT on March 27, 2026 and was resolved by 05:14 AM PDT the same day, lasting approximately 1 hour and 12 minutes. All SMS services returned to normal functioning once the network issues were resolved.

Minor March 27, 2026

March 2026: Operator Service Alert - Brazil (BR) - Claro (724/05;12;38) - 03/27/2026

Detected Mar 27, 2026 6:14 AM EDT · Resolved Mar 27, 2026 11:37 AM EDT · Duration about 5 hours

Telesign's SMS service experienced delays for messages sent through the Claro network operator in Brazil due to network issues on the operator's side. The incident lasted 5.4 hours from 02:30 AM PDT to 08:30 AM PDT on March 27, 2026, affecting SMS message delivery to Claro subscribers. The network issues were resolved by the operator and SMS services returned to normal functionality.

Major March 26, 2026

March 2026: Phone ID - Age Verify, Call Forward Detect, Number Deactivation and Contact Match - Scheduled Maintenance - United Kingdom (GB) - Vodafone

Detected Mar 26, 2026 8:23 PM EDT · Resolved Mar 26, 2026 11:27 PM EDT · Duration about 3 hours

Vodafone UK conducted scheduled maintenance from 3:30 PM to 8:20 PM PDT on March 26, 2026, affecting Telesign's Phone ID services including Age Verify, Call Forward Detect, Number Deactivation, and Contact Match. Customers experienced temporary delays when using these services during the maintenance window. The incident was resolved after approximately 3.1 hours when the maintenance was completed.

Minor March 26, 2026

March 2026: Operator Alert - Kazakhstan (KZ) - KaR-Tel LLP (Beeline) (401/01) - 3/26/26

Detected Mar 26, 2026 5:04 PM EDT · Resolved Mar 26, 2026 7:06 PM EDT · Duration about 2 hours

Telesign experienced SMS delivery delays to KaR-Tel LLP (Beeline) network users in Kazakhstan due to network issues with the mobile operator. The incident affected SMS message delivery times for users on the 401/01 network from 1:59 PM to 3:44 PM PDT on March 26, 2026. The operator resolved their network issues and SMS services returned to normal functioning after approximately 2 hours.

Minor March 26, 2026

March 2026: Operator Service Alert - Netherlands (NL) - Odido Netherlands B.V. (204/02;16;20) - 03/26/2026

Detected Mar 26, 2026 7:54 AM EDT · Resolved Mar 26, 2026 10:11 AM EDT · Duration about 2 hours

Telesign experienced SMS delivery delays for users in the Netherlands due to network issues at operator Odido Netherlands B.V. starting at 3:56 AM PDT on March 26, 2026. The operator's network problems caused degraded service quality and delayed SMS message delivery to end users. The issue was resolved at 7:06 AM PDT the same day after approximately 3 hours and 10 minutes, with all services returning to normal functionality.

Minor March 26, 2026

March 2026: Operator Alert - Vietnam (VN) - Viettel Mobile (452/04) - 03/26/2026

Detected Mar 26, 2026 6:05 AM EDT · Resolved Mar 26, 2026 7:39 AM EDT · Duration about 2 hours

Telesign experienced SMS delivery delays to Viettel Mobile (452/04) users in Vietnam due to network issues with the mobile operator. The incident lasted from 2:48 AM PDT to 3:56 AM PDT on March 26, 2026, affecting SMS message delivery times for approximately 1 hour and 8 minutes. The issue was resolved when Viettel Mobile restored their network services, returning SMS delivery to normal functionality.

Minor March 25, 2026

March 2026: Possible Delays

Detected Mar 25, 2026 2:41 PM EDT · Resolved Mar 25, 2026 4:45 PM EDT · Duration about 2 hours

Telesign experienced intermittent platform disruptions that caused delays in message delivery for approximately 29 minutes on March 25, 2026. The incident affected the delivery performance of their messaging platform. Network engineers identified and resolved the underlying issue, restoring normal service operations.

Minor March 25, 2026

March 2026: Operator Alert - Ecuador (EC) - Claro (Conecel / Porta) (740/01) - 3/25/26

Detected Mar 25, 2026 7:23 AM EDT · Resolved Mar 25, 2026 10:42 AM EDT · Duration about 3 hours

Telesign experienced SMS delivery delays for users on the Claro (Conecel/Porta) network in Ecuador due to network issues with the operator. The incident lasted approximately 3 hours and 14 minutes, from 3:17 AM to 6:31 AM PDT on March 25, 2026. The issue was resolved when the operator fixed their network problems, restoring normal SMS delivery functionality.

Minor March 25, 2026

March 2026: Operator Alert - Bangladesh (BD) - TeleTalk (470/04) - 03/25/2026

Detected Mar 25, 2026 5:55 AM EDT · Resolved Mar 25, 2026 8:52 AM EDT · Duration about 3 hours

TeleTalk (470/04) in Bangladesh experienced network issues from 02:37AM to 04:40AM PDT on March 25, 2026, causing delays in SMS message delivery. The network problems were resolved after approximately 2 hours, restoring normal SMS service functionality for end users.

Minor March 25, 2026

March 2026: Quality degradation - Mexico (MX) - ATT (Iusacell&Unefon&Nextel) (334/01;010;04;040;05;050;09;090;07;070;080) - 3/24/26

Detected Mar 25, 2026 3:25 AM EDT · Resolved Mar 25, 2026 4:31 AM EDT · Duration about 1 hour

Telesign experienced quality degradation affecting SMS message delivery to ATT network users (including Iusacell, Unefon, and Nextel) in Mexico starting at 22:36 PST on 3/24/26. Customers sending SMS messages to these ATT network subscribers encountered difficulties with message delivery. The incident was identified and teams were working on resolution, though the status remained ongoing at the time of the last update.