Increase

Cyber and operational findings

Analyst-reviewed records. The grade states how well the cause is established; event, first public observation and acknowledgement are separate dates.

No public findings for this organisation.

Provider status posts

Collected from the organisation's own public status page. These are its words; DFX adds only the wording classification.

• Elevated API latencyAug 20 15:14 UTC · resolved · major impact
  Investigation mentionedRestoration reported
  1. Aug 20 15:14 UTC investigating: We are observing elevated API latency and are currently investigating the issue.
  2. Aug 20 15:47 UTC investigating: We are still observing elevated API latency and are continuing to investigate the issue.
  3. Aug 20 15:58 UTC identified: We have identified that this issue is related to an incident affecting Google Cloud’s us-west1 region. We are continuing to investigate.
  4. Aug 20 16:30 UTC monitoring: API latency has come back down to normal levels now. We will continue to monitor our service health.
  5. Aug 20 19:55 UTC resolved: This incident has been resolved.
  View on the provider's status page
• FedACH delaysMar 3 04:23 UTC · resolved
  Service restricted or degradedRestoration reported
  1. Mar 3 04:23 UTC investigating: 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. Mar 3 07:02 UTC monitoring: 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...
  3. Mar 3 07:11 UTC monitoring: 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. Mar 3 12:50 UTC monitoring: 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...
  5. Mar 3 14:13 UTC monitoring: 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...
  6. Mar 3 15:37 UTC monitoring: 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...
  7. Mar 3 17:23 UTC monitoring: 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...
  8. Mar 3 18:59 UTC monitoring: 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...
  9. Mar 3 21:32 UTC monitoring: 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. Mar 4 04:11 UTC monitoring: 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...
  11. Mar 4 13:41 UTC resolved: This incident has been resolved.
  View on the provider's status page
• Elevated errors processing webhooksDec 15 20:19 UTC · resolved · major impact
  Restoration reported
  1. Dec 15 20:19 UTC investigating: We're experiencing an elevated level of errors processing webhooks and are currently looking into the issue.
  2. Dec 15 20:50 UTC monitoring: A fix has been implemented and we are monitoring the results.
  3. Dec 15 22:23 UTC resolved: This incident has been resolved.
  View on the provider's status page
• API degradedJul 10 21:20 UTC · resolved · critical impact
  Service restricted or degraded
  1. Jul 10 21:20 UTC investigating: We are currently looking into an issue that's resulting errors in the API and the dashboard.
  2. Jul 10 21:23 UTC resolved: Our systems are back in a healthy state.
  View on the provider's status page
• Intermittent issues due to Google Cloud API failuresJun 12 18:09 UTC · resolved · major impact
  Investigation mentionedRestoration reported
  1. Jun 12 18:09 UTC investigating: We are investigating an issue with card authorizations and file creation.
  2. Jun 12 18:44 UTC investigating: This is related to ongoing the Google Cloud DNS incident. We're observing heightened latency on some card authorizations and File creation.
  3. Jun 12 19:12 UTC monitoring: Our systems have stabilized and we're continuing to monitor all our services. All payment rails are processing.
  4. Jun 12 21:38 UTC resolved: This incident has been resolved.
  View on the provider's status page
• Elevated API ErrorsApr 9 19:44 UTC · resolved
  Restoration reported
  1. Apr 9 19:44 UTC resolved: 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.
  View on the provider's status page
• API errorsOct 29 18:00 UTC · resolved · major impact
  No classified wording
  1. Oct 29 18:07 UTC resolved: The API returned errors to some users on 2024-10-29 from 17:58 UTC to 18:00 UTC.
  View on the provider's status page
• Adding cards to digital walletsAug 1 16:48 UTC · resolved · minor impact
  Investigation mentionedRestoration reported
  1. Aug 1 16:48 UTC investigating: We are investigating an issue when adding cards to digital wallets, such as Apple Pay. Cards already added to digital wallets will continue to work.
  2. Aug 2 03:18 UTC investigating: We are continuing to investigate the issue with Visa.
  3. Aug 2 16:30 UTC resolved: This is now resolved. Note that this issue only impacted new additions to digital wallets and had no impact on other card functionality, such as card creation or payments.
  View on the provider's status page
• API unavailabilityMar 26 16:09 UTC · postmortem · major impact
  Service restricted or degradedRestoration reported
  1. Mar 26 16:09 UTC investigating: We're looking into an issue that's leading to API unavailability, starting at 16:02 UTC.
  2. Mar 26 16:26 UTC resolved: A fix has rolled out and the API is back in a healthy state as of 16:26 UTC.
  3. Mar 26 19:24 UTC postmortem: 24 minutes of API outage was caused by a failed database migration. The outage affected all Increase users. At 16:00 UTC, we executed a migration against Increase’s database. The migration partially failed, resulting in an inconsistency between the deployed code and database...
  View on the provider's status page
• API UnavailabilityMar 16 22:00 UTC · resolved
  No classified wording
  1. Mar 16 23:16 UTC resolved: Scheduled database maintenance by our infrastructure provider led to 16 seconds of API downtime between 22:19:19 and 22:19:35 UTC on 2024-03-16.
  View on the provider's status page
• API UnavailabilityFeb 26 17:00 UTC · resolved
  No classified wording
  View on the provider's status page
• Partial API UnavailabilityFeb 14 18:46 UTC · resolved · major impact
  Investigation mentionedRestoration reported
  View on the provider's status page
• API ErrorsJan 3 20:28 UTC · resolved
  No classified wording
  View on the provider's status page
• Infrastructure maintenanceDec 2 09:28 UTC · resolved · maintenance impact
  No classified wording
  View on the provider's status page
• API errorsNov 16 19:55 UTC · resolved
  No classified wording
  View on the provider's status page
• Erroneous ACH returnsNov 2 07:00 UTC · resolved
  Service restricted or degraded
  View on the provider's status page
• API timeoutsOct 5 21:25 UTC · resolved
  Restoration reported
  View on the provider's status page
• Digital wallet SMS verification issuesSep 22 19:52 UTC · resolved
  Investigation mentionedRestoration reported
  View on the provider's status page
• Check Transfer `note` parameter.Aug 18 21:19 UTC · resolved · minor impact
  Investigation mentionedRestoration reported
  View on the provider's status page
• Delayed inbound ACH TransfersMay 31 21:30 UTC · resolved
  Service restricted or degraded
  View on the provider's status page
• Card Authorizations are degradedMar 8 18:57 UTC · resolved · major impact
  Service restricted or degradedInvestigation mentionedRestoration reported
  View on the provider's status page
• Delayed ACH SubmissionMar 6 18:45 UTC · resolved
  Service restricted or degraded
  View on the provider's status page
• Service timeoutsFeb 4 21:44 UTC · resolved · major impact
  Restoration reported
  View on the provider's status page
• Degraded Fedwire connectionJan 28 15:45 UTC · resolved · minor impact
  Service restricted or degradedRestoration reported
  View on the provider's status page
• ACH processing delaysJan 27 07:00 UTC · resolved
  Service restricted or degraded
  View on the provider's status page