Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

LACNIC & Registro.BR uncertainty #263

Open
nbakker opened this issue Jul 25, 2023 · 0 comments · May be fixed by #341
Open

LACNIC & Registro.BR uncertainty #263

nbakker opened this issue Jul 25, 2023 · 0 comments · May be fixed by #341
Assignees
@mxsasha

Comments

@nbakker
Copy link

nbakker commented Jul 25, 2023

Not everybody has access to LACNIC, instead they use TC as IRRdb. Prefixes sometimes show up as Registro.BR and then check out, and sometimes as under LACNIC and then show a warning for only other IRRs.

Example: 2804:2ea0::/32 & 168.181.124.0/22

What is the decision process that the latter is shown with LACNIC as RIR and the former, Registro.BR (TC)? Both show up in delegated-lacnic-extended-latest.

https://irrexplorer.nlnog.net/asn/AS265356
@kiraum kiraum linked a pull request May 12, 2024 that will close this issue
Open
@mxsasha mxsasha linked a pull request Sep 30, 2024 that will close this issue
chore: prefer NIR over RIR #341
Open
@mxsasha mxsasha self-assigned this Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mxsasha mxsasha

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore: prefer NIR over RIR kiraum/irrexplorer
2 participants
@mxsasha @nbakker