Handle institution outages and sync delays

Fiskil retrieves data from institutions — banks and energy retailers, the data holders in each market. When an institution has an outage or degraded performance, it directly affects Fiskil's ability to sync data for users connected to that institution.

What causes institution outages

• Planned maintenance windows at the institution
• Unplanned system outages or technical failures
• High-load periods (for example, end of financial year)
• Infrastructure changes or deployments on the institution's data-sharing APIs
• Network connectivity issues between Fiskil and the institution

While an institution is unavailable, data already synced remains accessible through the API. New data simply won't arrive until the institution recovers.

How Fiskil handles outages

Fiskil automatically retries failed requests on a schedule. When an institution recovers, syncing resumes automatically — no action is needed from you or your end users. Scheduled outages are posted on the Institution Status page.

How to identify an institution outage

If multiple users connected to the same institution are all missing recent data at the same time, an institution outage is the likely cause. To confirm:

1. Check the Institution Status page for active incidents or scheduled outages.
2. In Australia (CDR), check the regulator's public performance dashboard, which tracks availability metrics for accredited data holders.
3. Contact Fiskil support, who can confirm whether there's a known issue with the institution.

Delays vs outages

Not every delay is an outage. Some institutions have inherent lag in their data:

• Some large institutions are known to report transactions with a 1–2 day delay.
• Some smaller institutions, such as building societies and credit unions, process transactions in batch cycles, so new transactions appear only once per day.
• International or cross-border transactions can take longer to appear.