← HonkWatch.com

Is Klavi down in Fr. S. Antarctic Lands?

Klavi has problems

People in Fr. S. Antarctic Lands: 0 reports in the last hour Official page: Partial outage reported, checked 2 min ago Our checks: loads from 35 of 35 places

2 open incidents: Pagamentos instantâneos via Open Finance (BACEN) - [Shopee] em manutenção não programada, Pagamentos automáticos via Open Finance (BACEN) - [Shopee] em manutenção não programada

Partial outage reported by Klavi 2 of 181 parts affected: Pagamentos Automáticos Open Finance (BACEN) / Shopee, Pagamentos Instantâneos Open Finance (BACEN) / Shopee. Going on for 4 d 11 h. Updated 7 Nov, 20:30 UTC, 2 min ago · Official status page
Report a problem
Change country

Known issues (from Klavi's status page)

Incidents

  • Pagamentos instantâneos via Open Finance (BACEN) - [Shopee] em manutenção não programada (investigating, major impact) Since 24 Jul 2026, 19:38 UTC. Affects Shopee · Details Latest update (24 Jul 2026, 19:38 UTC): A instituição informou que seus serviços de pagamento estão indisponíveis no momento. Assim que for corrigido, a funcionalidade será automaticamente restabelecida.
  • Pagamentos automáticos via Open Finance (BACEN) - [Shopee] em manutenção não programada (investigating, major impact) Since 24 Jul 2026, 19:38 UTC. Affects Shopee · Details Latest update (24 Jul 2026, 19:38 UTC): A instituição informou que seus serviços de pagamento estão indisponíveis no momento. Assim que for corrigido, a funcionalidade será automaticamente restabelecida.

In Klavi's own words, as we read them every 15 minutes, last 2 min ago. Read Klavi's status page

Reports from people in Fr. S. Antarctic Lands

Last 24 hours · Fr. S. Antarctic Lands · times in UTC

0 reports

No community reports in the last 24 hours from Fr. S. Antarctic Lands. Having trouble? Add your report.

Status page: partial outage, 3 Nov, 08:40 to now 024 00:0006:0012:0018:00 20:45-20:50 UTC: 31 of 31 places loaded it, typical 1058 ms20:50-21:00 UTC: 35 of 35 places loaded it, typical 940 to 992 ms21:00-21:05 UTC: 3 of 3 places loaded it, typical 904 ms21:05-21:10 UTC: 30 of 30 places loaded it, typical 1022 ms21:10-21:15 UTC: 33 of 33 places loaded it, typical 1049 ms21:15-21:20 UTC: 19 of 19 places loaded it, typical 1057 ms21:20-21:25 UTC: 35 of 35 places loaded it, typical 907 ms21:25-21:30 UTC: 18 of 18 places loaded it, typical 828 ms21:30-21:35 UTC: 29 of 29 places loaded it, typical 1108 ms21:35-21:45 UTC: 35 of 35 places loaded it, typical 1017 to 1059 ms21:45-21:50 UTC: 18 of 18 places loaded it, typical 997 ms21:50-21:55 UTC: 17 of 17 places loaded it, typical 1080 ms21:55-22:05 UTC: 35 of 35 places loaded it, typical 1027 to 1060 ms22:05-22:10 UTC: 23 of 23 places loaded it, typical 1038 ms22:10-22:20 UTC: 35 of 35 places loaded it, typical 953 to 1056 ms22:20-22:25 UTC: 30 of 30 places loaded it, typical 895 ms22:25-22:30 UTC: 24 of 24 places loaded it, typical 1057 ms22:30-23:10 UTC: 35 of 35 places loaded it, typical 920 to 1065 ms23:10-23:20 UTC: 32 of 32 places loaded it, typical 1044 to 1051 ms23:20-01:10 UTC: 35 of 35 places loaded it, typical 905 to 1070 ms01:10-01:15 UTC: 34 of 34 places loaded it, typical 893 ms01:15-09:10 UTC: 35 of 35 places loaded it, typical 854 to 1086 ms09:10-09:15 UTC: 34 of 34 places loaded it, typical 806 ms09:15-09:20 UTC: 29 of 29 places loaded it, typical 1075 ms09:20-10:15 UTC: 35 of 35 places loaded it, typical 896 to 1040 ms10:15-10:20 UTC: 9 of 9 places loaded it, typical 970 ms10:20-11:35 UTC: 35 of 35 places loaded it, typical 887 to 1068 ms11:35-11:40 UTC: 8 of 8 places loaded it, typical 1143 ms11:40-12:50 UTC: 35 of 35 places loaded it, typical 843 to 1077 ms12:50-12:55 UTC: 33 of 33 places loaded it, typical 1044 ms12:55-13:20 UTC: 35 of 35 places loaded it, typical 856 to 1007 ms13:20-13:25 UTC: 34 of 34 places loaded it, typical 900 ms13:25-19:05 UTC: 35 of 35 places loaded it, typical 850 to 1150 ms19:05-19:10 UTC: 34 of 34 places loaded it, typical 1074 ms19:10-19:55 UTC: 35 of 35 places loaded it, typical 882 to 1061 ms19:55-20:00 UTC: 33 of 33 places loaded it, typical 905 ms20:00-20:15 UTC: 35 of 35 places loaded it, typical 948 to 1087 ms20:15-20:20 UTC: 34 of 34 places loaded it, typical 1053 ms20:20-20:30 UTC: 35 of 35 places loaded it, typical 900 to 1081 ms Typical response time of the places that loaded it, at most 1150 ms

Bars: reports every 15 minutes. Reports alone do not confirm an outage; a flat chart does not prove everything works.

Tinted columns: when Klavi's status page showed a partial outage, a major outage, as we read it every 15 minutes; the times are when we saw it, not when the provider posted it. Strip under the bars: how many places loaded klavi.ai in each 5 minutes, of those that checked, and the line under it their typical response time. Any answer from the website counts as loaded, even an error page. Website checks don't test sign-in, payments or every feature. Tinted columns and our checks are worldwide; the bars count reports from Fr. S. Antarctic Lands only.

Latest checks, 20:20-20:30 UTC: 35 of 35 places loaded it, typical 900 to 1081 ms.

Report totals as of 7 Nov, 20:31 UTC

Report a problem with Klavi

Choose where you are, then tap what isn't working. Tapping a problem sends your report; no account needed.

What isn't working? Tap one to send

Anonymous · one report per service per hour. This adds your experience to the chart; the provider is not contacted.

Compare worldwide reports · Other services in Fr. S. Antarctic Lands

Where this status comes from

Provider updates and website checks — Worldwide

The evidence below covers the provider and our available checks. It is not a separate verdict for Fr. S. Antarctic Lands. The report chart above is filtered to Fr. S. Antarctic Lands.

Our own checks of klavi.ai

Every 5 minutes, from our probes

Our checks from 35 cities: all fine.

Bangalore: loaded in 1143 ms Port Louis: loaded in 1732 ms Atlanta: loaded in 781 ms Querétaro: loaded in 739 ms Singapore: loaded in 1229 ms Tel Aviv: loaded in 1084 ms New York: loaded in 691 ms Santiago: loaded in 396 ms Hamina: loaded in 770 ms Frankfurt: loaded in 641 ms Osaka: loaded in 1217 ms London: loaded in 666 ms Melbourne: loaded in 572 ms Warsaw: loaded in 749 ms Seoul: loaded in 1432 ms Amsterdam: loaded in 659 ms Toronto: loaded in 639 ms Cape Town: loaded in 1476 ms Hong Kong: loaded in 1413 ms Dallas: loaded in 900 ms São Paulo: loaded in 274 ms Johannesburg: loaded in 1106 ms Sydney: loaded in 1428 ms Delhi: loaded in 1368 ms New Jersey: loaded in 791 ms Madrid: loaded in 651 ms St. Louis: loaded in 1185 ms Lauterbourg: loaded in 701 ms Jakarta: loaded in 1203 ms Portsmouth: loaded in 896 ms Mumbai: loaded in 1014 ms Los Angeles: loaded in 844 ms Tokyo: loaded in 1196 ms Doha: loaded in 1226 ms Seattle: loaded in 1070 ms
  • BangaloreReachable1143 ms, 2 min ago
  • Port LouisReachable1732 ms, 2 min ago
  • AtlantaReachable781 ms, 2 min ago
  • QuerétaroReachable739 ms, 2 min ago
  • SingaporeReachable1229 ms, 2 min ago
  • Tel AvivReachable1084 ms, 2 min ago
  • New YorkReachable691 ms, 2 min ago
  • SantiagoReachable396 ms, 2 min ago
  • HaminaReachable770 ms, 2 min ago
  • FrankfurtReachable641 ms, 2 min ago
  • OsakaReachable1217 ms, 2 min ago
  • LondonReachable666 ms, 2 min ago
  • MelbourneReachable572 ms, 3 min ago
  • WarsawReachable749 ms, 3 min ago
  • SeoulReachable1432 ms, 3 min ago
  • AmsterdamReachable659 ms, 3 min ago
  • TorontoReachable639 ms, 3 min ago
  • Cape TownReachable1476 ms, 3 min ago
  • Hong KongReachable1413 ms, 3 min ago
  • DallasReachable900 ms, 3 min ago
  • São PauloReachable274 ms, 3 min ago
  • JohannesburgReachable1106 ms, 3 min ago
  • SydneyReachable1428 ms, 3 min ago
  • DelhiReachable1368 ms, 3 min ago
  • New JerseyReachable791 ms, 3 min ago
  • MadridReachable651 ms, 3 min ago
  • St. LouisReachable1185 ms, 3 min ago
  • LauterbourgReachable701 ms, 3 min ago
  • JakartaReachable1203 ms, 3 min ago
  • PortsmouthReachable896 ms, 3 min ago
  • MumbaiReachable1014 ms, 3 min ago
  • Los AngelesReachable844 ms, 3 min ago
  • TokyoReachable1196 ms, 4 min ago
  • DohaReachable1226 ms, 4 min ago
  • SeattleReachable1070 ms, 4 min ago

This is separate from the status page: we request klavi.ai and note whether it answers. These automated checks do not sign in or use the app's features.

Parts of Klavi

Klavi

Pagamentos Automáticos Open Finance (BACEN)

  • ShopeePartial outage

Pagamentos Instantâneos Open Finance (BACEN)

  • ShopeePartial outage

179 other parts are working.

Incidents and maintenance

Open incidents

  • Pagamentos instantâneos via Open Finance (BACEN) - [Shopee] em manutenção não programada (investigating) Since 24 Jul 2026, 19:38 UTC. Affects Shopee · Details
  • Pagamentos automáticos via Open Finance (BACEN) - [Shopee] em manutenção não programada (investigating) Since 24 Jul 2026, 19:38 UTC. Affects Shopee · Details
Outage history

Last 9030 days

0.00% of the time without a reported outage, since 3 Nov

Of the last 90 days, 5 had a partial or major outage, 0 had maintenance only and 85 have no data. Recent problems are listed in a table further down.

90 days ago30 days agoToday

No problems Partial outage Major outage Maintenance No data yet

Recent problems

3 Nov, 08:40 UTCPartial outagegoing on, 4 d 11 h2 of 181 parts affected: Pagamentos Automáticos Open Finance (BACEN) / Shopee, Pagamentos Instantâneos Open Finance (BACEN) / Shopee
What can I try?

Having trouble with Klavi?

  1. Compare reports from Fr. S. Antarctic Lands and check the latest update above. A quiet chart does not rule out a new or local problem.
  2. Try the service on another device or switch between WiFi and mobile data, if available. If other sites also fail, check your internet provider.
  3. Report a problem with the feature that is failing and the country where you are affected. Submit once; your report appears in the chart.

Reports describe people's experiences. One report alone does not confirm an outage.

Questions about these results

Questions

Is Klavi down, or is it just me?

Klavi itself reports a problem right now, so it is probably not just you.

How do we know?

We read the official Klavi status page and load klavi.ai from our own probes in several cities. People can also report problems here. Their reports appear separately and may reveal issues before a provider update.

How often do we check?

The status page every 15 minutes, day and night, and the website every 5 minutes. We keep 90 days of history: a day we have no reading for shows as "no data yet", never as working.

Other services in Finance and accounting

Each card shows that service's own status, not Klavi's. A problem listed here does not mean Klavi has one.

See the live outage feed for Fr. S. Antarctic Lands · Find another service