Is Text-Em-All down?
Last checked just nowNo incidents right now.
Text-Em-All is operational right now. Last checked just now; the most recent incident resolved 5d ago.
Real-time Text-Em-All status, recent outages, and incident history: pulled directly from Text-Em-All's official status page at status.text-em-all.com every 5 minutes. Pingoru tracks 14 Text-Em-All services and has captured 4 incidents in the last 90 days (99.91% uptime). Get email, Slack, Discord, or webhook alerts the moment Text-Em-All reports a new incident, free for 3 monitors, no credit card.
Recent outages & incidents
Past 90 days- Text MessagingText Messaging — 536bd6f1fd254d6008000281
Timeline · 3 updates
- investigating · Oct 28, 2026, 04:50 PM UTC
We are aware of an issue with Text Messaging. Broadcasts may go out slowly or appear stuck. Conversation messages are resulting in errors. We are currently investigating.
- monitoring · Oct 28, 2026, 05:22 PM UTC
We have put a fix in place for the issue with Text Messaging. Broadcasts should continue to go out without any further action. Conversation messages should now send successfully. We are currently monitoring. If you are experiencing any issues, please reach out [email protected].
- resolved · Oct 28, 2026, 05:47 PM UTC
The issue with Text Messaging is resolved. Broadcasts and Conversation messages should send normally. Any broadcasts that were impacted during the downtime will be retried and should send as normal. Thank you for your patience. If you are still experiencing issues, please reach out to our support team.
Latest: The issue with Text Messaging is resolved. Broadcasts and Conversation messages should send normally. Any broadcasts that were impacted during the downtime will be retried and shou…
-
- Text-Em-All Mobile AppText-Em-All Mobile App — 536bd6f1fd254d6008000281SOAP APISOAP API — 536bd6f1fd254d6008000281Text-Em-All WebsiteText-Em-All Website — 536bd6f1fd254d6008000281Text MessagingText Messaging — 536bd6f1fd254d6008000281Voice MessagingVoice Messaging — 536bd6f1fd254d6008000281
Timeline · 3 updates
- investigating · Oct 27, 2026, 02:18 AM UTC
We’re aware of an issue affecting access to platform. Some users may experience errors or be unable to access our application. Our engineering team is actively investigating, and we’ll post an update within 30 minutes or as soon as we have more information.
- monitoring · Oct 27, 2026, 02:52 AM UTC
A fix has been applied and service has been restored. We’re continuing to monitor the system closely to confirm stability before marking this incident resolved. If you’re still experiencing issues, please contact support.
- resolved · Oct 27, 2026, 03:54 AM UTC
This incident has been resolved. Service has been stable since the fix was applied and all systems are operating normally. We apologize for any disruption this caused and thank you for your patience.
Latest: This incident has been resolved. Service has been stable since the fix was applied and all systems are operating normally. We apologize for any disruption this caused and thank you…
-
- Text-Em-All WebsiteText-Em-All Website — 536bd6f1fd254d6008000281
Timeline · 3 updates
- investigating · Oct 09, 2026, 03:36 PM UTC
We are aware of an issue with importing contacts and groups into broadcasts from some integrations such as ChurchStaq. We are currently investigating.
- monitoring · Oct 09, 2026, 03:59 PM UTC
We've applied a change and are monitoring the results.
- resolved · Oct 09, 2026, 04:19 PM UTC
We've confirmed that the affected features have been restored to normal.
Latest: We've confirmed that the affected features have been restored to normal.
-
- Website: Internal536bd6f1fd254d6008000281
Timeline · 3 updates
- investigating · Sep 16, 2026, 06:20 PM UTC
Our payment processor is having an outage. We are unable to process credit card payments at this time.
- monitoring · Sep 16, 2026, 06:21 PM UTC
Our payment processor is having an outage. We are unable to process credit card payments at this time.
- resolved · Sep 16, 2026, 07:16 PM UTC
Our payment provider resolved the issue.
Latest: Our payment provider resolved the issue.
-
Incident record
Since April 2026 · Status.io · 14 components checked every 5 minutesThe longest incident in the last year, System Slowness on July 22, 2026, ran for 2 hours.
Most affected components, last 12 months
- SOAP API2
- SOAP API — 536bd6f1fd254d60080002812
- Text Messaging2
- Text Messaging — 536bd6f1fd254d60080002812
- Text-Em-All Mobile App2
Latest incidents
- Text Messaging is not fully working
We are aware of an issue with Text Messaging. Broadcasts may go out slowly or appear stuck. Conversation messages are resulting in errors. We are currently…
- Service Disruption
We’re aware of an issue affecting access to platform. Some users may experience errors or be unable to access our application. Our engineering team is actively…
- Contact integrations are not fully working
We are aware of an issue with importing contacts and groups into broadcasts from some integrations such as ChurchStaq. We are currently investigating.
- Text Messaging is not fully working ResolvedStarted Oct 28, 2026, 04:50 PM UTC · Resolved Oct 28, 2026, 05:47 PM UTC · 57m
- Service Disruption ResolvedStarted Oct 27, 2026, 02:18 AM UTC · Resolved Oct 27, 2026, 03:54 AM UTC · 1h 36m
- Started Oct 09, 2026, 03:36 PM UTC · Resolved Oct 09, 2026, 04:19 PM UTC · 42m
- Payment Processor Issues ResolvedStarted Sep 16, 2026, 06:20 PM UTC · Resolved Sep 16, 2026, 07:16 PM UTC · 55m