RIPEstats aparently broken
This is what the example query from https://stat.ripe.net/docs/02.data-api/announced-prefixes.html is returning: { "messages": [ [ "error", "There was a problem handling this request. The error has been logged and we will look into the cause as soon as possible. We apologise for any inconvenience." ], [ "warning", "There was a failure working out what the latest available data point is. Results may be incorrect!" ] ], "see_also": [], "version": "1.2", "data_call_name": "announced-prefixes", "data_call_status": "supported", "cached": false, "data": {}, "query_id": "20240802194014-83da148b-94dc-4cd3-9655-7146cf1fee0a", "process_time": 7, "server_id": "app114", "build_version": "live.2024.7.29.212", "status": "error", "status_code": 500, "time": "2024-08-02T19:40:14.012851" } I would assume this was not intentional... Rubens
I noticed this as well, however this is not the best place to report it, I think (?) RIPE NCC support's email is the best place, I assume someone at RIPE NCC staff is monitoring this anyway :) On Fri, 2 Aug 2024 at 22:55, Rubens Kuhl <rubensk@gmail.com> wrote:
This is what the example query from https://stat.ripe.net/docs/02.data-api/announced-prefixes.html is returning:
{ "messages": [ [ "error", "There was a problem handling this request. The error has been logged and we will look into the cause as soon as possible. We apologise for any inconvenience." ], [ "warning", "There was a failure working out what the latest available data point is. Results may be incorrect!" ] ], "see_also": [], "version": "1.2", "data_call_name": "announced-prefixes", "data_call_status": "supported", "cached": false, "data": {}, "query_id": "20240802194014-83da148b-94dc-4cd3-9655-7146cf1fee0a", "process_time": 7, "server_id": "app114", "build_version": "live.2024.7.29.212", "status": "error", "status_code": 500, "time": "2024-08-02T19:40:14.012851" }
I would assume this was not intentional...
Rubens ----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/routing-wg.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
Hi all, On Fri, 2 Aug 2024 at 23:57, Ben Cartwright-Cox via routing-wg <routing-wg@ripe.net> wrote:
I noticed this as well, however this is not the best place to report it, I think (?) RIPE NCC support's email is the best place, I assume someone at RIPE NCC staff is monitoring this anyway :)
On Fri, 2 Aug 2024 at 22:55, Rubens Kuhl <rubensk@gmail.com> wrote:
This is what the example query from https://stat.ripe.net/docs/02.data-api/announced-prefixes.html is returning:
{ "messages": [ [ "error", "There was a problem handling this request. The error has been logged and we will look into the cause as soon as possible. We apologise for any inconvenience." ], [ "warning", "There was a failure working out what the latest available data point is. Results may be incorrect!" ] ], "see_also": [], "version": "1.2", "data_call_name": "announced-prefixes", "data_call_status": "supported", "cached": false, "data": {}, "query_id": "20240802194014-83da148b-94dc-4cd3-9655-7146cf1fee0a", "process_time": 7, "server_id": "app114", "build_version": "live.2024.7.29.212", "status": "error", "status_code": 500, "time": "2024-08-02T19:40:14.012851" }
I would assume this was not intentional...
We had an issue with the HBase database underlying many RIPEstat datasets [0]. The issue was resolved by now. Please let us know if you see any further issues, or have further questions, at stat@ripe.net. Kind regards, Ties de Kock RIPE NCC [0]: https://status.ripe.net/incidents/8jm3b6j26kcf
Rubens ----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/routing-wg.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/routing-wg.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
participants (3)
-
Ben Cartwright-Cox -
Rubens Kuhl -
Ties de Kock