User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
sapiensia.com · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
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.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 3240 ms · 9 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:15 | 0 | 0.0 | 1836 ms | 0 |
| 03:30 | 0 | 0.0 | 2268 ms | 0 |
| 03:45 | 0 | 0.0 | 2035 ms | 0 |
| 04:00 | 0 | 0.0 | 1868 ms | 0 |
| 04:15 | 0 | 0.0 | 2675 ms | 0 |
| 04:30 | 0 | 0.0 | 3822 ms | 0 |
| 04:45 | 0 | 0.0 | 1781 ms | 0 |
| 05:00 | 0 | 0.0 | 1799 ms | 0 |
| 05:15 | 0 | 0.0 | 2685 ms | 0 |
| 05:30 | 0 | 0.0 | 1907 ms | 0 |
| 05:45 | 0 | 0.0 | 2818 ms | 0 |
| 06:00 | 0 | 0.0 | 1932 ms | 0 |
| 06:15 | 0 | 0.0 | 1932 ms | 0 |
| 06:30 | 0 | 0.0 | 2636 ms | 0 |
| 06:45 | 0 | 0.0 | 2192 ms | 0 |
| 07:00 | 0 | 0.0 | 1688 ms | 0 |
| 07:15 | 0 | 0.0 | 2486 ms | 0 |
| 07:30 | 0 | 0.0 | 2212 ms | 0 |
| 07:45 | 0 | 0.0 | 1931 ms | 0 |
| 08:00 | 0 | 0.0 | 2109 ms | 0 |
| 08:15 | 0 | 0.0 | 1802 ms | 0 |
| 08:30 | 0 | 0.0 | 2689 ms | 0 |
| 08:45 | 0 | 0.0 | 2457 ms | 0 |
| 09:00 | 0 | 0.0 | 1614 ms | 0 |
| 09:15 | 0 | 0.0 | 2501 ms | 0 |
| 09:30 | 0 | 0.0 | 1830 ms | 0 |
| 09:45 | 0 | 0.0 | 1939 ms | 0 |
| 10:00 | 0 | 0.0 | 2018 ms | 0 |
| 10:15 | 0 | 0.0 | 2277 ms | 0 |
| 10:30 | 0 | 0.0 | 2529 ms | 0 |
| 10:45 | 0 | 0.0 | 1962 ms | 0 |
| 11:00 | 0 | 0.0 | 2196 ms | 0 |
| 11:15 | 0 | 0.0 | 1983 ms | 0 |
| 11:30 | 0 | 0.0 | 2191 ms | 0 |
| 11:45 | 0 | 0.0 | 1908 ms | 0 |
| 12:00 | 0 | 0.0 | 1741 ms | 0 |
| 12:15 | 0 | 0.0 | 2007 ms | 0 |
| 12:30 | 0 | 0.0 | 2645 ms | 0 |
| 12:45 | 0 | 0.0 | 2029 ms | 0 |
| 13:00 | 0 | 0.0 | 1837 ms | 0 |
| 13:15 | 0 | 0.0 | 1890 ms | 0 |
| 13:30 | 0 | 0.0 | 3054 ms | 0 |
| 13:45 | 0 | 0.0 | 2639 ms | 0 |
| 14:00 | 0 | 0.0 | 3240 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Sapiens yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Sapiens goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Sapiens alerts to Slack, Discord or a webhook — free.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
If Sapiens is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Sapiens's side.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.