TeleSign Outage History

TeleSign partial outage · 6 active incidents View live status →

TeleSign had 147 outages in the last 2 years totaling 13131h 49m of downtime — averaging 6 incidents per month.

There were 147 TeleSign outages since January 13, 2025 totaling 13131h 49m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.telesign.com

Minor April 3, 2026

PhoneID Live Service Alert - United Kingdom

Detected by Pingoru
Apr 03, 2026, 06:47 PM UTC
Resolved
Apr 03, 2026, 07:47 PM UTC
Duration
59m
Affected: United Kingdom
Timeline · 2 updates
  1. identified Apr 03, 2026, 06:47 PM UTC

    Date: 04/03/26 Start Time: 11:10 AM PDT End Time: Ongoing We received notification from our partner that PhoneID Live is currently having issues in the United Kingdom, which may cause some delays. We will inform you once there is a resolution. We'd like to apologize for any inconvenience and appreciate your patience during this service window. If you have any questions, please contact us at [email protected].

  2. resolved Apr 03, 2026, 07:47 PM UTC

    Date: 04/03/2026 Start Time: 11:10 AM PDT End Time: 12:05 PM PDT We received notification from our partner that the issue previously noticed in the United Kingdom has been resolved. End users should no longer experience delays, as all services are back to functioning properly.

Read the full incident report →

Minor April 2, 2026

Operator Alert - Estonia (EE) - Telia Eesti AS (248/01)

Detected by Pingoru
Apr 02, 2026, 11:05 AM UTC
Resolved
Apr 02, 2026, 01:35 PM UTC
Duration
2h 29m
Affected: EMEA - All countries
Timeline · 2 updates
  1. investigating Apr 02, 2026, 11:05 AM UTC

    Start Time: 4:04 AM PDT - 04/02/26 End Time: Ongoing We received notification that Telia Eesti AS (248/01) from Estonia (EE) is currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. We will inform you once the operator has come to a resolution. SF 01152498

  2. resolved Apr 02, 2026, 01:35 PM UTC

    Start Time: 4:04 AM PDT - 04/02/26 End Time: 5:49 AM PDT - 04/02/26 We received notification that the network issues previously reported by Telia Eesti AS (248/01) from Estonia (EE) have been resolved. Telia Eesti AS (248/01) end users should no longer experience delays receiving SMS messages as all services are back to functioning properly. SF 01152498

Read the full incident report →

Minor April 2, 2026

Operator Alert - Ethiopia (ET) - Ethiopian Telecommunications (636/01) - 04/02/26

Detected by Pingoru
Apr 02, 2026, 10:59 AM UTC
Resolved
Apr 02, 2026, 03:31 PM UTC
Duration
4h 32m
Affected: EMEA - All countries
Timeline · 2 updates
  1. investigating Apr 02, 2026, 10:59 AM UTC

    Start Time: 03:50 am PDT - 04/02/26 End Time: Ongoing We received notification that Ethiopian Telecommunications (636/01) from Ethiopia (ET) is currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. We will inform you once the operator has come to a resolution. SF 01152496

  2. resolved Apr 02, 2026, 03:31 PM UTC

    Start Time: 03:50 am PDT - 04/02/26 End Time: 08:00 am PDT - 04/02/26 We received notification that the network issues previously reported by Ethiopian Telecommunications (636/01) from Ethiopia (ET) have been resolved. Ethiopian Telecommunications end users should no longer experience delays receiving SMS messages as all services are back to functioning properly. SF 01152496

Read the full incident report →

Notice April 2, 2026

Service disruption for phone ID Phone ID - Live - United Kingdom (GB)

Detected by Pingoru
Apr 02, 2026, 08:41 AM UTC
Resolved
Apr 02, 2026, 11:32 AM UTC
Duration
2h 50m
Affected: United Kingdom
Timeline · 3 updates
  1. investigating Apr 02, 2026, 08:41 AM UTC

    We have received notification that services for Phone ID - Live - United Kingdom are experiencing delays. We will inform you as soon as we receive a resolution.

  2. monitoring Apr 02, 2026, 09:53 AM UTC

    The previously reported issue is no longer present. We are actively monitoring the situation to confirm continued normal operation.

  3. resolved Apr 02, 2026, 11:32 AM UTC

    04/02/2026 START: 01:14 AM PDT END: 01:30 AM PDT We are pleased to confirm that the issues affecting Phone ID – Live – United Kingdom have been fully resolved. All services are now operating normally, and users should experience uninterrupted functionality. We appreciate your patience while we worked to restore service.

Read the full incident report →

Minor April 2, 2026

Operator Alert - Chile (CL) - Claro Chile (730/03) - 04/01/26

Detected by Pingoru
Apr 02, 2026, 04:23 AM UTC
Resolved
Apr 02, 2026, 06:45 AM UTC
Duration
2h 22m
Affected: Chile
Timeline · 2 updates
  1. investigating Apr 02, 2026, 04:23 AM UTC

    Start Time: 09:20 pm PDT - 04/01/26 End Time: Ongoing We received notification that Claro Chile (730/03) from Chile (CL) is currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. We will inform you once the operator has come to a resolution. SF 01152293

  2. resolved Apr 02, 2026, 06:45 AM UTC

    Start Time: 09:20 pm PDT - 04/01/26 End Time: 10:33 pm PDT - 04/01/26 We received notification that the network issues previously reported by Claro Chile (730/03) from Chile (CL) have been resolved. Claro Chile (730/03) end users should no longer experience delays receiving SMS messages as all services are back to functioning properly. SF 01152293

Read the full incident report →

Minor April 1, 2026

Operator Service Alert - Brazil (BR) - Claro (724/05;12;38)

Detected by Pingoru
Apr 01, 2026, 02:32 PM UTC
Resolved
Apr 01, 2026, 10:25 PM UTC
Duration
7h 52m
Affected: NA & LATAM - All countriesBrazil
Timeline · 2 updates
  1. investigating Apr 01, 2026, 02:32 PM UTC

    Issue: Operator - Brazil (BR) - Claro (724/05;12;38) Start Time: 06:46AM PDT - 04/01/26 End Time: Ongoing Summary: We received notification that Claro (724/05;12;38) from Brazil (BR) is currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. Telesign is engaged with the operators for updates on resolution. We'd like to apologize for any inconvenience and appreciate your patience during this service interruption. If you have any questions, please contact [email protected].

  2. resolved Apr 01, 2026, 10:25 PM UTC

    Start Time: 06:46 AM PDT - 04/01/26 End Time: 03:16 PM PDT - 04/01/26 We received notification that the network issues previously reported by Claro (724/05;12;38) from Brazil (BR) have been resolved. Claro (724/05;12;38) end users should no longer experience delays receiving SMS messages as all services are back to functioning properly. SF 01152062

Read the full incident report →

Notice March 31, 2026

Operator Alert - Serbia (RS) - Telekom Srbija (220/03)

Detected by Pingoru
Mar 31, 2026, 09:25 PM UTC
Resolved
Mar 31, 2026, 11:04 PM UTC
Duration
1h 39m
Affected: EMEA - All countries
Timeline · 2 updates
  1. investigating Mar 31, 2026, 09:25 PM UTC

    Start Time: 02:20 PM PST - 03/31/26 End Time: Ongoing We received notification that Telekom Srbija (220/03) from Serbia (RS) is currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. We will inform you once the operator has come to a resolution. SF 01151722

  2. resolved Mar 31, 2026, 11:04 PM UTC

    Start Time: 02:20 PM PST - 03/31/26 End Time: 03:23 PM PST - 03/31/26 We received notification that the network issues previously reported by Telekom Srbija (220/03) from Serbia (RS) have been resolved. Telekom Srbija (220/03) end users should no longer experience delays receiving SMS messages as all services are back to functioning properly. SF 01151722

Read the full incident report →

Minor March 31, 2026

Quality degradation - Italy (IT) - Multiple Operators - 03/31/26

Detected by Pingoru
Mar 31, 2026, 06:58 PM UTC
Resolved
Apr 01, 2026, 11:50 AM UTC
Duration
16h 51m
Affected: Italy
Timeline · 2 updates
  1. investigating Mar 31, 2026, 06:58 PM UTC

    Date: 03/31/26 Start Time: 11:22 AM PDT End Time: Ongoing Summary: We currently experience quality degradation toward Italy (IT) - Multiple Operators. Customers that send SMS messages to Italy (IT) - Multiple Operator users may notice a difficulties in message delivery. Our competent teams are working on solving this issue. We'd like to apologize for any inconvenience and appreciate your patience during this service window. If you have any questions, please contact us at [email protected].

  2. resolved Apr 01, 2026, 11:50 AM UTC

    Issue: Italy (IT) - Multiple Operators - Quality degradation Date: 03/31/26 Start Time: 11:22 AM PDT - 3/31/26 End Time: 4:00 AM PDT - 4/1/26 Summary: The quality issues toward Italy (IT) - Multiple Operators have been resolved. SMS messages to these operators are now being delivered normally without delays. Telesign worked closely with carrier partners to resolve the issue. We apologize for any inconvenience caused and appreciate your patience during the service interruption. If you have any further questions, please contact [email protected].

Read the full incident report →

Minor March 31, 2026

Operator Alert - Mexico (MX) - Altan Redes (334/140)

Detected by Pingoru
Mar 31, 2026, 06:26 PM UTC
Resolved
Mar 31, 2026, 09:12 PM UTC
Duration
2h 46m
Affected: Mexico
Timeline · 2 updates
  1. investigating Mar 31, 2026, 06:26 PM UTC

    Start Time: 11:24 AM PDT 03/31/26 End Time: Ongoing We received notification that Altan Redes (334/140) from Mexico (MX) is currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. We will inform you once the operator has come to a resolution. SF 01151647

  2. resolved Mar 31, 2026, 09:12 PM UTC

    Start Time: 11:24 AM PDT 03/31/26 End Time: 01:04 PM PDT 03/31/26 We received notification that the network issues previously reported by Altan Redes (334/140) from Mexico (MX) have been resolved. Altan Redes (334/140) end users should no longer experience delays receiving SMS messages as all services are back to functioning properly. SF 01151647

Read the full incident report →

Minor March 31, 2026

Quality degradation - United States (US) - Small Carriers - 3/31/26

Detected by Pingoru
Mar 31, 2026, 10:01 AM UTC
Resolved
Mar 31, 2026, 10:23 AM UTC
Duration
22m
Affected: United States
Timeline · 2 updates
  1. investigating Mar 31, 2026, 10:01 AM UTC

    Issue: United States (US) - Small Carriers - Quality degradation Start Time: 2:07AM PDT - 3/31/26 End Time: / Summary: We currently experience quality degradation toward United States (US) - Small Carriers. SMS messages towards these operators may face delays or difficulties in delivery. Telesign is engaged with carrier partners for updates on resolution. We'd like to apologize for any inconvenience and appreciate your patience during this service interruption. If you have any questions, please contact [email protected]. SF 01151346

  2. resolved Mar 31, 2026, 10:23 AM UTC

    Issue: United States (US) - Small Carriers - Quality degradation Start Time: 2:07AM PDT - 3/31/26 End Time: 2:54AM PDT - 3/31/26 Summary: The quality issues toward United States (US) - Small Carriers have been resolved. SMS messages to these operators are now being delivered normally without delays. Telesign worked closely with carrier partners to resolve the issue. We apologize for any inconvenience caused and appreciate your patience during the service interruption. If you have any further questions, please contact [email protected]. SF 01151346

Read the full incident report →

Major March 29, 2026

Operator Alert - Israel (IL) - Cellcom Israel Ltd. (425/02;15) 03/29/26

Detected by Pingoru
Mar 29, 2026, 07:36 AM UTC
Resolved
Mar 30, 2026, 01:04 AM UTC
Duration
17h 27m
Affected: EMEA - All countries
Timeline · 2 updates
  1. investigating Mar 29, 2026, 07:36 AM UTC

    Start Time: 00:31 AM PST- 03/29/26 End Time: Ongoing We received notification that Cellcom Israel Ltd. (425/02;15) from Israel (IL) is currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. We will inform you once the operator has come to a resolution. SF 01150428

  2. resolved Mar 30, 2026, 01:04 AM UTC

    Start Time: 00:31 AM PST- 03/29/26 End Time: 00:58 AM PST- 03/29/26 We received notification that the network issues previously reported by Cellcom Israel Ltd. (425/02;15) from Israel (IL) have been resolved. Cellcom Israel Ltd. (425/02;15) end users should no longer experience delays receiving SMS messages as all services are back to functioning properly. SF 01150428

Read the full incident report →

Major March 28, 2026

Operator Alert - Nepal (NP) - Nepal Mobile (Nepal Telecom) (429/01;03) [03/28/26]

Detected by Pingoru
Mar 28, 2026, 09:42 AM UTC
Resolved
Mar 28, 2026, 11:14 AM UTC
Duration
1h 32m
Affected: APAC - All countries
Timeline · 2 updates
  1. investigating Mar 28, 2026, 09:42 AM UTC

    Start Time: 02:36 AM PST - 03/28/26 End Time: Ongoing We received notification that Nepal Mobile (Nepal Telecom) (429/01;03) from Nepal (NP) is currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. We will inform you once the operator has come to a resolution. SF[01150237]

  2. resolved Mar 28, 2026, 11:14 AM UTC

    Start Time: 02:36 AM PST - 03/28/26 End Time: 03:12 AM PST - 03/28/26 We received notification that the network issues previously reported by Nepal Mobile (Nepal Telecom) (429/01;03) from Nepal (NP) have been resolved. Nepal Mobile (Nepal Telecom) (429/01;03) end users should no longer experience delays receiving SMS messages as all services are back to functioning properly. SF 01150237

Read the full incident report →

Major March 28, 2026

Operator Alert - Cameroon (CM) - Orange Cameroun S.A. (624/02) [03/27/26]

Detected by Pingoru
Mar 28, 2026, 06:24 AM UTC
Resolved
Mar 28, 2026, 05:35 PM UTC
Duration
11h 11m
Affected: EMEA - All countries
Timeline · 2 updates
  1. investigating Mar 28, 2026, 06:24 AM UTC

    Start Time: 23:20 PM PST - 03/27/26 End Time: Ongoing We received notification that Orange Cameroun S.A. (624/02) from Cameroon (CM) is currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. We will inform you once the operator has come to a resolution. SF[01150206]

  2. resolved Mar 28, 2026, 05:35 PM UTC

    This incident has been resolved.

Read the full incident report →

Major February 28, 2026

Operator Alert - Iran (IR) - Irancell (MTN) (432/35) - 02/28/2026

Detected by Pingoru
Feb 28, 2026, 11:03 AM UTC
Resolved
Apr 21, 2026, 12:21 PM UTC
Duration
52d 1h
Affected: EMEA - All countries
Timeline · 2 updates
  1. investigating Feb 28, 2026, 11:03 AM UTC

    Start 01:30 AM PST - 02/28/26 End Time: Ongoing We received notification that Irancell (MTN) (432/35) from Iran (IR) is currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. We will inform you once the operator has come to a resolution. SF 01136491

  2. resolved Apr 21, 2026, 12:21 PM UTC

    Start 01:30AM PDT - 02/28/26 End Time: 05:15AM PDT - 04/21/26 We received notification that the network issues previously reported by Irancell (MTN) (432/35) from Iran (IR) have been resolved. Irancell (MTN) (432/35) end users should no longer experience delays receiving SMS messages as all services are back to functioning properly. SF 01136491

Read the full incident report →

Major January 13, 2025

Operator Service Alert - SMS Services - Russia

Detected by Pingoru
Jan 13, 2025, 09:01 AM UTC
Resolved
May 19, 2026, 12:01 PM UTC
Duration
491d 2h
Affected: EMEA - All countriesRussia
Timeline · 2 updates
  1. identified Jan 13, 2025, 09:01 AM UTC

    Date: 03/08/22 End Time: Ongoing We received notification that due to the current political situation certain operators (carriers) in Russia are currently experiencing network issues, and this may cause a delay or failure in the delivery of SMS messages. We will inform you once the situation is resolved. We'd like to apologize for any inconvenience and appreciate your patience during this service interruption. If you have any questions, please contact [email protected].

  2. resolved May 19, 2026, 12:01 PM UTC

    This incident has been resolved.

Read the full incident report →