Is Central 1 down?

Last checked 7m ago
Current status
Central 1 has degraded performance

2 active incidents: INC226796 - Scheduled and Recurring e-Transfers Not Process…, INC224203 -- Saved logins issue on v18.1 iOS Forge App

Official status page: https://status.central1.com · Polled every 5 minutes · 5 components tracked

Central 1 is reporting degraded performance right now (last checked 7m ago). Services are up but slower or partially failing.

Real-time Central 1 status, recent outages, and incident history — pulled directly from Central 1's official status page at https://status.central1.com every 5 minutes. Pingoru tracks 5 Central 1 services and has captured 42 incidents in the last 90 days (96.43% uptime). Get email, Slack, Discord, or webhook alerts the moment Central 1 reports a new incident — free for 5 monitors, no credit card.

Users who monitor Central 1 also follow these Payments services: Square Authorize.Net Cash App FreedomPay Worldpay Clover Klarna JotForm Wise Breadcrumb View all 6,000+ providers
Central 1 uptime 96.43% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Active incidents 2

  1. Ongoing ● 17d 21h
    Started Aug 28, 2026, 08:29 PM UTC
    Payment ServicesDigital Banking Services
    Timeline · 4 updates
    • investigating · Aug 28, 2026, 08:29 PM UTC

      Central 1 is aware of an Interac issue they are having with the Scheduled and Recurring e-Transfers. Currently some e-Transfers are not being processed on the due date. Customers requiring immediate fund transfers may send an immediate e-Transfer instead of a scheduled or recurring e-Transfer at this time. We have reached out to Interac support to investigate and will provide updates as we receive them. Central 1 - [email protected] - 1.888.889.7878 Option 1

    • investigating · Sep 01, 2026, 09:36 PM UTC

      Central 1 continues to work with Interac to investigate an issue affecting a subset of Scheduled and Recurring e-Transfers (S&R). Our review of historical processing volumes indicates that the number of impacted Scheduled and Recurring e-Transfers is relatively low, and the majority continue to be processed successfully. The issue may affect any customer using Scheduled or Recurring e-Transfers. Scheduled and Recurring e-Transfers are managed by Interac within a separate system, and Central 1 is unable to directly view or identify pending S&R transactions. We continue to engage Interac for updates and will provide our next status update on Thursday, September 3 at 12:00 p.m. PT (3:00 p.m. ET). Central 1 - [email protected] - 1.888.889.7878 Option 1

    • identified · Sep 03, 2026, 11:21 PM UTC

      Central 1 continues to work with Interac to investigate an issue affecting a subset of Scheduled and Recurring e-Transfers (S&R). Interac has identified a potential fix and is currently conducting testing and validation activities to confirm the root cause and effectiveness of the solution. Subject to successful testing and approval, Interac is currently targeting deployment of the fix as part of its September 20 production release. The issue remains intermittent and may affect some customers using Scheduled or Recurring e-Transfers. Customers requiring immediate fund transfers should send an immediate e-Transfer instead of a Scheduled or Recurring e-Transfer until this issue has been resolved. We continue to work closely with Interac and will provide our next update, including any changes to the expected release timeline, on Wednesday, September 9. Central 1 - [email protected] - 1.888.889.7878 Option 1

    • identified · Sep 09, 2026, 10:31 PM UTC

      Central 1 continues to work with Interac on an issue affecting a subset of Scheduled and Recurring e-Transfers (S&R). Interac's fix remains targeted for September 20, 2026, and testing is currently underway. The majority of Scheduled and Recurring e-Transfers continue to process successfully. Customers requiring immediate fund transfers should use a standard e-Transfer until the issue is resolved. Our next update will be provided by Wednesday, September 16 or sooner if new information becomes available. Central 1 - [email protected] - 1.888.889.7878 Option 1

    Latest: Central 1 continues to work with Interac on an issue affecting a subset of Scheduled and Recurring e-Transfers (S&R). Interac's fix remains targeted for September 20, 2026, and tes…

  2. Ongoing ● 76d 21h
    Started Jun 30, 2026, 08:54 PM UTC
    Digital Banking ServicesIncident Alerting
    Timeline · 4 updates
    • investigating · Jun 30, 2026, 08:54 PM UTC

      We are currently investigating an issue affecting some users on iOS devices where saved login information is not being retained as expected on the v18.1 Forge App. Some members reported that the issue was resolved after upgrading their device to iOS 26.5 operating system. While we have not yet confirmed this as a universal solution, members experiencing this issue may wish to ensure their device is running the latest available version of iOS. Members can continue to access the service by manually entering their card number and password if their saved login is unavailable. Our team is actively investigating the issue and working to determine the root cause. Additional updates will be provided as more information becomes available. We apologize for any inconvenience and appreciate your patience while we work toward a resolution. [email protected] - 1.888.889.7878 (option 2)

    • investigating · Jul 08, 2026, 02:34 PM UTC

      We continue to investigate an issue affecting some members using the Forge App on iOS devices, where saved login information may not be retained as expected. Through our investigation, we have identified a valid workaround that allows saved login functionality to continue working as designed. Members should ensure that Biometric Login (Face ID or Touch ID) is enabled within the Forge App. We have observed that when Biometric Login is disabled, saved login information may be removed, either immediately or after a period of time. While the workaround has proven effective, our team continues to investigate the underlying cause. We have experienced challenges consistently reproducing the issue within our internal testing environments, which has extended the time required to identify the root cause and implement a permanent fix. Our team remains actively engaged in the investigation and will provide additional updates as more information becomes available. [email protected] - 1.888.889.7878 (option 2)

    • investigating · Aug 21, 2026, 01:11 PM UTC

      Please be assured that we continue to treat this as a priority investigation and remain actively engaged with our Development team. Over the past several weeks, we've dedicated significant effort to reproducing the behavior internally and identifying a reliable pattern that would help us isolate the root cause. Unfortunately, despite extensive testing, we have not yet been able to replicate the issue in our own environments. We've also worked with a small number of affected clients by providing debug versions of the iOS application to capture additional diagnostic information during reproduction attempts; however, these efforts have not yet produced any conclusive findings. While we do not have a meaningful update on the root cause at this time, the investigation remains active and ongoing. We understand the impact this issue has on your users and appreciate your patience as we continue working to gather the information necessary to move the investigation forward. In the meantime, we encourage affected staff members to continue testing with the debug iOS application where possible. For impacted clients who have not yet received the debug version and would like to assist with troubleshooting, please let us know and we would be happy to provide it. Should the issue occur again, any details surrounding the event would be extremely helpful to our investigation. In particular, we would appreciate information regarding the actions performed leading up to the login being cleared, the timestamp, the device type and model, the operating system version (iOS), and any screenshots or screen recordings that may help us better understand the circumstances under which the issue occurred. We remain committed to resolving this issue and will provide further updates as soon as we have any significant developments to share. Thank you for your continued patience and understanding. [email protected] - 1.888.889.7878 (option 2)

    • investigating · Sep 04, 2026, 10:38 PM UTC

      Our Development and Support teams continue to actively investigate reports of saved login credentials unexpectedly being cleared within the iOS Forge App. This remains a high-priority investigation, and we continue to devote resources toward identifying the underlying cause. As part of our ongoing troubleshooting efforts, we may have identified an instance where the issue was reproduced by a staff member using a debug version of the production iOS application. While this is an encouraging development, the investigation is still in progress and additional analysis is required. We continue to encourage users testing the debug version of the iOS application to report any occurrences of this issue and provide as much detail as possible to assist with our investigation. We understand the impact this issue has on affected users and appreciate your continued patience and cooperation. Please be assured that the investigation remains active and ongoing, and we will provide further updates as soon as significant new information becomes available. Thank you for your continued partnership as we work toward a resolution. [email protected] 1.888.889.7878 (option 2)

    Latest: Our Development and Support teams continue to actively investigate reports of saved login credentials unexpectedly being cleared within the iOS Forge App. This remains a high-prior…

Recent outages & incidents

Past 90 days
  1. Resolved
    Started Sep 10, 2026, 11:23 PM UTC · Resolved Sep 10, 2026, 11:23 PM UTC
    Payment ServicesDigital Banking Services
    Timeline · 1 update
    • resolved · Sep 10, 2026, 11:23 PM UTC

      Please be advised, there was a service outage on Interac e-Transfer 3.4 from 3:56 to 4:06 pm PT (6:56 pm to 7:06 pm ET). Your customers may have seen a timeout or error during this time when trying to send or manually receive e-Transfers. Central 1 Support - [email protected] | 1.888.889.7878 (press 1)

    Latest: Please be advised, there was a service outage on Interac e-Transfer 3.4 from 3:56 to 4:06 pm PT (6:56 pm to 7:06 pm ET). Your customers may have seen a timeout or error during this…

  2. Resolved 55m
    Started Sep 01, 2026, 05:35 PM UTC · Resolved Sep 01, 2026, 06:31 PM UTC
    Payment Services
    Timeline · 2 updates
    • investigating · Sep 01, 2026, 05:35 PM UTC

      Central 1 has identified that multiple credit unions are missing their ORPI cheque return reports this morning dated for 01/09/2026. Our technical team is currently investigating the issue. At this time, we have confirmed that the reports are not available via SFTP for affected clients. We will provide our next update by 12:00 p.m. PT (3:00 p.m. ET), or sooner if additional information becomes available. Central 1 Support - [email protected] | 1.888.889.7878 (press 1)

    • resolved · Sep 01, 2026, 06:31 PM UTC

      Central 1 has resolved the issue affecting ORPI cheque return reports. The impacted ORPI files have been regenerated and successfully transferred for delivery. Clients should note that the affected cheque return records will be included in tomorrow's MERG file. If you continue to experience issues accessing your ORPI report or believe records are missing after tomorrow's MERG file is received, please contact Central 1 Support with examples for investigation. Central 1 Support - [email protected] | 1.888.889.7878 (press 1)

    Latest: Central 1 has resolved the issue affecting ORPI cheque return reports. The impacted ORPI files have been regenerated and successfully transferred for delivery. Clients should note …

  3. Resolved 4d 4h
    Started Aug 13, 2026, 06:51 PM UTC · Resolved Aug 17, 2026, 11:30 PM UTC
    Payment ServicesTreasury ServicesDigital Banking Services
    Timeline · 5 updates
    • identified · Aug 13, 2026, 06:51 PM UTC

      Central 1 is aware of an issue that has temporarily caused User Management Security Officers and Business User Admins to lose their access privileges today. Our team has identified the root cause and is actively working to restore the affected permissions. At this time, regular users are not affected and can continue using the system as usual. If you require any urgent user access changes while Security Officer privileges are unavailable, please get in touch with our Support team, and we will work with you to address those requests. We will provide our next update by 10:00 a.m. PT (1 p.m. ET) on August 14, 2026, or sooner if the issue is resolved. We apologize for any inconvenience and appreciate your patience as we work to resolve this issue. Central 1 - [email protected] - 1.888.889.7878 Option 1

    • identified · Aug 14, 2026, 03:45 PM UTC

      We are continuing to work on a fix for this issue.

    • identified · Aug 14, 2026, 03:47 PM UTC

      As a follow-up to our previous notification, we would like to provide additional clarification regarding this incident. The issue is related to a delay in a background synchronization process. While Security Officers and MemberDirect Business User Administrators can continue to grant application permissions through User Management (UM) or MDB User Admin (BUA), and those changes appear to complete successfully, the corresponding permission updates are not currently being synchronized as expected. This delay does not affect: * Password changes, which take effect immediately. * Changes to a user's Active/Inactive status, which also take effect immediately. We anticipate the synchronization process will catch up by the end of the weekend. Once synchronization has been fully restored, any permissions granted yesterday, today, or over the weekend will be applied and reflected in users' accounts. We will provide our next update by 10:00 a.m. PT (1 p.m. ET) on August 17, 2026, or sooner if the issue is resolved. We apologize for any inconvenience this may cause and appreciate your patience.

    • identified · Aug 17, 2026, 04:45 PM UTC

      We are actively working to finalize the planned synching updates for the User Manager (UM) and Business User Administrator (BUA) tool. While progress is being made, the implementation is taking longer than expected. We sincerely apologize for any inconvenience this may cause and appreciate your understanding. If you have an urgent request, please reach out to Support for immediate assistance. We will provide our next update by 10:00 a.m. PT (1 p.m. ET) on August 18, 2026, or sooner if the issue is resolved. Central 1 - [email protected] - 1.888.889.7878 Option 1

    • resolved · Aug 17, 2026, 11:30 PM UTC

      After thorough investigation and remediation efforts, this incident has been resolved. User Management (UM) Security Officer and Business User Administrator (BUA) permissions have been fully restored, and the synchronization process is now operating as expected. Any pending permission updates have been successfully processed and reflected in user accounts. We sincerely apologize for any inconvenience this issue may have caused and appreciate your patience and understanding while we worked to restore service.

    Latest: After thorough investigation and remediation efforts, this incident has been resolved. User Management (UM) Security Officer and Business User Administrator (BUA) permissions have …

  4. Resolved 25m
    Started Aug 11, 2026, 04:56 PM UTC · Resolved Aug 11, 2026, 05:22 PM UTC
    Payment Services
    Timeline · 3 updates
    • investigating · Aug 11, 2026, 04:56 PM UTC

      We are currently investigating a potential issue impacting Central 1’s Remote Deposit Capture (RDC) error or mobile deposits. At approximately 9:30 a.m. PT (12:30 p.m. ET) we observed an increase in RDC errors. At this time, we are working to validate scope and confirm whether customer impact is present. We will provide an update within 1 hour or sooner as more information becomes available. Central 1 - [email protected] - 1.888.889.7878 Option 1

    • resolved · Aug 11, 2026, 05:22 PM UTC

      Central 1 has confirmed that a service interruption impacted Remote Deposit Capture (RDC) between 2:05 a.m. PT and 10:13 a.m. PT (5:05 a.m. ET and 1:13 p.m. ET) on August 11, 2026. The disruption lasted approximately 8 hours and 8 minutes. During this period, members may have experienced errors when attempting to submit mobile cheque deposits through participating financial institution applications utilizing Central 1's RDC service. Service was fully restored at 10:13 a.m. PT (1:13 p.m. ET), and we continue to monitor the platform to ensure ongoing stability. A root cause analysis is being prioritized and will be completed as part of our standard incident management process.

    • postmortem · Aug 24, 2026, 02:21 PM UTC

      **Postmortem: INC226099 – Mobile Remote Deposit Capture \(mRDC\) Service Interruption** On August 11, 2026, between 2:05 a.m. and 10:13 a.m. PT \(5:05 a.m. and 1:13 p.m. ET\), the Mobile Remote Deposit Capture \(mRDC\) service experienced an interruption, preventing members from successfully submitting mobile cheque deposits. During this period, deposit requests could not be processed due to a loss of connectivity between the mRDC application and supporting data services. **Point of Failure** As part of a database governance and standardization initiative, database service account permissions were updated to align with enterprise standards. This change exposed an undocumented user privilege dependency within the mRDC environment where the application access relied upon a legacy access permission for a service account. **Resolution** The team restored service by re-establishing the required database permissions and restarting the affected application, restoring connectivity and allowing deposit processing to resume. Once service was recovered, queued transactions were processed, and normal member activity resumed. While these actions resolved the immediate service interruption, the incident highlighted opportunities to strengthen platform resiliency and change validation processes. Central 1 has initiated a series of corrective measures to reduce dependency on legacy configurations, improve monitoring and alerting capabilities, strengthen change controls, and enable faster operational recovery should a similar event occur in the future. **Corrective Actions \(PRB011762\)** * Document and enhance the database user governance change process, including validation and testing requirements. – In Progress * Review remaining databases for legacy access dependencies and remediate where required. – In Progress * Implement post-change reviews of SQL Server logs to identify access and authentication issues immediately following user governance changes. – Complete * Enhance monitoring and alerting for RDC transaction failures and abnormal transaction patterns. – In Progress * Require all database user governance changes to be executed through the formal Change Management process. – Complete * Implement monitoring for RDC deposit confirmation transactions. – In Progress We sincerely apologize for the disruption and the impact this incident had on your members and operations. We appreciate your patience and understanding while services were restored and thank you for your continued partnership Liz Ackroyd Manager, Client Support Services [[email protected]](mailto:[email protected]) | 905.301.1337

    Latest: **Postmortem: INC226099 – Mobile Remote Deposit Capture \(mRDC\) Service Interruption** On August 11, 2026, between 2:05 a.m. and 10:13 a.m. PT \(5:05 a.m. and 1:13 p.m. ET\), the …

  5. Resolved 2d 20h
    Started Aug 10, 2026, 10:38 PM UTC · Resolved Aug 13, 2026, 07:29 PM UTC
    Payment Services
    Timeline · 2 updates
    • identified · Aug 10, 2026, 10:38 PM UTC

      *** This notice is for credit unions who have Everlink as their switch provider. *** Please be advised that Everlink has suspended processing of new INT network POS and SCD traces. This includes trace follow-up requests for the INT network, due to a technical issue within the Everlink processing stream. The issue has been escalated with Everlink and their settlement agent, PPJV, and we are actively working with them toward resolution. There is no impact to POS and SCD trace processing for other networks, including ME2, ME3, and CI3. Further updates will be provided as more information becomes available. Central 1 - [email protected] - 1.888.889.7878 Option 1

    • resolved · Aug 13, 2026, 07:29 PM UTC

      *** This notice is for credit unions who have Everlink as their switch provider. *** Everlink has resolved the issue affecting INT network POS and SCD trace processing, and credit unions may now resume submitting new INT network POS and SCD trace requests. Follow-up requests for previously submitted INT network traces will be completed after September 10, once PPJV has cleared the backlog of new trace requests. Thank you for your patience while this issue was being addressed. Central 1 - [email protected] - 1.888.889.7878 Option 1

    Latest: *** This notice is for credit unions who have Everlink as their switch provider. *** Everlink has resolved the issue affecting INT network POS and SCD trace processing, and credit …

See the full Central 1 outage history

18 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Central 1 outage history →

Or sign up free to get alerts when Central 1 breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 23 incidents View full outage history →