My experience with Cloudblast

averagedatahoarder

Have been a lurker on LET for a bit and more recently a member. I have several servers on @cloudblast so I thought I’d share my experience.

Will start with cons:

• NL servers are slow, they use 7551P and noticed ~40% hypervisor steal. US/UK regions worked fine so I suspect just an issue with NL.
• Support is a bit slow but faster on Discord.
• First top up didn’t get credited to my account but opened a ticket and they fixed it + provided credit.
  Routing was a bit cursed for me pulling data, but probably mostly my fault.

Pros:

• Unlimited bandwidth is (seems?) actually unlimited, I’ve pushed nearly 500TB of traffic through in a month with no throttling.
• Able to sustain 5-7Gbps up/down.
• Good dashboard, nice API. Accepts crypto.
• Great bandwidth to price ratio, probably the best I have found.

Overall very happy with their service (as someone optimizing for bandwidth) and running 4 servers with them. Performance on non-NL regions is good. Especially for bandwidth IMO it is a great option

averagedatahoarder

Also- had a lot of trouble getting a SLC VPS, so I setup a script that queried their API every few seconds to automatically provision something whenever it became available

itzsenu

@averagedatahoarder said: Unlimited bandwidth is (seems?) actually unlimited, I’ve pushed nearly 500TB of traffic through in a month with no throttling.

what are you running to actually use that much bandwidth?

@cloudblast if it’s truly unlimited, is it okay to use around 1 to 3 PB of bandwidth per month?

averagedatahoarder

what are you running to actually use that much bandwidth?

Mirroring Linux ISOs (jkjk)

averagedatahoarder

I guess I'd ask you @itzsenu, what are YOU hosting that needs 1-3PB of bandwidth? :P

itzsenu

@averagedatahoarder said:
I guess I'd ask you @itzsenu, what are YOU hosting that needs 1-3PB of bandwidth? :P

it’s a video streaming system where it only streams the changed pixels, with a max 1 to 2 ms delay on the server side, excluding the user’s network and location latency.

                    ┌─────────────────────────────────────────────────────┐
                    │              GLOBAL CONTROL PLANE                    │
                    │  - Session registry (distributed, replicated)        │
                    │  - Leader election (Raft/Paxos across mother nodes)  │
                    │  - Global health telemetry aggregator                │
                    └───────────────┬───────────────────────────────────────┘
                                    │
          ┌─────────────────────────┼─────────────────────────┐
          │                         │                          │
  ┌───────▼────────┐      ┌────────▼────────┐       ┌─────────▼───────┐
  │ MOTHER-REGION-A │◄────►│ MOTHER-REGION-B │◄─────►│ MOTHER-REGION-C  │  ← MOTHER TIER
  │ (Primary, Asia) │      │ (Primary, EU)   │       │ (Primary, LATAM) │    (multi-region,
  │  + hot standby  │      │  + hot standby  │       │  + hot standby   │     active-active)
  └───────┬─────────┘      └────────┬────────┘       └─────────┬────────┘
          │                         │                          │
    ┌─────┴─────┐             ┌─────┴─────┐              ┌─────┴─────┐
    │  TIER 1   │             │  TIER 1   │              │  TIER 1   │
    │  MESH A   │             │  MESH B   │              │  MESH C   │
    │ Child 1-N │◄──cross─────│ Child 1-N │──cross──────►│ Child 1-N │   (inter-region
    │ (VPS)     │  region     │ (VPS)     │  region      │ (VPS)     │    mesh sync for
    └─────┬─────┘  sync       └─────┬─────┘  sync        └─────┬─────┘    failover only)
          │                         │                          │
    ┌─────▼─────┐             ┌─────▼─────┐              ┌─────▼─────┐
    │  TIER 2   │             │  TIER 2   │              │  TIER 2   │
    │  RELAY A  │◄───────────►│  RELAY B  │◄────────────►│  RELAY C  │   (dedicated,
    │ (Dedicated│   sync      │ (Dedicated│   sync       │ (Dedicated│    active-active
    │  + backup)│             │  + backup)│              │  + backup)│    with failover)
    └─────┬─────┘             └─────┬─────┘              └─────┬─────┘
          │                         │                          │
    ┌─────▼──────┐            ┌─────▼──────┐             ┌─────▼──────┐
    │  TIER 3    │            │  TIER 3    │             │  TIER 3    │
    │  EDGE A1-N │            │  EDGE B1-N │             │  EDGE C1-N │   (geo-nearest
    │  (VPS)     │            │  (VPS)     │             │  (VPS)     │    to end users)
    └─────┬──────┘            └─────┬──────┘             └─────┬──────┘
          │                         │                          │
       Users                     Users                      Users
    (Asia region)              (EU region)               (LATAM region)

(note: this diagram was drawn by GPT, but the architecture behind it is the same.)