-
Notifications
You must be signed in to change notification settings - Fork 47
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
chore: add various COLBY AS4242422558 peerings #115
Conversation
Hello, We have started the deployment of new configuration on our side for the peering at our TOR1 PoP. You can use our Nodes page for PoP information to be used: https://dn42.routedbits.com/nodes/#tor1 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#115 Let us know if you have any questions or issues. Thanks, |
Hello, We have started the deployment of new configuration on our side for the peering at our EWR1 PoP. You can use our Nodes page for PoP information to be used: https://dn42.routedbits.com/nodes/#ewr1 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#115 Let us know if you have any questions or issues. Thanks, |
Hello, We have started the deployment of new configuration on our side for the peering at our AMS1 PoP. You can use our Nodes page for PoP information to be used: https://dn42.routedbits.com/nodes/#ams1 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#115 Let us know if you have any questions or issues. Thanks, |
Hello, We have started the deployment of new configuration on our side for the peering at our FRA1 PoP. You can use our Nodes page for PoP information to be used: https://dn42.routedbits.com/nodes/#fra1 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#115 Let us know if you have any questions or issues. Thanks, |
Hello, We have started the deployment of new configuration on our side for the peering at our CHI1 PoP. You can use our Nodes page for PoP information to be used: https://dn42.routedbits.com/nodes/#chi1 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#115 Let us know if you have any questions or issues. Thanks, |
Hello, We have started the deployment of new configuration on our side for the peering at our MIA1 PoP. You can use our Nodes page for PoP information to be used: https://dn42.routedbits.com/nodes/#mia1 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#115 Let us know if you have any questions or issues. Thanks, |
Hello, We have started the deployment of new configuration on our side for the peering at our TYO1 PoP. You can use our Nodes page for PoP information to be used: https://dn42.routedbits.com/nodes/#tyo1 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#115 Let us know if you have any questions or issues. Thanks, |
Hello, We have started the deployment of new configuration on our side for the peering at our SYD1 PoP. You can use our Nodes page for PoP information to be used: https://dn42.routedbits.com/nodes/#syd1 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#115 Let us know if you have any questions or issues. Thanks, |
Hello, We have started the deployment of new configuration on our side for the peering at our SIN1 PoP. You can use our Nodes page for PoP information to be used: https://dn42.routedbits.com/nodes/#sin1 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#115 Let us know if you have any questions or issues. Thanks, |
Hello, We have started the deployment of new configuration on our side for the peering at our LAX1 PoP. You can use our Nodes page for PoP information to be used: https://dn42.routedbits.com/nodes/#lax1 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#115 Let us know if you have any questions or issues. Thanks, |
Hello, We have started the deployment of new configuration on our side for the peering at our PAR1 PoP. You can use our Nodes page for PoP information to be used: https://dn42.routedbits.com/nodes/#par1 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#115 Let us know if you have any questions or issues. Thanks, |
Hello, We have started the deployment of new configuration on our side for the peering at our SEA1 PoP. You can use our Nodes page for PoP information to be used: https://dn42.routedbits.com/nodes/#sea1 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#115 Let us know if you have any questions or issues. Thanks, |
Hello, We have started the deployment of new configuration on our side for the peering at our LON1 PoP. You can use our Nodes page for PoP information to be used: https://dn42.routedbits.com/nodes/#lon1 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#115 Let us know if you have any questions or issues. Thanks, |
Hello, We have started the deployment of new configuration on our side for the peering at our STO1 PoP. You can use our Nodes page for PoP information to be used: https://dn42.routedbits.com/nodes/#sto1 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#115 Let us know if you have any questions or issues. Thanks, |
Z-Side PR: Colbyjdx/dn42-ansible#1 (may want to wait until this is merged)