Live  /  Pagarme  /  Incident

Pagarme: Instabilidade no Transacional PSP

Pagarme · pagar.meMinor incidentResolved2026-10-09 23:37 UTC
Public — what happened

Summary

Pagarme reported slower-than-normal performance in its Transacional PSP service, the system that handles payment transactions, on October 9, 2026, and labeled the issue as minor. The company posted about it at 23:01 UTC while its team looked into the problem, and by 23:16 UTC it said things had stabilized and it was keeping watch. Pagarme listed the window of impact as 19:14 to 19:54 local time, did not name a cause, and marked the incident resolved at 23:37 UTC.

Affected

API Pagar.me v5.0, API Pagar.me v1.0 a v4.0 (Legacy)

As listed on Pagarme’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Pagarme against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Pagarme: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Pagarme report →

More from Pagarme

Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.

The full archive is on the Pagarme status & history page.

Related: Pagarme status & history. SquidGrid is not affiliated with Pagarme.