Textable Outage History

Textable is up right now

Pingoru has recorded 22 incidents for Textable: 4 in the last 12 months and 0 in the last 90 days.

Source: status.textable.co

22incidents recorded
4last 12 months
0last 90 days
7 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Textable in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 2026123 of 744 (3%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 744 (0%)
November 202600 of 21 (0%)

Incidents, newest first

Minor May 27, 2026 User Management Operations are Failing 22h 40m Application, Application

Started May 27, 2026, 04:51 PM UTC· resolved May 28, 2026, 03:31 PM UTC

  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 3h 29m Application, Messaging Backend, API

Started Mar 25, 2026, 11:15 AM UTC· resolved Mar 25, 2026, 02:45 PM UTC

  1. investigating Mar 25, 2026, 11:15 AM 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 15m Messaging Backend

Started Mar 10, 2026, 06:40 PM UTC· resolved Mar 10, 2026, 06:55 PM UTC

  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 1h 41m Messaging Backend, API

Started Jan 14, 2026, 04:31 PM UTC· resolved Jan 14, 2026, 06:12 PM UTC

  1. investigating Jan 14, 2026, 04:31 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 2h 49m Application, Application

Started Jun 12, 2025, 06:17 PM UTC· resolved Jun 12, 2025, 09:06 PM UTC

  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 →