Is RaiseNow down?

Last checked 7m ago
Current status
RaiseNow is up

No incidents right now.

Official status page: https://status.raisenow.com · Polled every 5 minutes · 11 components tracked

RaiseNow is operational right now. Last checked 7m ago; the most recent incident resolved 14h ago.

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

Users who monitor RaiseNow also follow these Finance services: Affirm QuickBooks PayRange Avalara Plaid Xero Zuora Bill.com Xero Developer Platform Recharge View all 6,000+ providers
RaiseNow uptime 99.59% uptime · past 90 days
Mon Wed Fri
MayJunJulAug
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 4m
    Started Aug 02, 2026, 01:46 AM UTC · Resolved Aug 02, 2026, 01:51 AM UTC
    Timeline · 2 updates
    • investigating · Aug 02, 2026, 01:46 AM UTC

      We are aware of an issue affecting our services and currently working on identifying its root cause. You can expect an update on the incident in the next hour.

    • resolved · Aug 02, 2026, 01:51 AM UTC

      This incident has been resolved. We apologize for the inconvenience and thank you for your understanding. We are continuously working on improvements to make our services better.

    Latest: This incident has been resolved. We apologize for the inconvenience and thank you for your understanding. We are continuously working on improvements to make our services better.

  2. Resolved 9m
    Started Aug 02, 2026, 01:31 AM UTC · Resolved Aug 02, 2026, 01:41 AM UTC
    Timeline · 2 updates
    • investigating · Aug 02, 2026, 01:31 AM UTC

      We are aware of an issue affecting our services and currently working on identifying its root cause. You can expect an update on the incident in the next hour.

    • resolved · Aug 02, 2026, 01:41 AM UTC

      This incident has been resolved. We apologize for the inconvenience and thank you for your understanding. We are continuously working on improvements to make our services better.

    Latest: This incident has been resolved. We apologize for the inconvenience and thank you for your understanding. We are continuously working on improvements to make our services better.

  3. Resolved 14m
    Started Aug 01, 2026, 06:12 PM UTC · Resolved Aug 01, 2026, 06:26 PM UTC
    Timeline · 2 updates
    • investigating · Aug 01, 2026, 06:12 PM UTC

      We are aware of an issue affecting our services and currently working on identifying its root cause. You can expect an update on the incident in the next hour.

    • resolved · Aug 01, 2026, 06:26 PM UTC

      This incident has been resolved. We apologize for the inconvenience and thank you for your understanding. We are continuously working on improvements to make our services better.

    Latest: This incident has been resolved. We apologize for the inconvenience and thank you for your understanding. We are continuously working on improvements to make our services better.

  4. Resolved 2h 9m
    Started Aug 01, 2026, 06:12 PM UTC · Resolved Aug 01, 2026, 08:21 PM UTC
    Timeline · 10 updates
    • investigating · Aug 01, 2026, 06:12 PM UTC

      We are aware of an issue affecting our services and currently working on identifying its root cause. You can expect an update on the incident in the next hour.

    • investigating · Aug 01, 2026, 06:42 PM UTC

      We have identified the cause of the incident and are actively working on a resolution. As soon as a fix has been implemented, you'll find an update here.

    • investigating · Aug 01, 2026, 06:42 PM UTC

      We have identified the cause of the incident and are actively working on a resolution. As soon as a fix has been implemented, you'll find an update here.

    • investigating · Aug 01, 2026, 07:12 PM UTC

      We have identified the cause of the incident and are actively working on a resolution. As soon as a fix has been implemented, you'll find an update here.

    • investigating · Aug 01, 2026, 07:12 PM UTC

      We have identified the cause of the incident and are actively working on a resolution. As soon as a fix has been implemented, you'll find an update here.

    • investigating · Aug 01, 2026, 07:42 PM UTC

      We have identified the cause of the incident and are actively working on a resolution. As soon as a fix has been implemented, you'll find an update here.

    • investigating · Aug 01, 2026, 07:43 PM UTC

      We have identified the cause of the incident and are actively working on a resolution. As soon as a fix has been implemented, you'll find an update here.

    • investigating · Aug 01, 2026, 08:13 PM UTC

      We have identified the cause of the incident and are actively working on a resolution. As soon as a fix has been implemented, you'll find an update here.

    • investigating · Aug 01, 2026, 08:13 PM UTC

      We have identified the cause of the incident and are actively working on a resolution. As soon as a fix has been implemented, you'll find an update here.

    • resolved · Aug 01, 2026, 08:21 PM UTC

      This incident has been resolved. We apologize for the inconvenience and thank you for your understanding. We are continuously working on improvements to make our services better.

    Latest: This incident has been resolved. We apologize for the inconvenience and thank you for your understanding. We are continuously working on improvements to make our services better.

  5. Resolved 43m
    Started Aug 01, 2026, 04:33 PM UTC · Resolved Aug 01, 2026, 05:16 PM UTC
    Timeline · 4 updates
    • investigating · Aug 01, 2026, 04:33 PM UTC

      We are aware of an issue affecting our services and currently working on identifying its root cause. You can expect an update on the incident in the next hour.

    • investigating · Aug 01, 2026, 05:03 PM UTC

      We have identified the cause of the incident and are actively working on a resolution. As soon as a fix has been implemented, you'll find an update here.

    • investigating · Aug 01, 2026, 05:03 PM UTC

      We have identified the cause of the incident and are actively working on a resolution. As soon as a fix has been implemented, you'll find an update here.

    • resolved · Aug 01, 2026, 05:16 PM UTC

      This incident has been resolved. We apologize for the inconvenience and thank you for your understanding. We are continuously working on improvements to make our services better.

    Latest: This incident has been resolved. We apologize for the inconvenience and thank you for your understanding. We are continuously working on improvements to make our services better.

See the full RaiseNow outage history

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

Browse RaiseNow outage history →

Or sign up free to get alerts when RaiseNow breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 23 incidents View full outage history →
  • Started Aug 02, 2026, 01:46 AM UTC · Resolved Aug 02, 2026, 01:51 AM UTC · 4m
  • Started Aug 02, 2026, 01:31 AM UTC · Resolved Aug 02, 2026, 01:41 AM UTC · 9m
  • Started Aug 01, 2026, 06:12 PM UTC · Resolved Aug 01, 2026, 06:26 PM UTC · 14m
  • Started Aug 01, 2026, 06:12 PM UTC · Resolved Aug 01, 2026, 08:21 PM UTC · 2h 9m
  • Started Aug 01, 2026, 04:33 PM UTC · Resolved Aug 01, 2026, 05:16 PM UTC · 43m
  • Started Aug 01, 2026, 03:59 PM UTC · Resolved Aug 01, 2026, 05:21 PM UTC · 1h 21m
  • Started Jul 31, 2026, 11:02 AM UTC · Resolved Jul 31, 2026, 11:06 AM UTC · 3m
  • Started Jul 30, 2026, 09:49 PM UTC · Resolved Jul 30, 2026, 10:13 PM UTC · 24m