Previous incidents

Dear Customer the incident is now solved and the situation is back to normality, we'll continue to improve our services in order to avoid future problems. We also would like to apologize for the inconvenience this may have caused.

The root cause for the issue about callbacks not being properly sent was fixed at around 20:40 CEST. The situation has been gradually going back to normal, and now the services are fully operational.

We are continuing to monitor the situation.

The root cause for the issue about callbacks not being properly sent was fixed at around 20:40 CEST. The situation has been gradually going back to normal, and now the services are fully operational.

We are continuing to monitor the situation.

We have fixed the root cause of the issue. PreventGo / IdDocCheck / IdSelf services are now fully operational

The issue has been resolved and the service has been fully restored. All systems are back to normal operation. We are continuing to closely monitor the situation over the coming hours to ensure stability.

We apologize for the inconvenience caused and thank you for your patience.

Status updated

We've found the problem and we applied the resolution. Currently the situation is stable and we see no errors. We still monitor the situation

Incident Resolved – Trust and Sign and Prevent

The incident affecting communication latency between our hosting sites has now been resolved.

The Trust and Sign and Prevent services are operating normally again, and our teams are no longer observing any disruptions related to this incident.

Thank you for your patience and understanding throughout the incident.

The Namirial Team

Dear Customer,

The incident affecting PVID workflows has now been resolved.

Our teams have implemented the necessary corrective actions, and the service is fully operational again.

We apologize for any inconvenience caused and thank you for your patience and understanding.

We have identified and resolved the root cause of the issue. All the systems are working nominally.

Dear customer, the team has resolved the issues and will continue to monitor the situation to prevent it from recurring.

This is just a test notification

The issue has been fully resolved.
Our engineering team identified that the temporary service degradation was caused by an internal rate-limiting component enforcing a
safety threshold. Adjusting the rate-limit configuration immediately resolved the issue and restored normal traffic flow.
To prevent this from happening again, we will be introducing supervised procedures to progressively tune this configuration value over time. We apologize for any inconvenience this may have caused.

English version (Italian version follows underneath)

The issue causing electronic invoices to be rejected with error code 00002 – Duplicate file name has been fully resolved. System monitoring has confirmed that operations are stable, and this incident is now closed.

We apologize for the inconvenience and thank you for your patience.

Versione in italiano

Il problema che causava lo scarto delle fatture elettroniche con codice 00002 – Nome file duplicato è stato completamente risolto. Il mo...