Koordinates Outage History

Koordinates is up right now

Koordinates had 6 outages in the last 2 years totaling 15h 38m of downtime — averaging 0.2 incidents per month.

There were 6 Koordinates outages since June 11, 2025 totaling 15h 38m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.koordinates.com

Critical May 5, 2026

Koordinates.com was offline

Detected by Pingoru
May 05, 2026, 06:54 AM UTC
Resolved
May 05, 2026, 07:57 AM UTC
Duration
1h 3m
Affected: ExportsWeb InterfaceTile Services (including WMTS)WFSData query API's
Timeline · 5 updates
  1. investigating May 05, 2026, 06:54 AM UTC

    We are currently investigating an issue with Koordinates.com. Thanks for your patience - we are working to get the site up as soon as possible.

  2. investigating May 05, 2026, 06:54 AM UTC

    We are continuing to investigate this issue.

  3. investigating May 05, 2026, 07:08 AM UTC

    We are continuing to investigate this issue.

  4. monitoring May 05, 2026, 07:46 AM UTC

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

  5. resolved May 05, 2026, 07:57 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 14, 2026

We're experiencing delays processing new downloads

Detected by Pingoru
Apr 14, 2026, 10:58 PM UTC
Resolved
Apr 14, 2026, 11:28 PM UTC
Duration
30m
Affected: ExportsWeb Interface
Timeline · 3 updates
  1. investigating Apr 14, 2026, 10:58 PM UTC

    We are currently investigating an issue which is delaying the processing of new downloads. Thanks for your patience - we are working to bring downloads back to normal as soon as possible.

  2. identified Apr 14, 2026, 11:21 PM UTC

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

  3. resolved Apr 14, 2026, 11:28 PM UTC

    This incident has been resolved.

Read the full incident report →

Major November 18, 2025

We're experiencing errors / timeouts on Koordinates

Detected by Pingoru
Nov 18, 2025, 12:46 PM UTC
Resolved
Nov 18, 2025, 07:52 PM UTC
Duration
7h 5m
Affected: Web Interface
Timeline · 3 updates
  1. identified Nov 18, 2025, 12:46 PM UTC

    We have identified an issue with one of our providers and are working to resolve the issue.

  2. monitoring Nov 18, 2025, 02:38 PM UTC

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

  3. resolved Nov 18, 2025, 07:52 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 23, 2025

Koordinates Cloud sites are currently offline

Detected by Pingoru
Oct 23, 2025, 03:29 AM UTC
Resolved
Oct 23, 2025, 05:07 AM UTC
Duration
1h 37m
Timeline · 3 updates
  1. investigating Oct 23, 2025, 03:29 AM UTC

    We are currently investigating a loading issue with sites on Koordinates and are working to restore service as soon as possible

  2. monitoring Oct 23, 2025, 04:46 AM UTC

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

  3. resolved Oct 23, 2025, 05:07 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical October 20, 2025

Koordinates.com is currently offline

Detected by Pingoru
Oct 20, 2025, 07:36 AM UTC
Resolved
Oct 20, 2025, 12:22 PM UTC
Duration
4h 46m
Timeline · 3 updates
  1. identified Oct 20, 2025, 07:36 AM UTC

    We have identified the cause and are working to resolve the issue.

  2. monitoring Oct 20, 2025, 08:39 AM UTC

    All sites are now operational but with reduced features.

  3. resolved Oct 20, 2025, 12:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 23, 2025

Koordinates sites are currently slow to respond

Detected by Pingoru
Jul 23, 2025, 04:49 AM UTC
Resolved
Jul 23, 2025, 05:25 AM UTC
Duration
35m
Affected: ExportsWeb InterfaceTile Services (including WMTS)WFSData query API's
Timeline · 3 updates
  1. investigating Jul 23, 2025, 04:49 AM UTC

    We are currently investigating an issue with the Koordinates platform. Thanks for your patience - we are working to get the site up as soon as possible.

  2. identified Jul 23, 2025, 05:00 AM UTC

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

  3. resolved Jul 23, 2025, 05:25 AM UTC

    This incident has been resolved.

Read the full incident report →