New Multi-region uptime checks and custom-domain status pages

Kaleyra Outage History

Daily provider-status observations and published incident history for Kaleyra.

Operational

Kaleyra is operational. Verified . Official provider source.

Looking for an update now? Check the current status, or follow Kaleyra for future changes.

100% of 35 verified observed days had no reported provider issue

90-Day Trend

Jul 3Sep 30

Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.

Monthly Status Summary

Month Issue-free days Days Tracked Days with issues
September 2026 100% 30 0

This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.

Recorded Daily Status (Last 91 Days)

Jul 2 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

No source-attested incident records are available for the current collector history. Older legacy archive records remain available below.

Legacy Incident Archive

4 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.

August 2026
Observing Call connectivity outage Incoming/outgoing issue from TTSL
critical Source not attested
Last archived state: resolved
View archived record details
investigating
Observing Call connectivity outage Incoming/outgoing issue from TTSL Working with the operator team to resolve the same- Timings:- 2:10 Pm IST Will keep you posted as soon as we have an update.
July 2026
Degraded Performance on Voice Applications
major Source not attested
Last archived state: resolved
View archived record details
identified
Team still analysing the issue.
identified
Identified sudden spike in traffic caused the issue, Still investigating is going on
investigating
Team is still investigating the issue.
investigating
Initial investigation indicates Redis-related errors triggered an instance scale-up at around 8:30 PM. Despite the scaling event, errors continue to be observed, and the team is actively working to identify and resolve the root cause.
investigating
Observed an issue with Voice Core Application, At the moment it is pointed to one customer, We are reviewing performance of the Voice Applications.
June 2026
Incoming Calls Affected - TTSL Bangalore
critical Source not attested
Last archived state: resolved
View archived record details
monitoring
There was network issue which was resolved. This is under monitoring
identified
We have identified Network Congestion causing the connectivity from Voice Server to DB, Our team still analysing the issue.
investigating
Incoming calls affected for all Customer using Enterprise Platform.
April 2026
Planned Merging Activity for Airtel Pune (2047132870)
major Source not attested
Last archived state: resolved
View archived record details
investigating
Planned merging activity for Airtel Pune (20 47132870), We expect all incoming and outgoing services to be intermittently interrupted for all customers who uses DID in Pilot Number (20 47132870). This is a Business-Critical activity to ensure high reliability and flexibility in scaling.