SignalX BGP VPS Service – Setup and Usage Guide Print

  • bgp, vps, bgp-vps, ip transit, ipv4 transit, ipv6 transit, bgp setup
  • 0

If you have ordered SignalX’s BGP VPS service, you benefit from full IP transit on both IPv4 and IPv6.

Once your BGP VPS is activated, you will receive your login credentials by email and can begin using the service.

⚠️ Important: BGP sessions are activated only after the customer confirms that their local BGP configuration is properly set up.


BGP Session Details with SignalX

  • ASN: 214402

  • AS-SET: AS214402:AS-SIGNALX

All BGP VPS customers are automatically added to our AS-SET to ensure proper routing control and filtering with our upstream carriers.


IP Addressing

  • IPv4: By default, each BGP VPS receives a non-routable IPv4 address (from an internal range dedicated to BGP).
    If you require a public IPv4 address, this is available as an add-on service and can be requested by opening a Support Ticket.

  • IPv6: A public IPv6 address is assigned by default.


Requirements for Announcing Prefixes

When establishing BGP sessions and announcing your prefixes via SignalX, you must:

  1. Create a ROA in the relevant IRR where your subnet is registered (RIPE, ARIN, APNIC, or RADB). These are the only IRRs currently supported.

  2. Enable RPKI for the subnet(s) you intend to announce through SignalX.

This significantly reduces validation time and ensures our systems can verify that the prefix announcement is authorized from your ASN.


Service Cancellation

If the BGP VPS service is canceled, your ASN will automatically be removed from our AS-SET. No manual action is required on your side.


Propagation Timelines

Please note that prefix announcements are not immediately visible globally, due to upstream route filtering policies. Expected propagation times are:

  • ~8 hours → visibility on SignalX IX route servers (if ROA/RPKI is in place).

  • 12–24 hours → visibility through Tier-1 and Tier-2 ISPs/carriers connected to SignalX (if ROA/RPKI is in place).

This delay is caused by upstream carriers’ fixed route-filter refresh intervals. While we can raise a ticket to request a manual refresh, there is no guarantee that visibility will be accelerated.


Support

For any questions regarding BGP setup, troubleshooting, or best practices, please open a Support Ticket via your My SignalX account. Our network engineers will be glad to assist.


Was this answer helpful?

« Back

Powered by WHMCompleteSolution