BlockChyp Outage History

BlockChyp is up right now

BlockChyp had 3 outages in the last 2 years totaling 25h 27m of downtime — averaging 0.1 incidents per month.

There were 3 BlockChyp outages since November 19, 2025 totaling 25h 27m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.blockchyp.com

Notice March 3, 2026

Funding Delay due to Issues at the Federal Reserve

Detected by Pingoru
Mar 03, 2026, 03:01 PM UTC
Resolved
Mar 04, 2026, 04:24 PM UTC
Duration
1d 1h
Affected: Funding
Timeline · 3 updates
  1. monitoring Mar 03, 2026, 03:01 PM UTC

    We have been informed that the Federal Reserve is experiencing an issue that may result in a funding delay for some merchants. This is not related to the bank change that was communicated yesterday. We will continue to provide updates as the provider communicates them.

  2. monitoring Mar 03, 2026, 07:23 PM UTC

    The Federal Reserve has completed remediation of the impacted services. We have been informed that settlement funding for the March 2nd and March 3rd business days may still be delayed.

  3. resolved Mar 04, 2026, 04:24 PM UTC

    This incident has been resolved

Read the full incident report →

Minor November 19, 2025

BlockChyp Customer Portal Inaccessible

Detected by Pingoru
Nov 19, 2025, 03:27 PM UTC
Resolved
Nov 19, 2025, 03:31 PM UTC
Duration
4m
Affected: Merchant and Partner Dashboard
Timeline · 2 updates
  1. identified Nov 19, 2025, 03:27 PM UTC

    The BlockChyp customer portal is currently inaccessible. Teams are working on identifying and remediating the issue.

  2. resolved Nov 19, 2025, 03:31 PM UTC

    The issue with the BlockChyp customer portal has been resolved. Thank you.

Read the full incident report →

Notice November 19, 2025

Intermittent Outage Resolved

Detected by Pingoru
Nov 19, 2025, 02:53 PM UTC
Resolved
Nov 19, 2025, 02:53 PM UTC
Duration
Affected: Processing Back Ends
Timeline · 1 update
  1. resolved Nov 19, 2025, 02:53 PM UTC

    We experienced a brief service disruption on November 18th at 5:00 PM EST, which was quickly resolved. We apologize for the disruption.

Read the full incident report →