Landax Outage History

Landax is up right now

Landax had 13 outages in the last 2 years totaling 472h 57m of downtime, averaging 0.5 incidents per month.

There were 13 Landax outages since October 23, 2024 totaling 472h 57m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.landax.no

Minor May 27, 2026

Some problems on servers

Detected by Pingoru
May 27, 2026, 10:55 AM UTC
Resolved
May 27, 2026, 11:02 AM UTC
Duration
7m
Affected: Web Application
Timeline · 5 updates
  1. investigating May 27, 2026, 10:55 AM UTC

    We are currently investigating this issue.

  2. investigating May 27, 2026, 10:56 AM UTC

    We are continuing to investigate this issue.

  3. identified May 27, 2026, 10:57 AM UTC

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

  4. monitoring May 27, 2026, 11:00 AM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved May 27, 2026, 11:02 AM UTC

    This incident has been resolved.

Read the full incident report →

Major March 2, 2026

Application issues causing slowness

Detected by Pingoru
Mar 02, 2026, 11:42 AM UTC
Resolved
Mar 02, 2026, 02:39 PM UTC
Duration
2h 56m
Affected: Web ApplicationMobile Applications
Timeline · 5 updates
  1. investigating Mar 02, 2026, 11:42 AM UTC

    We are currently investigating this issue.

  2. investigating Mar 02, 2026, 11:43 AM UTC

    We are continuing to investigate this issue.

  3. identified Mar 02, 2026, 12:05 PM UTC

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

  4. monitoring Mar 02, 2026, 12:21 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Mar 02, 2026, 02:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Major December 10, 2025

Problems with web application

Detected by Pingoru
Dec 10, 2025, 07:17 AM UTC
Resolved
Dec 10, 2025, 07:41 AM UTC
Duration
23m
Affected: Web Application
Timeline · 4 updates
  1. investigating Dec 10, 2025, 07:17 AM UTC

    We are currently investigating this issue.

  2. identified Dec 10, 2025, 07:23 AM UTC

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

  3. monitoring Dec 10, 2025, 07:34 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Dec 10, 2025, 07:41 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical November 5, 2025

Problems with servers

Detected by Pingoru
Nov 05, 2025, 06:18 PM UTC
Resolved
Nov 05, 2025, 06:25 PM UTC
Duration
6m
Affected: Web Application
Timeline · 4 updates
  1. investigating Nov 05, 2025, 06:18 PM UTC

    We are currently investigating this issue.

  2. investigating Nov 05, 2025, 06:20 PM UTC

    We are continuing to investigate this issue.

  3. investigating Nov 05, 2025, 06:22 PM UTC

    We are continuing to investigate this issue.

  4. resolved Nov 05, 2025, 06:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Major November 5, 2025

Problems with SMS and mail sending

Detected by Pingoru
Nov 05, 2025, 08:26 AM UTC
Resolved
Nov 05, 2025, 08:46 AM UTC
Duration
19m
Affected: Notification
Timeline · 4 updates
  1. investigating Nov 05, 2025, 08:26 AM UTC

    We are currently investigating this issue.

  2. identified Nov 05, 2025, 08:40 AM UTC

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

  3. monitoring Nov 05, 2025, 08:46 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Nov 05, 2025, 08:46 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical October 29, 2025

Azure problems causing downtime

Detected by Pingoru
Oct 29, 2025, 05:05 PM UTC
Resolved
Oct 29, 2025, 09:10 PM UTC
Duration
4h 4m
Affected: Web ApplicationMobile Applications
Timeline · 3 updates
  1. investigating Oct 29, 2025, 05:05 PM UTC

    We are currently investigating this issue.

  2. monitoring Oct 29, 2025, 09:10 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Oct 29, 2025, 09:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 3, 2025

Microsoft user synchronisation is currently not working

Detected by Pingoru
Oct 03, 2025, 07:05 AM UTC
Resolved
Oct 22, 2025, 11:11 AM UTC
Duration
19d 4h
Affected: Web Application
Timeline · 3 updates
  1. identified Oct 03, 2025, 07:05 AM UTC

    The sync causes downtime and has been turned off. We are working on identifying the real issue.

  2. identified Oct 22, 2025, 11:11 AM UTC

    We are continuing to work on a fix for this issue.

  3. resolved Oct 22, 2025, 11:11 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical August 18, 2025

Landax is down

Detected by Pingoru
Aug 18, 2025, 01:31 PM UTC
Resolved
Aug 18, 2025, 01:33 PM UTC
Duration
1m
Affected: Web Application
Timeline · 5 updates
  1. investigating Aug 18, 2025, 01:31 PM UTC

    We are currently investigating this issue.

  2. investigating Aug 18, 2025, 01:32 PM UTC

    We are continuing to investigate this issue.

  3. identified Aug 18, 2025, 01:32 PM UTC

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

  4. monitoring Aug 18, 2025, 01:32 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Aug 18, 2025, 01:33 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 11, 2025

Some problems with the search engines.

Detected by Pingoru
Aug 11, 2025, 07:05 AM UTC
Resolved
Aug 11, 2025, 10:08 AM UTC
Duration
3h 2m
Affected: Search
Timeline · 2 updates
  1. investigating Aug 11, 2025, 07:05 AM UTC

    Some customers are experiencing some disruptions related to the search engine

  2. resolved Aug 11, 2025, 10:08 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 23, 2025

Landax App is not available in AppStore at the moment

Detected by Pingoru
May 23, 2025, 07:36 AM UTC
Resolved
May 23, 2025, 07:54 AM UTC
Duration
18m
Affected: Mobile Applications
Timeline · 4 updates
  1. investigating May 23, 2025, 07:36 AM UTC

    We are currently investigating this issue.

  2. identified May 23, 2025, 07:46 AM UTC

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

  3. monitoring May 23, 2025, 07:54 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved May 23, 2025, 07:54 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical May 2, 2025

Landax Down

Detected by Pingoru
May 02, 2025, 01:09 PM UTC
Resolved
May 02, 2025, 01:16 PM UTC
Duration
6m
Affected: Web ApplicationMobile Applications
Timeline · 4 updates
  1. investigating May 02, 2025, 01:09 PM UTC

    We are currently investigating this issue.

  2. identified May 02, 2025, 01:16 PM UTC

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

  3. monitoring May 02, 2025, 01:16 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved May 02, 2025, 01:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 27, 2025

Webapplication in new design is down

Detected by Pingoru
Jan 27, 2025, 08:21 AM UTC
Resolved
Jan 27, 2025, 08:36 AM UTC
Duration
15m
Affected: Web Application
Timeline · 4 updates
  1. investigating Jan 27, 2025, 08:21 AM UTC

    We are currently investigating this issue.

  2. identified Jan 27, 2025, 08:29 AM UTC

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

  3. monitoring Jan 27, 2025, 08:31 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jan 27, 2025, 08:36 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical October 23, 2024

Problems with email sending

Detected by Pingoru
Oct 23, 2024, 01:28 PM UTC
Resolved
Oct 23, 2024, 02:37 PM UTC
Duration
1h 8m
Affected: Notification
Timeline · 2 updates
  1. investigating Oct 23, 2024, 01:28 PM UTC

    We are currently investigating this issue.

  2. resolved Oct 23, 2024, 02:37 PM UTC

    This incident has been resolved.

Read the full incident report →