update on recent incident, reverting the banner back to normal #107
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rebert
approved these changes
Jan 19, 2026
hansmannj
deleted the
revert_status_page_back_to_normal_add_inofo_on_recent_incident
branch
| Our WMS service is experiencing problems on PROD. There are issues observed with layers, that are served via WMS. | ||
| We are working on a fix for this issue. | ||
|
|
||
| #### [2026-01-19 12:10] Issue with service-wms solved |
Contributor
There was a problem hiding this comment.
@hansmannj @rebert For another time: The incident history is ordered by most recent. So, ideally, this would be on top. 😇
Member
Author
There was a problem hiding this comment.
👍 Thanks for the reminder, @asteiner-swisstopo, I will quickly do another PR and re-order things
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Test link