Zipwhip Status | Software Status

Zipwhip | Status

All Systems Operational

Uptime over the past 90 days. View historical uptime.

Usage Reporting 1.0 / 2.0 Operational

2.0 Web App Operational

1.0/Legacy Web App Operational

Desktop App Operational

Mobile App Operational

Integrations Operational

Messages Operational

Click-to-Text Operational

Chrome Extension Operational

Provision Dashboard Operational

API Operational

Keyword Reporting (1.0/Legacy) Operational

Delivery Receipts Operational

Zipwhip 1.0 (Legacy) Operational

Billing Services Operational

Help Center Operational

Keyword Reporting 2.0 Operational

Zipwhip.com Homepage Operational

90 days ago

100.0 % uptime

Today

Operational

Degraded Performance

Partial Outage

Major Outage

Maintenance

Past Incidents

Feb 25, 2021

Verizon SMS Deliverability

Resolved - The potential degradation of landline delivery of SMS to Verizon Wireless is resolved and normal functionality is in place.
Feb 25, 10:39 PST

Monitoring - Zipwhip engineering are continuing to monitor landline delivery of SMS to Verizon Wireless.
Feb 25, 09:59 PST

Investigating - Zipwhip engineering is investigating a possible degradation with landline delivery of SMS to Verizon Wireless.
Feb 25, 09:31 PST

Feb 24, 2021

No incidents reported.

Feb 23, 2021

No incidents reported.

Feb 22, 2021

No incidents reported.

Feb 21, 2021

No incidents reported.

Feb 20, 2021

No incidents reported.

Feb 19, 2021

No incidents reported.

Feb 18, 2021

No incidents reported.

Feb 17, 2021

No incidents reported.

Feb 16, 2021

No incidents reported.

Feb 15, 2021

T-Mobile SMS Delivery and Receipt Failure

Resolved - This incident has been resolved. Message delivery towards T-Mobile has returned to normal.
Feb 15, 09:45 PST

Monitoring - Zipwhip engineering has implemented a fix and we are monitoring the results. Zipwhip is currently processing the backlog of messages towards T-Mobile. Messages towards T-Mobile will continue to experience delays while Zipwhip processes the backlog.
Feb 15, 08:45 PST

Update - Zipwhip engineering is continuing to work with the carrier to restore connectivity. Currently SMS messages sent to T-Mobile are experiencing a delay of several hours however these messages will be delivered once connectivity is reestablished.
Feb 15, 07:34 PST

Update - We are continuing to work with the carrier to restore connectivity. Currently, SMS messages sent to T-Mobile phone numbers are experiencing a delay of several hours. Thank you for your patience as we resolve this issue.
Feb 15, 04:08 PST

Identified - Carrier maintenance is affecting Zipwhip's connectivity to T-Mobile.
Feb 15, 01:36 PST

Investigating - We are currently investigation this issue.
Feb 15, 01:19 PST

Feb 14, 2021

No incidents reported.

Feb 13, 2021

No incidents reported.

Feb 12, 2021

No incidents reported.

Feb 11, 2021

T-Mobile - Message Destinations - Degraded

Resolved - Zipwhip Operations has verified the issue with SMS messages destined for T-Mobile is Resolved

Users may have experienced latency or failure when sending SMS to T-Mobile Destinations during this incident.

We will be following up with the Carrier for the Root Cause. Thank you for your patience during this Incident.
Feb 11, 11:50 PST

Monitoring - Zipwhip Operations has verified the issue with SMS messages destined for T-Mobile is Resolved, and we're currently Monitoring this issue.

Users may have experienced latency or failure when sending SMS to T-Mobile Destinations during this incident.

We're following up with the Carrier for the cause.
Feb 11, 10:55 PST

Identified - Zipwhip Operations has Identified the issue with SMS messages destined for T-Mobile

Users may experience latency or failure when sending SMS to T-Mobile Destinations

We're currently following up with the Carrier. Thank you for your patience.
Feb 11, 10:33 PST

Investigating - Zipwhip Operations is currently investigating issues with SMS messages destined for T-Mobile

Users may experience latency or failure when sending SMS to T-Mobile Destinations

We will update this issue when we have more info.
Feb 11, 10:12 PST

Related