Textable Outage History

Textable is up right now

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

There were 4 Textable outages since January 14, 2026 totaling 27h 51m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.textable.co

Minor May 27, 2026

User Management Operations are Failing

Detected by Pingoru
May 27, 2026, 04:51 PM UTC
Resolved
May 28, 2026, 03:31 PM UTC
Duration
22h 40m
Affected: ApplicationApplication
Timeline · 5 updates
  1. investigating May 27, 2026, 04:51 PM UTC

    We've received a number of reports that adding / editing / deleting users is failing. We've identified an issue with our billing platform causing synchronous rejections of updates to billing details. We are working towards a resolution

  2. identified May 27, 2026, 05:54 PM UTC

    We are working with our billing vendor to restore the integration that supports our user management operations. We are also developing an application patch to gracefully handle billing update failures in a way that does not block user management operations.

  3. identified May 27, 2026, 07:49 PM UTC

    We are preparing to deploy a patch to affected customers within the next 30 minutes

  4. monitoring May 27, 2026, 08:15 PM UTC

    We've deployed a patch and are monitoring logs to confirm resolution. If you were affected by this issue, please re-try any operations which previously failed. If you still experience failures while managing users, please open a support case.

  5. resolved May 28, 2026, 03:31 PM UTC

    We've received notification from our billing vendor (Stripe) that they had "an outage affecting some customers between 19:09 UTC on May 26th to 18:35 UTC on May 27th where some of our merchants received an elevated 429 errors on their Stripe accounts, tied to rate limited API requests. " These errors were an unintended result of a recent change on Stripe's end to update the rate limit configuration for certain types of requests. Our observations are aligned with Stripe's outage description, and we believe this incident is fully resolved.

Read the full incident report →

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 →