User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
Is Pagarme down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → pagar.me—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
Our checks
Reaching it
Last checked 1 hr ago. Last stored result reached it in 506 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 08 | 0 | 0.0 | 353 ms | 0 |
| Tue 10 | 0 | 0.0 | 817 ms | 0 |
| Tue 12 | 0 | 0.0 | 506 ms | 0 |
| Tue 14 | 0 | 0.0 | 460 ms | 0 |
| Tue 16 | 0 | 0.0 | 275 ms | 0 |
| Tue 19 | 0 | 0.0 | 547 ms | 0 |
| Tue 21 | 0 | 0.0 | 540 ms | 0 |
| Tue 23 | 0 | 0.0 | 238 ms | 0 |
| Wed 01 | 0 | 0.0 | 113 ms | 0 |
| Wed 04 | 0 | 0.0 | 532 ms | 0 |
| Wed 06 | 0 | 0.0 | 618 ms | 0 |
| Wed 08 | 0 | 0.0 | 581 ms | 0 |
| Wed 10 | 0 | 0.0 | 416 ms | 0 |
| Wed 13 | 0 | 0.0 | 436 ms | 0 |
| Wed 15 | 0 | 0.0 | 547 ms | 0 |
| Wed 17 | 0 | 0.0 | 763 ms | 0 |
| Wed 19 | 0 | 0.0 | 543 ms | 0 |
| Wed 21 | 0 | 0.0 | 602 ms | 0 |
| Wed 23 | 0 | 0.0 | 602 ms | 0 |
| Thu 02 | 0 | 0.0 | 324 ms | 0 |
| Thu 04 | 0 | 0.0 | 536 ms | 0 |
| Thu 06 | 0 | 0.0 | 497 ms | 0 |
| Thu 08 | 0 | 0.0 | 552 ms | 0 |
| Thu 10 | 0 | 0.0 | 462 ms | 0 |
| Thu 12 | 0 | 0.0 | 1086 ms | 0 |
| Thu 14 | 0 | 0.0 | 450 ms | 0 |
| Thu 16 | 0 | 0.0 | 551 ms | 0 |
| Thu 18 | 0 | 0.0 | 452 ms | 0 |
| Thu 20 | 0 | 0.0 | 704 ms | 0 |
| Thu 22 | 0 | 0.0 | 620 ms | 0 |
| Fri 00 | 0 | 0.0 | 242 ms | 0 |
| Fri 02 | 0 | 0.0 | 504 ms | 0 |
| Fri 04 | 0 | 0.0 | 565 ms | 0 |
| Fri 06 | 0 | 0.0 | 439 ms | 0 |
| Fri 08 | 0 | 0.0 | 108 ms | 0 |
| Fri 11 | 0 | 0.0 | 456 ms | 0 |
| Fri 13 | 0 | 0.0 | 201 ms | 0 |
| Fri 15 | 0 | 0.0 | 472 ms | 0 |
| Fri 17 | 0 | 0.0 | 462 ms | 0 |
| Fri 18 | 0 | 0.0 | 504 ms | 0 |
| Fri 20 | 0 | 0.0 | 611 ms | 0 |
| Fri 22 | 0 | 0.0 | 620 ms | 0 |
| Sat 00 | 0 | 0.0 | 455 ms | 0 |
| Sat 01 | 0 | 0.0 | 486 ms | 0 |
| Sat 03 | 0 | 0.0 | 507 ms | 0 |
| Sat 04 | 0 | 0.0 | 557 ms | 0 |
| Sat 05 | 0 | 0.0 | 410 ms | 0 |
| Sat 07 | 0 | 0.0 | 506 ms | 0 |
Reliability
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 9 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Pagarme badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Pagarme yet. Outages of 10 minutes or more get their own page here.
Having trouble with Pagarme?
One report per service every 10 minutes from this network. No account.
Follow Pagarme
Get an email when Pagarme goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Pagarme alerts to Slack, Discord or a webhook — free.
About Pagarme
We track Pagarme (pagar.me) as part of the Cloud & developer group. No Pagar.me, conectamos milhares de sites e aplicativos a toda a cadeia de pagamentos e tiramos a complexidade de vender online.
Pagarme publishes an official status page at status.pagar.me; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 454 ms average, 108–620 ms range across 14 successful checks.
Questions
Is Pagarme down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Pagarme last down?
We have not recorded a public Pagarme incident since monitoring began 9 days ago.
What is Pagarme's uptime?
From our own checks: 100% over 9 days of checks.
How fast does Pagarme respond?
454 ms on average over the last 24 hours (108–620 ms).
Does Pagarme have an official status page?
Yes, at https://status.pagar.me.
Pagarme not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Pagarme here at once, the problem is on Pagarme's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Pagarme. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.