Increase Outage History

Increase is up right now

Pingoru has recorded 25 incidents for Increase: 3 in the last 12 months and 1 in the last 90 days.

Source: status.increase.com

25incidents recorded
3last 12 months
1last 90 days
13 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Increase in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202615 of 744 (1%)
September 202600 of 720 (0%)
October 202600 of 568 (0%)

Incidents, newest first

Major August 20, 2026 Elevated API latency 4h 40m API

Started Aug 20, 2026, 03:14 PM UTC· resolved Aug 20, 2026, 07:55 PM UTC

  1. investigating Aug 20, 2026, 03:14 PM UTC

    We are observing elevated API latency and are currently investigating the issue.

  2. investigating Aug 20, 2026, 03:47 PM UTC

    We are still observing elevated API latency and are continuing to investigate the issue.

  3. identified Aug 20, 2026, 03:58 PM UTC

    We have identified that this issue is related to an incident affecting Google Cloud’s us-west1 region. We are continuing to investigate.

  4. monitoring Aug 20, 2026, 04:30 PM UTC

    API latency has come back down to normal levels now. We will continue to monitor our service health.

  5. resolved Aug 20, 2026, 07:55 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 3, 2026 FedACH delays 1d 9h ACH Transfers

Started Mar 03, 2026, 04:23 AM UTC· resolved Mar 04, 2026, 01:41 PM UTC

  1. investigating Mar 03, 2026, 04:23 AM UTC

    The Federal Reserve is experiencing file processing delays with FedACH, which may delay some ACH transfers. You can view the status of FedACH at https://www.frbservices.org/app/status/serviceStatus.do.

  2. monitoring Mar 03, 2026, 07:02 AM UTC

    The Federal Reserve is experiencing file processing delays with FedACH. ACH transfers are not currently reaching their recipients. This means we are not receiving inbound transfers and returns. We'll continue to monitor the network and provide updates. There's no action you need to take at this time. If you've already submitted an ACH transfer to Increase, you do not need to re-send it. You can view the status of FedACH at https://www.frbservices.org/app/status/outage.do?oId=145787.

  3. monitoring Mar 03, 2026, 07:11 AM UTC

    We are now seeing some inbound ACH transfers and returns arrive from the Federal Reserve. We will continue to monitor the network and any transfers already received by Increase.

  4. monitoring Mar 03, 2026, 12:50 PM UTC

    The Federal Reserve has finished processing most ACH transfers from 2026-03-02, but transfers from the final transmission window have not yet been distributed to recipients. The Federal Reserve has not yet started processing ACH transfers for 2026-03-03. We'll continue to monitor the network and provide updates. You can view the status of FedACH at https://www.frbservices.org/app/status/outage.do?oId=145787.

  5. monitoring Mar 03, 2026, 02:13 PM UTC

    The Federal Reserve's FedACH processing continues to be delayed: https://www.frbservices.org/app/status/outage.do?oId=145787. If you sent ACH transfer instructions to Increase before 9:45PM Eastern on 2026-03-02, your transfers have been processed and received by the recipient bank. If you sent transfers between 9:45PM ET and 2:15AM ET on 2026-03-03, your transfers may not yet have reached their recipient bank. You might have inbound ACH transfers or returns that have not yet been delivered to Increase. We are continuing to monitor the network and transfers sent and received by Increase.

  6. monitoring Mar 03, 2026, 03:37 PM UTC

    The Federal Reserve has completed processing for 2026-03-02. All ACH transfers sent to Increase before 2:15AM ET this morning have been delivered to the recipient banks. We're continuing to monitor the situation as the 2026-03-03 ACH day progresses. The Federal Reserve's status updates are at https://frbservices.org/app/status/outage.do?oId=145787 .

  7. monitoring Mar 03, 2026, 05:23 PM UTC

    We are continuing to monitor The Federal Reserve's FedACH processing delays: https://frbservices.org/app/status/outage.do?oId=145787. ACH transfer instructions sent to Increase since 2:15AM ET have not yet been delivered to recipient banks. While you should not re-send ACH transfers, you can consider using an alternative payment rail (for example, wires or Real-Time Payments) for new transfers. We're available to help with any questions in our shared Slack channels or [email protected].

  8. monitoring Mar 03, 2026, 06:59 PM UTC

    The Federal Reserve's FedACH is now operating normally: https://www.frbservices.org/app/status/outage.do?oId=145787. ACH transfers sent to Increase for the 2025-03-03 processing day are now reaching their recipient banks. We are also seeing inbound ACH transfers, returns, and are receiving acknowledgement files for our originated transfers. We will continue to monitor FedACH and transfers.

  9. monitoring Mar 03, 2026, 09:32 PM UTC

    The Federal Reserve's FedACH continues to experience processing delays: https://www.frbservices.org/app/status/outage.do?oId=145788. We will continue to monitor FedACH and provide updates.

  10. monitoring Mar 04, 2026, 04:11 AM UTC

    FedACH has been processing normally since around 8:30PM Eastern time on 2026-03-03. The Federal Reserve's status page (https://www.frbservices.org/app/status/serviceStatus.do) shows all clear. All of Increase's internal monitoring does as well. We'll continue to monitor FedACH timing availability overnight.

  11. resolved Mar 04, 2026, 01:41 PM UTC

    This incident has been resolved.

Read the full incident report →

Major December 15, 2025 Elevated errors processing webhooks 2h 4m Webhooks

Started Dec 15, 2025, 08:19 PM UTC· resolved Dec 15, 2025, 10:23 PM UTC

  1. investigating Dec 15, 2025, 08:19 PM UTC

    We're experiencing an elevated level of errors processing webhooks and are currently looking into the issue.

  2. monitoring Dec 15, 2025, 08:50 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Dec 15, 2025, 10:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical July 10, 2025 API degraded 2m API

Started Jul 10, 2025, 09:20 PM UTC· resolved Jul 10, 2025, 09:23 PM UTC

  1. investigating Jul 10, 2025, 09:20 PM UTC

    We are currently looking into an issue that's resulting errors in the API and the dashboard.

  2. resolved Jul 10, 2025, 09:23 PM UTC

    Our systems are back in a healthy state.

Read the full incident report →

Major June 12, 2025 Intermittent issues due to Google Cloud API failures 3h 29m API, Cards

Started Jun 12, 2025, 06:09 PM UTC· resolved Jun 12, 2025, 09:38 PM UTC

  1. investigating Jun 12, 2025, 06:09 PM UTC

    We are investigating an issue with card authorizations and file creation.

  2. investigating Jun 12, 2025, 06:44 PM UTC

    This is related to ongoing the Google Cloud DNS incident. We're observing heightened latency on some card authorizations and File creation.

  3. monitoring Jun 12, 2025, 07:12 PM UTC

    Our systems have stabilized and we're continuing to monitor all our services. All payment rails are processing.

  4. resolved Jun 12, 2025, 09:38 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 9, 2025 Elevated API Errors – API, Webhooks, ACH Transfers, Wire Transfers and 3 more

Started Apr 09, 2025, 07:44 PM UTC· resolved Apr 09, 2025, 07:44 PM UTC

  1. resolved Apr 09, 2025, 07:44 PM UTC

    We experienced an elevated level of API errors and increased latency for between 19:30:00UTC and 19:36:40UTC. Once our engineers identified the issues, we rolled back immediately and the platform recovered. All service should be restored now.

Read the full incident report →

Major October 29, 2024 API errors 2m

Started Oct 29, 2024, 05:58 PM UTC· resolved Oct 29, 2024, 06:00 PM UTC

  1. resolved Oct 29, 2024, 06:07 PM UTC

    The API returned errors to some users on 2024-10-29 from 17:58 UTC to 18:00 UTC.

Read the full incident report →