Artifik Outage History

Artifik is up right now

Artifik had 11 outages in the last 2 years totaling 60h 5m of downtime, averaging 0.5 incidents per month.

There were 11 Artifik outages since January 30, 2025 totaling 60h 5m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.artifik.no

Critical October 12, 2026

Service outage

Detected by Pingoru
Oct 12, 2026, 07:04 PM UTC
Resolved
Oct 13, 2026, 07:33 AM UTC
Duration
12h 29m
Affected: ProcurementContractsSupplier bids and submissionsUsers and organizationsPublication serviceSMS and Email ServiceOpen API'sTranslation serivceDigital signingSingle Sign OnArchive integration
Timeline · 8 updates
  1. investigating Oct 12, 2026, 07:04 PM UTC

    We are currently experiencing a service outage. Our developers are investigating the issue as we speak, and we will try to bring the service back to normal as soon as possible. We will come with a new update 21.30 CEST.

  2. investigating Oct 12, 2026, 07:07 PM UTC

    We are continuing to investigate this issue.

  3. investigating Oct 12, 2026, 07:30 PM UTC

    We are continuing to investigate this issue. We will give another update at 22.00CEST.

  4. investigating Oct 12, 2026, 07:33 PM UTC

    We are continuing to investigate this issue.

  5. investigating Oct 12, 2026, 08:02 PM UTC

    The cause has been confirmed as an issue with AWS App Runner. We are in dialogue with our service provider. We will update again at 22.30 CEST.

  6. monitoring Oct 12, 2026, 08:04 PM UTC

    A fix is in place and Artifik is working normally again. We're monitoring to make sure it stays stable.

  7. monitoring Oct 13, 2026, 06:15 AM UTC

    The system has stayed stable. We are still monitoring the situation closely.

  8. resolved Oct 13, 2026, 07:33 AM UTC

    The incident is resolved.

Read the full incident report →

Major July 3, 2026

Error messages and instabilities

Detected by Pingoru
Jul 03, 2026, 04:46 PM UTC
Resolved
Jul 03, 2026, 05:14 PM UTC
Duration
28m
Affected: ProcurementContractsSupplier bids and submissionsUsers and organizations
Timeline · 3 updates
  1. identified Jul 03, 2026, 04:46 PM UTC

    The solution is currently inaccessible to users, both on the buyer and supplier sides, who will get error messages when trying to log in or navigate the system. We are working on solving the issue as soon as possible.

  2. monitoring Jul 03, 2026, 04:53 PM UTC

    This incident is resolved, and the system is back to normal. We will continue to monitor the situation.

  3. resolved Jul 03, 2026, 05:14 PM UTC

    The incident has been resolved.

Read the full incident report →

Major May 11, 2026

Issue with creating draft tender on procurements using eBevis

Detected by Pingoru
May 11, 2026, 06:49 AM UTC
Resolved
May 11, 2026, 03:43 PM UTC
Duration
8h 54m
Affected: Supplier bids and submissions
Timeline · 3 updates
  1. identified May 11, 2026, 06:49 AM UTC

    We have identified an issue where suppliers are unable to create draft bids on procurements set up to use eBevis. We are investigating the issue with high priority and will update this page as soon as we have more information.

  2. identified May 11, 2026, 08:18 AM UTC

    We have identified the issue and are working on a general fix. Affected suppliers with upcoming deadlines can contact us at [email protected] for assistance.

  3. resolved May 11, 2026, 03:43 PM UTC

    The incident has been resolved.

Read the full incident report →

Major March 6, 2026

Mobile signing is temporarily unavailable for non-Norwegian users

Detected by Pingoru
Mar 06, 2026, 07:04 AM UTC
Resolved
Mar 06, 2026, 10:28 AM UTC
Duration
3h 23m
Affected: Supplier bids and submissionsDigital signing
Timeline · 3 updates
  1. identified Mar 06, 2026, 07:04 AM UTC

    Due to an issue in Signicat’s signing solution, it is currently not possible to use mobile signing for bids or contracts. If you are unable to use Norwegian BankID, please contact support. We are in contact with Signicat to resolve the issue.

  2. identified Mar 06, 2026, 09:02 AM UTC

    The issues are restricted to users in certain regions. Users with Norwegian numbers are not affected. We are working together with Signicat to solve the issue.

  3. resolved Mar 06, 2026, 10:28 AM UTC

    The incident has been resolved.

Read the full incident report →

Minor March 3, 2026

Temporary delays and error messages

Detected by Pingoru
Mar 03, 2026, 08:59 AM UTC
Resolved
Mar 03, 2026, 03:14 PM UTC
Duration
6h 15m
Affected: ProcurementContractsSupplier bids and submissions
Timeline · 5 updates
  1. investigating Mar 03, 2026, 08:59 AM UTC

    We are currently experiencing delays in the system, and some users may see error messages. The issue affects both suppliers and contracting authorities. We are investigating the issue and working to resolve it as quickly as possible.

  2. monitoring Mar 03, 2026, 10:37 AM UTC

    We have implemented mitigations to improve system performance. End users should no longer experience delays or error messages. We will continue to monitor the situation closely.

  3. investigating Mar 03, 2026, 11:01 AM UTC

    We are still experiencing delays in the system. We are investigating the situation with high priority and will update this page as soon as we have more information.

  4. identified Mar 03, 2026, 01:55 PM UTC

    Additional mitigations have been implemented, and end users should no longer experience delays. We have also identified the cause of the issue and are working on implementing a permanent fix. We estimate that this will be finalized later today. We will post a new update as soon as we have more information.

  5. resolved Mar 03, 2026, 03:14 PM UTC

    A hotfix has been deployed to the production environment and the service is back to normal operation. We will continue monitoring closely.

Read the full incident report →

Major January 30, 2026

Versjon 3.21: Milepæler på avtaler er utilgjengelig

Detected by Pingoru
Jan 30, 2026, 05:40 AM UTC
Resolved
Jan 30, 2026, 09:03 AM UTC
Duration
3h 23m
Affected: Contracts
Timeline · 3 updates
  1. investigating Jan 30, 2026, 05:40 AM UTC

    We are experiencing an issue that makes milestones on contracts unavailable. We are working on a hotfix and will restore the functionality as soon as possible. Vi opplever for øyeblikket en feil som gjør at milepæler på avtaler ikke er tilgjengelig. Vi jobber med en hotfix og vil gjenopprette funksjonen så snart som mulig.

  2. identified Jan 30, 2026, 07:21 AM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Jan 30, 2026, 09:03 AM UTC

    The incident is resolved, and milestones on contracts are available again.

Read the full incident report →

Major January 9, 2026

Mobile phone signature is unavailable

Detected by Pingoru
Jan 09, 2026, 10:09 AM UTC
Resolved
Jan 09, 2026, 02:42 PM UTC
Duration
4h 32m
Affected: Supplier bids and submissionsDigital signing
Timeline · 3 updates
  1. investigating Jan 09, 2026, 10:09 AM UTC

    We are currently investigating the issue. Please contact [email protected] if you have a deadline approaching.

  2. identified Jan 09, 2026, 11:04 AM UTC

    The issue has been identified, a workaround has been found and the code change for the permanent fix is being reviewed.

  3. resolved Jan 09, 2026, 02:42 PM UTC

    This incident has been hotfixed and resolved. It's now possible to use the mobile phone signature method as expected again.

Read the full incident report →

Minor November 28, 2025

Award Criteria section is not visible on Procurement details page

Detected by Pingoru
Nov 28, 2025, 10:23 AM UTC
Resolved
Nov 28, 2025, 02:52 PM UTC
Duration
4h 29m
Affected: Procurement
Timeline · 3 updates
  1. investigating Nov 28, 2025, 10:23 AM UTC

    We have identified an issue where the award criteria section is not visible on the Procurement details page of a published procurement. The award criteria are visible for suppliers after they create a draft bid. We are investigating the issue and will publish an update within 2 hours.

  2. identified Nov 28, 2025, 10:26 AM UTC

    The root cause has been identified, and we are working on implementing a fix.

  3. resolved Nov 28, 2025, 02:52 PM UTC

    The issue has been resolved.

Read the full incident report →

Major August 19, 2025

Issues with SMS service

Detected by Pingoru
Aug 19, 2025, 08:59 AM UTC
Resolved
Aug 19, 2025, 11:25 AM UTC
Duration
2h 26m
Affected: Procurement
Timeline · 4 updates
  1. identified Aug 19, 2025, 08:59 AM UTC

    We are experiencing issues with our SMS service, affecting the sending of one time login codes. We are investigating the issue and will update status page when we have more information.

  2. identified Aug 19, 2025, 09:13 AM UTC

    When you have entered your phone number and no code is received on your phone, you can use the option to send the code to your email instead.

  3. identified Aug 19, 2025, 11:24 AM UTC

    Issue is resolved

  4. resolved Aug 19, 2025, 11:25 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 26, 2025

Doffin translation service is down

Detected by Pingoru
Feb 26, 2025, 08:20 AM UTC
Resolved
Feb 26, 2025, 09:02 PM UTC
Duration
12h 42m
Affected: Procurement
Timeline · 4 updates
  1. investigating Feb 26, 2025, 08:20 AM UTC

    Our monitoring has detected that the Doffin translation service is down. This stops the process of publishing above EEA threshold, as translation is the final step before sending the eForm to Doffin (and thus TED).

  2. identified Feb 26, 2025, 08:20 AM UTC

    Root cause has been identified, and we have gotten confirmation from the Doffin team that they are working on the issue.

  3. monitoring Feb 26, 2025, 01:41 PM UTC

    Doffin seems to be up again. Their issue is not yet updated (https://github.com/anskaffelser/eforms-sdk-nor/issues/101), but endpoints respond now. We continue to monitor this issue.

  4. resolved Feb 26, 2025, 09:02 PM UTC

    We'll set this to resolved, as the Doffin API has been up for a while now and we have seen customer translations pass through as they should. We will update this incident with a post-mortem report from Doffin once it becomes available.

Read the full incident report →

Major January 30, 2025

Problems with bid signing

Detected by Pingoru
Jan 30, 2025, 10:13 AM UTC
Resolved
Jan 30, 2025, 11:14 AM UTC
Duration
1h 1m
Affected: Procurement
Timeline · 4 updates
  1. investigating Jan 30, 2025, 10:13 AM UTC

    There is currently a problem with signing bids i Artifik. We are working with our supplier for the digital signing solution to identify the root cause. While the incident is ongoing, reach out to [email protected] if you need to sign your bid and we'll try to provide you with a workaround solution.

  2. identified Jan 30, 2025, 10:37 AM UTC

    The root cause has been identified as a problem on our secure signing sub-supplier's side, more information in real-time can be found here: https://status.signicat.com/incidents/9hjqfzv2xl7b We will update this issue as soon as we have more information.

  3. monitoring Jan 30, 2025, 10:52 AM UTC

    A fix has been implemented on our sub-supplier's side. If you are not able to sign your bid, you can try to cancel and resubmit (no changes needed in documents or other responses) to go through the flow again. We will continue to monitor the service and are looking at adding additional monitoring that will notify us ahead of time the next time this happens to offer even smoother workarounds for those affected. Do not hesitate to reach out to [email protected] if you need help or have questions.

  4. resolved Jan 30, 2025, 11:14 AM UTC

    The incident has been resolved. Reach out at [email protected] if you experience any problems. As part of our post-mortem, we'll firm up our alternative signing procedures for situations like this (problems with sub-supplier as in this case, or issues in general with our signing) and improve our probes for this kind of error (that was logged, but we were only alerted when the first support issue was reported today). Timeline of the incident (see also logging of the status updates that should be roughly in sync with this): - First signing error logged in Artifik: 10:28 CET - First support issue to Artifik: 10:37 CET - Artifik senior engineers working on analyzing the issue: 10:50 CET - Signicat publishes error on their side: 10:55 CET - Signicat publishes fix on their side: 11:10 CET, - Signicat publishes resolution message on their side: 11:30 CET, pointing to the issue having started around 10:20 CET and documents submitted after 11:00 CET being fine

Read the full incident report →