EZ Texting Outage History

14 incidents recorded over the last 365 days, 14 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Every Recorded EZ Texting Incident

EZ Texting incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 27, 2026Inbound Voice TrafficThis incident has been resolved.25 minResolved
May 8, 2026Degraded Message Delivery on AT&T with Trackable LinksOur records show a minor impact on message delivery to AT&T devices for messages that between 4/29-5/7. The incident has now been resolved.2h 37mResolved
Apr 30, 2026AT&T carrier network — intermittent delivery failuresAs of 1:30 AM EST, the AT&T delivery issue has been resolved. Messages are delivering normally.14h 54mResolved
Apr 25, 2026Service Access OutageThe service access outage has been fully resolved. Customers can now log in and access their EZTexting accounts as normal. We apologize for the disruption this caused and thank you for your patience throughout this…1h 56mResolved
Apr 22, 2026AMEX Credit Card Transaction IssueAmerican Express transactions have been fully reinstated and are processing normally. We apologize for the inconvenience this caused and thank you for your continued patience.22h 56mResolved
Jan 22, 2026Provisioning DelaysThe provisioning delays have been resolved. Our team worked with our aggregator partners to restore normal provisioning timelines. All provisioning is now processing as expected. Thank you for your patience.25h 26mResolved
Jan 16, 2026Inbound 10DLC SMS DisruptionInbound SMS traffic to 10DLC local numbers (non-toll-free, non-short code) was unavailable due to an upstream carrier connectivity issue. Monitoring alerts triggered around 6:07 AM PST indicating no inbound message…-433 minResolved
Jan 15, 2026Service Alert — Inbound 10DLC Messaging ImpactInbound SMS traffic to 10DLC numbers (non-toll-free, non-short code) was unavailable between approximately 12:30 AM PST and 7:30 AM PST. Outbound messaging was not impacted during this time. Service has since been…6 minResolved
Jan 14, 2026Verizon SMS/MMS Delivery DelaysResolved — Verizon Messaging Issue The Verizon carrier issue impacting message delivery has been resolved. Normal service has been restored. If any messages to Verizon contacts were impacted during the incident, we…18h 0mResolved
Dec 23, 2025Provisioning DelaysThe provisioning delays have been resolved. Our team worked closely with our aggregator partners to restore normal provisioning timelines. Services are now operating as expected. Thank you for your patience while we…141h 50mResolved
Dec 15, 2025EZ Texting Service Access DegradationThe issue preventing access to EZ Texting accounts has been resolved. Customers should now be able to log in normally. Thank you for your patience while our team worked to address this issue.2h 3mResolved
Dec 11, 2025Multi-Factor Authentication (MFA) FunctionalityThe issue affecting the new Multi-Factor Authentication process has been fully resolved. Users should now be able to log in without any interruptions. Thank you for your patience while our team worked to identify the…26 minResolved
Dec 5, 2025Inbound AT&T Messages appearing as “Removed attachment of banned MimeType”The issue causing messages from AT&T subscribers to appear in your inbox with the error “Removed attachment of banned MimeType.” has been resolved. We thank you for your patience while we worked with the carrier to…3h 39mResolved
Nov 9, 2025Outage - Message Delivery and Reporting AffectedWe have finished our investigation and monitoring; our team found that the outage was partial, not full, and the majority of messages sent during the service issue period were confirmed delivered. If you see any…1h 59mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next EZ Texting incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This EZ Texting Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before EZ Texting acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single EZ Texting outage in this window ran 5d 21h, against a mean recovery of 18h 11m. If you depend on EZ Texting in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.