All Systems Operational

About This Site

Welcome to the FISPAN J.P. Morgan Chase Bank integration status page. This page describes feature availability for the J.P. Morgan Chase Bank integration. The below uptimes are an unofficial combined view of all areas that can impact client functionality. Have any questions? Please reach out to our support at https://support.fispan.com/jpmorgan

Uptime over the past 90 days. View historical uptime.
API - Information Reporting Operational
90 days ago
100.0 % uptime
Today
ERP Connector Operational
90 days ago
100.0 % uptime
Today
AWS Data Centre Operational
90 days ago
100.0 % uptime
Today
Sandbox Environment Operational
90 days ago
100.0 % uptime
Today
Auth0 Operational
90 days ago
100.0 % uptime
Today
Web UI Operational
90 days ago
100.0 % uptime
Today
SFTP Connection Operational
90 days ago
100.0 % uptime
Today
AWS s3-us-west-2 Operational
AWS rds-us-west-2 Operational
AWS ec2-us-west-2 Operational
AWS kms-us-west-2 Operational
AWS secretsmanager-us-west-2 Operational
AWS elb-us-west-2 Operational
Auth0 Management API Operational
Auth0 Multi-factor Authentication Operational
Auth0 User Authentication Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Scheduled Maintenance

[SERVICE DISRUPTION] [Production] Scheduled Service Maintenance on Sunday, July 12, 2026, from 12:00 AM to 4:00 AM ET Jul 12, 2026 00:00-04:00 EDT

On Sunday, July 12, 2026, from 12:00 AM to 4:00 AM ET, our Production environment will undergo scheduled maintenance and may be unavailable during this time. This period will be utilized for infrastructure enhancements and platform testing to ensure continued uptime and stability.

Please be advised that during this 4-hour window, the Production environment will be inaccessible for clients, preventing access to the UI and payment initiation.
Posted on Jul 06, 2026 - 14:12 EDT
Jul 10, 2026

No incidents reported today.

Jul 9, 2026

No incidents reported.

Jul 8, 2026

No incidents reported.

Jul 7, 2026

No incidents reported.

Jul 6, 2026

No incidents reported.

Jul 5, 2026

No incidents reported.

Jul 4, 2026

No incidents reported.

Jul 3, 2026

No incidents reported.

Jul 2, 2026

No incidents reported.

Jul 1, 2026

No incidents reported.

Jun 30, 2026

No incidents reported.

Jun 29, 2026
Sage Intacct Bank Feed Activation Issue
Resolved - We have successfully identified and resolved the issue causing new Sage Intacct bank account connections to become stuck in a “Connection Requested” status.

Our engineering team isolated a configuration error that was preventing the Sage platform and our setup page from properly exchanging the final activation success message. A network security update has been deployed, and testing confirms that the onboarding flow is now fully operational.

Billboard Notifications have been updated for impacted clients. Clients are now able to complete the Bank Feeds activation steps by logging into Sage Intacct -> navigating to the Bank Accounts page -> locating the impacted bank account -> clicking Edit -> and then clicking the Connect button to retry linking their feed. Product Guide Instructions for Enabling Bank Feeds can be found in the following documentation link: https://support.fispan.com/jpmorgan/enabling-bank-feeds-intacct

We appreciate your patience and collaboration while our team worked to resolve this issue.
Jun 29, 18:30 EDT
Investigating - We are investigating an issue where new bank account connections for Sage Intacct bank feeds are becoming stuck in a "Connection Requested" status. Please note that active, existing bank feeds remain fully operational.

Our logs confirm that no new creation requests or connection payloads are being transmitted to our platform from Sage for these impacted accounts, and no Sage fabric has been generated. Because this issue is occurring entirely within the Sage Intacct platform before reaching our network, this is currently blocking clients from successfully enabling new feeds.

Sage has advised that impacted clients should open a support case directly with the Sage Intacct team to resolve this stuck status. We are continuing to monitor the situation and are coordinating with Sage as they investigate a fix.
Jun 25, 16:20 EDT
Jun 28, 2026

No incidents reported.

Jun 27, 2026

No incidents reported.

Jun 26, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage