[Resolved] Incidence in some AOC Services

We inform you that the incident that affected some of the AOC services has been resolved, such as: EACAT, e-NOTUM, Via Oberta, Unified Registry. If you have any questions about this incident, you can contact us through the Support Portal.

[Completed] Intervention scheduled for maintenance tasks

The scheduled maintenance intervention on 08/29 at 19:00 p.m. on the platform has been successfully completed. iArxiu of the production environment. If you need more information about this scheduled intervention, you can contact the AOC Consortium support service through the contact form

[Resolved] Incidence in INSS and TGSS services

For reasons beyond the AOC's control, INSS and TGSS services were interrupted today from 11:39 a.m. to 12:18 p.m. The services are now working properly. If you have any questions about this incident, you can contact us through the Support Portal.

[Completed] Intervention scheduled for maintenance tasks

Due to an intervention scheduled for Wednesday 29/08 at 3:30 p.m., several AOC services and platforms may be affected. The estimated duration of the intervention is 30 minutes. The services that will be affected will be: Via Oberta e-NOTUM e-BOARD EACAT Unified Registry (MUX) For more information about this intervention you can contact us at [...]

[Resolved] Incidence in some AOC Services.

The incident affecting some of the AOC's services has been resolved, such as: EACAT, e-NOTUM, Via Oberta, Unified Registry. If you have any questions about this incident, you can contact us through the Support Portal.

[Resolved] Incidence on FNMT provider certificate validations

We inform you that the incident that existed in the validations of the FNMT lender's certificates, through the Validator of the AOC Consortium, has been resolved. For more information about this incident you can contact us through the Validator Support Portal.

[Solved]Problems with settlements

Due to an incident in the Inter-Administrative Collaboration Platform, some errors have occurred when creating entries in the registry.EACAT and to the own records integrated with the MUXIn this sense, some procedures ofEACAT have not been completed correctly, causing in some cases the corresponding entry number in the entity [...]

[Resolved]Incident detected in the Unified Registry service (MUX)

The incident detected around 11:05 on August 14, where we began to suffer a degradation of the system with exclusive impact on the Unified Registry service (MUX), causing errors in certain queries of the auxiliary register or document retrieval. To improve the service, the functionality had to be temporarily stopped […]