Textable incident

Inbound Message Rejection

Notice Resolved View vendor source →
Started
Mar 10, 2026, 07:03 PM UTC
Resolved
Mar 10, 2026, 07:03 PM UTC
Duration
Detected by Pingoru
Mar 10, 2026, 07:03 PM UTC

Affected components

Messaging Backend

Update timeline

  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

Looking to track Textable downtime and outages?

Pingoru polls Textable's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Textable reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Textable alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Textable for free

5 free monitors · No credit card required