Is RaiseNow down?

Last checked 2m 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 2m ago; the most recent incident resolved 13d 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 9 incidents in the last 90 days (100.00% 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 100.00% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 2h 4m
    Started May 31, 2026, 06:22 AM UTC · Resolved May 31, 2026, 08:27 AM UTC
    Timeline · 12 updates
    • investigating · May 31, 2026, 06:22 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 · May 31, 2026, 06:27 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 · May 31, 2026, 06:31 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 · May 31, 2026, 07:01 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 · May 31, 2026, 07:01 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 · May 31, 2026, 07:15 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 · May 31, 2026, 07:17 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 · May 31, 2026, 07:47 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 · May 31, 2026, 07:48 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 · May 31, 2026, 08:18 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 · May 31, 2026, 08:18 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 · May 31, 2026, 08:27 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 25s
    Started May 31, 2026, 02:04 AM UTC · Resolved May 31, 2026, 02:04 AM UTC
    Timeline · 2 updates
    • investigating · May 31, 2026, 02:04 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 · May 31, 2026, 02:04 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 23s
    Started May 23, 2026, 02:04 AM UTC · Resolved May 23, 2026, 02:04 AM UTC
    Timeline · 2 updates
    • investigating · May 23, 2026, 02:04 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 · May 23, 2026, 02:04 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.

  4. Resolved
    Started May 16, 2026, 04:50 PM UTC · Resolved May 16, 2026, 04:50 PM UTC
    Timeline · 2 updates
    • investigating · May 16, 2026, 04:50 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 · May 16, 2026, 04:50 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 6m
    Started Apr 25, 2026, 05:29 AM UTC · Resolved Apr 25, 2026, 05:35 AM UTC
    Timeline · 4 updates
    • investigating · Apr 25, 2026, 05:29 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 · Apr 25, 2026, 05: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 · Apr 25, 2026, 05:31 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 · Apr 25, 2026, 05:35 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

4 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 · 9 incidents View full outage history →
  • Started May 31, 2026, 06:22 AM UTC · Resolved May 31, 2026, 08:27 AM UTC · 2h 4m
  • Started May 31, 2026, 02:04 AM UTC · Resolved May 31, 2026, 02:04 AM UTC · 25s
  • Started May 23, 2026, 02:04 AM UTC · Resolved May 23, 2026, 02:04 AM UTC · 23s
  • Started May 16, 2026, 04:50 PM UTC · Resolved May 16, 2026, 04:50 PM UTC ·
  • Started Apr 25, 2026, 05:29 AM UTC · Resolved Apr 25, 2026, 05:35 AM UTC · 6m
  • Started Apr 25, 2026, 02:21 AM UTC · Resolved Apr 25, 2026, 02:44 AM UTC · 22m
  • Started Apr 25, 2026, 12:07 AM UTC · Resolved Apr 25, 2026, 01:01 AM UTC · 53m
  • Started Mar 22, 2026, 01:27 AM UTC · Resolved Mar 22, 2026, 01:31 AM UTC · 3m