Hi Rubens,
On Fri, 2 Aug 2024 at 23:19, Rubens Kuhl wrote:
>
> What would be really convenient was to propagate the internal HTTP
> error to the external handler. It's returning HTTP 200 with this in
> the body:
>
> "status": "error",
> "status_code": 500,
>
> Returning HTTP 500 would have mad
What would be really convenient was to propagate the internal HTTP
error to the external handler. It's returning HTTP 200 with this in
the body:
"status": "error",
"status_code": 500,
Returning HTTP 500 would have made my script happier, as it would move
ahead without that data. But because it
On Fri, 2 Aug 2024 at 13:49, Rubens Kuhl wrote:
>
> This is what the example query from
> https://stat.ripe.net/docs/02.data-api/announced-prefixes.html is
> returning:
https://status.ripe.net/ - they know and are working to fix things.
RIPE conveniently has a status page for this exact incident
https://status.ripe.net/incidents/8jm3b6j26kcf
--
Peter
On Fri, Aug 2, 2024 at 4:51 PM Rubens Kuhl wrote:
> This is what the example query from
> https://stat.ripe.net/docs/02.data-api/announced-prefixes.html is
> returning:
>
> {
>
On Fri 2024-08-02 17:48:17-0300 Rubens wrote:
> I would assume this was not intentional... are any other users out
> there affected by this issue ?
I have a custom nagios check, ripestat_monitor_routes.py, that has been
returning HTTP Error 500: Internal Server Error for about 8 hours.
Regards,
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
6 matches
Mail list logo
