Provider

Provider · Bids

Bid where demand runs.

Buyers post capacity; providers bid. The score weights declared uptime first, then rating, then inverse price. Your declared uptime shapes where your bids land.

Open requests2capacity seeking a provider
My active bids1submitted, awaiting award
Awarded1wins this window
My declared uptime99.910%this period

For the cross-provider view, see themarket-wide bid book, which ranks every bid across every request and provider.

RequestREQ-881 · ORD-DFW · 10G · performance

Leading score95/100, Aurora Transit, rank 1 of 4

My positionRank 3 of 4, score 74/100

Leaderboard · ORD-DFW

SLA-weighted · score = uptime 50% + rating 20% + price 30%
Bids for REQ-881 (ORD-DFW, 10000 Mbps, performance tier), ranked by SLA-weighted score. Each row names the provider, the rank, the monthly price, the declared uptime, the rating, the score, and the uptime, rating, and price components.
RankProviderPriceDeclaredRatingScoreComponents
1 / 4leadingAurora Transit$1,190/mo99.950%4.4 / 595up95rt88px100
2 / 4Corepath Networks$1,280/mo99.970%4.6 / 585up97rt92px59
3 / 4youMeridian Capacity Co.BID-5403$1,340/mo99.910%4.8 / 574up91rt96px32
4 / 4Blue Harbor DC$1,410/mo99.920%4.2 / 563up92rt84px0

My bids

all requests · live rank
Bids submitted by the demo provider across every request. Each row names the bid, the request, the route, the tier, the monthly price, the declared uptime, the state, and the score.
BidRequestRouteTierPriceDeclaredStateScore
BID-5403REQ-881ORD-DFWperformance$1,340/mo99.910%open74rank 3
BID-5340REQ-870LAX-PHXstandard$980/mo99.950%awarded97

Declared uptime is 99.992% this period; the score weights uptime at 50%, so a five-nines edge is hard to outprice.

Back to Sell