Service Incidents

2025

Incident

Start Time (UTC)

End Time (UTC)

Components

Responsible

Taken actions

Out-of-order hardware component in the data storage system.

2025-11-25 15:40

2025-11-25 15:43

boro.elecard.com

Provider

Hardware component replaced.

Notification system malfunction: trigger queue processing is too low.

2025-11-18 19:12

2025-11-21 15:59

boro.elecard.eu

Elecard

Software issue resolved; trigger queue was processed ’til the date mentioned above.

Node server hardware failure:

  • Service completely unavailable between 06:35 UTC and 07:30 UTC (troubleshooting and replacement of the out-of-order server by the provider).

  • Service unavailable via IPv6 till 09:58 UTC.

2025-10-07 06:35

2025-10-07 09:58

boro.elecard.eu

Provider
New hardware implemented, service back online.
IPv6 support re-established.

System failure, an overflow of the file system with DB:

  • most of the task statistics for the indicated period were lost;

  • the service was completely unavailable between 14:10 and 14:40 UTC.

2025-09-14 13:10

2025-09-14 15:10

boro.elecard.eu

Elecard
DB functionality has been restored.
All user tasks that were running at the moment the incident started have been restored.
The cause of the incident has been determined; a work plan for preventing such incidents has been drawn up.

Webhook/Slack/PagerDuty notifications not working.

2025-03-19 11:20

2025-03-20 08:52

boro.elecard.com

Elecard

A software issue has been resolved.

2024

Incident

Start Time (UTC)

End Time (UTC)

Components

Responsible

Taken actions

Scheduled maintenance

2024-12-05 03:30

2024-12-05 05:30
boro.elecard.eu
boro.elecard.com

Provider

Hardware failure

2024-10-19 00:40

2024-10-19 06:12

boro.elecard.com

Elecard

Hardware failure

2024-03-02 13:36

2024-03-02 16:40

boro.elecard.com

Elecard

2023

Incident

Start Time (UTC)

End Time (UTC)

Components

Responsible

Taken actions

Scheduled maintenance

2023-11-16 03:00

2023-11-16 05:00

boro.elecard.eu

Provider