BGP / BYOIP

Misaka.io supports Border Gateway Protocol (BGP) (opens in a new tab) for advertising routes to your Misaka.io servers. Both IPv4 and IPv6 are supported.

To enable this feature, please read the linked document and open a support ticket if you agree with the terms and conditions.

Available Regions

The service is available in all regions but not all our providers update filters automatically and some of them may require manual intervention. If you are interested in a specific region, please open a support ticket.

Below is a list of our available regions and their IP transit blends. We may have more providers in a region than listed below, but we only list the ones that are generally available to all customers.

Code	Type	CDN77	GSL	RETN	PCCW	Lumen	Arelion	Cogent	IX
IAD01	Core	✅	❌	❌	✅	❌	❌	❌	Equinix Ashburn
EWR02	Core	❌	❌	❌	❌	❌	❌	❌
MIA02	Core	✅	❌	❌	❌	❌	❌	❌	FL-IX
SEA02	Core	✅	❌	❌	❌	❌	❌	❌	SIX Seattle
MCI01	Core	❌	❌	❌	❌	❌	❌	❌	KCIX
SJC10	Core	✅	❌	❌	❌	❌	✅	✅	Equinix San Jose
LAX07	Edge	✅	❌	❌	❌	❌	❌	❌
BER02	Core	❌	❌	✅	❌	✅	❌	❌	BCIX
MOW01	Core	❌	❌	✅	❌	❌	❌	❌
HKG12	Core	✅	✅	✅	✅	❌	❌	❌
TPE01	Core	❌	❌	❌	❌	❌	❌	❌	TPIX-TW, STUIX
NRT04	Core	✅	✅	❌	✅	❌	❌	❌
SIN03	Core	✅	✅	❌	✅	❌	❌	❌
JNB01	Core	✅	❌	❌	✅	❌	❌	❌	NAPAfrica Johannesburg
SAO03	Edge	✅	❌	❌	❌	❌	❌	❌	IX.BR

Notes

IPv4 prefixes in TPE01 POP would be announced to TPIX and STUIX only. Domestic peering with eyeballs are unreasonably expensive and need manual approval by the carriers so it won't be available unless you pay additional fees.
Egress of all customer prefixes will be routed using the standard routing profile regardless what instance type you are using. That means prefixes announced from a S2P instance will be routed using the same routing profile as a S2N instance.

Filtering

We currently use access-list instead of uRPF (opens in a new tab) for maximum flexibility.

There are some exceptions due to the limitations of our providers.

In MOW01, our provider AS56630 (opens in a new tab) uses uRPF (opens in a new tab) and we cannot change it. Please announce your routes to AS56630 with no-export and no-advertise community even you don't want to use them for ingress in case of reachability issues.
In all locations with AS60068 (opens in a new tab), manual intervention is NOW required to update the filters. Please open a support ticket if you need to announce a new prefix and the current expected time to update the filters is 1 month.

Configuration

Once the BGP feature is enabled for your account, you can configure BGP sessions in the Networking tab of each VM.

Networking Tab

One VM can only have one BGP session pair (IPv4 + IPv6 under same ASN).
If you need to have multiple BGP sessions, you can create multiple VMs and configure them separately.

IP Replacement Route BGP with BIRD