Textable incident

User Management Operations are Failing

Minor Resolved View vendor source →

Textable experienced a minor incident on May 27, 2026 affecting Application and Application, lasting 22h 40m. The incident has been resolved; the full update timeline is below.

Started
May 27, 2026, 04:51 PM UTC
Resolved
May 28, 2026, 03:31 PM UTC
Duration
22h 40m
Detected by Pingoru
May 27, 2026, 04:51 PM UTC

Affected components

ApplicationApplication

Update timeline

  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.