MercadoPago status

Updated just now

MercadoPago reports Operational

2 incidents reported in the last 24 hours.

MercadoPago status history

  • Down
  • Warning

Incidents

Provider incidents

Degraded Today at 01:59 UTC Resolved

Online Payments – Checkout Pro

We are experiencing degraded performance in Checkout Pro.
This incident has been resolved.

Degraded Today at 01:52 UTC Resolved

InStore QR – Rejected Payments (MLA)

We are investigating an increase in payment declines affecting in-store QR transactions in Argentina (MLA).
This incident has been resolved.

Degraded 20 Oct at 22:02 UTC Resolved

InStore QR – Rejected Payments (MLB)

We are investigating an increase in payment declines affecting in-store QR transactions in Brazil (MLB).
This incident has been resolved.

Degraded 20 Oct at 03:32 UTC Resolved

InStore QR – Rejected Payments (MLB)

We are investigating an increase in payment declines affecting in-store QR transactions in Brazil (MLB).
This incident has been resolved.

Degraded 19 Oct at 12:57 UTC Resolved

InStore QR – Rejected Payments (MLB)

We are investigating an increase in payment declines affecting in-store QR transactions in Brazil (MLB).
This incident has been resolved.

Degraded 19 Oct at 12:07 UTC Resolved

InStore QR – Rejected Payments (MLB)

We are investigating an increase in payment declines affecting in-store QR transactions in Brazil (MLB).
This incident has been resolved.

Degraded 19 Oct at 10:05 UTC Resolved

QR MLA - Billeteras Locales

Caída parcial detectada en pagos QR Billeteras Locales en Argentina (MLA).
La caída en QR Billeteras Locales MLA fue resuelta. El servicio opera con normalidad.

Degraded 19 Oct at 10:02 UTC Resolved

InStore QR – Rejected Payments (MLA)

We are investigating an increase in payment declines affecting in-store QR transactions in Argentina (MLA).
This incident has been resolved.

Degraded 18 Oct at 09:55 UTC Resolved

QR MLC - QRC Aprobaciones

Anomalía detectada en las aprobaciones QRC en Chile (MLC).
La anomalía en QRC Aprobaciones MLC fue resuelta. El servicio opera con normalidad.

Degraded 18 Oct at 05:12 UTC Resolved

InStore QR – Rejected Payments (MLB)

We are investigating an increase in payment declines affecting in-store QR transactions in Brazil (MLB).
This incident has been resolved.

Degraded 18 Oct at 05:02 UTC Resolved

InStore QR – Rejected Payments (MLA)

We are investigating an increase in payment declines affecting in-store QR transactions in Argentina (MLA).
This incident has been resolved.

Degraded 18 Oct at 04:22 UTC Resolved

InStore QR – Rejected Payments (MLB)

We are investigating an increase in payment declines affecting in-store QR transactions in Brazil (MLB).
This incident has been resolved.

Degraded 18 Oct at 03:52 UTC Resolved

InStore QR – Rejected Payments (MLB)

We are investigating an increase in payment declines affecting in-store QR transactions in Brazil (MLB).
This incident has been resolved.

Degraded 18 Oct at 02:37 UTC Resolved

InStore QR – Rejected Payments (MLB)

We are investigating an increase in payment declines affecting in-store QR transactions in Brazil (MLB).
This incident has been resolved.

Degraded 18 Oct at 01:38 UTC Resolved

Point - Rejection Incident - MLU

We are investigating a payment rejection incident affecting Point in Uruguay (MLU).
This incident has been resolved.

Degraded 17 Oct at 09:57 UTC Resolved

InStore QR – Rejected Payments (MLB)

We are investigating an increase in payment declines affecting in-store QR transactions in Brazil (MLB).
This incident has been resolved.

Degraded 17 Oct at 03:12 UTC Resolved

ALL SITES - Delay in Webhook Payments notifications

We are investigating an increase in response times for Webhook Payments notifications.
This incident has been resolved.

Degraded 17 Oct at 03:11 UTC Resolved

ALL SITES - Delay in IPN Payments notifications

We are investigating an increase in response times for IPN Payments notifications.
This incident has been resolved.

Degraded 16 Oct at 13:45 UTC Resolved

ALL SITES - Delay in IPN Payments notifications

We are investigating an increase in response times for IPN Payments notifications.
This incident has been resolved.

Degraded 16 Oct at 12:42 UTC Resolved

InStore QR – Rejected Payments (MLB)

We are investigating an increase in payment declines affecting in-store QR transactions in Brazil (MLB).
This incident has been resolved.

Community reports

No community reports yet

No users have reported issues with this provider yet.

About MercadoPago status page

  • Monitoring since Oct 2026
  • 42 services and components tracked
  • 105 incidents total
  • Last updated: Oct 22, 2026

Frequently asked questions

Quick answers for payment teams and merchants investigating an incident. Firemap explains the evidence; it does not diagnose your merchant account.

Is MercadoPago down right now?

No. MercadoPago currently reports normal operation on its official status page. PayAtlas last checked it today at 20:54 UTC.

What do Operational, Degraded, Outage and Resolved mean?

They are the states MercadoPago publishes on its official status page. Operational means the service works normally. Degraded means part of it is slower or failing for some customers, regions or payment methods, while the rest still works. Outage means a major disruption: a service, or a key part of it, is unavailable. Resolved marks an incident MercadoPago has closed; the time it was resolved shows when you hover it.

Does this confirm that my merchant account or customers are affected?

Not on its own. Firemap shows what MercadoPago publishes about its platform, not the state of your account. An incident may affect only some regions, payment methods or integrations. Check your own transaction logs and decline codes, and contact MercadoPago support with specific transaction IDs if you see failures.

Where does Firemap get this status information?

From official status pages only. Firemap reads each page it tracks automatically every few minutes and records every status change and incident the provider publishes there. Nothing about MercadoPago is added or edited by hand.

Why can official and community signals disagree?

They come from different sources. The official status is what MercadoPago has confirmed, and providers often post an incident only after the first failures. Community reports come from users and can show a problem earlier, but it may be local: one bank, one country or one integration. Treat reports without an official incident as an early signal, not a confirmed outage.

What should I check before changing payment routing?

Start with your own data: error rates, decline codes and response times by payment method, card scheme and country. Compare them with the scope of the incident on the status page. Make sure the backup provider supports the same methods and currencies, move a small share of traffic first, and switch back once the incident is resolved and your metrics recover.

What is Firemap’s coverage and method?

Firemap tracks the official status pages of payment providers listed on PayAtlas. Each page is checked automatically, and every incident is stored with its start time and, once resolved, its end time. When Firemap has data for MercadoPago, this page shows up to 90 days of status history and incidents from the last 30 days.

What can Firemap confirm, and what can’t it?

Firemap can confirm only what MercadoPago has published on its status page: the current status, incidents with their start time and, once resolved, end time, and how long the page has been tracked. It cannot confirm the impact on a specific merchant, transaction or region unless MercadoPago says so, and it cannot see problems the provider has not reported.

PayAtlas Stack

Manage Your Payment Stack in One Place

Save the providers you work with and get instant access to their status, coverage, insights, comparisons, and recommended alternatives whenever you need them.

Coming soon
  • Free monitoring
  • 5 minutes setup
Company created
Your company has been added to PayAtlas.