User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
iconstruye.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 28 min ago. Last stored result reached it in 131 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 23 | 0 | 0.0 | 170 ms | 0 |
| Tue 01 | 0 | 0.0 | 97 ms | 0 |
| Tue 03 | 0 | 0.0 | 143 ms | 0 |
| Tue 05 | 0 | 0.0 | 108 ms | 0 |
| Tue 07 | 0 | 0.0 | 149 ms | 0 |
| Tue 09 | 0 | 0.0 | 234 ms | 0 |
| Tue 12 | 0 | 0.0 | 184 ms | 0 |
| Tue 14 | 0 | 0.0 | 58 ms | 0 |
| Tue 16 | 0 | 0.0 | 114 ms | 0 |
| Tue 18 | 0 | 0.0 | 103 ms | 0 |
| Tue 20 | 0 | 0.0 | 135 ms | 0 |
| Tue 23 | 0 | 0.0 | 203 ms | 0 |
| Wed 01 | 0 | 0.0 | 196 ms | 0 |
| Wed 03 | 0 | 0.0 | 125 ms | 0 |
| Wed 05 | 0 | 0.0 | 299 ms | 0 |
| Wed 08 | 0 | 0.0 | 279 ms | 0 |
| Wed 10 | 0 | 0.0 | 167 ms | 0 |
| Wed 12 | 0 | 0.0 | 86 ms | 0 |
| Wed 14 | 0 | 0.0 | 121 ms | 0 |
| Wed 16 | 0 | 0.0 | 187 ms | 0 |
| Wed 18 | 0 | 0.0 | 234 ms | 0 |
| Wed 21 | 0 | 0.0 | 218 ms | 0 |
| Wed 23 | 0 | 0.0 | 217 ms | 0 |
| Thu 01 | 0 | 0.0 | 329 ms | 0 |
| Thu 03 | 0 | 0.0 | 80 ms | 0 |
| Thu 05 | 0 | 0.0 | 156 ms | 0 |
| Thu 07 | 0 | 0.0 | 142 ms | 0 |
| Thu 09 | 0 | 0.0 | 143 ms | 0 |
| Thu 11 | 0 | 0.0 | 189 ms | 0 |
| Thu 13 | 0 | 0.0 | 180 ms | 0 |
| Thu 15 | 0 | 0.0 | 172 ms | 0 |
| Thu 18 | 0 | 0.0 | 154 ms | 0 |
| Thu 20 | 0 | 0.0 | 63 ms | 0 |
| Thu 22 | 0 | 0.0 | 154 ms | 0 |
| Fri 00 | 0 | 0.0 | 44 ms | 0 |
| Fri 02 | 0 | 0.0 | 63 ms | 0 |
| Fri 04 | 0 | 0.0 | 187 ms | 0 |
| Fri 06 | 0 | 0.0 | 200 ms | 0 |
| Fri 08 | 0 | 0.0 | 123 ms | 0 |
| Fri 09 | 0 | 0.0 | 47 ms | 0 |
| Fri 11 | 0 | 0.0 | 113 ms | 0 |
| Fri 13 | 0 | 0.0 | 114 ms | 0 |
| Fri 15 | 0 | 0.0 | 161 ms | 0 |
| Fri 17 | 0 | 0.0 | 282 ms | 0 |
| Fri 18 | 0 | 0.0 | 270 ms | 0 |
| Fri 20 | 0 | 0.0 | 159 ms | 0 |
| Fri 22 | 0 | 0.0 | 174 ms | 0 |
| Sat 00 | 0 | 0.0 | 131 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 iConstruye 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 iConstruye goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send iConstruye alerts to Slack, Discord or a webhook — free.
We track iConstruye (iconstruye.com) as part of the Cloud & developer group. Conéctate con la comunidad de la construcción más grande de Chile, optimiza tus procesos y potencia tu negocio con ICONSTRUYE. Solicita una demo ahora.
iConstruye publishes an official status page at status.iconstruye.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: 156 ms average, 11–355 ms range across 19 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public iConstruye incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
156 ms on average over the last 24 hours (11–355 ms).
Yes, at https://status.iconstruye.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 iConstruye here at once, the problem is on iConstruye'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 iConstruye. 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.