Flinks logo

Is Flinks Down?

FinTech & PaymentsLive status, outages, and incident history

No. Flinks is up right now.

Every monitored Flinks system is operational as of November 14, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 3m agoLive · every 60s1 active incident

Know the moment Flinks breaks

Flinks is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official Flinks status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Flinks Status Summary

As of 03:57 UTC on 14 November 2026, Flinks is operational. PulsAPI checked Flinks's official status page and found 7 of 7 components operational, with 1 active incident. The latest incident, "Scotia", was on Nov 13, 2026 and lasted 3h 20m.

Cite as: PulsAPI, “Flinks status”, checked 14 November 2026, 03:57 UTC. https://www.pulsapi.com/services/flinks

Flinks Component Status

The main Flinks systems on this page. All 7 are operational right now.

7operational
Client Dashboard
Operational
Data Aggregation - Retail and Business
Operational
Flinks Connect Widget
Operational

4 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Flinks Enrichment / Attributes, Flinks Outbound - Retail and Business, Flinks Pay, Flinks Upload.

See all of them free

Component statuses may change independently during partial outages.

Recent Flinks Outages & Incidents

Incident history from the official Flinks status page, including resolution updates.

ScotiaResolved Nov 13, 2026 · 3h 20mResolved

The issue affecting **[Scotia](https://app.incident.io/flinksteam/catalog/01JX2TSMFWK712RCKG1A559622/01JYS6JHQ3S9JAAX5W073FXJ60)** has been resolved. Systems are operating normally again. Thank you for your patience. --- [2026-11-13T10:58:02Z] (identified) We have identified that [Scotia](https://app.incident.io/flinksteam/catalog/01JX2TSMFWK712RCKG1A559622/01JYS6JHQ3S9JAAX5W073FXJ60) is experiencing an outage at this time. We will monitor this outage and notify you when this Financial Institution is back up and running. We appreciate your patience and understanding of this process. The Development team

Data Aggregation - Retail and BusinessResolved Nov 12, 2026 · 2h 53mResolved

The issue affecting **[Data Aggregation - Retail and Business](https://app.incident.io/flinksteam/catalog/01JX2TSMFWK712RCKG1A559622/01JX2TSMGZ5D6RVK4SV4X72SN0)** has been resolved. Systems are operating normally again. Thank you for your patience. --- [2026-11-12T16:51:48Z] (identified) We’ve identified the root cause of the issue affecting **[Data Aggregation - Retail and Business](https://app.incident.io/flinksteam/catalog/01JX2TSMFWK712RCKG1A559622/01JX2TSMGZ5D6RVK4SV4X72SN0)**. A fix is currently in progress. We will share an update as soon as more information becomes available. Thank you for your patience. Flinks Team --- [2026-11-12T16:33:40Z] (investigating) We are currently investigating an issue affecting **[Data Aggregation - Retail and Business](https://app.incident.io/flinksteam/catalog/01JX2TSMFWK712RCKG1A559622/01JX2TSMGZ5D6RVK4SV4X72SN0)**. Users may experience **Degraded Performance**. Our team is actively working to identify the root cause and implement a solution. We will share an update as soon as more information becomes available. Thank you for your patience. Flinks Team

CIBCResolved Nov 12, 2026 · 2h 46mResolved

The issue affecting **[CIBC](https://app.incident.io/flinksteam/catalog/01JX2TSMFWK712RCKG1A559622/01JXZK64BBZ99Z7ZDSS3639NYA)** has been resolved. Systems are operating normally again. Thank you for your patience. --- [2026-11-12T11:22:29Z] (identified) We have identified that [CIBC](https://app.incident.io/flinksteam/catalog/01JX2TSMFWK712RCKG1A559622/01JXZK64BBZ99Z7ZDSS3639NYA) is experiencing an outage at this time. We will monitor this outage and notify you when this Financial Institution is back up and running. We appreciate your patience and understanding of this process. The Development team

Flinks Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Flinks incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history3 days observed
Nov 12100.00% averageNov 14

Live Flinks Outage Reports

Problems reported by engineers using Flinks. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Flinks problems reported yet.

Something wrong with Flinks on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Flinks

Flinks posts its status at status.flinks.com. The page covers 7 components, among them Client Dashboard, Data Aggregation - Retail and Business and Flinks Connect Widget. Past incidents and uptime for Flinks stay on this page, which helps when you want to know how often it has trouble.

Flinks Status FAQ

Is Flinks down right now?

The verdict at the top of this page comes from the latest poll of the official Flinks status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Flinks is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Flinks recovers.

How do I check Flinks uptime history?

PulsAPI tracks Flinks uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Flinks changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Flinks outages?

PulsAPI reads the official Flinks status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Flinks components?

Yes. PulsAPI monitors 7 individual Flinks components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Flinks goes down?

Yes. Create a free account and subscribe to Flinks: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Flinks to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Flinks problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Flinks?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Flinks plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Flinks with the rest of your stack

4372+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services