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
The API's /realtime endpoint frequently returns a 503 response when queried. Over the past week, the site has returned a 503 response about 24% of the time. This number comes from some VictoriaMetrics + Prometheus monitoring I set up that periodically queries the Hoboken realtime endpoint at https://path.api.razza.dev/v1/stations/hoboken/realtime.
Here's a graph of the response code over time:
Not trying to complain here, just stating the way things are. I realize that running this service is probably expensive and PATH doesn't go out of their way to make it easier for you! I'm happy to help out with funding or running the service since I use it every day.
The text was updated successfully, but these errors were encountered:
Not sure what went wrong. This will probably repro and requires more investigation when it does. I reset the jobs, let me know if this has (at least temporarily) improved this.
The API's /realtime endpoint frequently returns a 503 response when queried. Over the past week, the site has returned a 503 response about 24% of the time. This number comes from some VictoriaMetrics + Prometheus monitoring I set up that periodically queries the Hoboken realtime endpoint at https://path.api.razza.dev/v1/stations/hoboken/realtime.
Here's a graph of the response code over time:
Not trying to complain here, just stating the way things are. I realize that running this service is probably expensive and PATH doesn't go out of their way to make it easier for you! I'm happy to help out with funding or running the service since I use it every day.
The text was updated successfully, but these errors were encountered: