Stark Bank Outage History

Stark Bank is up right now

Stark Bank had 16 outages in the last 2 years totaling 90h 8m of downtime — averaging 0.7 incidents per month.

There were 16 Stark Bank outages since June 3, 2025 totaling 90h 8m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.starkbank.com

Major May 11, 2026

Instability in the communication with Visa - Acquiring

Detected by Pingoru
May 11, 2026, 03:57 PM UTC
Resolved
May 12, 2026, 07:28 PM UTC
Duration
1d 3h
Affected: API Card Acquiring
Timeline · 3 updates
  1. identified May 11, 2026, 03:57 PM UTC

    We are currently experiencing an issue with our acquiring service that is preventing some Visa transactions from being approved. All other card networks are operating normally. Our team is actively working with Visa to resolve this as quickly as possible.

  2. monitoring May 12, 2026, 03:45 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved May 12, 2026, 07:28 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 21, 2026

Pix Cash-out Status Update Delay

Detected by Pingoru
Apr 21, 2026, 04:21 PM UTC
Resolved
Apr 21, 2026, 03:30 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Apr 21, 2026, 04:21 PM UTC

    The status of some Transfers and BrcodePayments experienced a delay in updates between 12:35 and 12:55 BRT. The incident has been resolved and all statuses are now reflecting correctly. No transactions were lost or affected, only the status updates were delayed during this window.

Read the full incident report →

Minor April 14, 2026

Settlement Bank Boleto, BoletoPayment and TaxPayment instability

Detected by Pingoru
Apr 14, 2026, 03:59 PM UTC
Resolved
Apr 14, 2026, 05:21 PM UTC
Duration
1h 22m
Affected: API BoletoAPI Boleto PaymentAPI Utility & Tax Payment
Timeline · 3 updates
  1. identified Apr 14, 2026, 03:59 PM UTC

    There is an instability in the communication with our settlement bank. The resolution status for yesterday’s boleto settlements, boleto payments, tax payments and utility payments is delayed.

  2. identified Apr 14, 2026, 04:18 PM UTC

    The issue has been identified as an instability with our settlement bank.

  3. resolved Apr 14, 2026, 05:21 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 11, 2026

System instability

Detected by Pingoru
Apr 11, 2026, 11:14 PM UTC
Resolved
Apr 11, 2026, 02:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Apr 11, 2026, 11:14 PM UTC

    We observed widespread system instability across our infrastructure, resulting in elevated error rates. The incident occurred from 11:02 on April 10th until 00:22 on April 11th. The issue has been mitigated and services have returned to normal operation.

Read the full incident report →

Major March 1, 2026

Instability in the communication with Central Bank's DICT

Detected by Pingoru
Mar 01, 2026, 02:49 AM UTC
Resolved
Mar 01, 2026, 11:24 PM UTC
Duration
20h 35m
Affected: API Pix Key
Timeline · 4 updates
  1. identified Mar 01, 2026, 02:49 AM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring Mar 01, 2026, 03:14 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. identified Mar 01, 2026, 03:27 AM UTC

    The issue has been identified and a fix is being implemented.

  4. resolved Mar 01, 2026, 11:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 13, 2026

Webhook delivery latency

Detected by Pingoru
Feb 13, 2026, 06:24 PM UTC
Resolved
Feb 13, 2026, 06:24 PM UTC
Duration
8s
Affected: API Webhook
Timeline · 2 updates
  1. monitoring Feb 13, 2026, 06:24 PM UTC

    A fix has been implemented and we are monitoring the results.

  2. resolved Feb 13, 2026, 06:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 22, 2026

There is an instability in our gateway system.

Detected by Pingoru
Jan 22, 2026, 09:03 PM UTC
Resolved
Jan 22, 2026, 09:03 PM UTC
Duration
—
Affected: API GatewayWeb BankingAPI Pix KeyAPI TransferAPI BoletoWeb HomepageAPI Boleto PaymentAPI InvoiceApp iOSAPI Utility & Tax PaymentAPI DepositApp AndroidAPI Brcode PaymentApp VTEXAPI WebhookAPI ApprovalAPI Corporate CardAPI Card AcquiringAPI Fixed IncomeAPI Analytics
Timeline · 1 update
  1. resolved Jan 22, 2026, 09:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 22, 2026

There is an instability in the Brcode system.

Detected by Pingoru
Jan 22, 2026, 06:36 PM UTC
Resolved
Jan 22, 2026, 06:37 PM UTC
Duration
56s
Affected: API InvoiceAPI Deposit
Timeline · 2 updates
  1. identified Jan 22, 2026, 06:36 PM UTC

    The issue has been identified and a fix is being implemented.

  2. resolved Jan 22, 2026, 06:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 19, 2026

There is an instability in Central Bank's system.

Detected by Pingoru
Jan 19, 2026, 05:48 PM UTC
Resolved
Jan 19, 2026, 06:20 PM UTC
Duration
31m
Affected: API Pix KeyAPI TransferAPI InvoiceAPI DepositAPI Brcode Payment
Timeline · 4 updates
  1. monitoring Jan 19, 2026, 05:48 PM UTC

    We are currently experiencing a Pix instability due to an issue in the Central Bank’s systems. Our team is monitoring the situation and will provide updates as more information becomes available.

  2. monitoring Jan 19, 2026, 05:51 PM UTC

    The current issue is affecting the Central Bank’s DICT system, preventing the use of Pix keys in any capacity.

  3. monitoring Jan 19, 2026, 06:13 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Jan 19, 2026, 06:20 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 16, 2025

Card Acquiring authorization instability

Detected by Pingoru
Dec 16, 2025, 10:35 PM UTC
Resolved
Dec 10, 2025, 10:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Dec 16, 2025, 10:35 PM UTC

    Between 10/dez 18:50 and 11/12 09:30 (GMT-3), some card purchase transactions were not approved due to an internal issue in the acquiring authorization flow. The issue was resolved, and all systems have been operating normally since then.

Read the full incident report →

Minor November 5, 2025

Settlement Bank communication instability

Detected by Pingoru
Nov 05, 2025, 11:32 AM UTC
Resolved
Nov 05, 2025, 12:15 PM UTC
Duration
43m
Affected: API BoletoAPI Boleto PaymentAPI Utility & Tax Payment
Timeline · 2 updates
  1. investigating Nov 05, 2025, 11:32 AM UTC

    There is an instability in the communication with our settlement bank. The resolution status for yesterday’s boleto settlements, boleto payments, tax payments and utility payments is delayed.

  2. resolved Nov 05, 2025, 12:15 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 23, 2025

Instability in provider postal code lookup (physical card requests)

Detected by Pingoru
Oct 23, 2025, 07:33 PM UTC
Resolved
Oct 24, 2025, 01:02 PM UTC
Duration
17h 29m
Affected: API Corporate Card
Timeline · 3 updates
  1. investigating Oct 23, 2025, 07:33 PM UTC

    We’re currently investigating an instability in the provider postal code lookup service, which affects only the address search step in physical card requests.

  2. monitoring Oct 23, 2025, 08:02 PM UTC

    After further investigation, we identified that the issue was caused by an instability in our provider’s services. The service now appears to have stabilized, and our team is currently monitoring to ensure everything remains fully operational.

  3. resolved Oct 24, 2025, 01:02 PM UTC

    We have been monitoring the provider’s service since yesterday, and it has remained stable during this period. As the functionality has been consistently operating as expected, we are now marking this incident as resolved.

Read the full incident report →

Major October 6, 2025

There is an instability in Central Bank's DICT system. PixKey queries and BR Code previews are unavailable.

Detected by Pingoru
Oct 06, 2025, 09:43 PM UTC
Resolved
Oct 06, 2025, 11:11 PM UTC
Duration
1h 28m
Affected: API Pix KeyAPI Brcode Payment
Timeline · 3 updates
  1. investigating Oct 06, 2025, 09:43 PM UTC

    We are currently investigating this issue.

  2. monitoring Oct 06, 2025, 09:43 PM UTC

    We are monitoring

  3. resolved Oct 06, 2025, 11:11 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 23, 2025

Instability in Pix settlement

Detected by Pingoru
Sep 23, 2025, 09:21 PM UTC
Resolved
Sep 23, 2025, 09:46 PM UTC
Duration
24m
Affected: API Pix KeyAPI TransferAPI InvoiceAPI DepositAPI Brcode Payment
Timeline · 2 updates
  1. investigating Sep 23, 2025, 09:21 PM UTC

    There is an instability in processing Pix operations.

  2. resolved Sep 23, 2025, 09:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 12, 2025

Infrastructure instability

Detected by Pingoru
Jun 12, 2025, 06:00 PM UTC
Resolved
Jun 13, 2025, 02:02 PM UTC
Duration
20h 1m
Affected: API GatewayWeb BankingAPI Pix KeyAPI TransferAPI BoletoWeb HomepageAPI Boleto PaymentAPI InvoiceApp iOSAPI Utility & Tax PaymentAPI DepositApp AndroidAPI Brcode PaymentApp VTEXAPI WebhookAPI ApprovalAPI Corporate CardAPI Card AcquiringAPI Fixed IncomeAPI Analytics
Timeline · 4 updates
  1. investigating Jun 12, 2025, 06:43 PM UTC

    We are currently investigating an infrastructure instability affecting multiple services.

  2. identified Jun 12, 2025, 07:01 PM UTC

    The issue was identified as a global problem in Google Cloud, already reported on their status page.

  3. monitoring Jun 12, 2025, 09:53 PM UTC

    The Google incident has not been officially resolved yet; however, our services are currently stable and functional. We'll continue to monitor the situation closely until Google officially confirms the issue has been resolved.

  4. resolved Jun 13, 2025, 02:02 PM UTC

    The services have been monitored and remain stable. Additionally, Google has reported the resolution of the incidents on their status page; therefore, we are closing the incident.

Read the full incident report →