User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
palisis.com · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps 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. Every report with a known place can appear on the map. Updates every minute.
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.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 2 hr ago. Last stored result reached it in 799 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 00 | 0 | 0.0 | 817 ms | 0 |
| Tue 02 | 0 | 0.0 | 2967 ms | 0 |
| Tue 04 | 0 | 0.0 | 979 ms | 0 |
| Tue 06 | 0 | 0.0 | 549 ms | 0 |
| Tue 07 | 0 | 0.0 | 860 ms | 0 |
| Tue 09 | 0 | 0.0 | 874 ms | 0 |
| Tue 11 | 0 | 0.0 | 948 ms | 0 |
| Tue 13 | 0 | 0.0 | 853 ms | 0 |
| Tue 15 | 0 | 0.0 | 938 ms | 0 |
| Tue 17 | 0 | 0.0 | 956 ms | 0 |
| Tue 20 | 0 | 0.0 | 866 ms | 0 |
| Tue 22 | 0 | 0.0 | 1014 ms | 0 |
| Wed 00 | 0 | 0.0 | 870 ms | 0 |
| Wed 02 | 0 | 0.0 | 2064 ms | 0 |
| Wed 05 | 0 | 0.0 | 852 ms | 0 |
| Wed 07 | 0 | 0.0 | 1016 ms | 0 |
| Wed 09 | 0 | 0.0 | — | 0 |
| Wed 11 | 0 | 0.0 | 1217 ms | 0 |
| Wed 14 | 0 | 0.0 | 1031 ms | 0 |
| Wed 16 | 0 | 0.0 | 863 ms | 0 |
| Wed 18 | 0 | 0.0 | 2265 ms | 0 |
| Wed 20 | 0 | 0.0 | 959 ms | 0 |
| Wed 22 | 0 | 0.0 | 850 ms | 0 |
| Thu 00 | 0 | 0.0 | 1020 ms | 0 |
| Thu 02 | 0 | 0.0 | 908 ms | 0 |
| Thu 04 | 0 | 0.0 | 833 ms | 0 |
| Thu 07 | 0 | 0.0 | 906 ms | 0 |
| Thu 09 | 0 | 0.0 | 813 ms | 0 |
| Thu 11 | 0 | 0.0 | 963 ms | 0 |
| Thu 13 | 0 | 0.0 | 550 ms | 0 |
| Thu 15 | 0 | 0.0 | 890 ms | 0 |
| Thu 17 | 0 | 0.0 | 822 ms | 0 |
| Thu 19 | 0 | 0.0 | 903 ms | 0 |
| Thu 21 | 0 | 0.0 | 871 ms | 0 |
| Thu 23 | 0 | 0.0 | 1864 ms | 0 |
| Fri 01 | 0 | 0.0 | 1800 ms | 0 |
| Fri 03 | 0 | 0.0 | 832 ms | 0 |
| Fri 05 | 0 | 0.0 | 919 ms | 0 |
| Fri 07 | 0 | 0.0 | 991 ms | 0 |
| Fri 09 | 0 | 0.0 | 831 ms | 0 |
| Fri 10 | 0 | 0.0 | 772 ms | 0 |
| Fri 12 | 0 | 0.0 | 904 ms | 0 |
| Fri 14 | 0 | 0.0 | 795 ms | 0 |
| Fri 16 | 0 | 0.0 | 835 ms | 0 |
| Fri 18 | 0 | 0.0 | 901 ms | 0 |
| Fri 19 | 0 | 0.0 | 851 ms | 0 |
| Fri 21 | 0 | 0.0 | 1217 ms | 0 |
| Fri 23 | 0 | 0.0 | 799 ms | 0 |
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.
No outages on record for Palisis 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 Palisis goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Palisis alerts to Slack, Discord or a webhook — free.
Palisis, at palisis.com, is one of the Cloud & developer services we monitor. Unlock the full potential of your experience-based business with Palisis. Streamline your operations and boost revenue today. Explore now!
Palisis publishes an official status page at status.palisis.com; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
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: 908 ms average, 311–2123 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Palisis incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
908 ms on average over the last 24 hours (311–2123 ms).
Yes, at https://status.palisis.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Palisis here at once, the problem is on Palisis'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 Palisis. 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.