Status and uptime,
published as targets
Our targets for availability, latency and head lag are measured by independent probes from three regions. Every month we reconcile them with our internal metrics and publish the result, including the months we miss.
View status page
What do we publish?
We publish targets for availability, latency and chain head lag, and we report against them on a public status page. We are a new company with no operating history yet, so this page states targets only. Live history will appear on status.thetessellatelabs.com once the launch chains go live in Q1 2027.
published as targets
Measured at our edge, per region, per month, on shared tiers
Availability
Target of 99.9% on shared tiers, about 43.2 minutes of downtime a month
Latency
p95 under 60 ms for cached reads and under 250 ms for eth_call in the nearest region
Head lag
Within two blocks of canonical for 99.9% of minutes
How we measure
independent probes
Independent probes
Probes run from three regions every minute
Down means down
A minute counts as down if two of three probes fail
Monthly reconciliation
Probe results are reconciled monthly with internal metrics
Incident reviews
Reviews are published in full, with root cause and fixes
Live history
Appears on status.thetessellatelabs.com from Q1 2027
three regions
Chain-level halts
Excluded; we detect within five minutes and notify within fifteen
Scheduled maintenance
Excluded up to four hours a month, with five business days’ notice
Enterprise commitments
99.9% from Q2 2027, 99.95% from Q3 2027, 99.99% from Q4 2027
Reading the numbers
Targets are not guarantees. Contracted commitments carry credits.
Targets versus commitments
Targets apply to shared tiers; contracts add credits for misses
What counts as downtime?
01
Failed probes
A minute is down if at least two of the three independent probes fail. A single failing region does not count on its own, and we do not discount minutes in which clients failed to connect for reasons on their side.
02
What is excluded
Chain-level halts and scheduled maintenance of up to four hours a month, announced five business days ahead, are excluded from availability. We still report them on the status page, and the incident reviews are published in full.
03
No history yet
We have not run production traffic at scale, so we state no historical uptime figure. When the launch chains go live in Q1 2027, the record will appear on the status page, including any month in which we miss a target.
01
Failed probes
Our targets for availability, latency and head lag are measured by independent probes from three regions every minute and reconciled monthly with internal metrics.
02
What is excluded
A minute counts as down if two of three probes fail. Chain-level halts and scheduled maintenance are excluded, and we report both separately incident reviews. Reviews of every significant incident are published in full.
03
No history yet
We state no historical uptime figure yet. Live history will appear on status.thetessellatelabs.com once the launch chains go live in Q1 2027, including the months we miss.
Want our targets in a contract?
Fill out the form and we will reach out to help you get started.
Tessellate respects your privacy. By submitting this form, you are acknowledging that you have read and agree to our Privacy Policy, which details how we collect and use your information.