Localpayments status

No, but Localpayments reports degraded performance: its services work, but some are slower or return more errors than usual. Open incident: 3rd Party Apparent Incident for Payout in Peru. It started today at 18:57 UTC. Firemap last read the status page today at 19:06 UTC.

They are the four status levels Firemap uses for Localpayments, the same scale most status pages use. Operational means everything works normally. Degraded means the services work, but some are slower or return more errors than usual. Partial outage means some services, regions or payment methods are unavailable, while the rest still work. Major outage means a key service is unavailable for most customers. When Localpayments publishes it, each official incident also shows its stage: Investigating, Identified, Monitoring or Resolved. In the status history, each day shows its incidents by level, and a purple strip marks days with community reports.

Not on its own. Firemap shows what Localpayments 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 Localpayments support with specific transaction IDs if you see failures.

From the official Localpayments status page, once Firemap has connected it. Firemap then reads the page automatically every few minutes and records each status change and incident Localpayments publishes there. Community reports come from PayAtlas users and appear in their own block; they do not change the official status.

They come from different sources. Official incidents are what Localpayments has confirmed, and providers often post one 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.

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.

It shows how old the data is instead of guessing. When Firemap has a status for Localpayments, the top of this page shows when Firemap last read the official status page, for example “Updated 2h ago”. If a check fails, the page keeps the last status Firemap read, with its time. If there has been no reading for 7 days, or Firemap has no working status page for Localpayments, the page shows “Status page not connected” instead of a status. The status history counts incidents, so a day without incidents stays green even if the page could not be read that day.

Firemap tracks the official status pages of payment providers listed on PayAtlas. It checks each page automatically and stores every incident with its start time and, once resolved, its end time. When Firemap has data for Localpayments, this page shows 30 days of status history, every official incident that is still open and the resolved incidents that started in the last 30 days. Community reports from the last 30 days are shown for every provider.

Firemap can confirm only what Localpayments 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 Localpayments says so, and it cannot see problems the provider has not reported.