Is Namely down in the US?
Vendor reports no incidentWhat Namely reports
Namely reports no incident on its status page.
As of the last successful poll, 2026-11-05 16:31 UTC.
Our regional reading
This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.
Checks passingin the US, measured from Ashburn and San Jose
All 2 of our probes in the US, in Ashburn and San Jose, read checks passing when they last checked Namely at Nov 5, 2026, 4:42 PM UTC.
Over the last 24 hours we completed 248 checks from Ashburn and San Jose and 248 answered cleanly, 100.00% availability.
Of the 2 other regions we check Namely from, all 2 read checks passing right now.
Email me when Namely reports an incident on its status page, and again when it reports it resolved.
What our Ashburn and San Jose probes measured
Last checked Nov 5, 2026, 4:42 PM UTC.
Namely from Ashburn and San Jose over the last 30 days
Over the last 30 days, Namely answered our Ashburn probe in 1,686 ms on average, and 1 check in 20 took longer than 2,927 ms.
Over the last 30 days, Namely answered our San Jose probe in 2,250 ms on average, and 1 check in 20 took longer than 3,440 ms.
Ranked by average response time across the 4 cities we check Namely from, Ashburn 1st, San Jose 2nd; Ashburn was fastest at 1,686 ms and Tokyo slowest at 3,825 ms.
From Ashburn and San Jose we ran 761 checks of Namely in 4 days, and 743 answered cleanly: 97.63% availability.
2 of the 4 days had at least one failed check. The weakest was Nov 4 (UTC), at 93.97% across 249 checks.
In Ashburn local time (EST), Namely was slowest around 2 AM, at 2,487 ms on average over the last 14 days, and quickest around 12 AM, at 1,128 ms.
| Day (UTC) | Checks | Availability | Average response |
|---|---|---|---|
| Thu, Nov 5 | 166 | 100.00% | 2,039 ms |
| Wed, Nov 4 | 249 | 93.97% | 1,820 ms |
| Tue, Nov 3 | 244 | 98.77% | 1,812 ms |
| Mon, Nov 2 | 102 | 100.00% | 2,290 ms |
Namely outages measured from the US
Our Ashburn and San Jose probes measured no confirmed Namely outage in the last 90 days.
How the other regions read right now
Of the 2 other regions we check Namely from, all 2 read checks passing right now.
| Probe city | Right now | Last 24h |
|---|---|---|
| Frankfurt | Checks passing | 100.00% of 97 checks |
| Tokyo | Checks passing | 100.00% of 58 checks |
Other countries we check Namely from
How we measured this
The US readings on this page come from RealUptime's own Ashburn and San Jose probes against Namely's public endpoints. They are not user reports, and they are not Namely's own status page.
See Namely's full check readings, the 90-day history by region, or the outage tracker methodology.
The US readings here are taken from that country and show the time of the last one, but Namely has not yet accumulated enough continuous history for us to publish this page to search engines.
Check your own site from Ashburn
This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.
Start monitoring your own serversRun a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter