Skip to main content
Lattice logo

Is Lattice Down?

No — Lattice is up

Reachable from all 8 checked regions

Average response time: 136ms

Last checked · checks run every 6 hours

Official status page: https://status.lattice.com

Lattice uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
156ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 17 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

17-day clean streak
Sep 12: no data
Sep 13: no data
Sep 14: no data
Sep 15: no data
Sep 16: no data
Sep 17: no data
Sep 18: no data
Sep 19: no data
Sep 20: no data
Sep 21: no data
Sep 22: no data
Sep 23: no data
Sep 24: no data
Sep 25: 100.00% uptime, 16 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 31 checks
Sep 30: 100.00% uptime, 32 checks
Oct 1: 100.00% uptime, 32 checks
Oct 2: 100.00% uptime, 31 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Sep 12 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

iad
108ms
DNS 56ms TCP 1ms TLS 11ms TTFB 102ms
jnb
228ms
DNS 183ms TCP 1ms TLS 12ms TTFB 224ms
lax
145ms
DNS 97ms TCP 1ms TLS 14ms TTFB 139ms
lhr
91ms
DNS 25ms TCP 2ms TLS 12ms TTFB 82ms
nrt
153ms
DNS 113ms TCP 2ms TLS 11ms TTFB 146ms
ord
93ms
DNS 46ms TCP 1ms TLS 12ms TTFB 87ms
sin
137ms
DNS 91ms TCP 1ms TLS 13ms TTFB 132ms
sjc
134ms
DNS 76ms TCP 3ms TLS 14ms TTFB 122ms

What Lattice does

Lattice is an HR and people management platform. Companies use it for performance reviews, goals and OKRs, engagement surveys, 1:1s, feedback, career growth and compensation cycles, with notifications sent by email, Slack and Microsoft Teams. It connects to HRIS systems for employee data. Employees sign in at their company's own address, in the form account-name.latticehq.com, and there are iOS and Android apps.

What an outage looks like

Pages show a Something Went Wrong error, or the login page and other screens load very slowly or time out. Recent incidents broke single pages, such as the compensation cycle recommendations table or Goals, while the rest of the app worked. Others stopped email and Slack notifications, stalled automated review cycles so they did not advance or send reminders, or failed API requests that create and update data.

What to do about it

Check the Lattice Application row on status.lattice.com; the Lattice Homepage row covers only the homepage. Before refreshing a review, look for the Autosaved now notice in the upper right, since Lattice autosaves drafts while the cycle is open. In recent incidents Lattice re-sent delayed notifications and replayed missed review-cycle changes after the fix, so you should not need to resend reminders by hand.

Is it down for everyone, or just you?

If this page says Lattice is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

BambooHR
BambooHR
Rippling
Rippling
Slack
Slack
Cloudflare
Cloudflare

Lattice outage FAQ

Is it a Lattice outage or just my login?
Check the error first. Lattice's help center says a login error about an unexpected token and invalid JSON follows too many failed sign-in attempts; wait 5 to 10 minutes, fully quit and restart the browser, and clear its cache. Also confirm you are using your company's address, account-name.latticehq.com/login. If none of that works, check status.lattice.com for a login incident.
Will I lose a review I was writing during an outage?
No, as long as the cycle is still open. Lattice's help center says reviews autosave as they are written, so drafted responses are kept while the review cycle and direction remain open. Look for the Autosaved now notice in the upper right of the review page before refreshing or leaving. Engagement survey answers are autosaved too, so a partly finished survey keeps its responses.
Will Lattice resend notifications that failed during an outage?
In recent incidents, yes. When an upstream email provider failed in February 2026, Lattice delivered every delayed notification afterwards, some up to a day late. When automated review cycles stalled for several days in August 2026, it moved each cycle to its intended status and sent the missed reminders. After a 30-minute email and Slack failure that month, it warned messages from the window may arrive late.
Does a Cloudflare outage affect Lattice?
Yes. Lattice names Cloudflare as an upstream provider in its incident history. A Cloudflare issue in December 2025 caused an outage of the Lattice platform, and another in July 2026 slowed the site and caused connection timeout errors for some users. If Lattice and other sites fail at the same time, check Cloudflare's status as well.
Is lattice.com being down the same as Lattice being down?
No. This page checks lattice.com, the company homepage, which the status page tracks as its own Lattice Homepage row. Your workspace runs at your company's latticehq.com address and is tracked as Lattice Application. The homepage can load while the application is failing, and the reverse, so use the Lattice Application row to judge the product itself.

How we measure this

  • We request Lattice's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Lattice publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Lattice goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required