Snapshot 55188
Normalized text
Scripts and page chrome removed; this is what change detection compares.
{
"pages": [
{
"end_time": "2026-10-31T23:59:59-07:00",
"months": [
{
"incidents": [],
"name": "October",
"year": 2026
},
{
"incidents": [],
"name": "September",
"year": 2026
},
{
"incidents": [
{
"code": "r4w1zvpph6qj",
"impact": "major",
"message": "This incident has been resolved.",
"name": "Inbound Voice Traffic",
"timestamp": "Aug \u003cvar data-var='date'\u003e27\u003c/var\u003e, \u003cvar data-var='time'\u003e07:54\u003c/var\u003e - \u003cvar data-var='time'\u003e08:20\u003c/var\u003e PDT"
}
],
"name": "August",
"year": 2026
}
],
"start_time": "2026-08-01T00:00:00-07:00",
"time_zone": "Pacific Time (US \u0026 Canada)"
},
{
"end_time": "2026-07-31T23:59:59-07:00",
"months": [
{
"incidents": [],
"name": "July",
"year": 2026
},
{
"incidents": [],
"name": "June",
"year": 2026
},
{
"incidents": [
{
"code": "1ktbdzmc5992",
"impact": "minor",
"message": "Our records show a minor impact on message delivery to AT\u0026amp;T devices for messages that between 4/29-5/7. The incident has now been resolved.",
"name": "Degraded Message Delivery on AT\u0026T with Trackable Links",
"timestamp": "May \u003cvar data-var='date'\u003e8\u003c/var\u003e, \u003cvar data-var='time'\u003e11:15\u003c/var\u003e - \u003cvar data-var='time'\u003e13:52\u003c/var\u003e PDT"
},
{
"code": "90kcf1k794d0",
"impact": "minor",
"message": "As of 1:30 AM EST, the AT\u0026amp;T delivery issue has been resolved. Messages are delivering normally.",
"name": "AT\u0026T carrier network — intermittent delivery failures",
"timestamp": "Apr \u003cvar data-var='date'\u003e30\u003c/var\u003e, \u003cvar data-var='time'\u003e15:21\u003c/var\u003e - May \u003cvar data-var='date'\u003e1\u003c/var\u003e, \u003cvar data-var='time'\u003e06:16\u003c/var\u003e PDT"
}
],
"name": "May",
"year": 2026
}
],
"start_time": "2026-05-01T00:00:00-07:00",
"time_zone": "Pacific Time (US \u0026 Canada)"
},
{
"end_time": "2026-04-30T23:59:59-07:00",
"months": [
{
"incidents": [
{
"code": "z1qpv5zxmw6f",
"impact": "critical",
"message": "The 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 incident.",
"name": "Service Access Outage",
"timestamp": "Apr \u003cvar data-var='date'\u003e25\u003c/var\u003e, \u003cvar data-var='time'\u003e08:46\u003c/var\u003e - \u003cvar data-var='time'\u003e10:43\u003c/var\u003e PDT"
},
{
"code": "ndxbx62gc0l0",
"impact": "critical",
"message": "American Express transactions have been fully reinstated and are processing normally. We apologize for the inconvenience this caused and thank you for your continued patience.",
"name": "AMEX Credit Card Transaction Issue",
"timestamp": "Apr \u003cvar data-var='date'\u003e22\u003c/var\u003e, \u003cvar data-var='time'\u003e11:00\u003c/var\u003e - Apr \u003cvar data-var='date'\u003e23\u003c/var\u003e, \u003cvar data-var='time'\u003e09:56\u003c/var\u003e PDT"
}
],
"name": "April",
"year": 2026
},
{
"incidents": [],
"name": "March",
"year": 2026
},
{
"incidents": [],
"name": "February",
"year": 2026
}
],
"start_time": "2026-02-01T00:00:00-08:00",
"time_zone": "Pacific Time (US \u0026 Canada)"
},
{
"end_time": "2026-01-31T23:59:59-08:00",
"months": [
{
"incidents": [
{
"code": "6l1dpbq536ld",
"impact": "minor",
"message": "The 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.",
"name": "Provisioning Delays",
"timestamp": "Jan \u003cvar data-var='date'\u003e22\u003c/var\u003e, \u003cvar data-var='time'\u003e06:24\u003c/var\u003e - Jan \u003cvar data-var='date'\u003e23\u003c/var\u003e, \u003cvar data-var='time'\u003e07:51\u003c/var\u003e PST"
},
{
"code": "0bbwk6yfydnt",
"impact": "minor",
"message": "Inbound 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 responses. The issue was caused by inbound message connections being rejected at the carrier level, preventing messages from being delivered to 10DLC numbers. Outbound messaging was not impacted. Service was restored around 7:00 AM PST",
"name": "Inbound 10DLC SMS Disruption",
"timestamp": "Jan \u003cvar data-var='date'\u003e16\u003c/var\u003e, \u003cvar data-var='time'\u003e03:00\u003c/var\u003e - \u003cvar data-var='time'\u003e03:00\u003c/var\u003e PST"
},
{
"code": "vsm8nbds1ymd",
"impact": "major",
"message": "Inbound SMS traffic to 10DLC numbers (non-toll-free, non-short code) was unavailable between approximately 12:30 AM PST and 7:30 AM PST.\n\nOutbound messaging was not impacted during this time.\n\nService has since been restored and inbound messages are processing normally. If you believe any inbound messages were missed during the incident window, please contact support for assistance.\n\nWe appreciate your patience.",
"name": "Service Alert — Inbound 10DLC Messaging Impact",
"timestamp": "Jan \u003cvar data-var='date'\u003e15\u003c/var\u003e, \u003cvar data-var='time'\u003e07:33\u003c/var\u003e - \u003cvar data-var='time'\u003e07:40\u003c/var\u003e PST"
},
{
"code": "kmn9w20qn5gm",
"impact": "major",
"message": "Resolved — Verizon Messaging Issue\n\nThe Verizon carrier issue impacting message delivery has been resolved. Normal service has been restored.\n\nIf any messages to Verizon contacts were impacted during the incident, we recommend resending them.\n\nThank you for your patience",
"name": "Verizon SMS/MMS Delivery Delays",
"timestamp": "Jan \u003cvar data-var='date'\u003e14\u003c/var\u003e, \u003cvar data-var='time'\u003e12:30\u003c/var\u003e - Jan \u003cvar data-var='date'\u003e15\u003c/var\u003e, \u003cvar data-var='time'\u003e06:31\u003c/var\u003e PST"
}
],
"name": "January",
"year": 2026
},
{
"incidents": [
{
"code": "g2f3y5qft1cw",
"impact": "minor",
"message": "The 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 addressed this issue.",
"name": "Provisioning Delays",
"timestamp": "Dec \u003cvar data-var='date'\u003e23\u003c/var\u003e, \u003cvar data-var='time'\u003e11:59\u003c/var\u003e - Dec \u003cvar data-var='date'\u003e29\u003c/var\u003e, \u003cvar data-var='time'\u003e09:49\u003c/var\u003e PST"
},
{
"code": "gkv6fxwfb246",
"impact": "none",
"message": "The 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.",
"name": "EZ Texting Service Access Degradation",
"timestamp": "Dec \u003cvar data-var='date'\u003e15\u003c/var\u003e, \u003cvar data-var='time'\u003e13:27\u003c/var\u003e - \u003cvar data-var='time'\u003e15:30\u003c/var\u003e PST"
},
{
"code": "m90g4smcn5m6",
"impact": "minor",
"message": "The issue affecting the new Multi-Factor Authentication process has been fully resolved. Users should now be able to log in without any interruptions.\n\nThank you for your patience while our team worked to identify the cause and implement the fix.",
"name": "Multi-Factor Authentication (MFA) Functionality",
"timestamp": "Dec \u003cvar data-var='date'\u003e11\u003c/var\u003e, \u003cvar data-var='time'\u003e07:13\u003c/var\u003e - \u003cvar data-var='time'\u003e07:40\u003c/var\u003e PST"
},
{
"code": "jg24ypxhv8tp",
"impact": "minor",
"message": "The issue causing messages from AT\u0026amp;T subscribers to appear in your inbox with the error “Removed attachment of banned MimeType.” has been resolved.\n\nWe thank you for your patience while we worked with the carrier to address this issue.",
"name": "Inbound AT\u0026T Messages appearing as “Removed attachment of banned MimeType”",
"timestamp": "Dec \u003cvar data-var='date'\u003e5\u003c/var\u003e, \u003cvar data-var='time'\u003e14:02\u003c/var\u003e - \u003cvar data-var='time'\u003e17:41\u003c/var\u003e PST"
}
],
"name": "December",
"year": 2025
},
{
"incidents": [
{
"code": "bcznx1bthfkj",
"impact": "critical",
"message": "We 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. \n\nIf you see any inconsistencies with your delivery reporting during the outage period of 9:30am to 1:30pm PT, please let our customer support team know at answers@eztexting.com. Thank you for your patience.",
"name": "Outage - Message Delivery and Reporting Affected",
"timestamp": "Nov \u003cvar data-var='date'\u003e9\u003c/var\u003e, \u003cvar data-var='time'\u003e12:52\u003c/var\u003e - \u003cvar data-var='time'\u003e14:51\u003c/var\u003e PST"
},
{
"code": "sx3xx4csw1sb",
"impact": "minor",
"message": "The earlier MMS sending delays caused by our messaging aggregators have been resolved. Message delivery has returned to normal, and all systems are operating as expected.\n\nThank you for your patience and understanding while we worked to restore full service.",
"name": "We are currently experiencing a platform degradation impacting MMS traffic",
"timestamp": "Nov \u003cvar data-var='date'\u003e4\u003c/var\u003e, \u003cvar data-var='time'\u003e09:59\u003c/var\u003e - \u003cvar data-var='time'\u003e12:55\u003c/var\u003e PST"
}
],
"name": "November",
"year": 2025
}
],
"start_time": "2025-11-01T00:00:00-07:00",
"time_zone": "Pacific Time (US \u0026 Canada)"
}
]
}