Textable Outage History

Textable is up right now

Textable had 4 outages in the last 2 years totaling 8h 0m of downtime — averaging 0.2 incidents per month.

There were 4 Textable outages since June 12, 2025 totaling 8h 0m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.textable.co

Major March 25, 2026

Some customers are down

Detected by Pingoru
Mar 25, 2026, 11:15 AM UTC
Resolved
Mar 25, 2026, 02:45 PM UTC
Duration
3h 29m
Affected: ApplicationMessaging BackendAPI
Timeline · 3 updates
  1. investigating Mar 25, 2026, 01:39 PM UTC

    We are currently investigating this issue

  2. monitoring Mar 25, 2026, 01:51 PM UTC

    The issue has been resolved, and we are continuing to monitor for any lingering issues. This seems to have affected a very small number of customers between Mar 25, 2026 @ 07:16:31.109 and Mar 25, 2026 @ 09:28:39.902 Eastern Time.

  3. resolved Mar 25, 2026, 02:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 10, 2026

Inbound Message Rejection

Detected by Pingoru
Mar 10, 2026, 07:03 PM UTC
Resolved
Mar 10, 2026, 07:03 PM UTC
Duration
—
Affected: Messaging Backend
Timeline · 2 updates
  1. resolved Mar 10, 2026, 07:03 PM UTC

    Beginning around 2:40PM ET, some customers may have seen inbound messages from their messaging provider rejected by our API. This was caused by the deployment of a patch designed improve how we handle group MMS; however, the patch negatively affected parsing inbound webhooks from some messaging providers. This should be fully resolved as of 2:55 PM ET

  2. postmortem Mar 10, 2026, 07:05 PM UTC

    This was caused by the deployment of a patch designed improve how we handle group MMS; however, the patch negatively affected parsing inbound webhooks from some messaging providers. This should be fully resolved as of 2:55 PM ET

Read the full incident report →

Major January 14, 2026

Message delivery and API outage for some customers

Detected by Pingoru
Jan 14, 2026, 04:31 PM UTC
Resolved
Jan 14, 2026, 06:12 PM UTC
Duration
1h 41m
Affected: Messaging BackendAPI
Timeline · 5 updates
  1. investigating Jan 14, 2026, 04:38 PM UTC

    We are aware of the issue, beginning around 11:31 AM ET, and are deploying a resolution

  2. identified Jan 14, 2026, 05:19 PM UTC

    A secondary issue has been identified which we are deploying now.

  3. identified Jan 14, 2026, 05:38 PM UTC

    The resolution deployment is nearly complete, we expect it to be live in a few minutes

  4. monitoring Jan 14, 2026, 05:47 PM UTC

    The resolution has been deployed, and server logs indicate the resolution was successful. Please contact support if you are still experiencing issues. We are continuing to monitor for any ongoing issues.

  5. resolved Jan 14, 2026, 06:12 PM UTC

    Affected customers have reported this issue is resolved.

Read the full incident report →

Critical June 12, 2025

Service Outage - Authentication Failures

Detected by Pingoru
Jun 12, 2025, 06:17 PM UTC
Resolved
Jun 12, 2025, 09:06 PM UTC
Duration
2h 49m
Affected: ApplicationApplication
Timeline · 6 updates
  1. investigating Jun 12, 2025, 06:17 PM UTC

    We are receiving numerous reports that users are unable to log in to web and mobile applications. The error "Invalid e-mail address or password" is displayed Inbound and Outbound messaging appears to be unaffecfted. We are investigating

  2. identified Jun 12, 2025, 06:27 PM UTC

    Google Cloud is down globally. Many public services are currently affected.

  3. identified Jun 12, 2025, 07:05 PM UTC

    Beginning at Jun 12, 2025 @ 14:04:54.780 Eastern Time , we noticed a significant increase of errors from the Google Compute authentication service. These errors prevent us from validating the identities of our users and subsequently prevents our users from accessing our application(s). We are attempting to escalate the situation to Google Cloud Support, but the outage appears to also affect our ability to request support. This incident appears to affect many other services as is visible on https://downdetector.com/ as well as on Google's own status page: https://status.cloud.google.com/ We are doing everything we can to restore service. Thank you.

  4. monitoring Jun 12, 2025, 08:04 PM UTC

    As of Jun 12, 2025 @ 15:56 ET, it looks like authentication failures have stopped. There may still be lingering issues with message deliverability and API access. We are continuing to investigate the situation.

  5. monitoring Jun 12, 2025, 08:16 PM UTC

    Some authentication failures continue as of 16:14 ET; however, the vast majority of requests are succeeding. We've identified some data loss of received MMS attachments, so users may need to request that their contacts re-send any missing attachments. We are continuing to investigate this situation.

  6. resolved Jun 12, 2025, 09:06 PM UTC

    Our monitoring systems indicate that our platform is now fully operational. Additionally, the Google Cloud status page indicates that they have resolved the issues

Read the full incident report →