User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / 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 1 hr ago. Last stored result reached it in 369 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 417 ms | 0 |
| Mon 22 | 0 | 0.0 | 266 ms | 0 |
| Tue 01 | 0 | 0.0 | 539 ms | 0 |
| Tue 03 | 0 | 0.0 | 254 ms | 0 |
| Tue 05 | 0 | 0.0 | 219 ms | 0 |
| Tue 07 | 0 | 0.0 | 280 ms | 0 |
| Tue 09 | 0 | 0.0 | 269 ms | 0 |
| Tue 11 | 0 | 0.0 | 404 ms | 0 |
| Tue 13 | 0 | 0.0 | 401 ms | 0 |
| Tue 15 | 0 | 0.0 | 370 ms | 0 |
| Tue 17 | 0 | 0.0 | 389 ms | 0 |
| Tue 20 | 0 | 0.0 | 360 ms | 0 |
| Tue 22 | 0 | 0.0 | 397 ms | 0 |
| Wed 00 | 0 | 0.0 | 282 ms | 0 |
| Wed 02 | 0 | 0.0 | 283 ms | 0 |
| Wed 05 | 0 | 0.0 | 262 ms | 0 |
| Wed 07 | 0 | 0.0 | 333 ms | 0 |
| Wed 09 | 0 | 0.0 | 214 ms | 0 |
| Wed 11 | 0 | 0.0 | 278 ms | 0 |
| Wed 13 | 0 | 0.0 | 485 ms | 0 |
| Wed 15 | 0 | 0.0 | 422 ms | 0 |
| Wed 17 | 0 | 0.0 | 498 ms | 0 |
| Wed 20 | 0 | 0.0 | 291 ms | 0 |
| Wed 22 | 0 | 0.0 | 322 ms | 0 |
| Thu 00 | 0 | 0.0 | 354 ms | 0 |
| Thu 02 | 0 | 0.0 | 338 ms | 0 |
| Thu 04 | 0 | 0.0 | 400 ms | 0 |
| Thu 06 | 0 | 0.0 | 311 ms | 0 |
| Thu 08 | 0 | 0.0 | 312 ms | 0 |
| Thu 10 | 0 | 0.0 | 399 ms | 0 |
| Thu 12 | 0 | 0.0 | 390 ms | 0 |
| Thu 15 | 0 | 0.0 | 379 ms | 0 |
| Thu 17 | 0 | 0.0 | 270 ms | 0 |
| Thu 19 | 0 | 0.0 | 396 ms | 0 |
| Thu 21 | 0 | 0.0 | 347 ms | 0 |
| Thu 23 | 0 | 0.0 | 332 ms | 0 |
| Fri 01 | 0 | 0.0 | 430 ms | 0 |
| Fri 03 | 0 | 0.0 | 327 ms | 0 |
| Fri 05 | 0 | 0.0 | 331 ms | 0 |
| Fri 07 | 0 | 0.0 | 344 ms | 0 |
| Fri 09 | 0 | 0.0 | 362 ms | 0 |
| Fri 10 | 0 | 0.0 | 326 ms | 0 |
| Fri 12 | 0 | 0.0 | 340 ms | 0 |
| Fri 14 | 0 | 0.0 | 309 ms | 0 |
| Fri 16 | 0 | 0.0 | 195 ms | 0 |
| Fri 17 | 0 | 0.0 | 361 ms | 0 |
| Fri 19 | 0 | 0.0 | 291 ms | 0 |
| Fri 21 | 0 | 0.0 | 369 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Casar 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 Casar goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Casar alerts to Slack, Discord or a webhook — free.
Casar is listed in our Cloud & developer category and checked at casar.com. Crie seu site de casamento gratuito no Casar.com! O único com atendimento até as 21h e com tudo que você precisa: lista de presentes, RSVP e muito mais.
Casar publishes an official status page at status.casar.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 333 ms average, 195–430 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Casar incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
333 ms on average over the last 24 hours (195–430 ms).
Yes, at https://status.casar.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 Casar here at once, the problem is on Casar'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 Casar. 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.