This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/routing-wg@ripe.net/
[routing-wg] RIPE Stat routing info
- Previous message (by thread): [routing-wg] RIPE Stat routing info
- Next message (by thread): [routing-wg] RIPE Stat routing info
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Agustin Formoso
aformoso at ripe.net
Wed Jul 29 17:55:01 CEST 2020
Hello, This is indeed an issue related to RIPEstat, and affecting the _latest_ routing information for prefixes. You should still able to access historical data. Thanks for reporting the issue, we'll come back as soon as we have a fix in place. Sorry for any inconvenience this might be causing. — Agustín RIPE NCC > On 29 Jul 2020, at 17:45, Massimo Candela <massimo at us.ntt.net> wrote: > > There is clearly an outage going on with RIPEstat at the moment. > Basically all prefix visibility stopped at midnight. > This is affecting only the RIPEstat API but not the RIS/RIS live data. > > I already contacted the RIPEstat team. I hope they will fix it soon. > > Ciao, > Massimo > > > On 29/07/2020 15:12, Sergey Myasoedov via routing-wg wrote: >> Hello, >> >> For the every IPv4/v6 network I'm checking, RIPE Stat gives me >> "announced": false >> result. >> >> I'm observing this since last hour or two. >> >> Is this the outage or output format change in the RIPE Stat? >> >> Thank you. >> >> >> -- >> Kind regards, >> Sergey Myasoedov >> >> > >
- Previous message (by thread): [routing-wg] RIPE Stat routing info
- Next message (by thread): [routing-wg] RIPE Stat routing info
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]