Is Kushki down?

Last checked 6m ago
Current status
Kushki is up

No incidents right now.

Get alerts when Kushki breaks →

Free · no credit card

Official status page: https://status.kushkipagos.com · Polled every 5 minutes · 54 components tracked

Real-time Kushki status, recent outages, and incident history — pulled directly from Kushki's official status page at https://status.kushkipagos.com every 5 minutes. Pingoru tracks 54 Kushki services and has captured 50 incidents in the last 90 days (99.45% uptime). Get email, Slack, Discord, or webhook alerts the moment Kushki reports a new incident — free for 5 monitors, no credit card.

Users who monitor Kushki also follow these Payments services: Square Authorize.Net Cash App FreedomPay Worldpay Clover Klarna JotForm Wise Breadcrumb View all 6,000+ providers
Kushki uptime 99.45% uptime · past 90 days
Mon Wed Fri
JanFebMarApr
Less More

Recent outages & incidents

Past 7 days
  1. Resolved 4h 23m
    Started Apr 28, 2026, 06:37 PM UTC · Resolved Apr 28, 2026, 11:00 PM UTC
    ACH (CO)
    2 updates · show timeline
    • investigating · Apr 28, 2026, 06:37 PM UTC

      Se observa ingreso de rechazos para el emisor por mensaje “NOT_AUTHORIZED” y FAILED. Se ha escalado el caso al procesador para sus respectivas validaciones. Se mantiene en monitoreo y cualquier novedad se estará informando.

    • resolved · Apr 28, 2026, 11:00 PM UTC

      Se ha mantenido en monitoreo y se valida mejoría a nivel transaccional para ACH (CO) con la entidad Nequi desde aproximadamente las 15:30 pm (GMT-5). En validaciones con el procesador confirma que se evidenciaron novedades con el emisor mismas que fueron reportadas al banco, sin embargo desde las 4:20 pm (GMT-5) han ido normalizando. Adicionalmente los monitores relacionados a la intermitencia se encuentran estables, razón por la cual se procede con el cierre del presente caso.

    Latest: Se ha mantenido en monitoreo y se valida mejoría a nivel transaccional para ACH (CO) con la entidad Nequi desde aproximadamente las 15:30 pm (GMT-5). En validaciones con el procesa…

  2. Resolved 2h 8m
    Started Apr 27, 2026, 06:50 PM UTC · Resolved Apr 27, 2026, 08:59 PM UTC
    ETPay (CH)
    2 updates · show timeline
    • investigating · Apr 27, 2026, 06:50 PM UTC

      Se evidencia un comportamiento inusual para el Banco Itaú (CL), el procesador informa que tras una revisión exhaustiva, han identificado inconsistencias en Banco Itaú en el servicio de Login. Debido a ello, han decidido proceder con la desactivación temporal de dicho banco, con el objetivo de garantizar la integridad de las operaciones y evitar posibles inconvenientes adicionales. Se mantiene en monitoreo y cualquier novedad se informará de manera oportuna.

    • resolved · Apr 27, 2026, 08:59 PM UTC

      En procesador ETPay informa que el servicio de Banco Itaú se ha restablecido y operamos con normalidad. Adicionalmente los monitores relacionados a la intermitencia se encuentran estables, razón por la cual se procede con el cierre del presente caso.

    Latest: En procesador ETPay informa que el servicio de Banco Itaú se ha restablecido y operamos con normalidad. Adicionalmente los monitores relacionados a la intermitencia se encuentran e…

  3. Resolved 3h 13m
    Started Apr 27, 2026, 03:46 PM UTC · Resolved Apr 27, 2026, 07:00 PM UTC
    ACH (CO)
    3 updates · show timeline
    • investigating · Apr 27, 2026, 03:46 PM UTC

      Se han identificado anomalías a nivel transaccional respecto al servicio de pse avanza de ACH, teniendo de inicio un incremento de rechazos y posterior a ello un corte transaccional. De momento se mantiene en validaciones entre el procesador y el equipo interno ya que se observa nuevamente un grupo de rechazos. Se mantiene en monitoreo y cualquier novedad se informará oportunamente.

    • monitoring · Apr 27, 2026, 04:39 PM UTC

      Se ha mantenido en monitoreo y se valida estabilidad a nivel transaccional para el servicio de PSE AVANZA desde aproximadamente las 10:45 am (GMT-5). En validaciones con ACH se ha logrado identificar la causa y queda resuelta. Se mantiene en monitoreo por un periodo de tiempo más hasta validar estabilidad a nivel transaccional respecto al histórico y cualquier novedad se informará oportunamente.

    • resolved · Apr 27, 2026, 07:00 PM UTC

      Se ha mantenido en monitoreo y se confirma estabilidad a nivel transaccional para el servicio de PSE AVANZA desde aproximadamente las 10:45 am (GMT-5). Por lo que se procede con el cierre del presente caso, sin embargo se mantendrá en monitoreo y en caso de evidenciar un comportamiento similar estaremos informando.

    Latest: Se ha mantenido en monitoreo y se confirma estabilidad a nivel transaccional para el servicio de PSE AVANZA desde aproximadamente las 10:45 am (GMT-5). Por lo que se procede con el…

  4. Resolved 9h 51m
    Started Apr 27, 2026, 03:02 AM UTC · Resolved Apr 27, 2026, 12:53 PM UTC
    BITSO (MX)
    3 updates · show timeline
    • identified · Apr 27, 2026, 03:02 AM UTC

      Se observa rechazo total por causal “Transacccion rechazada.”, el equipo técnico de Bitso ha informado que "están trabajando para solucionarlo lo antes posible”. De nuestro lado se mantiene en monitoreo y cualquier novedad se informará oportunamente.

    • monitoring · Apr 27, 2026, 10:56 AM UTC

      Se ha recibido comunicado por parte del procesador el cual informa que “Continuamos investigando este asunto y les mantendremos informados. Pedimos disculpas por cualquier inconveniente que esto pueda causar”. Se mantiene en monitoreo.

    • resolved · Apr 27, 2026, 12:53 PM UTC

      Se ha recibido comunicado por parte del procesador el cual informa que “el problema se ha solucionado. Les pedimos disculpas por las molestias ocasionadas. Nuestro equipo está a su disposición para ayudarles en caso de que surja algún problema.”. Por lo que de nuestro lado se finaliza el incidente, se mantiene en monitoreo.

    Latest: Se ha recibido comunicado por parte del procesador el cual informa que “el problema se ha solucionado. Les pedimos disculpas por las molestias ocasionadas. Nuestro equipo está a su…

  5. Resolved 6h 54m
    Started Apr 26, 2026, 06:53 PM UTC · Resolved Apr 27, 2026, 01:48 AM UTC
    BITSO (MX)
    4 updates · show timeline
    • identified · Apr 26, 2026, 06:53 PM UTC

      Se recibe comunicado por parte del procesador Bitso (MX) en el cual se informa que actualmente están experimentando problemas con los retiros en MXN. Debido a esto, los retiros en MXN están desactivados temporalmente. Su equipo de ingeniería está trabajando para identificar la causa raíz y restaurar el procesamiento normal lo más rápido posible. Se mantiene en monitoreo

    • identified · Apr 26, 2026, 08:59 PM UTC

      Se continúa observando rechazo total para el procesador por respuesta “Transaccion rechazada. ”. De parte del procesador no se tiene actualización del incidente reportado. De nuestra parte se continúa insistiendo por avances del caso relacionado a problemas con los retiros en MXN. Se mantiene en monitoreo

    • monitoring · Apr 26, 2026, 11:42 PM UTC

      Se recibe update por parte del procesador Bitso (MX), en el cual se informa que “Los retiros están habilitados nuevamente en MXN”. Se mantiene en monitoreo hasta confirmar estabilidad.

    • resolved · Apr 27, 2026, 01:48 AM UTC

      Se observa estabilidad con el procesador. Por ello, se da por cerrada la novedad.

    Latest: Se observa estabilidad con el procesador. Por ello, se da por cerrada la novedad.

See the full Kushki outage history

17 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Sign up free to unlock full history

10 free monitors · No credit card

Outage history

Past 30 days · 22 incidents
  • Intermitencia Transfer Processor ACH/PSE (CO) - NEQUI Resolved
    Started Apr 28, 2026, 06:37 PM UTC · Resolved Apr 28, 2026, 11:00 PM UTC · 4h 23m
  • Intermitencia Transfer Processor ETPay (CL) - Banco Itau Resolved
    Started Apr 27, 2026, 06:50 PM UTC · Resolved Apr 27, 2026, 08:59 PM UTC · 2h 8m
  • Intermitencia Transfer Processor ACH - PSE AVANZA (CO) Resolved
    Started Apr 27, 2026, 03:46 PM UTC · Resolved Apr 27, 2026, 07:00 PM UTC · 3h 13m
  • Intermitencia Transfer Processor Bitso (MX) Resolved
    Started Apr 27, 2026, 03:02 AM UTC · Resolved Apr 27, 2026, 12:53 PM UTC · 9h 51m
  • Intermitencia Transfer Processor Bitso (MX) Resolved
    Started Apr 26, 2026, 06:53 PM UTC · Resolved Apr 27, 2026, 01:48 AM UTC · 6h 54m
  • Intermitencia Transfer Processor ACH/PSE (CO) - DAVIbank S.A. Resolved
    Started Apr 26, 2026, 02:38 PM UTC · Resolved Apr 26, 2026, 09:24 PM UTC · 6h 46m
  • Intermitencia Transfer Processor ETPay (CL) Resolved
    Started Apr 26, 2026, 04:40 AM UTC · Resolved Apr 26, 2026, 09:29 AM UTC · 4h 49m
  • Intermitencia Transfer Processor ACH/PSE (CO) - Banco Bogota y Daviplata Resolved
    Started Apr 25, 2026, 05:04 AM UTC · Resolved Apr 25, 2026, 07:08 AM UTC · 2h 4m

See Kushki in your Pingoru dashboard

Monitor Kushki alongside every other service your stack depends on — same alerts, same timeline, same calendar — all in one place.

Every status page, one dashboard

Add Kushki to your Pingoru monitors and it sits next to AWS, Stripe, GitHub, and every other vendor in your stack — a single dashboard for the live status of every cloud and SaaS provider you depend on. One subscription, one inbox, every incident.

Incident timeline, this provider or all of them

Every Kushki incident — when it started, when it resolved, which services were affected, how bad it was, how long it lasted — laid out in one feed you can scan in 30 seconds. Filter to just Kushki or see every provider at once.

Maintenance calendar

Scheduled Kushki maintenance windows land in the same calendar as every other vendor you depend on — see what's running now, what's coming up, and a calendar view. Plan around your vendors instead of being caught out by them.

Every Kushki status change, one inbox

Pingoru watches Kushki's official status page every 5 minutes and delivers incident, resolution, and maintenance events to your email, Slack, Discord, Teams, or webhook.

Only alert on the services you use

Kushki reports on 54 services. Subscribe to the ones you actually use — everything else stays silent.

Email + Slack + Discord + Teams

Signed webhooks on every plan. Route Kushki alerts wherever your team already lives — no per-integration billing, no tier-gating the channels that matter.

Maintenance, not surprises

Upcoming Kushki maintenance windows appear in your maintenance calendar days in advance. Plan deploys and rollouts around them instead of finding out during an incident.

Fine-grained alert control

Per-monitor switches for opened, updated, resolved, and maintenance events. Silence the noisy Kushki services without silencing the monitor entirely.

Invite your team

Premium includes 10 team seats. Everyone watching Kushki from the same account, with per-user notification preferences for any monitor.

Get notified on Kushki status changes

Pingoru watches Kushki's official status page and sends your team instant alerts when incidents open, change severity, or resolve. Route notifications to email, Slack, Discord, or a webhook — wherever your team already lives.

Start monitoring Kushki free

Monitor Kushki along with everything else

Pingoru tracks 6,000+ cloud and SaaS status pages in one dashboard. Add Kushki and every other provider you depend on — AWS, Stripe, GitHub, Cloudflare, OpenAI — and get a single view of the health of every service your app depends on.

Browse the full service directory

Track Kushki uptime & incident history

See 90 days of Kushki uptime at a glance, with every past incident linked to its component and update timeline. Export the history as CSV or JSON for SLA reports, postmortems, or vendor evaluations — data your team actually needs, not marketing numbers.

See Kushki uptime history

Frequently asked questions

What is Kushki's uptime?
Over the last 90 days, Kushki reported 99.45% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.kushkipagos.com — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see Kushki's uptime history rolling forward in real time.
Has Kushki had outages in 2026?
Yes — Kushki has had 37 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.
When was the last Kushki outage?
The most recent Kushki incident was "Intermitencia Transfer Processor ACH/PSE (CO) - NEQUI", which started on April 28, 2026 and was resolved on April 28, 2026. Pingoru captured this directly from https://status.kushkipagos.com. See the full incident card above for affected components and the update timeline.
How often does Kushki have outages?
Based on the last 90 days, Kushki averages 12.3 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.
Where is Kushki's status page?
Kushki's official status page is https://status.kushkipagos.com. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.
Is Kushki down right now?
Kushki is up. Pingoru checks the official status page every 5 minutes and flips this headline the moment Kushki reports a change. Current status is based on 54 tracked services.
How does Pingoru know if Kushki is down?
We read https://status.kushkipagos.com directly, using Kushki's own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.
Where can I get notified when Kushki has an outage?
Create a free Pingoru account and add Kushki as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.
Kushki's status page says the service is up, but I'm having issues — what's wrong?
Three common reasons: • A real Kushki incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real Kushki issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.
Where does Pingoru get the official Kushki status?
We use Kushki's own status page at https://status.kushkipagos.com. Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.
What does "Up" mean?
All tracked Kushki components are reporting operational. No incidents are currently affecting service.

Stop finding out from your users.

We watch Kushki's official status page every 5 minutes. The moment they report an incident, you get an email — often before the outage is widely noticed.

Monitor Kushki free →

10 monitors free · email alerts · no credit card

Want the full picture first? See everything Pingoru does →