- Detected by Pingoru
- May 21, 2026, 07:23 AM UTC
- Resolved
- May 21, 2026, 08:39 AM UTC
- Duration
- 1h 16m
Affected: Netaxept TerminalNetaxept API
Timeline · 3 updates
-
investigating May 21, 2026, 07:23 AM UTC
We are currently investigating this issue.
-
identified May 21, 2026, 07:43 AM UTC
The issue has been identified and a fix is being implemented.
-
identified May 21, 2026, 08:14 AM UTC
We are continuing to work with highest priority on a fix for this issue.
Read the full incident report →
- Detected by Pingoru
- May 21, 2026, 07:05 AM UTC
- Resolved
- May 22, 2026, 06:04 AM UTC
- Duration
- 22h 58m
Affected: Netaxept TerminalNetaxept API
Timeline · 8 updates
-
investigating May 21, 2026, 08:29 AM UTC
We are currently investigating this issue.
-
investigating May 21, 2026, 08:30 AM UTC
We are continuing to work with highest priority on a fix for this issue.
-
investigating May 21, 2026, 09:11 AM UTC
We are still addressing the ongoing network issue. While resolution is taking longer than expected, our engineers are actively working to restore full service. We appreciate your understanding.
-
monitoring May 21, 2026, 12:07 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring May 21, 2026, 01:30 PM UTC
Operations have been stable since 14:35, we will continue to monitor the situation closely.
-
monitoring May 21, 2026, 03:13 PM UTC
We are experiencing transaction impact again since 16:57
-
monitoring May 21, 2026, 03:25 PM UTC
Update: Operations have been stable again since 17:10
-
resolved May 22, 2026, 06:04 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 19, 2026, 02:40 PM UTC
- Resolved
- May 19, 2026, 03:50 PM UTC
- Duration
- 1h 9m
Affected: Netaxept TerminalNetaxept API
Timeline · 5 updates
-
investigating May 19, 2026, 02:54 PM UTC
We are currently investigating an issue causing an elevated number of transaction failures on Netaxept.
-
monitoring May 19, 2026, 03:18 PM UTC
Situation is stable and services operating normally.
-
identified May 19, 2026, 03:47 PM UTC
Elevated number of transaction failures on Netaxept is back.
-
monitoring May 19, 2026, 03:52 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved May 19, 2026, 04:01 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 05, 2026, 08:20 AM UTC
- Resolved
- May 05, 2026, 08:35 AM UTC
- Duration
- 15m
Affected: Netaxept Other Components
Timeline · 2 updates
-
investigating May 05, 2026, 08:28 AM UTC
We are currently investigating this issue.
-
resolved May 05, 2026, 08:37 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 15, 2026, 08:19 PM UTC
- Resolved
- Apr 15, 2026, 09:01 PM UTC
- Duration
- 41m
Timeline · 2 updates
-
investigating Apr 15, 2026, 08:54 PM UTC
We are investigating an issue that affects Netaxept. This is an automated message.
-
resolved Apr 15, 2026, 09:17 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 31, 2026, 08:00 AM UTC
- Resolved
- Mar 31, 2026, 08:09 AM UTC
- Duration
- 9m
Affected: Netaxept Other Components
Timeline · 2 updates
-
investigating Mar 31, 2026, 08:05 AM UTC
Our customer support phone lines are temporarily unavailable. We are actively investigating the issue. https://payments.nets.eu/contact-support
-
resolved Mar 31, 2026, 08:09 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 30, 2026, 11:45 AM UTC
- Resolved
- Mar 30, 2026, 12:38 PM UTC
- Duration
- 52m
Affected: Netaxept TerminalNetaxept API
Timeline · 3 updates
-
investigating Mar 30, 2026, 11:59 AM UTC
We are currently investigating this issue.
-
monitoring Mar 30, 2026, 12:21 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 30, 2026, 12:38 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 27, 2026, 09:25 AM UTC
- Resolved
- Mar 27, 2026, 09:41 AM UTC
- Duration
- 15m
Affected: Netaxept TerminalNetaxept API
Timeline · 2 updates
-
identified Mar 27, 2026, 09:39 AM UTC
VippsMobilePay confirmed an issue on their side, affecting transactions. https://status.vippsmobilepay.com/incidents/nycy3f139jf8
-
resolved Mar 27, 2026, 10:06 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 11, 2026, 08:29 PM UTC
- Resolved
- Mar 11, 2026, 08:39 PM UTC
- Duration
- 10m
Affected: Netaxept TerminalNetaxept API
Timeline · 2 updates
-
investigating Mar 12, 2026, 07:32 AM UTC
We are currently investigating this issue.
-
resolved Mar 12, 2026, 07:32 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 10, 2026, 08:10 AM UTC
- Resolved
- Mar 10, 2026, 12:37 PM UTC
- Duration
- 4h 26m
Affected: Netaxept Other Components
Timeline · 3 updates
-
investigating Mar 10, 2026, 08:17 AM UTC
Our customer support phone lines are temporarily unavailable. We are actively investigating the issue. https://payments.nets.eu/contact-support
-
investigating Mar 10, 2026, 09:27 AM UTC
Our phone system provider has identified the issue and is implementing a workaround.
-
resolved Mar 10, 2026, 12:37 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 27, 2026, 01:08 PM UTC
- Resolved
- Feb 27, 2026, 01:35 PM UTC
- Duration
- 26m
Affected: Netaxept API
Timeline · 2 updates
-
investigating Feb 27, 2026, 01:26 PM UTC
We are currently investigating this issue.
-
resolved Feb 27, 2026, 01:30 PM UTC
This incident has been resolved. Netaxept Query API experienced degraded performance.
Read the full incident report →
- Detected by Pingoru
- Feb 18, 2026, 11:28 AM UTC
- Resolved
- Feb 18, 2026, 11:48 AM UTC
- Duration
- 20m
Affected: Netaxept API
Timeline · 2 updates
-
investigating Feb 18, 2026, 11:40 AM UTC
We are currently investigating this issue.
-
resolved Feb 18, 2026, 11:57 AM UTC
This incident has been resolved. Netaxept Query API experienced degraded performance.
Read the full incident report →
- Detected by Pingoru
- Feb 17, 2026, 08:15 PM UTC
- Resolved
- Feb 17, 2026, 08:50 PM UTC
- Duration
- 35m
Affected: Netaxept TerminalNetaxept API
Timeline · 2 updates
-
investigating Feb 18, 2026, 09:35 AM UTC
We are currently investigating this issue.
-
resolved Feb 18, 2026, 09:38 AM UTC
The incident has been solved. An internal change on Netaxept caused unexpected disturbance.
Read the full incident report →
- Detected by Pingoru
- Feb 16, 2026, 07:00 AM UTC
- Resolved
- Feb 16, 2026, 08:12 AM UTC
- Duration
- 1h 12m
Affected: Netaxept Customer Test
Timeline · 2 updates
-
investigating Feb 16, 2026, 07:29 AM UTC
We are currently experiencing an issue affecting the Netaxept Test environment.
-
resolved Feb 16, 2026, 08:12 AM UTC
The issue affecting Netaxept Test has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 02, 2026, 02:00 PM UTC
- Resolved
- Feb 02, 2026, 02:16 PM UTC
- Duration
- 16m
Affected: Netaxept TerminalNetaxept API
Timeline · 2 updates
-
identified Feb 02, 2026, 02:23 PM UTC
We are currently investigating slow API response time.
-
resolved Feb 02, 2026, 02:27 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 23, 2026, 09:20 AM UTC
- Resolved
- Jan 23, 2026, 01:50 PM UTC
- Duration
- 4h 29m
Affected: Netaxept TerminalNetaxept Customer Test
Timeline · 2 updates
-
identified Jan 23, 2026, 09:54 AM UTC
Click to Pay on iOS Safari is currently displaying visual issues in production and test. Our team has identified the problem and a fix is in progress.
-
resolved Jan 23, 2026, 01:52 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 19, 2026, 07:05 PM UTC
- Resolved
- Jan 19, 2026, 09:35 PM UTC
- Duration
- 2h 30m
Affected: Netaxept TerminalNetaxept API
Timeline · 2 updates
-
identified Jan 20, 2026, 08:01 AM UTC
We are investigating an issue affecting Nexi authorisationsystem in Finland
-
resolved Jan 20, 2026, 08:01 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 19, 2026, 09:50 AM UTC
- Resolved
- Jan 19, 2026, 10:20 AM UTC
- Duration
- 29m
Affected: Netaxept TerminalNetaxept API
Timeline · 2 updates
-
identified Jan 19, 2026, 10:14 AM UTC
Vipps MobilePay is experiencing issues affecting transactions. https://status.vippsmobilepay.com/incidents/0qmhyt9df92b
-
resolved Jan 19, 2026, 10:31 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 12, 2026, 08:00 AM UTC
- Resolved
- Jan 12, 2026, 01:15 PM UTC
- Duration
- 5h 14m
Affected: Netaxept TerminalNetaxept API
Timeline · 5 updates
-
identified Jan 12, 2026, 08:32 AM UTC
MitID is currently experiencing instability.
-
monitoring Jan 12, 2026, 09:45 AM UTC
A fix has been implemented and we are monitoring the results.
-
identified Jan 12, 2026, 09:58 AM UTC
MitID is currently experiencing instability.
-
monitoring Jan 12, 2026, 11:58 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jan 12, 2026, 01:15 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 15, 2025, 08:00 AM UTC
- Resolved
- Dec 15, 2025, 12:45 PM UTC
- Duration
- 4h 45m
Affected: Netaxept Customer Test
Timeline · 2 updates
-
identified Dec 15, 2025, 09:15 AM UTC
We are currently experiencing an issue affecting the test environment.
-
resolved Dec 15, 2025, 12:54 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 12, 2025, 08:14 AM UTC
- Resolved
- Nov 12, 2025, 08:22 AM UTC
- Duration
- 8m
Affected: Netaxept TerminalNetaxept API
Timeline · 2 updates
-
investigating Nov 12, 2025, 08:21 AM UTC
We are currently investigating this issue.
-
resolved Nov 12, 2025, 08:38 AM UTC
Incident was identified as disturbance with Vipps MobilePay payments. Issue has been resolved. https://status.vippsmobilepay.com/incidents/kkfxky0sftm2
Read the full incident report →
- Detected by Pingoru
- Nov 11, 2025, 07:10 PM UTC
- Resolved
- Nov 11, 2025, 07:14 PM UTC
- Duration
- 4m
Affected: Netaxept TerminalNetaxept API
Timeline · 2 updates
-
investigating Nov 12, 2025, 07:27 AM UTC
We are currently investigating this issue.
-
resolved Nov 12, 2025, 07:27 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 11, 2025, 05:46 PM UTC
- Resolved
- Nov 11, 2025, 05:52 PM UTC
- Duration
- 6m
Affected: Netaxept TerminalNetaxept API
Timeline · 2 updates
-
investigating Nov 12, 2025, 08:37 AM UTC
We are currently investigating this issue.
-
resolved Nov 12, 2025, 08:37 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 15, 2025, 08:30 AM UTC
- Resolved
- Oct 15, 2025, 08:50 AM UTC
- Duration
- 19m
Affected: Netaxept API
Timeline · 2 updates
-
identified Oct 15, 2025, 09:04 AM UTC
We have identified slowness on API
-
resolved Oct 15, 2025, 09:09 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 12, 2025, 07:10 AM UTC
- Resolved
- Oct 12, 2025, 07:30 AM UTC
- Duration
- 20m
Affected: Netaxept TerminalNetaxept API
Timeline · 2 updates
-
investigating Oct 17, 2025, 08:50 AM UTC
We are currently investigating this issue.
-
resolved Oct 17, 2025, 08:50 AM UTC
This incident has been resolved.
Read the full incident report →