Is Domo down?

Last checked just now
Current status
Domo has degraded performance

7 active incidents: 617980 - Minor Incident - AWS US-East-1 - Apps, 617883 - Minor Incident - Azure East US - Other · +5 more

Get alerts when Domo breaks →

Free · no credit card

Official status page: https://status.domo.com · Polled every 5 minutes · 0 components tracked

Real-time Domo status, recent outages, and incident history — pulled directly from Domo's official status page at https://status.domo.com every 5 minutes. Pingoru tracks 0 Domo services and has captured 10 incidents in the last 90 days (87.78% uptime). Get email, Slack, Discord, or webhook alerts the moment Domo reports a new incident — free for 5 monitors, no credit card.

Users who monitor Domo also follow these Analytics services: New Relic Grafana Fivetran Segment Amplitude Mixpanel Hudl Qualtrics Hotjar Branch View all 6,000+ providers
Domo uptime 87.78% uptime · past 90 days
Mon Wed Fri
JanFebMarApr
Less More

Recent outages & incidents

Past 7 days
  1. 617980 - Minor Incident - AWS US-East-1 - Apps
    Ongoing ● 5d
    Started Apr 24, 2026, 06:17 PM UTC
    1 update · show timeline
    • monitoring · Apr 24, 2026, 06:17 PM UTC

      <b>Fri, 24 Apr 2026 11:33:17 Pacific</b> <br />We are currently experiencing increased card refresh rates issues with the our Distribute & Domo Everywhere features across all regions..<br /> <b>Fri, 24 Apr 2026 11:45:00 Pacific</b> <br />The Domo Operations team has identified the increased card refresh rates issues with the our Distribute & Domo Everywhere features is NOT across all regions. It is for a single customer instance and use case.<br />

    Latest: <b>Fri, 24 Apr 2026 11:33:17 Pacific</b> <br />We are currently experiencing increased card refresh rates issues with the our Distribute & Domo Everywhere features across all regio…

  2. 617883 - Minor Incident - Azure East US - Other
    Ongoing ● 5d 3h
    Started Apr 24, 2026, 02:24 PM UTC
    1 update · show timeline
    • monitoring · Apr 24, 2026, 03:34 PM UTC

      <b>Fri, 24 Apr 2026 08:24:30 Pacific</b> <br />Domo Operations has now applied a fix and are monitoring Domo’s systems to ensure normal operation is restored.<br /> <b>Fri, 24 Apr 2026 08:37:30 Pacific</b> <br />Domo Operations has resolved this issue. No data was lost and all systems are operating as usual.<br />

    Latest: <b>Fri, 24 Apr 2026 08:24:30 Pacific</b> <br />Domo Operations has now applied a fix and are monitoring Domo’s systems to ensure normal operation is restored.<br /> <b>Fri, 24 Apr …

  3. 617514 - Minor Incident - AWS AP-Northeast-1, AWS AP-South-1, AWS AP-Southeast-2, AWS CA-Central-1, AWS EU-West-1, AWS US-East-1, AWS US-West-2, Azure East US, GCP US-East4, OCI US-Ashburn-1 - Distribute and Domo Everywhere
    Ongoing ● 6d 9h
    Started Apr 23, 2026, 08:38 AM UTC
    1 update · show timeline
    • monitoring · Apr 23, 2026, 08:38 AM UTC

      <b>Tue, 21 Apr 2026 03:51:01 Pacific</b> <br />Domo detected an issue affecting a subset of Domo Everywhere Publish customer's job run times. Domo’s Operations team is investigating the cause of this issue. <br /> <b>Thu, 23 Apr 2026 09:00:00 Pacific</b> <br />Domo Operations has now applied a fix and are monitoring Domo’s systems to ensure normal operation is restored.<br /> <b>Thu, 23 Apr 2026 10:54:40 Pacific</b> <br />Domo Operations has resolved this issue. No data was lost and all systems are operating as usual.<br />

    Latest: <b>Tue, 21 Apr 2026 03:51:01 Pacific</b> <br />Domo detected an issue affecting a subset of Domo Everywhere Publish customer's job run times. Domo’s Operations team is investigatin…

  4. 617976 - Minor Incident - AWS AP-Northeast-1, AWS AP-South-1, AWS AP-Southeast-2, AWS CA-Central-1, AWS EU-West-1, AWS US-East-1, AWS US-West-2, Azure East US, GCP US-East4, OCI US-Ashburn-1 - Distribute and Domo Everywhere
    Ongoing ● 6d 21h
    Started Apr 22, 2026, 09:00 PM UTC
    1 update · show timeline
    • monitoring · Apr 24, 2026, 06:02 PM UTC

      <br />Domo detected an issue affecting Scheduled Reports redirect links. Domo’s Operations team is investigating the cause of this issue.<br />

    Latest: <br />Domo detected an issue affecting Scheduled Reports redirect links. Domo’s Operations team is investigating the cause of this issue.<br />

  5. 616356 - Minor Incident - AWS AP-Northeast-1, AWS US-East-1 - Data Ingestion, Data Transformation, Visualize
    Resolved 13d 12h
    Started Apr 15, 2026, 11:05 AM UTC · Resolved Apr 28, 2026, 11:58 PM UTC
    1 update · show timeline
    • monitoring · Apr 15, 2026, 11:05 AM UTC

      <b>Wed, 15 Apr 2026 03:11:00 Pacific</b> <br />Domo detected an issue affecting a small percentage of customers. Customers may experience delays with data updates, visualizations, and data transformation. Domo’s Operations team is investigating the cause of this issue.<br /> <b>Wed, 15 Apr 2026 06:00:00 Pacific</b> <br />Domo Operations has resolved this issue. No data was lost and all systems are operating as usual.<br />

    Latest: <b>Wed, 15 Apr 2026 03:11:00 Pacific</b> <br />Domo detected an issue affecting a small percentage of customers. Customers may experience delays with data updates, visualizations, …

See the full Domo outage history

5 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Sign up free to unlock full history

10 free monitors · No credit card

Outage history

Past 30 days · 10 incidents
  • 617980 - Minor Incident - AWS US-East-1 - Apps Ongoing
    Started Apr 24, 2026, 06:17 PM UTC · ● 5d
  • 617883 - Minor Incident - Azure East US - Other Ongoing
    Started Apr 24, 2026, 02:24 PM UTC · ● 5d 3h
  • 617514 - Minor Incident - AWS AP-Northeast-1, AWS AP-South-1, AWS AP-Southeast-2, AWS CA-Central-1, AWS EU-West-1, AWS US-East-1, AWS US-West-2, Azure East US, GCP US-East4, OCI US-Ashburn-1 - Distribute and Domo Everywhere Ongoing
    Started Apr 23, 2026, 08:38 AM UTC · ● 6d 9h
  • 617976 - Minor Incident - AWS AP-Northeast-1, AWS AP-South-1, AWS AP-Southeast-2, AWS CA-Central-1, AWS EU-West-1, AWS US-East-1, AWS US-West-2, Azure East US, GCP US-East4, OCI US-Ashburn-1 - Distribute and Domo Everywhere Ongoing
    Started Apr 22, 2026, 09:00 PM UTC · ● 6d 21h
  • 617139 - Minor Incident - AWS US-East-1 - Data Connections, Data Ingestion Ongoing
    Started Apr 21, 2026, 02:22 PM UTC · ● 8d 4h
  • 616966 - Minor Incident - AWS US-East-1 - Data Connections Ongoing
    Started Apr 20, 2026, 03:12 PM UTC · ● 9d 3h
  • 616875 - Minor Incident - AWS CA-Central-1 - Data Connections Ongoing
    Started Apr 16, 2026, 09:42 PM UTC · ● 12d 20h
  • 616356 - Minor Incident - AWS AP-Northeast-1, AWS US-East-1 - Data Ingestion, Data Transformation, Visualize Resolved
    Started Apr 15, 2026, 11:05 AM UTC · Resolved Apr 28, 2026, 11:58 PM UTC · 13d 12h

See Domo in your Pingoru dashboard

Monitor Domo alongside every other service your stack depends on — same alerts, same timeline, same calendar — all in one place.

Every status page, one dashboard

Add Domo to your Pingoru monitors and it sits next to AWS, Stripe, GitHub, and every other vendor in your stack — a single dashboard for the live status of every cloud and SaaS provider you depend on. One subscription, one inbox, every incident.

Incident timeline, this provider or all of them

Every Domo incident — when it started, when it resolved, which services were affected, how bad it was, how long it lasted — laid out in one feed you can scan in 30 seconds. Filter to just Domo or see every provider at once.

Maintenance calendar

Scheduled Domo maintenance windows land in the same calendar as every other vendor you depend on — see what's running now, what's coming up, and a calendar view. Plan around your vendors instead of being caught out by them.

Every Domo status change, one inbox

Pingoru watches Domo's official status page every 5 minutes and delivers incident, resolution, and maintenance events to your email, Slack, Discord, Teams, or webhook.

Only alert on the services you use

Subscribe to the specific Domo services you rely on. Everything else stays silent.

Email + Slack + Discord + Teams

Signed webhooks on every plan. Route Domo alerts wherever your team already lives — no per-integration billing, no tier-gating the channels that matter.

Maintenance, not surprises

Upcoming Domo maintenance windows appear in your maintenance calendar days in advance. Plan deploys and rollouts around them instead of finding out during an incident.

Fine-grained alert control

Per-monitor switches for opened, updated, resolved, and maintenance events. Silence the noisy Domo services without silencing the monitor entirely.

Invite your team

Premium includes 10 team seats. Everyone watching Domo from the same account, with per-user notification preferences for any monitor.

Get notified on Domo status changes

Pingoru watches Domo's official status page and sends your team instant alerts when incidents open, change severity, or resolve. Route notifications to email, Slack, Discord, or a webhook — wherever your team already lives.

Start monitoring Domo free

Monitor Domo along with everything else

Pingoru tracks 6,000+ cloud and SaaS status pages in one dashboard. Add Domo and every other provider you depend on — AWS, Stripe, GitHub, Cloudflare, OpenAI — and get a single view of the health of every service your app depends on.

Browse the full service directory

Track Domo uptime & incident history

See 90 days of Domo uptime at a glance, with every past incident linked to its component and update timeline. Export the history as CSV or JSON for SLA reports, postmortems, or vendor evaluations — data your team actually needs, not marketing numbers.

See Domo uptime history

Frequently asked questions

What is Domo's uptime?
Over the last 90 days, Domo reported 87.78% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.domo.com — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see Domo's uptime history rolling forward in real time.
Has Domo had outages in 2026?
Yes — Domo has had 3 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.
When was the last Domo outage?
The most recent Domo incident was "616356 - Minor Incident - AWS AP-Northeast-1, AWS US-East-1 - Data Ingestion, Data Transformation, Visualize", which started on April 15, 2026 and was resolved on April 28, 2026. Pingoru captured this directly from https://status.domo.com. See the full incident card above for affected components and the update timeline.
How often does Domo have outages?
Based on the last 90 days, Domo averages 1.0 reported incident per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.
Where is Domo's status page?
Domo's official status page is https://status.domo.com. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.
Is Domo down right now?
Domo has degraded performance. Pingoru checks the official status page every 5 minutes and flips this headline the moment Domo reports a change. Current status is based on 0 tracked services.
How does Pingoru know if Domo is down?
We read https://status.domo.com directly, using Domo's own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.
Where can I get notified when Domo has an outage?
Create a free Pingoru account and add Domo as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.
Domo's status page says the service is up, but I'm having issues — what's wrong?
Three common reasons: • A real Domo incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real Domo issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.
Where does Pingoru get the official Domo status?
We use Domo's own status page at https://status.domo.com and cross-reference their homepage (https://www.domo.com). Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.
What does "Degraded" mean?
Domo is reporting degraded performance — services are up but slower than usual, or a subset of requests is failing.

Stop finding out from your users.

We watch Domo's official status page every 5 minutes. The moment they report an incident, you get an email — often before the outage is widely noticed.

Monitor Domo free →

10 monitors free · email alerts · no credit card

Want the full picture first? See everything Pingoru does →