Easypay PT Outage History

Easypay PT is up right now

Pingoru has recorded 4 incidents for Easypay PT: 4 in the last 12 months and 1 in the last 90 days.

Source: status.easypay.pt

4incidents recorded
4last 12 months
1last 90 days
6 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Easypay PT in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026224 of 720 (3%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202610 of 744 (0%)
August 202600 of 744 (0%)
September 202611 of 720 (0%)
October 202600 of 573 (0%)

Incidents, newest first

Minor September 8, 2026 Degraded payment processing 1h 15m Single Payments, Frequent Payments, Subscription Payments, Out Payments and 1 more

Started Sep 08, 2026, 03:15 PM UTC· resolved Sep 08, 2026, 04:30 PM UTC

  1. investigating Sep 08, 2026, 03:15 PM UTC

    We are currently experiencing degraded performance affecting payment processing. Some payment requests may fail or experience increased response times. Our team is investigating the issue and working to restore normal service.

  2. investigating Sep 08, 2026, 03:54 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Sep 08, 2026, 03:55 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Sep 08, 2026, 06:32 PM UTC

    The issue has been identified and resolved. All services are operating normally. We apologise for any inconvenience caused.

Read the full incident report →

Notice July 2, 2026 SMS delivery disruption – Backoffice

Started Jul 02, 2026, 05:13 PM UTC· resolved Jul 02, 2026, 05:13 PM UTC

  1. resolved Jul 02, 2026, 05:13 PM UTC

    Between 05:00 and 18:20 (Lisbon time, WEST), SMS messages were not delivered due to an issue with an upstream dependency. During this period: * Users with SMS-based two-factor authentication were unable to log in to the Backoffice. * New account registrations could not be completed because phone verification was unavailable. * Pay By Link customers did not receive payment links via SMS. As of 18:15, SMS delivery has been restored, and all affected services are operating normally. We apologise for the inconvenience caused.

Read the full incident report →

Major April 22, 2026 MB WAY payments failing due to TLS certificate validation issue 23h 59m Single Payments, Frequent Payments, Pay By Link

Started Apr 22, 2026, 08:58 AM UTC· resolved Apr 23, 2026, 08:58 AM UTC

  1. resolved Apr 22, 2026, 09:09 AM UTC

    We experienced failures affecting MB WAY payments due to TLS certificate validation errors when calling the SIBS Payments API. From 23:58 UTC to 08:58 UTC, users were unable to complete MB WAY payments due to TLS certificate validation failures when calling the SIBS Payments API. The issue was caused by an outdated CA certificate bundle in our runtime environment, which did not trust the updated certificate chain presented by the SIBS API. The issue has been resolved by redeploying the affected service with updated CA certificates. Other payment methods were not affected. All systems are now operating normally. Root cause: outdated CA trust store in application container.

Read the full incident report →

Notice April 17, 2026 Blocked API calls without UserAgent header –

Started Apr 17, 2026, 02:30 PM UTC· resolved Apr 17, 2026, 02:30 PM UTC

  1. resolved Apr 21, 2026, 03:01 PM UTC

    Blocked all API calls (api.prod.easypay.pt) without UserAgent header (2026/04/17 between 15:45 and 16:19)

Read the full incident report →