Is RaiseNow down?

Last checked 5m 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 5m ago; the most recent incident resolved 12h 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 17 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
MayJunJul
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 3m
    Started Jul 31, 2026, 11:02 AM UTC · Resolved Jul 31, 2026, 11:06 AM UTC
    Timeline · 2 updates
    • investigating · Jul 31, 2026, 11:02 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 · Jul 31, 2026, 11:06 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 24m
    Started Jul 30, 2026, 09:49 PM UTC · Resolved Jul 30, 2026, 10:13 PM UTC
    Timeline · 4 updates
    • investigating · Jul 30, 2026, 09:49 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 · Jul 30, 2026, 09:56 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 · Jul 30, 2026, 10:00 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 · Jul 30, 2026, 10:13 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.

  3. Resolved 3h
    Started Jul 30, 2026, 10:21 AM UTC · Resolved Jul 30, 2026, 01:22 PM UTC
    Timeline · 17 updates
    • investigating · Jul 30, 2026, 10:21 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.

    • investigating · Jul 30, 2026, 10:22 AM 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 · Jul 30, 2026, 10:24 AM 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 · Jul 30, 2026, 10:54 AM 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 · Jul 30, 2026, 10:58 AM 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 · Jul 30, 2026, 11:28 AM 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 · Jul 30, 2026, 11:30 AM 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 · Jul 30, 2026, 12:00 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 · Jul 30, 2026, 12: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 · Jul 30, 2026, 12:33 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 · Jul 30, 2026, 12:38 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 · Jul 30, 2026, 12:38 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 · Jul 30, 2026, 12:51 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 · Jul 30, 2026, 01:21 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 · Jul 30, 2026, 01:21 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 · Jul 30, 2026, 01:21 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 · Jul 30, 2026, 01:22 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 7m
    Started Jul 30, 2026, 06:06 AM UTC · Resolved Jul 30, 2026, 06:14 AM UTC
    Timeline · 2 updates
    • investigating · Jul 30, 2026, 06:06 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 · Jul 30, 2026, 06:14 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.

  5. Resolved 1h
    Started Jul 16, 2026, 07:02 AM UTC · Resolved Jul 16, 2026, 08:03 AM UTC
    Timeline · 7 updates
    • investigating · Jul 16, 2026, 07:02 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.

    • investigating · Jul 16, 2026, 07:02 AM 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 · Jul 16, 2026, 07:32 AM 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 · Jul 16, 2026, 07:32 AM 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 · Jul 16, 2026, 08:02 AM 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 · Jul 16, 2026, 08:03 AM 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 · Jul 16, 2026, 08:03 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.

See the full RaiseNow outage history

12 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 · 17 incidents View full outage history →
  • 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
  • Started Jul 30, 2026, 10:21 AM UTC · Resolved Jul 30, 2026, 01:22 PM UTC · 3h
  • Started Jul 30, 2026, 06:06 AM UTC · Resolved Jul 30, 2026, 06:14 AM UTC · 7m
  • Started Jul 16, 2026, 07:02 AM UTC · Resolved Jul 16, 2026, 08:03 AM UTC · 1h
  • Started Jul 16, 2026, 05:33 AM UTC · Resolved Jul 16, 2026, 06:39 AM UTC · 1h 6m
  • Started Jul 15, 2026, 08:53 AM UTC · Resolved Jul 15, 2026, 09:31 AM UTC · 37m
  • Started Jul 14, 2026, 08:05 AM UTC · Resolved Jul 14, 2026, 08:51 AM UTC · 45m