Dutchie logo

Is Dutchie Down?

SaaSLive status, outages, and incident history

Partly. Some of Dutchie is down.

Dutchie is in a partial outage as of November 9, 2026. Some components are down and others are still running, so check the list below to see whether your region or feature is affected.

Partial OutageChecked just nowLive · every 60s1 active incident

Don't find out like this next time

You searched to find out Dutchie was down. Next time we tell you, usually before your customers do, and always before you think to check.

Free, no password, no card. Unsubscribe in one click.

Official Dutchie status page
How we know: the official Dutchie status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Dutchie Status Summary

As of 14:55 UTC on 9 November 2026, Dutchie has a partial outage. PulsAPI checked Dutchie's official status page and found 21 of 23 components operational, with 1 active incident. Over the last 30 days PulsAPI measured 99.91% uptime for Dutchie, counting degraded performance as up. The latest incident, "POS and Backoffice Access Issues", started on Nov 9, 2026 and is still open.

Cite as: PulsAPI, “Dutchie status”, checked 9 November 2026, 14:55 UTC. https://www.pulsapi.com/services/dutchie

Dutchie Component Status

2 of 23 Dutchie components are impaired. Worst problems listed first.

2partial outage21operational
Backoffice
Partial Outage
Register
Partial Outage
BioTrack
Operational

20 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Connect, Consumer Menus, Dispensary Portal, Dutchie Hub, Dutchie Plus, Dutchie POS API, Integrated Payments, Leaf Data, MassCIP, Metrc, MMUR, MN OMC, and 8 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Dutchie Outages & Incidents

Incident history from the official Dutchie status page, including resolution updates.

POS and Backoffice Access IssuesStarted Nov 9, 2026Investigating

We’re investigating reports that some customers are unable to access POS and Backoffice. We are aware of an upstream failure between Cloudflare & Multiple ISPs that is impacting service operating near the Midwest region. --- [2026-11-09T14:35:17Z] (investigating) We’re investigating reports that some customers are unable to access POS and Backoffice. Our team is actively working to identify the cause and will share updates as soon as more information is available.

Regional ISP Issues Causing LatencyResolved Nov 6, 2026 · 25h 34mResolved

Dutchie has been working with our infrastructure provider Cloudflare and has received confirmation that the issue has been identified and resolved --- [2026-11-06T16:37:54Z] (investigating) We are aware some users are experiencing slow load times in Back Office, primarily affecting customers in Arizona. This appears to be related to an issue with multiple regional internet service providers. Some users may see long delays or blank screens when loading the Catalog, Discounts, Distribution and Cultivation batches. Point of Sale is not affected. We are currently investigating.

Massachusetts Delivery ErrorsResolved Nov 5, 2026 · 6h 45mResolved

This issue has been resolved. Metrc restored the affected permissions at 4:42 PM ET today, and deliveries for Massachusetts dispensaries are now processing normally. Thank you for your patience. --- [2026-11-05T17:09:34Z] (investigating) We're currently seeing elevated errors when creating deliveries for Massachusetts dispensaries, related to a validation requirement from Metrc for transporter facility information. This may affect deliveries where a driver is not configured in Dutchie as a third-party operator. We're working directly with Metrc to resolve this and will share updates here. If your delivery drivers are genuine third-party operators, please confirm their configuration under Delivery settings in your Backoffice; for all other drivers, no action is needed and we do not recommend changing this setting as a workaround.

Dutchie Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Dutchie incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
Aug 1199.82% average · 7 days with incidentsNov 9

Going further back: Dutchie uptime by month and every recorded Dutchie outage.

Live Dutchie Outage Reports

Problems reported by engineers using Dutchie. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Dutchie problems reported yet.

Are you seeing Dutchie problems too?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Dutchie

Is Dutchie down? Dutchie reports live availability for 21 components at status.dutchie.com, among them Metrc, Consumer Menus and Dutchie Hub. Track Dutchie outages, degradations and past incidents here, with uptime history and alerts across your SaaS stack.

Over the past 30 days, PulsAPI has measured Dutchie uptime at 99.91%. Response times, incident history, and SLA tracking for Dutchie are available on the PulsAPI dashboard.

Dutchie Status FAQ

Is Dutchie down right now?

The verdict at the top of this page comes from the latest poll of the official Dutchie status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Dutchie is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Dutchie recovers.

How do I check Dutchie uptime history?

PulsAPI tracks Dutchie uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 99.91%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Dutchie changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Dutchie outages?

PulsAPI reads the official Dutchie status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Dutchie components?

Yes. PulsAPI monitors 23 individual Dutchie components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Dutchie goes down?

Yes. Create a free account and subscribe to Dutchie: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Dutchie to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Dutchie problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Dutchie?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Dutchie plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Dutchie with the rest of your stack

2660+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services