EN
Contact us

Status Page

Open Finance status, bank by bank.

A free, public page that shows how Open Finance banks and services are performing. The data is measured by our own production infrastructure.

See the status nowMeet Cumbuca
  • CAIXA2 APIs unstable
  • Mercado PagoAPI unstable
  • C6 BankOperational
  • SicrediOperational
  • BradescoOperational
  • Banco InterOperational
  • Banco SantanderOperational
  • ItaúOperational
  • PicPayOperational
  • Banco do BrasilOperational
  • NubankOperational
  • banco BVLow traffic

Live at via.cumbuca.com · updated at 13:29 BRT

The problem

When something fails in Open Finance, the cause isn't always clear.

Failures in the ecosystem don't come with a warning. Usually, the first sign is a customer complaining or a transaction that stopped going through. The information about the failure exists, but it takes time to reach the people who operate.

Every company investigates alone

Is the problem in your code, your provider, the bank on the other end or the whole ecosystem? Without a public reference, every company investigates from scratch, all at the same time.

The cost is time

Every hour of investigation costs engineering time, reputation and revenue. The question "is it us or the ecosystem?" should have an answer in seconds.

The solution

We measure every bank with our own traffic.

We track the calls our infrastructure makes to the APIs of each Open Finance institution, in the two regulated-use groups: customer data and payments. Availability is calculated over a rolling 1-hour window.

  • Coverage

    Data and payments, bank by bank

    We monitor customer data APIs (registration, accounts, cards, credit and investments) and payment APIs (one-off Pix, Pix Automático and the device binding of the Redirect-free Journey). Brands under the same CNPJ are combined in the calculation.

  • Availability

    Status per institution and per API

    An institution's overall availability dilutes isolated failures: an endpoint with a 60% error rate can disappear into a 98% average. That is why we also assess each API separately, and a single degraded API already changes the bank's status.

  • Failures

    Criteria on the provider's side

    We count as a failure any server error (5xx) or call with no response. Caller errors (4xx), such as an invalid request or a revoked consent, are left out, because they are not the bank's failure.

  • Journey

    Response time and conversion

    We show the median (p50) response time per institution and per endpoint, and the journey completion rate: how many users redirected to the bank came back with a valid authorization. Conversion does not change the status, because it usually reflects friction in the bank's flow.

For people who depend on Open Finance to operate.

  • Fintechs and advisory firms

    Companies that buy Open Finance infrastructure and need to know whether the problem is the vendor's, the bank's or the ecosystem's.

  • Operations teams

    The people who run payments and credit day to day and need to answer quickly whether a failure is internal or external.

  • Engineering teams

    Anyone integrating with Open Finance who needs a status source to investigate production issues without opening a ticket.

  • Licensed institutions

    Account-holding institutions, initiators and transmitters that track the health of their connected partners and of the ecosystem.

  • Payment initiators

    Anyone initiating payments through Open Finance who needs to know when a bank's payment APIs degrade, before payments fail at scale.

  • Data aggregators

    Platforms that depend on several bank connections and need to tell a bank's failure from an ecosystem failure.

How it works

Measured by our infrastructure, not declared by the banks.

  1. Checks in production

    Our production infrastructure checks the availability of each participant and of the central services, per institution, per service and per endpoint.

  2. Frequency that adjusts

    Every 15 minutes outside business hours and every 10 during business hours. When many people open the page at once, a sign of an incident, checks run every 5 minutes and can go down to every minute.

  3. Open publication

    When something deviates from the norm, the status changes on the next check and is visible to anyone, with no login.

Built to show up when you search.

When a bank goes down, everyone searches. The Status Page was built to show up in those moments, with measured data.

  • PCM down
  • SCR unavailable
  • [bank] open finance status
  • open finance outage
  • metrics collection platform status

We publish what we already measure.

Cumbuca operates at the heart of Brazilian Open Finance and makes real calls every day to participants' data and payment APIs and to the Credit Information System (SCR). When something fails in the ecosystem, our infrastructure notices early.

Publishing this information was a decision. Many status pages sit behind a login. Ours is open, because transparency builds trust in the ecosystem.

“If the information exists and helps the ecosystem, it should be public.”

See the Open Finance status now.

The 83 Open Finance participants, the Metrics Collection Platform (PCM), the Data Quality Engine (MQD) and the Credit Information System (SCR), open to everyone.

See the status nowMeet Cumbuca
Participants
83
Coverage
24/7
Login
No

Explore the other tools.