Vertex outage on November 19, 2026
Measured window 18:19 UTC to 20:57 UTC on November 19, 2026, 2 hours 38 minutes. Worst status observed: major.
StatusBird recorded Vertex as non-operational from 18:19 UTC on 19 November 2026. The worst state observed was major. We polled every 2 minutes and logged 30 non-operational readings, covering 1 hour. Vertex had posted its own incident at 18:18 UTC, titled "Tax Performance Engine (TPE) Service Disruption". The service had not recovered when this recap was written.
Incident at a glance
| Service | Vertex |
|---|---|
| Date | November 19, 2026 |
| StatusBird first saw it | 18:19 UTC |
| Vendor posted an incident | 18:18 UTC |
| Recovery observed | 20:57 UTC |
| Duration | 2 hours 38 minutes |
| Worst status observed | major |
| Non-operational readings | 79 |
All times UTC. StatusBird polls Vertex every 2 minutes from its own infrastructure, so the true start and end sit within 2 minutes of the times above.
Was Vertex down on November 19, 2026?
Yes. StatusBird recorded Vertex as major from 18:19 UTC until 20:57 UTC, a measured 2 hours 38 minutes. 79 consecutive checks came back non-operational.
Tax calculations may be failing at checkout.
What caused the Vertex outage?
The cause is not known. Vertex opened an incident on its own status page at 18:18 UTC under the title "Tax Performance Engine (TPE) Service Disruption", but it has published no root cause statement that StatusBird can read. We will not guess at what sat behind the disruption.
Vertex published an incident titled "Tax Performance Engine (TPE) Service Disruption" at 18:18 UTC. A root cause has not yet been published by the vendor, so nothing on this page attributes one.
How long was Vertex down?
2 hours 38 minutes, measured from the first non-operational reading at 18:19 UTC to the first reading that cleared it at 20:57 UTC. StatusBird counts a service down from the first reading it fails, not from the moment the vendor admits it, which is why this number can be larger than the one on the vendor's own incident report.
Timeline, in UTC
| Time (UTC) | Event |
|---|---|
| 18:18 UTC | The vendor posts an incident on its own status page |
| 18:19 UTC | StatusBird records its first non-operational reading |
| 18:22 UTC | A second consecutive non-operational reading confirms the outage, alerts go out and this page is published |
| 20:57 UTC | StatusBird records the first reading that clears the outage |
Who and what was affected
This hits any store that calls Vertex to work out tax at checkout. While the service is down, tax calculations may fail, so carts can stall at the tax step, orders may be rejected, and quotes or invoices that need a tax figure may not complete. Back office work that recalculates tax, such as refunds, order edits and exchanges, can fail in the same way.
How StatusBird detected it
StatusBird recorded its first non-operational reading for Vertex at 18:19 UTC, and Vertex's own status page confirms the incident, posted at 18:18 UTC. StatusBird polls every 2 minutes from its own infrastructure, so these are two independent records of the same window.
Method: StatusBird reads Vertex's published status endpoint every 2 minutes and records every reading. Availability figures count major and critical only. The full method is at statusbird.io/methodology.
Lessons for merchants
- Decide in advance what checkout does when the tax service does not answer: block the order, hold it for later pricing, or apply a stored fallback rate.
- Log every failed tax call with the cart details so orders can be repriced and reconciled once the service returns.
- Subscribe to the Vertex status page directly, since its incident went up at 18:18 UTC, one minute before our first non-operational reading.
- Keep a manual process ready for refunds and order edits that need a fresh tax figure during an outage.
The longer version, with the checks specific to this service, is in the Vertex outage playbook.
Frequently asked questions
Was Vertex down on November 19, 2026?
Yes. StatusBird recorded Vertex as major from 18:19 UTC on November 19, 2026, for a measured 2 hours 38 minutes.
How long was Vertex down?
2 hours 38 minutes, measured from the first non-operational reading at 18:19 UTC to the first clear reading at 20:57 UTC. Readings are taken every 2 minutes, so the true start and end sit within 2 minutes of those times.
What caused the Vertex outage?
Vertex published an incident titled "Tax Performance Engine (TPE) Service Disruption" at 18:18 UTC. A root cause has not yet been published by the vendor, so nothing on this page attributes one.
How was this Vertex outage detected?
StatusBird recorded its first non-operational reading for Vertex at 18:19 UTC, and Vertex's own status page confirms the incident, posted at 18:18 UTC. StatusBird polls every 2 minutes from its own infrastructure, so these are two independent records of the same window.
Was my store affected?
If your store calls Vertex during checkout or fulfillment, the requests to check are the ones made between 18:19 UTC and 20:57 UTC on November 19, 2026. Tax calculations may be failing at checkout.
Monitor Vertex with StatusBird
This page exists because StatusBird was already watching. It checks Vertex and the rest of the stack an online store runs on every 2 minutes and sends an SMS, email, Slack, Teams or Discord alert the moment a reading goes non-operational, which on this incident was 18:19 UTC.