Webtext Status - Incident history https://status.webtext.com Webtext Mon, 10 Aug 2026 13:55:17 +0000 Outbound Messaging Failing Type: Incident Duration: 1 hour and 12 minutes Affected Components: SMS Aug 10, 13:55:17 GMT+0 - Investigating - We are currently investigating this incident impacting failure to deliver outbound SMS Messages. Aug 10, 14:21:52 GMT+0 - Identified - We have identified the issue impacting outbound SMS and are working to resolve. Aug 10, 15:07:10 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 hour and 12 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 10</var>, <var data-var='time'>13:55:17</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident impacting failure to deliver outbound SMS Messages. .</p> <p><small>Aug <var data-var='date'> 10</var>, <var data-var='time'>14:21:52</var> GMT+0</small><br><strong>Identified</strong> - We have identified the issue impacting outbound SMS and are working to resolve..</p> <p><small>Aug <var data-var='date'> 10</var>, <var data-var='time'>15:07:10</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 10 Aug 2026 13:55:17 +0000 https://status.webtext.com/incident/cmsnan8361b3a1apqctakcjt3 https://status.webtext.com/incident/cmsnan8361b3a1apqctakcjt3 HTTP/SMPP API Outbound Message Sending Failures Type: Incident Duration: 4 hours and 22 minutes Affected Components: HTTPS, SMPP Nov 5, 16:23:00 GMT+0 - Investigating - We’re aware of an issue impacting message sends through our API HTTP endpoint. Nov 5, 17:29:11 GMT+0 - Investigating - We are currently investigating this incident. Nov 5, 18:11:02 GMT+0 - Investigating - We are continuing to investigate the issue affecting message sends via the API through both HTTP and SMPP methods. We’ll share more details as soon as they’re available. Nov 5, 19:15:39 GMT+0 - Investigating - Our team is actively investigating ongoing delivery issues impacting API message sends over HTTP and SMPP. Restoring normal operation is our top priority. Nov 5, 20:18:38 GMT+0 - Identified - Our engineering teams have identified a contention issue within our infrastructure, tied to an underlying service that supports the healthy run-time of our Outbound messaging processors. We're taking direct action to get things back into a performant state, and will provide additional details once recovery has been established. Nov 5, 20:45:29 GMT+0 - Resolved - Our recovery efforts were completed at approximately 3:38PM Eastern, and we're seeing stable run-time of messaging services (HTTP, SMPP, etc). Service logging shows that messages are flowing though to our carriers, and validation testing performed by the Care Team has also resulted in successfully received messages. Please reach out to the Care Team, if you're still not seeing recovery for any Outbound messaging systems/processes that engage with our end-points. Type: Incident

Duration: 4 hours and 22 minutes

Affected Components: ,

<p><small>Nov <var data-var='date'> 5</var>, <var data-var='time'>16:23:00</var> GMT+0</small><br><strong>Investigating</strong> - We’re aware of an issue impacting message sends through our API HTTP endpoint..</p> <p><small>Nov <var data-var='date'> 5</var>, <var data-var='time'>17:29:11</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Nov <var data-var='date'> 5</var>, <var data-var='time'>18:11:02</var> GMT+0</small><br><strong>Investigating</strong> - We are continuing to investigate the issue affecting message sends via the API through both HTTP and SMPP methods. We’ll share more details as soon as they’re available..</p> <p><small>Nov <var data-var='date'> 5</var>, <var data-var='time'>19:15:39</var> GMT+0</small><br><strong>Investigating</strong> - Our team is actively investigating ongoing delivery issues impacting API message sends over HTTP and SMPP. Restoring normal operation is our top priority..</p> <p><small>Nov <var data-var='date'> 5</var>, <var data-var='time'>20:18:38</var> GMT+0</small><br><strong>Identified</strong> - Our engineering teams have identified a contention issue within our infrastructure, tied to an underlying service that supports the healthy run-time of our Outbound messaging processors. We're taking direct action to get things back into a performant state, and will provide additional details once recovery has been established. .</p> <p><small>Nov <var data-var='date'> 5</var>, <var data-var='time'>20:45:29</var> GMT+0</small><br><strong>Resolved</strong> - Our recovery efforts were completed at approximately 3:38PM Eastern, and we're seeing stable run-time of messaging services (HTTP, SMPP, etc). Service logging shows that messages are flowing though to our carriers, and validation testing performed by the Care Team has also resulted in successfully received messages. Please reach out to the Care Team, if you're still not seeing recovery for any Outbound messaging systems/processes that engage with our end-points..</p> ]]> Wed, 5 Nov 2025 16:23:00 +0000 https://status.webtext.com/incident/cmhm9ubrx02gatayvodkpz61b https://status.webtext.com/incident/cmhm9ubrx02gatayvodkpz61b Intermittent Toll-Free Outbound and SMPP Connection failures Type: Incident Duration: 8 hours and 49 minutes Affected Components: SMS, MMS, SMPP Aug 11, 19:02:55 GMT+0 - Resolved - This incident has been resolved. Aug 11, 17:49:07 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Aug 11, 17:00:46 GMT+0 - Identified - We are currently experiencing intermittent failures affecting Toll-Free Outbound calling and SMPP connections. Impacted customers may encounter periodic call failures or messaging disruptions. Our team has isolated the root cause and is actively working on implementing a fix to restore full service stability. Aug 11, 20:11:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. Aug 12, 01:49:54 GMT+0 - Resolved - We have identified faults impacting the service and have corrected them. We will work through individual customer tickets to resolve any remnants of impact. Type: Incident

Duration: 8 hours and 49 minutes

Affected Components: , ,

<p><small>Aug <var data-var='date'> 11</var>, <var data-var='time'>19:02:55</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Aug <var data-var='date'> 11</var>, <var data-var='time'>17:49:07</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Aug <var data-var='date'> 11</var>, <var data-var='time'>17:00:46</var> GMT+0</small><br><strong>Identified</strong> - We are currently experiencing intermittent failures affecting Toll-Free Outbound calling and SMPP connections. Impacted customers may encounter periodic call failures or messaging disruptions. Our team has isolated the root cause and is actively working on implementing a fix to restore full service stability..</p> <p><small>Aug <var data-var='date'> 11</var>, <var data-var='time'>20:11:00</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Aug <var data-var='date'> 12</var>, <var data-var='time'>01:49:54</var> GMT+0</small><br><strong>Resolved</strong> - We have identified faults impacting the service and have corrected them. We will work through individual customer tickets to resolve any remnants of impact..</p> ]]> Mon, 11 Aug 2025 17:00:46 +0000 https://status.webtext.com/incident/cme7czoy900niomq9ag98okzw https://status.webtext.com/incident/cme7czoy900niomq9ag98okzw Toll Free Numbers failing to deliver outbound Type: Incident Duration: 1 hour and 15 minutes Affected Components: , SMS, MMS, Receipts, Toll Free Messaging → Jul 13, 20:00:00 GMT+0 - Investigating - We are aware of an incident currently impacting Toll Free Number message delivery and messages showing in a "Pending" delivery status. We are currently investigating this incident. Jul 13, 21:15:18 GMT+0 - Resolved - This incident impacting Toll Free Outbound Message Delivery has been resolved. Any failed/pending message was kept in backlog and delivered upon service being restored. Type: Incident

Duration: 1 hour and 15 minutes

Affected Components: , , ,

<p><small>Jul <var data-var='date'> 13</var>, <var data-var='time'>20:00:00</var> GMT+0</small><br><strong>Investigating</strong> - We are aware of an incident currently impacting Toll Free Number message delivery and messages showing in a "Pending" delivery status. We are currently investigating this incident..</p> <p><small>Jul <var data-var='date'> 13</var>, <var data-var='time'>21:15:18</var> GMT+0</small><br><strong>Resolved</strong> - This incident impacting Toll Free Outbound Message Delivery has been resolved. Any failed/pending message was kept in backlog and delivered upon service being restored. .</p> ]]> Sun, 13 Jul 2025 20:00:00 +0000 https://status.webtext.com/incident/cmd23uzyi000mxf9nlh3ecib4 https://status.webtext.com/incident/cmd23uzyi000mxf9nlh3ecib4 Webtext Service Desk Interruption Type: Incident Oct 29, 18:19:04 GMT+0 - Resolved - Working with our Service Desk vendor (JIRA), the Care Team discovered that our "[Support@Webtext.com](mailto:Support@Webtext.com)" inbox monitoring entered a degraded state on 18OCT24\. The underlying issue has been resolved as of 2:01PM Eastern on 29OCT24\. If you had submitted a new service request or responded to an existing incident via to the "[Support@Webtext.com](mailto:Support@Webtext.com)" inbox between those dates, your message was unable to trigger the necessary automation for support case generation and updates to have been received. Please reach out to us in the event you are still experiencing any misbehavior associated to use of the Webtext product suite or are having difficulty getting in contact with our Care Team! Type: Incident

<p><small>Oct <var data-var='date'> 29</var>, <var data-var='time'>18:19:04</var> GMT+0</small><br><strong>Resolved</strong> - Working with our Service Desk vendor (JIRA), the Care Team discovered that our "[Support@Webtext.com](mailto:Support@Webtext.com)" inbox monitoring entered a degraded state on 18OCT24\. The underlying issue has been resolved as of 2:01PM Eastern on 29OCT24\. If you had submitted a new service request or responded to an existing incident via to the "[Support@Webtext.com](mailto:Support@Webtext.com)" inbox between those dates, your message was unable to trigger the necessary automation for support case generation and updates to have been received. Please reach out to us in the event you are still experiencing any misbehavior associated to use of the Webtext product suite or are having difficulty getting in contact with our Care Team!.</p> ]]> Tue, 29 Oct 2024 18:19:04 +0000 https://status.webtext.com/incident/cm2urur6f000thw1azeny2wqu https://status.webtext.com/incident/cm2urur6f000thw1azeny2wqu smsgw.webtext.us.com/send_text.html endpoint unresponsive Type: Incident Duration: 33 minutes Affected Components: HTTPS, MMS, Receipts, SMS, SMS, MMS, Receipts, SMPP Sep 27, 15:20:28 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Sep 27, 15:38:55 GMT+0 - Resolved - This incident has been resolved. Sep 27, 15:06:15 GMT+0 - Investigating - We are aware of impact to customers leveraging the [smsgw.webtext.us.com](http://smsgw.webtext.us.com) endpoint to send outbound messages. You may be receiving a 500, 503, or timeout upon request. We have all resources engaged and are working to resolve the issue as soon as possible. Type: Incident

Duration: 33 minutes

Affected Components: , , , , , , ,

<p><small>Sep <var data-var='date'> 27</var>, <var data-var='time'>15:20:28</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Sep <var data-var='date'> 27</var>, <var data-var='time'>15:38:55</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Sep <var data-var='date'> 27</var>, <var data-var='time'>15:06:15</var> GMT+0</small><br><strong>Investigating</strong> - We are aware of impact to customers leveraging the [smsgw.webtext.us.com](http://smsgw.webtext.us.com) endpoint to send outbound messages. You may be receiving a 500, 503, or timeout upon request. We have all resources engaged and are working to resolve the issue as soon as possible..</p> ]]> Fri, 27 Sep 2024 15:06:15 +0000 https://status.webtext.com/incident/cm1kuvjcw000aht9wdnc2903m https://status.webtext.com/incident/cm1kuvjcw000aht9wdnc2903m MMS Failures to Canadian Recipients Type: Incident Duration: 3 hours and 23 minutes Affected Components: SMS, MMS Jun 4, 20:32:58 GMT+0 - Resolved - This incident has been resolved. Jun 4, 17:10:00 GMT+0 - Investigating - Our provider is currently investigating an issue causing some failed MMS deliveries to Canadian recipients. Messages are being queued and will complete delivery once the issue is resolved. Jun 4, 18:56:08 GMT+0 - Identified - Our provider's partner has identified the issue and is actively working to resolve it. Currently, there is no estimated time for resolution. Jun 4, 19:37:31 GMT+0 - Monitoring - As of Jun 04, 2024 - 15:24 EDT, our vendor has successfully implemented a fix, and we're now monitoring for stability. We will continue to closely monitor the situation. Type: Incident

Duration: 3 hours and 23 minutes

Affected Components: ,

<p><small>Jun <var data-var='date'> 4</var>, <var data-var='time'>20:32:58</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jun <var data-var='date'> 4</var>, <var data-var='time'>17:10:00</var> GMT+0</small><br><strong>Investigating</strong> - Our provider is currently investigating an issue causing some failed MMS deliveries to Canadian recipients. Messages are being queued and will complete delivery once the issue is resolved..</p> <p><small>Jun <var data-var='date'> 4</var>, <var data-var='time'>18:56:08</var> GMT+0</small><br><strong>Identified</strong> - Our provider's partner has identified the issue and is actively working to resolve it. Currently, there is no estimated time for resolution..</p> <p><small>Jun <var data-var='date'> 4</var>, <var data-var='time'>19:37:31</var> GMT+0</small><br><strong>Monitoring</strong> - As of Jun 04, 2024 - 15:24 EDT, our vendor has successfully implemented a fix, and we're now monitoring for stability. We will continue to closely monitor the situation..</p> ]]> Tue, 4 Jun 2024 17:10:00 +0000 https://status.webtext.com/incident/clx0rd8be81791b7oi0m5ylatv https://status.webtext.com/incident/clx0rd8be81791b7oi0m5ylatv