Skip to content

group incidents by year #92

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

group incidents by year #92

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
4845e9d
group incidents by year
hansmannj Nov 20, 2025
6a846ba
Nested grouping of details
hansmannj Nov 20, 2025
880b00a
Adding third level sections
hansmannj Nov 20, 2025
eb5cca2
expand all incidents by default
hansmannj Nov 21, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 29 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -80,3 +80,32 @@ To add a release note, follow these steps:
```

2. Save the file and commit your changes.

## How to add a new incident details section

1. Edit the file [`status-page.md`](./page/status-page.md)
1. If there already is a section of the current year, such as e.g. `::::: details 2025 {open}`, add the incident on top of that section, leaving one blank line after the `::::: details 2025`
1. If it is the first incident of the current year, create a new section for the new year, e.g. `::::: details 2026 {open}` and already the closing `:::::`, so basically like this:

```markdown
::::: details 2026 {open}

:::::
```

1. Add the new incident either in the section of the new year or in the already existing section of the current year like this:

```markdown
::::: details 2026

:::: details MONTH, DAY(, TIME) - [SHORT HEADING OF THE INCIDENT] {open}

::: info MONTH, DAY(, Time) [LONGER HEADING OF THE INCIDENT]

[DETAILED TEXT ABOUT THE INCIDENT]
:::
::::
:::::
```

The five `:` are only when you start and end a new year, otherwise, only the part that starts and ends with four `:` is relevant for you.
69 changes: 40 additions & 29 deletions page/status-page.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,9 +44,14 @@ This page provides the latest status updates for all \*.geo.admin.ch web service

## Incident History

### [2025-11-12] Issues with search service
<!-- Please check the README.md for details on how to add new incidents or start a new year, thanks!
-->

#### [2025-11-14] Information on recent problems when changing address data from RBD to the official directory of building addresses
::::: details 2025

:::: details Nov 12 - Issues with search service {open}

::: info Nov 14 - Information on recent problems when changing address data from RBD to the official directory of building addresses

On Wednesday, November 12, 2025, the Search Service was switched from the register of buildings and dwellings (RBD) to the new default data source of the official directory of building addresses.

Expand All @@ -65,29 +70,31 @@ On the SearchServer endpoint, you can either perform a type=featuresearch or a t
For your information, there are three ways to perform an address search:

1. Swisssearch search with origins=address; if desired, the feature ID can be transferred to the feature endpoint of the specialist layer ch.swisstopo.amtliches-gebaeudeadressverzeichnis
1. FeatureSearch in the layer ch.swisstopo.amtliches-gebaeudeadressverzeichnis; if desired, the feature ID can be transferred to the feature endpoint of the thematic layer ch.swisstopo.amtliches-gebaeudeadressverzeichnis
1. FeatureSearch in the layer ch.bfs.gebaeude_wohnungs_register; if desired, the feature ID can be transferred to the feature endpoint of the specialist layer ch.bfs.gebaeude_wohnungs_register.
2. FeatureSearch in the layer ch.swisstopo.amtliches-gebaeudeadressverzeichnis; if desired, the feature ID can be transferred to the feature endpoint of the thematic layer ch.swisstopo.amtliches-gebaeudeadressverzeichnis
3. FeatureSearch in the layer ch.bfs.gebaeude_wohnungs_register; if desired, the feature ID can be transferred to the feature endpoint of the specialist layer ch.bfs.gebaeude_wohnungs_register.

Specific documentation for this topic: [Search | \*.geo.admin.ch](https://docs.geo.admin.ch/access-data/search.html#request-details)
:::
::::
:::: details Nov 12 - Incident with Service Stac {open}

### [2025-11-12] Incident with Service Stac

#### [2025-11-12 19:15] Disruption of Service Stac - Resolved
::: info Nov 12, 19:15 - Disruption of Service Stac - Resolved

The root cause that led to the outage of STAC API could be identified and resolved. The problem was a
misconfigration of database logging that was done earlier today
that led to a rapid increase in log volume and eventually resulted in full disk of the database cluster. Disk
space has been increased and the logging configuration change rolled back.

STAC API is functioning normal again.

#### [2025-11-12 19:15] Disruption of Service Stac
:::
::: info Nov 12, 19:15 - Disruption of Service Stac

The STAC API on data.geo.admin.ch is currently unavailable. We're investigating the cause and will give an update later tonight.
:::
::::
:::: details July 2nd - Incident with Printing {open}

### [2025-07-02] Incident with Printing

#### [2025-07-03 10:00] Incident Resolved
::: info July 3, 10:00 - Incident Resolved

An update to map.geo.admin.ch made on July 2, 2025 caused a temporarily disruption to the system's printing service.
This resulted in a problem with the browser cache storing the information.
Expand Down Expand Up @@ -122,15 +129,16 @@ SAFARI

- In Safari, go to "Settings" > "Advanced" and enable "Show Develop menu in menu bar."
- Click on ‘Develop’ in the menu and then on "Empty Cache."

#### [2025-07-02 16:00] Incident Detected
:::
::: info July 2, 16:00 - Incident Detected

The printing functionality of map.geo.admin.ch is currently unavailable.
We are analysing the problem and keep you updated on this page.
:::
::::
:::: details April 30 - Incident with WMS/WMTS {open}

### [2025-04-30] Incident with WMS/WMTS

#### [2025-05-06] Root Cause Analysis
::: info May 6 - Root Cause Analysis

On the 30th of April and 1st of May, the WMS service and WMTS service provided by geo.admin.ch were restricted or unavailable, which also affected the print function in the map viewer.

Expand All @@ -142,25 +150,25 @@ The problem was resolved by our specialists by rolling out new system components
We apologise for any inconvenience caused.

Thank you for your understanding and patience.

#### [2025-05-01, 16:00] Incident Resolved
:::
::: info May 1, 16:00 - Incident Resolved

The disruption has been resolved.

All services on \*geo.admin.ch are now available as usual.

We thank you for your understanding and patience.

#### [2025-05-01, 12:00] Update
:::
::: info May 1, 12:00 - Update

No change since the update at 9:25 a.m.
We are continuing to work intensively to resolve the problem.

The next update will be provided today at around 4 p.m. or as soon as the disruption has been resolved.

We apologise for any inconvenience caused and thank you in advance for your patience.

#### [2025-05-01, 09:25] Update
:::
::: info May 1, 09:25 Update

The extent of the disruption has been reduced in the meantime.
Certain WMS layers and the printing service are still affected.
Expand All @@ -169,8 +177,8 @@ No other services provided by \*geo.admin.ch are affected. We are continuing to
The next update will be provided today at around 12 noon or as soon as the disruption has been resolved.

We apologise for any inconvenience caused and thank you in advance for your patience.

#### [2025-04-30, 16:00] Update
:::
::: info April 30, 16:00 Update

The disruption to the WMS, WMTS and print services is still ongoing.
No other services provided by \*geo.admin.ch are affected.
Expand All @@ -179,17 +187,17 @@ We are working intensively to resolve the problem.
The next update will be provided tomorrow, 1 May, at 9 a.m. or as soon as the disruption has been resolved.

We apologise for any inconvenience caused and thank you in advance for your patience.

#### [2025-04-30, 12:00] Update
:::
::: info April 30, 12:00 Update

The disruption to WMS and WMTS services is still ongoing.
We are continuing to work hard to resolve the issue.

The next update will be provided today at around 4 p.m. or as soon as the disruption has been resolved.

We apologise for any inconvenience caused and thank you in advance for your patience.

#### [2025-04-30, 10:00] Incident Detected
:::
::: info April 30, 10:00 Incident Detected

We are currently experiencing some problems with our WMS and WMTS services, which we are analysing and will resolve as quickly as possible.
The duration of the disruption is still unknown.
Expand All @@ -198,3 +206,6 @@ We will keep you updated on this page.
The next update will be provided today at around 12 noon or as soon as the disruption has been resolved.

We apologise for any inconvenience caused and thank you in advance for your patience.
:::
::::
:::::
Loading