- Service Status
- /
- Lattice

Is Lattice Down?
- Lattice's status page
- Operational · no open incidents
- FlareWarden checks
- Website reachable · 8 of 8 regions · 120 ms
Right now
The verdict is the worse of these two. How we decide
Lattice's status page
status.lattice.com · read · checked every 3 minutes
| Component | Status |
|---|---|
| Lattice Application | Operational |
| Lattice Homepage | Operational |
FlareWarden checks
lattice.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 8 of 8
- Response
- 120 ms
- Checked
By region
- Amsterdam reachable, 135 ms
- Ashburn reachable, 146 ms
- Dallas reachable, 82 ms
- Frankfurt reachable, 104 ms
- Newark reachable, 92 ms
- Paris reachable, 108 ms
- Stockholm reachable, 121 ms
- São Paulo reachable, 172 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Amsterdam | 53 ms | 2 ms | 26 ms | 126 ms |
| Ashburn | 14 ms | 1 ms | 13 ms | 122 ms |
| Dallas | 14 ms | 3 ms | 15 ms | 72 ms |
| Frankfurt | 21 ms | 2 ms | 14 ms | 96 ms |
| Newark | 43 ms | 2 ms | 11 ms | 85 ms |
| Paris | 34 ms | 1 ms | 13 ms | 102 ms |
| Stockholm | 71 ms | 1 ms | 16 ms | 116 ms |
| São Paulo | 118 ms | 2 ms | 11 ms | 164 ms |
History
Incidents Lattice reported
Since Oct 22, 2 days · from status.lattice.com
- Incidents
- 0
- Major or critical
- 0
- Median to resolve
- —
No incidents reported in this window.
Lattice website availability
Measured by FlareWarden · lattice.com
- Last 7 days
- 100%
- Last 30 days
- 100%
- Last 90 days
- 100%
- Avg response, 30 days
- 148ms
Last 30 days
28-day clean streakMeasured by FlareWarden's own checks of lattice.com from multiple regions every 6 hours. Lattice's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 28 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
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.
Related services
Lattice outage FAQ
Is it a Lattice outage or just my login?
Will I lose a review I was writing during an outage?
Will Lattice resend notifications that failed during an outage?
Does a Cloudflare outage affect Lattice?
Is lattice.com being down the same as Lattice being down?
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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Lattice itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.
Get alerted when Lattice goes down
We check Lattice every 6 hours, and again when you open this page if that was more than 30 minutes ago. 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


