User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
loggro.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 293 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 7 | 0 | 0.0 | 289 ms | 0 |
| Nov 7 | 0 | 0.0 | 276 ms | 0 |
| Nov 8 | 0 | 0.0 | 278 ms | 0 |
| Nov 8 | 0 | 0.0 | 284 ms | 0 |
| Nov 8 | 0 | 0.0 | 241 ms | 0 |
| Nov 8 | 0 | 0.0 | 256 ms | 0 |
| Nov 9 | 0 | 0.0 | 273 ms | 0 |
| Nov 9 | 0 | 0.0 | 242 ms | 0 |
| Nov 9 | 0 | 0.0 | 289 ms | 0 |
| Nov 9 | 0 | 0.0 | 259 ms | 0 |
| Nov 10 | 0 | 0.0 | 275 ms | 0 |
| Nov 10 | 0 | 0.0 | 314 ms | 0 |
| Nov 10 | 0 | 0.0 | 321 ms | 0 |
| Nov 10 | 0 | 0.0 | 257 ms | 0 |
| Nov 11 | 0 | 0.0 | 295 ms | 0 |
| Nov 11 | 0 | 0.0 | 300 ms | 0 |
| Nov 11 | 0 | 0.0 | 278 ms | 0 |
| Nov 11 | 0 | 0.0 | 317 ms | 0 |
| Nov 12 | 0 | 0.0 | 262 ms | 0 |
| Nov 12 | 0 | 0.0 | 284 ms | 0 |
| Nov 12 | 0 | 0.0 | 303 ms | 0 |
| Nov 12 | 0 | 0.0 | 280 ms | 0 |
| Nov 13 | 0 | 0.0 | 307 ms | 0 |
| Nov 13 | 0 | 0.0 | 253 ms | 0 |
| Nov 13 | 0 | 0.0 | 323 ms | 0 |
| Nov 13 | 0 | 0.0 | 293 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 Loggro 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 Loggro goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Loggro alerts to Slack, Discord or a webhook — free.
Loggro, at loggro.com, is one of the Cloud & developer services we monitor. Somos tu solucion empresarial con más de 30 años de experiencia en Software y ERP. ¡Descubre tecnología para negocios de todos los tamaños!
Loggro publishes an official status page at status.loggro.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: 285 ms average, 203–360 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Loggro incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
285 ms on average over the last 24 hours (203–360 ms).
Yes, at https://status.loggro.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 Loggro here at once, the problem is on Loggro'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 Loggro. 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.