Skip to main content
Avalara

Avalara Cross Border Restrictions Service Degradation

Degraded Lasted 17m · started · Avalara's page

Level
confirmed
Worst impact
Degraded
Components
Cross Border Restrictions
Down Index
15of 100

What to do

  • Check whether you use Avalara Cross Border Restrictions. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 17m it lasted.

    Anything that failed between 2026-09-17 18:27 UTC and 2026-09-17 18:44 UTC may need a replay.
  • Subscribe to Avalara's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=avalara works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Avalara 2

  1. investigating

    Avalara Cross Border Restrictions customers may be experiencing degraded service levels. A response team is actively investigating the issue. This page will be kept up to date with new information.

    provider

  2. resolved

    The Avalara Cross Border Restrictions service has been fully restored.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-113412ff12

Is Avalara still down?

No, this incident was resolved 2026-09-17 18:44 UTC. For Avalara's live state, see https://down.guide/avalara.

How long did it last?

17m, from 2026-09-17 18:27 UTC to 2026-09-17 18:44 UTC, by the times Avalara posted.

What was affected?

Avalara named Cross Border Restrictions.

What caused it?

Avalara hasn't published a root cause. If it does, it shows here.

Where does this come from?

Avalara's official status page, https://status.avalara.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.