We started checking Zip on November 2, 2026, which is 6 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Zip reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Zip's own status page declared. Below it, any public chatter we saw about Zip and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Zip's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Unverified user reportsNo reports about Zip in the last 24 hours, which is not evidence that nothing is wrong.
Zip's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Zip's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Zip next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
198
US-West
100.00%
157
Europe
100.00%
141
Asia-Pacific
100.00%
85
Their declared record
Zip's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Disrupted MFA log-in servicesAll systems operational
Aug 10, 2026, 1:00 PM UTC to Aug 10, 2026, 1:00 PM UTC (0 min)resolved
their latest update (Aug 10, 2026, 1:00 PM UTC): Our team noticed an increase in reports of users with MFA issues logging in.
We identified an issue with our SMS delivery service and have since resolved it.
We are monitoring to ensure full restoration of services.
Unexpected Rate Limiting Responses in Zip REST API CallsAll systems operational
Jun 2, 2026, 5:44 PM UTC to Jun 2, 2026, 8:30 PM UTC (2h 46m)resolved
their latest update (Jun 2, 2026, 8:30 PM UTC): This incident has been resolved.
Zip Degraded Platform PerformanceMinor incident
May 28, 2026, 4:38 PM UTC to May 28, 2026, 5:48 PM UTC (1h 10m)resolved
their latest update (May 28, 2026, 5:48 PM UTC): This incident has been resolved.
Zip Platform Experiencing Degraded PerformanceMinor incident
Apr 30, 2026, 9:11 PM UTC to Apr 30, 2026, 9:51 PM UTC (40 min)resolved
their latest update (Apr 30, 2026, 9:51 PM UTC): The Zip team has fully resolved this incident. Thank you for your patience as we got to the bottom of the issue.
If you are continuing to experience any performance issues, please reach out to support@ziphq.com for further assistance.
Zip Global Search Indexing DegredationPartial outage
Mar 10, 2026, 4:29 PM UTC to Mar 10, 2026, 6:01 PM UTC (1h 32m)resolved
their latest update (Mar 10, 2026, 6:01 PM UTC): Update: The issue impacting Global Search indexing has now been resolved. Global Search results should be returning as expected.
If you continue to experience any issues or notice missing results, please submit a Support ticket so our team can investigate further.
Thank you fo…
Zip Platform instability caused by AWS EC2 errorsMajor outage
Feb 12, 2026, 9:50 PM UTC to Feb 12, 2026, 9:59 PM UTC (8 min)resolved
their latest update (Feb 12, 2026, 9:59 PM UTC): The Zip team has fully resolved this incident. Thank you for your patience as we got to the bottom of the issue. If you are still experiencing any issues please reach out to support@ziphq.com for further assistance.
Cloudflare outage - Ziphq.com not accessibleMajor outage
Nov 18, 2025, 12:14 PM UTC to Nov 18, 2025, 4:17 PM UTC (4h 4m)resolved
their latest update (Nov 18, 2025, 4:17 PM UTC): I’m happy to share that the Cloudflare outage has now been resolved. We’ve tested our infrastructure extensively, and everything appears to be back to normal. Our engineering team will continue to monitor and please do submit a support request if you see any unexpected behavior. …
AWS Outage Causing Partial Zip Service DegradationMinor incident
Oct 20, 2025, 11:40 PM UTC to Oct 20, 2025, 11:40 PM UTC (0 min)resolved
their latest update (Oct 20, 2025, 11:40 PM UTC): The earlier AWS-related latency issue has been fully mitigated. Zip has been operating normally throughout, with all core capabilities fully available.
Zip Performance IssuePartial outage
Aug 19, 2025, 6:49 PM UTC to Aug 19, 2025, 7:00 PM UTC (12 min)resolved
their latest update (Aug 19, 2025, 7:00 PM UTC): The Zip team has fully resolved this incident. Thank you for your patience as we got to the bottom of the issue. If you are still experiencing any issues with Zip, please reach out to support@ziphq.com for further assistance.
Zip Front End InconsistenciesMinor incident
May 27, 2025, 2:13 PM UTC to May 27, 2025, 4:59 PM UTC (2h 46m)resolved
their latest update (May 27, 2025, 4:59 PM UTC): Our third-party provider has resolved the issue. Thank you for your patience during this resolution. If you are still experiencing any issues, please reach out to support@ziphq.com.
Showing the 10 most recent of 28 incidents Zip has declared in the history we hold.
These entries are Zip's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Zip's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.