User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Money
Is Namely down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → namely.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
Our checks
Reaching it
Last checked 55 min ago. Last stored result reached it in 287 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 17 | 0 | 0.0 | 371 ms | 0 |
| Mon 19 | 0 | 0.0 | 351 ms | 0 |
| Mon 21 | 0 | 0.0 | 328 ms | 0 |
| Mon 23 | 0 | 0.0 | 337 ms | 0 |
| Tue 01 | 0 | 0.0 | 353 ms | 0 |
| Tue 03 | 0 | 0.0 | 290 ms | 0 |
| Tue 05 | 0 | 0.0 | 378 ms | 0 |
| Tue 08 | 0 | 0.0 | 266 ms | 0 |
| Tue 10 | 0 | 0.0 | 259 ms | 0 |
| Tue 12 | 0 | 0.0 | 287 ms | 0 |
| Tue 14 | 0 | 0.0 | 263 ms | 0 |
| Tue 16 | 0 | 0.0 | 303 ms | 0 |
| Tue 19 | 0 | 0.0 | 373 ms | 0 |
| Tue 21 | 0 | 0.0 | 277 ms | 0 |
| Tue 23 | 0 | 0.0 | 323 ms | 0 |
| Wed 01 | 0 | 0.0 | 299 ms | 0 |
| Wed 03 | 0 | 0.0 | 255 ms | 0 |
| Wed 04 | 0 | 0.0 | 362 ms | 0 |
| Wed 06 | 0 | 0.0 | 334 ms | 0 |
| Wed 09 | 0 | 0.0 | 329 ms | 0 |
| Wed 11 | 0 | 0.0 | 335 ms | 0 |
| Wed 13 | 0 | 0.0 | 303 ms | 0 |
| Wed 15 | 0 | 0.0 | 358 ms | 0 |
| Wed 17 | 0 | 0.0 | 314 ms | 0 |
| Wed 19 | 0 | 0.0 | 297 ms | 0 |
| Wed 22 | 0 | 0.0 | 208 ms | 0 |
| Thu 00 | 0 | 0.0 | 149 ms | 0 |
| Thu 02 | 0 | 0.0 | 375 ms | 0 |
| Thu 04 | 0 | 0.0 | 404 ms | 0 |
| Thu 06 | 0 | 0.0 | 367 ms | 0 |
| Thu 08 | 0 | 0.0 | 361 ms | 0 |
| Thu 10 | 0 | 0.0 | 363 ms | 0 |
| Thu 12 | 0 | 0.0 | 252 ms | 0 |
| Thu 14 | 0 | 0.0 | 289 ms | 0 |
| Thu 16 | 0 | 0.0 | 262 ms | 0 |
| Thu 18 | 0 | 0.0 | 311 ms | 0 |
| Thu 21 | 0 | 0.0 | 361 ms | 0 |
| Thu 23 | 0 | 0.0 | 212 ms | 0 |
| Fri 01 | 0 | 0.0 | 328 ms | 0 |
| Fri 03 | 0 | 0.0 | 314 ms | 0 |
| Fri 05 | 0 | 0.0 | 314 ms | 0 |
| Fri 07 | 0 | 0.0 | 257 ms | 0 |
| Fri 09 | 0 | 0.0 | 341 ms | 0 |
| Fri 11 | 0 | 0.0 | 220 ms | 0 |
| Fri 13 | 0 | 0.0 | 392 ms | 0 |
| Fri 15 | 0 | 0.0 | 315 ms | 0 |
| Fri 17 | 0 | 0.0 | 283 ms | 0 |
| Fri 19 | 0 | 0.0 | 287 ms | 0 |
Reliability
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 7 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Namely badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Namely yet. Outages of 10 minutes or more get their own page here.
Having trouble with Namely?
One report per service every 10 minutes from this network. No account.
Follow Namely
Get an email when Namely goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Namely alerts to Slack, Discord or a webhook — free.
About Namely
Namely is listed in our Money category and checked at namely.com. Manage your people more efficiently and accurately with Namely’s Human Capital Management (HCM) platform and managed services. Power-up payroll, compliance, benefits, and analytics with an all-in-one HCM solution.
Namely publishes an official status page at status.namely.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with money services: login and two-factor problems, payments or transfers failing, and app errors.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 304 ms average, 212–436 ms range across 16 successful checks.
Questions
Is Namely down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Namely last down?
We have not recorded a public Namely incident since monitoring began 7 days ago.
What is Namely's uptime?
From our own checks: 100% over 7 days of checks.
How fast does Namely respond?
304 ms on average over the last 24 hours (212–436 ms).
Does Namely have an official status page?
Yes, at https://status.namely.com.
Namely not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For money services, watch for login and two-factor problems, payments or transfers failing, and app errors. If many people report Namely here at once, the problem is on Namely's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Namely. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.