marcel,
i think nick and cynthia answered your question. but there remains the
question of where the heck one goes for day to day routing ops help. as
cynthia pointed out, this wg is more for the policy and technical
underpinnings, not actuall operations. what's strange is that it is not
at
Hi Marcel,
I just want to start out by saying that the working groups are not a
support channel and this more routing than anything db related.
But with regards to your case, according to ripestat the prefixes are
announced by 2 ASNs but overall have 100% visibility (99% for the v6).
I am
Marcel Zimmer via db-wg wrote on 13/03/2021 08:07:
Do you have a tip for me where I should go troubleshooting?
the prefixes are being originated by both as8422 and as212033. If you
ask as8422 to stop announcing it, it should swing over to 212033.
Nick
Good morning dear community,
it is an honor to be part of it :)
We have applied for and been assigned our own AS at the beginning of the year
(AS212033). Since yesterday the link to the first peering partner Lumen
(AS3356) is available and the following networks should be announced:
IPv4
