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

[Production] Scheduled Service Maintenance on Sunday, February 8, 2026 from 12AM-4AM ET Feb 8, 2026 00:00-04:00 EST

On Sunday, February 8, 2026, between 12:00 AM and 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 Feb 02, 2026 - 16:53 EST
Feb 3, 2026

No incidents reported today.

Feb 2, 2026

No incidents reported.

Feb 1, 2026

No incidents reported.

Jan 31, 2026

No incidents reported.

Jan 30, 2026

No incidents reported.

Jan 29, 2026

No incidents reported.

Jan 28, 2026

No incidents reported.

Jan 27, 2026

No incidents reported.

Jan 26, 2026

No incidents reported.

Jan 25, 2026

No incidents reported.

Jan 24, 2026

No incidents reported.

Jan 23, 2026

No incidents reported.

Jan 22, 2026

No incidents reported.

Jan 21, 2026
[RESOLVED] Intermittent Connectivity Issues - ERP and API Connectivity
Resolved - Following successful monitoring, the issue with intermittent connectivity and timeouts is fully resolved. All services remain stable; clients should be free from any further degraded performance and may continue with normal activity.
Jan 21, 20:09 EST
Monitoring - FISPAN has successfully restored full system stability following a transition to our high-availability secondary database. This action has resolved the intermittent connectivity issues and timeouts identified.

All services are now fully operational. Intermittent instability was observed between approximately 5:30PM and 11:45PM ET.

FISPAN Engineering remains in a state of heightened monitoring to ensure sustained performance. We are currently conducting a deep-dive analysis into the primary environment performance to determine the root cause.
Jan 21, 02:56 EST
Investigating - We are investigating an issue currently affecting the stability of our ERP integration and API services.

Our monitoring systems have detected intermittent performance fluctuations. As a result, users may encounter temporary timeouts when accessing services through their integrated ERPs or the FISPAN Portal during session activity.

Transactions processed via API rails may experience delayed status responses or brief connection interruptions.

Our teams have implemented stabilization measures and are closely monitoring for sustained performance. If a service timeout occurs, we recommend retrying the request after a brief interval.

We are working toward a full resolution and will provide further updates as new information becomes available.
Jan 20, 19:46 EST
Jan 20, 2026
← Incident History Powered by Atlassian Statuspage