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

Add a warning if roto-api cannot be reached #37

Open
AlexanderBand opened this issue Oct 1, 2021 · 2 comments
Open

Add a warning if roto-api cannot be reached #37

AlexanderBand opened this issue Oct 1, 2021 · 2 comments

Comments

@AlexanderBand
Copy link
Member

Another case of a user not being able to use roto-api. The UI fails really silently, and should be clearer:
NLnetLabs/routinator#658
@density215
Copy link
Member

I had it flail silently on purpose, since it has nothing to do with the functioning of routinator perse?

@AlexanderBand
Copy link
Member Author

I understand. The thing is: there are now users who enter a prefix, expect a BGP/Allocation result, don't get one and wonder why.

The last update times of BGP/RIR data being absent is the only hint.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@density215 @AlexanderBand