Is TeleSign down?

Last checked 3m ago
Current status
TeleSign is having a partial outage

6 active incidents: Operator Alert - Cameroon (CM) - Orange Cameroun S.A. (624/…, Regulatory Update: 📢 Important Update: Spain Sender ID Reg… · +4 more

Get alerts when TeleSign breaks →

Free · no credit card

Official status page: https://status.telesign.com · Polled every 5 minutes · 201 components tracked

Real-time TeleSign status, recent outages, and incident history — pulled directly from TeleSign's official status page at https://status.telesign.com every 5 minutes. Pingoru tracks 201 TeleSign services and has captured 50 incidents in the last 90 days (99.69% uptime). Get email, Slack, Discord, or webhook alerts the moment TeleSign reports a new incident — free for 5 monitors, no credit card.

Users who monitor TeleSign also follow these Identity Management services: JumpCloud Dropbox Sign Ping Identity MobileIron GBG Onfido Persona Identities Thycotic Beyond Identity Ekata View all 6,000+ providers
TeleSign uptime 99.69% uptime · past 90 days
Mon Wed Fri
JanFebMarApr
Less More

Recent outages & incidents

Past 7 days
  1. Operator Alert - Cameroon (CM) - Orange Cameroun S.A. (624/02)
    Ongoing ● 25m
    Started Apr 29, 2026, 07:25 PM UTC
    EMEA - All countries
    1 update · show timeline
    • investigating · Apr 29, 2026, 07:25 PM UTC

      Start Time: 12:23 PM PST - 04/29/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 01164299

    Latest: Start Time: 12:23 PM PST - 04/29/26 End Time: Ongoing We received notification that Orange Cameroun S.A. (624/02) from Cameroon (CM) is currently experiencing network issues, and t…

  2. Operator Alert - Costa Rica (CR) - Telefonica Moviles Costa Rica (712/04)
    Resolved 12h 6m
    Started Apr 29, 2026, 05:08 AM UTC · Resolved Apr 29, 2026, 05:15 PM UTC
    NA & LATAM - All countries
    2 updates · show timeline
    • investigating · Apr 29, 2026, 05:08 AM UTC

      Start Time: 09:59 PM PDT - 04/28/26 End Time: Ongoing We received notification that Telefonica Moviles Costa Rica (712/04) from Costa Rica (CR) 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 01163854

    • resolved · Apr 29, 2026, 05:15 PM UTC

      Start Time: 09:59 PM PDT - 04/28/26 End Time: 09:02 AM PDT - 04/29/26 We received notification that the network issues previously reported by Telefonica Moviles Costa Rica (712/04) from Costa Rica (CR) have been resolved. Telefonica Moviles Costa Rica (712/04) end users should no longer experience delays receiving SMS messages as all services are back to functioning properly. SF 01163854

    Latest: Start Time: 09:59 PM PDT - 04/28/26 End Time: 09:02 AM PDT - 04/29/26 We received notification that the network issues previously reported by Telefonica Moviles Costa Rica (712/04)…

  3. Operator Alert - Cameroon (CM) - Orange Cameroun S.A. (624/02)
    Resolved 9h 57m
    Started Apr 28, 2026, 07:40 PM UTC · Resolved Apr 29, 2026, 05:37 AM UTC
    EMEA - All countries
    2 updates · show timeline
    • investigating · Apr 28, 2026, 07:40 PM UTC

      Start Time: 12:35 PM PST - 04/28/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 01163665

    • resolved · Apr 29, 2026, 05:37 AM UTC

      Start Time: 12:35 PM PST - 04/28/26 End Time: 09:38 PM PST - 04/28/26 We received notification that the network issues previously reported by Orange Cameroun S.A. (624/02) from Cameroon (CM) have been resolved. Orange Cameroun S.A. (624/02) end users should no longer experience delays receiving SMS messages as all services are back to functioning properly. SF 01163665

    Latest: Start Time: 12:35 PM PST - 04/28/26 End Time: 09:38 PM PST - 04/28/26 We received notification that the network issues previously reported by Orange Cameroun S.A. (624/02) from Cam…

  4. Operator Alert - South Korea (KR) - KTF (450/02;04;08)
    Resolved 56m
    Started Apr 28, 2026, 06:55 PM UTC · Resolved Apr 28, 2026, 07:51 PM UTC
    South Korea
    2 updates · show timeline
    • investigating · Apr 28, 2026, 06:55 PM UTC

      Start Time: 11:52 AM PST - 28/04/26 End Time: Ongoing We received notification that KTF (450/02;04;08) from South Korea (KR) 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 01163657

    • resolved · Apr 28, 2026, 07:51 PM UTC

      Start Time: 11:52 AM PST - 28/04/26 End Time: 12:35 PM PST - 28/04/26 We received notification that the network issues previously reported by KTF (450/02;04;08) from South Korea (KR) have been resolved. KTF (450/02;04;08) end users should no longer experience delays receiving SMS messages as all services are back to functioning properly. SF 01163657

    Latest: Start Time: 11:52 AM PST - 28/04/26 End Time: 12:35 PM PST - 28/04/26 We received notification that the network issues previously reported by KTF (450/02;04;08) from South Korea (K…

  5. Operator Alert - Germany (DE) - Lebara (Group 3G) (262/14)
    Resolved 2h 4m
    Started Apr 28, 2026, 04:27 PM UTC · Resolved Apr 28, 2026, 06:32 PM UTC
    Germany
    2 updates · show timeline
    • investigating · Apr 28, 2026, 04:27 PM UTC

      Start Time: 09:24 AM PST - 04/28/26 End Time: Ongoing We received notification that Lebara (Group 3G) (262/14) from Germany (DE) 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 01163602

    • resolved · Apr 28, 2026, 06:32 PM UTC

      Start Time: 11:00 AM PST - 04/28/26 End Time: 09:24 AM PST - 04/28/26 We received notification that the network issues previously reported by Lebara (Group 3G) (262/14) from Germany (DE) have been resolved. Lebara (Group 3G) (262/14) end users should no longer experience delays receiving SMS messages as all services are back to functioning properly. SF 01163602

    Latest: Start Time: 11:00 AM PST - 04/28/26 End Time: 09:24 AM PST - 04/28/26 We received notification that the network issues previously reported by Lebara (Group 3G) (262/14) from German…

See the full TeleSign outage history

28 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Sign up free to unlock full history

10 free monitors · No credit card

Outage history

Past 30 days · 33 incidents
  • Operator Alert - Cameroon (CM) - Orange Cameroun S.A. (624/02) Ongoing
    Started Apr 29, 2026, 07:25 PM UTC · ● 25m
  • Operator Alert - Costa Rica (CR) - Telefonica Moviles Costa Rica (712/04) Resolved
    Started Apr 29, 2026, 05:08 AM UTC · Resolved Apr 29, 2026, 05:15 PM UTC · 12h 6m
  • Operator Alert - Cameroon (CM) - Orange Cameroun S.A. (624/02) Resolved
    Started Apr 28, 2026, 07:40 PM UTC · Resolved Apr 29, 2026, 05:37 AM UTC · 9h 57m
  • Operator Alert - South Korea (KR) - KTF (450/02;04;08) Resolved
    Started Apr 28, 2026, 06:55 PM UTC · Resolved Apr 28, 2026, 07:51 PM UTC · 56m
  • Operator Alert - Germany (DE) - Lebara (Group 3G) (262/14) Resolved
    Started Apr 28, 2026, 04:27 PM UTC · Resolved Apr 28, 2026, 06:32 PM UTC · 2h 4m
  • Operator Alert - Ireland (IE) - UPC Communications (272/15) Ongoing
    Started Apr 28, 2026, 03:52 PM UTC · ● 1d 3h
  • Operator Alert - Pakistan (PK) - Jazz (410/01;07) - 4/27/26 Resolved
    Started Apr 27, 2026, 09:30 PM UTC · Resolved Apr 28, 2026, 01:16 AM UTC · 3h 45m
  • Operator Alert - Norway (NO) - Netcom - Telia (242/02;05) Resolved
    Started Apr 27, 2026, 02:58 PM UTC · Resolved Apr 27, 2026, 05:27 PM UTC · 2h 28m

See TeleSign in your Pingoru dashboard

Monitor TeleSign alongside every other service your stack depends on — same alerts, same timeline, same calendar — all in one place.

Every status page, one dashboard

Add TeleSign to your Pingoru monitors and it sits next to AWS, Stripe, GitHub, and every other vendor in your stack — a single dashboard for the live status of every cloud and SaaS provider you depend on. One subscription, one inbox, every incident.

Incident timeline, this provider or all of them

Every TeleSign incident — when it started, when it resolved, which services were affected, how bad it was, how long it lasted — laid out in one feed you can scan in 30 seconds. Filter to just TeleSign or see every provider at once.

Maintenance calendar

Scheduled TeleSign maintenance windows land in the same calendar as every other vendor you depend on — see what's running now, what's coming up, and a calendar view. Plan around your vendors instead of being caught out by them.

Every TeleSign status change, one inbox

Pingoru watches TeleSign's official status page every 5 minutes and delivers incident, resolution, and maintenance events to your email, Slack, Discord, Teams, or webhook.

Only alert on the services you use

TeleSign reports on 201 services. Subscribe to the ones you actually use — everything else stays silent.

Email + Slack + Discord + Teams

Signed webhooks on every plan. Route TeleSign alerts wherever your team already lives — no per-integration billing, no tier-gating the channels that matter.

Maintenance, not surprises

Upcoming TeleSign maintenance windows appear in your maintenance calendar days in advance. Plan deploys and rollouts around them instead of finding out during an incident.

Fine-grained alert control

Per-monitor switches for opened, updated, resolved, and maintenance events. Silence the noisy TeleSign services without silencing the monitor entirely.

Invite your team

Premium includes 10 team seats. Everyone watching TeleSign from the same account, with per-user notification preferences for any monitor.

Get notified on TeleSign status changes

Pingoru watches TeleSign's official status page and sends your team instant alerts when incidents open, change severity, or resolve. Route notifications to email, Slack, Discord, or a webhook — wherever your team already lives.

Start monitoring TeleSign free

Monitor TeleSign along with everything else

Pingoru tracks 6,000+ cloud and SaaS status pages in one dashboard. Add TeleSign and every other provider you depend on — AWS, Stripe, GitHub, Cloudflare, OpenAI — and get a single view of the health of every service your app depends on.

Browse the full service directory

Track TeleSign uptime & incident history

See 90 days of TeleSign uptime at a glance, with every past incident linked to its component and update timeline. Export the history as CSV or JSON for SLA reports, postmortems, or vendor evaluations — data your team actually needs, not marketing numbers.

See TeleSign uptime history

Frequently asked questions

What is TeleSign's uptime?
Over the last 90 days, TeleSign reported 99.69% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.telesign.com — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see TeleSign's uptime history rolling forward in real time.
Has TeleSign had outages in 2026?
Yes — TeleSign has had 42 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.
When was the last TeleSign outage?
The most recent TeleSign incident was "Operator Alert - Costa Rica (CR) - Telefonica Moviles Costa Rica (712/04)", which started on April 29, 2026 and was resolved on April 29, 2026. Pingoru captured this directly from https://status.telesign.com. See the full incident card above for affected components and the update timeline.
How often does TeleSign have outages?
Based on the last 90 days, TeleSign averages 14.0 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.
Where is TeleSign's status page?
TeleSign's official status page is https://status.telesign.com. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.
Is TeleSign down right now?
TeleSign is having a partial outage. Pingoru checks the official status page every 5 minutes and flips this headline the moment TeleSign reports a change. Current status is based on 201 tracked services.
How does Pingoru know if TeleSign is down?
We read https://status.telesign.com directly, using TeleSign's own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.
Where can I get notified when TeleSign has an outage?
Create a free Pingoru account and add TeleSign as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.
TeleSign's status page says the service is up, but I'm having issues — what's wrong?
Three common reasons: • A real TeleSign incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real TeleSign issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.
Where does Pingoru get the official TeleSign status?
We use TeleSign's own status page at https://status.telesign.com. Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.
What does "Partial Outage" mean?
TeleSign has a partial outage — one or more components are down, but the rest of the service is operational.

Stop finding out from your users.

We watch TeleSign's official status page every 5 minutes. The moment they report an incident, you get an email — often before the outage is widely noticed.

Monitor TeleSign free →

10 monitors free · email alerts · no credit card

Want the full picture first? See everything Pingoru does →