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.

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

Add peerings for AS4242420157 #219

Merged
merged 4 commits into from
Nov 19, 2024
Merged

Conversation

Ichbinjoe
Copy link
Contributor

Title - adds peerings to CHI, SJC, SEA & TYO to my respective nodes in the same city.

@jvoss jvoss merged commit e89e20c into routedbits:main Nov 19, 2024
2 checks passed
Copy link

Hello,

We have started the deployment of new configuration on our side for the peering at our SEA1 PoP.
It is ready for the configuration on your side.

You can find the relevant information for this PoP on our Nodes page: https://dn42.routedbits.com/nodes/#sea1
It can also be obtained programmatically via nodes.json

We manage configuration via our dn42-peers repository, you can submit pull requests to add/remove/change your own peerings. Once accepted and merged, the changes are pushed to our routers within a few minutes.

Pull Request: routedbits/dn42-peers#219

Let us know if you have any questions or issues.

Thanks,
NOC, RoutedBits

Copy link

Hello,

We have started the deployment of new configuration on our side for the peering at our TYO1 PoP.
It is ready for the configuration on your side.

You can find the relevant information for this PoP on our Nodes page: https://dn42.routedbits.com/nodes/#tyo1
It can also be obtained programmatically via nodes.json

We manage configuration via our dn42-peers repository, you can submit pull requests to add/remove/change your own peerings. Once accepted and merged, the changes are pushed to our routers within a few minutes.

Pull Request: routedbits/dn42-peers#219

Let us know if you have any questions or issues.

Thanks,
NOC, RoutedBits

Copy link

Hello,

We have started the deployment of new configuration on our side for the peering at our FNC1 PoP.
It is ready for the configuration on your side.

You can find the relevant information for this PoP on our Nodes page: https://dn42.routedbits.com/nodes/#fnc1
It can also be obtained programmatically via nodes.json

We manage configuration via our dn42-peers repository, you can submit pull requests to add/remove/change your own peerings. Once accepted and merged, the changes are pushed to our routers within a few minutes.

Pull Request: routedbits/dn42-peers#219

Let us know if you have any questions or issues.

Thanks,
NOC, RoutedBits

Copy link

Hello,

We have started the deployment of new configuration on our side for the peering at our CHI1 PoP.
It is ready for the configuration on your side.

You can find the relevant information for this PoP on our Nodes page: https://dn42.routedbits.com/nodes/#chi1
It can also be obtained programmatically via nodes.json

We manage configuration via our dn42-peers repository, you can submit pull requests to add/remove/change your own peerings. Once accepted and merged, the changes are pushed to our routers within a few minutes.

Pull Request: routedbits/dn42-peers#219

Let us know if you have any questions or issues.

Thanks,
NOC, RoutedBits

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants