You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At this moment, the NMBS servers are struggling. This means that neither the official app nor iRail can provide any travel information. While many apps can benefit from their own status feed for an in-app banner or notification (that also can handle app update notifications in case of a botched release or an app <-> iRail issue that isn't a problem on iRail's side), these "app-specific" feeds need to be able to fetch the iRail/NMBS status automatically. A status endpoint could contain one status object for each endpoint, where each status object contains a status enum and an error message in Dutch, French, German and English. The error message should only be used in case the endpoint is unhealthy.
The status can be fetched from uptimeRobot (status.irail.be)
To prevent incorrect warnings, the used tests should be down for at least a minute before marking an endpoint as unhealthy.
To prevent incorrect "up-again!" data, the used tests should be up for at least two minutes before marking an endpoint as recovering. During the recovering period, the endpoint is usable, but might go down again, or might fail random requests.
An endpoint can be marked as healthy after 15 minutes.
Optionally, the down time or datetime when the endpoint went offline can be included
The text was updated successfully, but these errors were encountered:
At this moment, the NMBS servers are struggling. This means that neither the official app nor iRail can provide any travel information. While many apps can benefit from their own status feed for an in-app banner or notification (that also can handle app update notifications in case of a botched release or an app <-> iRail issue that isn't a problem on iRail's side), these "app-specific" feeds need to be able to fetch the iRail/NMBS status automatically. A status endpoint could contain one status object for each endpoint, where each status object contains a status enum and an error message in Dutch, French, German and English. The error message should only be used in case the endpoint is unhealthy.
The text was updated successfully, but these errors were encountered: