Network

The network under
your server.

Every server gets a public IPv4 address and a firewall you write the rules for. Inbound DDoS scrubbing runs by default. Transit into each region comes from multiple carriers, so when one of them has a bad hour, routes move to the others without anyone filing a ticket.

1 public IPv4 · on every server
Ch1 · Transit

Multiple carriers into every region

If a carrier drops or starts routing badly, BGP shifts traffic onto another one. Between regions, your packets cross the public internet, the same as everyone else's. We don't run fiber of our own.

Ch2 · DDoS scrubbing

Inbound scrubbing, on by default

Traffic coming into your server passes through scrubbing first, so volumetric floods are absorbed before they reach the box. You don't switch it on, and it isn't a paid tier. Application-layer abuse still lands on you.

Ch3 · Addresses & firewall

One public IPv4 per server

Every server boots with its own public IPv4, included in the plan price. A reserved IP outlives the server it was attached to: $3/mo, up to three per account. It keeps billing for as long as it exists, even while it sits detached.

Bandwidth

What each plan includes

Bandwidth comes with the plan and is counted per server, per month. Houston and Singapore cost the same.

PlanMonthlyBandwidth
Ember$51 TB
Flare$102 TB
Blaze$203 TB

Past the allowance, bandwidth is $0.01/GB.

Included

What comes with every server

Public IPv4one per server, in the plan price
Firewallyour rules, per server, no extra charge
DDoS scrubbinginbound, on by default, in every region
Multiple transit carriersroutes move when one carrier drops
Bandwidth1 TB on Ember, 2 TB on Flare, 3 TB on Blaze
Reserved IP$3/mo, up to three, billed while it exists
Network FAQ

Common questions

Do I get a public IPv4?

Yes. One per server, included in the plan price.

Can I run BGP with you or bring my own IP space?

No. Neither is offered today. Write to us if you need it and we'll tell you where it stands.

What latency should I expect from my users?

Latency depends mostly on distance, so a server in Houston will answer someone in Texas sooner than it answers someone in Sydney, and the rest of it depends on their ISP and the hour of day, which is why the only figure worth trusting is the one you measure on your own path. We publish no latency numbers here because we haven't measured them.

How do I measure it myself?

Run ping, traceroute or MTR from a server to your users, or from your users back to the server. Deploy in each region and compare the paths.

Is DDoS scrubbing an extra charge?

No. Inbound scrubbing runs in every region by default, and volumetric floods are absorbed before they reach your server. Attacks aimed at your application still get through to it, which is what your firewall and rate limits are for.

Which regions can I deploy in?

Houston and Singapore, at the same price in both.