Open metrics, live
Last week 874 of 929 builds went live. One incident in the last 30 days: on 23 Oct, new server-rendered deployments failed to start for 9 h 15 min.
Live from our production database, updated , every 10 minutes. Check it yourself
Is it working right now? That is what status.deploybase.eu is for.
94.07%
of builds went live last week
874 of 929. A failure in the site's own code counts against this.
40 s
median build
Over 5,272 builds that went live.
99.87%
of function and server-rendered requests without a platform error
41 of 32,174 failed on our side in 30 days.
1
incident in the last 30 days
Latest on 23 Oct, 9 h 15 min. What happened
What the platform did
The last 12 weeks, from our database. Grey is work done, amber is work that failed; this week, faded, is still running.
Builds and deploys
94.07% went live last week
Branch previews
37 built last week
Forms
56 delivered last week
Server renderingbeta
99.88% without a platform error, 30 days
HTTP functionsbeta
99.27% without a platform error, 30 days
What beta means for functions and server rendering
No SLA and no service credits yet. Your data and deployments are kept exactly as for everything else on deploybase, and breaking changes are announced in the changelog. Each kind leaves beta on its own, once every line under "To leave beta" is met.
| Server rendering | HTTP functions | |
|---|---|---|
| Last 30 days | ||
| Requests | 31,761 | 413 |
| Without a platform error | 99.88% | 99.27% |
| Failed on our side | 38 | 3 |
| Hit the time limit (504) | 0 | 0 |
| Errors from the site's own code | 2 | 0 |
| Answered within 1 s | 93% | 72% |
| Hours measured | 719 of 720 | 719 of 720 |
| Sites live now | 7 | n/a |
| To leave beta | ||
| 99.5% without a platform error, 30 days, 10,000+ requests | Not yet | Not yet |
| No incident over an hour in 30 days | Not yet | Met |
| Monitoring and alerts for server rendering | Not yet | n/a |
| A per-team cap on running functions | Not yet | Not yet |
719 of 720 hours measured so far; the rate counts once all 30 days are.
Server rendering: the 23 Oct incident leaves the window on 22 Nov.
A platform error is a 502, a 503 or a cold start that never came up: our side failed. Requests the visitor cancelled are left out. Errors from the site's own code are shown but not counted against us, and "within 1 s" includes the app's own render time. The gateway in front of every function only sees status codes, so a site that deliberately answers 502 or 503 is counted as our failure.
| Starter | Pro | Scale | |
|---|---|---|---|
| Time limit, HTTP functions | 60 s | 60 s | 60 s |
| Time limit, server rendering | 50 s | 50 s | 50 s |
| Request body | 10 MiB | 10 MiB | 10 MiB |
| Memory per instance | 512 MB | 512 MB | 1 GB |
| Requests per instance | 5 | 10 | 25 |
| Instances per function | up to 3 | up to 3 | up to 3 |
Past its requests per instance, another instance starts, up to the instance limit.
The rest of the numbers
| Building | ||
|---|---|---|
| Builds run Deployments that started a build. Ones still queued are not counted. | 7,077 | Deployments that started a build. Ones still queued are not counted. |
| Went live, all time 6,254 of 7,054 finished builds. Cancelled builds are left out; failures in a site's own code count. | 88.6% | 6,254 of 7,054 finished builds. Cancelled builds are left out; failures in a site's own code count. |
| Build minutes Every minute a build ran, as metered for billing. | 7,770 | Every minute a build ran, as metered for billing. |
| Median build Over 5,272 builds that went live. The mean is 1 min 4 s. | 40 s | Over 5,272 builds that went live. The mean is 1 min 4 s. |
| Busiest week Deployments in the week of 19 Oct 2026. | 1,089 | Deployments in the week of 19 Oct 2026. |
| Building right now Builds running when this snapshot was taken. | 0 | Builds running when this snapshot was taken. |
| Serving | ||
| Bandwidth served Delivered to visitors from our edge, as metered for billing. | 223.7 GB | Delivered to visitors from our edge, as metered for billing. |
| Custom domains Customer domains that passed verification and are serving. | 133 | Customer domains that passed verification and are serving. |
| Projects Sites connected to a repository or set up for uploads. | 310 | Sites connected to a repository or set up for uploads. |
| Teams Every team that signed up, including ones that never deployed. | 489 | Every team that signed up, including ones that never deployed. |
Incidents
9 h 15 min
New server-rendered deployments failed to start. Older deployments kept their server functions running, and those filled a shared quota. Sites already live kept serving.
Superseded server functions are now retired automatically, and we are alerted well before the quota fills.
This list starts in October 2026. Anything that stops customers' work across the platform goes here, dated, with what we changed.
Every number by week and month
| Week of | Deployed | Failed | Cancelled | Forms | Previews |
|---|---|---|---|---|---|
| 2026-02-09 | 13 | 1 | 0 | 0 | 0 |
| 2026-02-16 | 2 | 0 | 0 | 0 | 0 |
| 2026-02-23 | 0 | 0 | 0 | 0 | 0 |
| 2026-03-02 | 0 | 0 | 0 | 0 | 0 |
| 2026-03-09 | 4 | 1 | 0 | 0 | 0 |
| 2026-03-16 | 3 | 4 | 0 | 0 | 0 |
| 2026-03-23 | 3 | 0 | 0 | 0 | 0 |
| 2026-03-30 | 3 | 0 | 0 | 0 | 1 |
| 2026-04-06 | 7 | 5 | 2 | 0 | 0 |
| 2026-04-13 | 1 | 0 | 0 | 0 | 0 |
| 2026-04-20 | 1 | 0 | 0 | 0 | 0 |
| 2026-04-27 | 1 | 4 | 0 | 0 | 0 |
| 2026-05-04 | 4 | 2 | 0 | 0 | 0 |
| 2026-05-11 | 1 | 0 | 0 | 0 | 0 |
| 2026-05-18 | 3 | 0 | 0 | 0 | 1 |
| 2026-05-25 | 4 | 0 | 0 | 0 | 0 |
| 2026-06-01 | 15 | 9 | 0 | 0 | 1 |
| 2026-06-08 | 6 | 0 | 0 | 0 | 0 |
| 2026-06-15 | 7 | 6 | 0 | 0 | 0 |
| 2026-06-22 | 1 | 0 | 0 | 0 | 0 |
| 2026-06-29 | 48 | 5 | 1 | 0 | 6 |
| 2026-07-06 | 15 | 6 | 1 | 0 | 0 |
| 2026-07-13 | 15 | 1 | 0 | 0 | 0 |
| 2026-07-20 | 14 | 2 | 0 | 0 | 1 |
| 2026-07-27 | 6 | 2 | 0 | 4 | 0 |
| 2026-08-03 | 22 | 8 | 0 | 1 | 0 |
| 2026-08-10 | 15 | 15 | 0 | 0 | 0 |
| 2026-08-17 | 268 | 22 | 1 | 3 | 5 |
| 2026-08-24 | 127 | 19 | 0 | 3 | 3 |
| 2026-08-31 | 234 | 35 | 0 | 2 | 6 |
| 2026-09-07 | 376 | 76 | 0 | 4 | 41 |
| 2026-09-14 | 175 | 111 | 0 | 6 | 8 |
| 2026-09-21 | 377 | 78 | 1 | 11 | 9 |
| 2026-09-28 | 453 | 71 | 1 | 12 | 10 |
| 2026-10-05 | 359 | 46 | 5 | 21 | 9 |
| 2026-10-12 | 968 | 96 | 2 | 27 | 59 |
| 2026-10-19 | 1025 | 61 | 3 | 44 | 53 |
| 2026-10-26 | 571 | 37 | 3 | 81 | 18 |
| 2026-11-02 | 874 | 55 | 2 | 56 | 37 |
| 2026-11-09 | 233 | 22 | 1 | 15 | 3 |
| Week of | Kind | Requests | Platform errors | 504s | App errors | Hours measured |
|---|---|---|---|---|---|---|
| 2026-09-21 | ssr | 0 | 0 | 0 | 0 | 36 |
| 2026-09-28 | ssr | 0 | 0 | 0 | 0 | 168 |
| 2026-10-05 | ssr | 388 | 1 | 0 | 5 | 168 |
| 2026-10-12 | ssr | 3696 | 1 | 0 | 0 | 168 |
| 2026-10-19 | ssr | 6373 | 2 | 0 | 0 | 168 |
| 2026-10-26 | ssr | 7410 | 1 | 0 | 0 | 168 |
| 2026-11-02 | ssr | 12571 | 34 | 0 | 2 | 168 |
| 2026-11-09 | ssr | 1555 | 0 | 0 | 0 | 35 |
| 2026-09-21 | http | 79 | 0 | 4 | 0 | 36 |
| 2026-09-28 | http | 86 | 2 | 4 | 1 | 168 |
| 2026-10-05 | http | 812 | 5 | 2 | 71 | 168 |
| 2026-10-12 | http | 18 | 3 | 0 | 0 | 168 |
| 2026-10-19 | http | 169 | 0 | 0 | 0 | 168 |
| 2026-10-26 | http | 3 | 0 | 0 | 0 | 168 |
| 2026-11-02 | http | 129 | 0 | 0 | 0 | 168 |
| 2026-11-09 | http | 94 | 0 | 0 | 0 | 35 |
| Week of | Came up | Failed, ours | Failed, site build | Failed, conflict | Unclassified |
|---|---|---|---|---|---|
| 2026-10-05 | 15 | 0 | 0 | 0 | 0 |
| 2026-10-12 | 22 | 0 | 0 | 0 | 0 |
| 2026-10-19 | 111 | 11 | 0 | 0 | 0 |
| 2026-10-26 | 22 | 2 | 0 | 0 | 0 |
| 2026-11-02 | 136 | 1 | 0 | 0 | 0 |
| 2026-11-09 | 14 | 0 | 0 | 0 | 0 |
| Month | Bandwidth (GB) | Build minutes |
|---|---|---|
| 2025-09-01 | 0.00 | 0 |
| 2025-10-01 | 0.03 | 0 |
| 2025-11-01 | 0.06 | 0 |
| 2025-12-01 | 0.00 | 0 |
| 2026-01-01 | 0.00 | 0 |
| 2026-02-01 | 0.00 | 21 |
| 2026-03-01 | 2.33 | 73 |
| 2026-04-01 | 0.00 | 6 |
| 2026-05-01 | 0.01 | 124 |
| 2026-06-01 | 0.77 | 109 |
| 2026-07-01 | 11.70 | 93 |
| 2026-08-01 | 20.75 | 919 |
| 2026-09-01 | 31.03 | 2114 |
| 2026-10-01 | 124.20 | 3548 |
| 2026-11-01 | 32.87 | 763 |
Check our math.
Anyone can call this endpoint, with no key and no account, and it returns every number on this page, including the weekly and monthly series.
curl https://api.deploybase.eu/api/v1/public/stats
{
"deployments_total": 7077,
"builds_total": 7077,
"build_success_rate": 0.8866,
"functions": {
"ssr": {
"requests": 31761,
"platform_errors": 38
}
},
"generated_at": "2026-11-10T12:25:12.818781333Z"
}A few fields of the real reply, from the same snapshot this page is built on.
What we will publish next.
- Build times per framework Once enough builds have recorded a framework for the figure to mean anything, and never for a framework so few teams use that it could point at one of them.
- Availability history for sites and the API The status page shows whether they are up right now. A record of how often they were, over the last 30 days, belongs here.
No dates on any of these. They are what we are working towards, not a commitment, and this list is here so you can hold us to the direction.
Who runs this.
I put this page up because I think the internet gets better when companies show their work. Transparency builds trust and helps customers understand the product better. Most companies do not share anything, and when they do share, it is for their stakeholders, not the actual people who use the product.
The numbers here come from the same place I look every day: the database that serves the product. You will see exactly what I see, and hopefully, together, we can build a more transparent internet.
deploybase is self-funded: I pay for it myself. Your sites are your own files, built from your own repository or folder, so you can always take them somewhere else.
Antoine, founder