Start with what the machine is for
Most configuration mistakes happen before any option is chosen — when nobody asked what the machine is actually for. So settle that first.
Hosting a site, an API, a dev environment? Then it is application memory, data growth, and whether visitors need IPv4. Ordinary sites and dev environments run happily on conventional networking; there is genuinely nothing to agonise over on the routing side. Bringing your own prefix? Answer three questions before anything else: who originates it publicly, who runs BGP, and how traffic reaches your VPS. Here to learn BGP? Pick concrete exercises — bring up a neighbour, test an export filter, watch a route get accepted. Concrete goals make concrete configurations.
| What you are doing | Settle first | Read first |
|---|---|---|
| Hosting a site, API or dev environment | Application resources, storage growth, whether visitors need IPv4 | Cloud configurations and address options |
| Using a prefix you control or are authorised to use | Who originates, who runs BGP, how traffic reaches the VPS | Own ASN versus provider-managed routing |
| Learning BGP | What you want to practise, and what you may announce | BGP basics and the networking FAQ |
Standard or BGP VPS?
Two sentences. Standard: conventional networking, no BGP session. BGP VPS: one session per tier, extendable to two, and the additional /48 lives only here. Native IPv6, optional public IPv4, Enterprise SSD or NVMe storage — both sides have all of that.
The second session deserves its own sentence: it adds one to a counter. Whether that is redundancy or decoration depends on which routers the sessions land on, which lines they ride, and which failure points they share. Think that through before you tick the box.
The address options — do not buy the wrong one
Native IPv6: one address, inside a prefix announced by AS219361. The option provides an address for an application — but it is one address, not a resource you hold.
Additional IPv6 /48 (BGP VPS only): under the published plan, AS219361 announces it and routes it to your machine; no ASN required on your side. It is not PI space you can carry elsewhere, and the ROA does not transfer to you.
Your own prefix: you bring the prefix, the authority to use it and the intended origin ASN, and we check the routing records together. Said plainly, before anything else: a working session grants no right to use somebody else's addresses.
How to read the configuration page
Memory has three mouths to feed: the application processes, the database and its caches, and — if routing runs here — the daemon's appetite for routes, filters and post-restart convergence. Storage covers the system, the data, the logs and growth.
“2 GB RAM” on a package cannot answer “will it hold the full table”; address families, route counts, software and policy decide that. The better question: which application runs next to which routing workload on this machine.
The 1 Gbps figure and the monthly traffic allowance are configuration references, not promised rates. If a business depends on the allowance, ask first what is counted, when it resets, and what happens at the limit.
What to have ready before you talk to us
Four things make any configuration conversation short and useful. Bringing your own prefix? Add a fifth, noted at the end.
- Application: what runs, what must be reachable, what a short outage costs.
- Addresses: one address or a whole block, who authorises it, who originates it publicly.
- Routing: how many sessions and which feed, and what each one is for.
- Operations: who runs the OS and the app, where backups live, who you call about the network.
- Your own prefix (if any): the ASN, the prefix list, links to the public records, and a note on who originates and who runs BGP — the ROA and IRR records should agree with that choice.
Save your configuration
The configuration tool exists for browsing before buying: compare product type, tier, storage and network options, with a running summary alongside — monthly traffic and session count included.
Copy configuration link keeps a URL carrying your choices; Copy configuration list gives a plain-text summary. Reopen the link any time; switching languages keeps it. Bringing a saved configuration to a conversation beats reciting package names — both sides look at the same options.
The usual caveat: saving creates no order, collects nothing, reserves no capacity, allocates no addresses. When ordering opens, we all read the final scope and terms together then.
Questions & answers
Do I need BGP VPS just to host a website?
No. Conventional networking carries a website fine; size it by application resources and the address families its visitors need. The day your design truly needs routes exchanged or a prefix announced is the day to revisit.
Does the extra /48 need my own public ASN?
No. AS219361 announces that block and routes it to your VPS — provider-originated. Announcing under your own ASN is a different arrangement.
A second session means redundancy, right?
It means the counter says two. Redundancy depends on the routers, upstreams and shared failure points behind the sessions — and on the application surviving the switch. “2” does not imply “independent”.
What should I keep from the configuration tool?
The link or the copied summary, plus two sentences: what the application does and what you want from routing. Whoever reads it knows exactly what you need — and the save itself orders nothing.