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 2 hr ago. Last stored result reached it in 513 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 01 | 0 | 0.0 | 514 ms | 0 |
| Tue 04 | 0 | 0.0 | 514 ms | 0 |
| Tue 06 | 0 | 0.0 | 578 ms | 0 |
| Tue 08 | 0 | 0.0 | 540 ms | 0 |
| Tue 10 | 0 | 0.0 | 473 ms | 0 |
| Tue 12 | 0 | 0.0 | 470 ms | 0 |
| Tue 14 | 0 | 0.0 | 1199 ms | 0 |
| Tue 16 | 0 | 0.0 | 496 ms | 0 |
| Tue 19 | 0 | 0.0 | 580 ms | 0 |
| Tue 21 | 0 | 0.0 | 541 ms | 0 |
| Tue 23 | 0 | 0.0 | 472 ms | 0 |
| Wed 01 | 0 | 0.0 | 570 ms | 0 |
| Wed 04 | 0 | 0.0 | 596 ms | 0 |
| Wed 06 | 0 | 0.0 | 517 ms | 0 |
| Wed 08 | 0 | 0.0 | 1142 ms | 0 |
| Wed 10 | 0 | 0.0 | 576 ms | 0 |
| Wed 13 | 0 | 0.0 | 514 ms | 0 |
| Wed 15 | 0 | 0.0 | 509 ms | 0 |
| Wed 17 | 0 | 0.0 | 644 ms | 0 |
| Wed 19 | 0 | 0.0 | 499 ms | 0 |
| Wed 21 | 0 | 0.0 | 523 ms | 0 |
| Wed 23 | 0 | 0.0 | 1572 ms | 0 |
| Thu 02 | 0 | 0.0 | 512 ms | 0 |
| Thu 04 | 0 | 0.0 | 539 ms | 0 |
| Thu 06 | 0 | 0.0 | 452 ms | 0 |
| Thu 08 | 0 | 0.0 | 499 ms | 0 |
| Thu 10 | 0 | 0.0 | 494 ms | 0 |
| Thu 12 | 0 | 0.0 | 488 ms | 0 |
| Thu 14 | 0 | 0.0 | 1174 ms | 0 |
| Thu 16 | 0 | 0.0 | 643 ms | 0 |
| Thu 18 | 0 | 0.0 | 532 ms | 0 |
| Thu 20 | 0 | 0.0 | 1231 ms | 0 |
| Thu 22 | 0 | 0.0 | 589 ms | 0 |
| Fri 00 | 0 | 0.0 | 1663 ms | 0 |
| Fri 03 | 0 | 0.0 | 1338 ms | 0 |
| Fri 05 | 0 | 0.0 | 512 ms | 0 |
| Fri 07 | 0 | 0.0 | 478 ms | 0 |
| Fri 09 | 0 | 0.0 | 517 ms | 0 |
| Fri 11 | 0 | 0.0 | 518 ms | 0 |
| Fri 13 | 0 | 0.0 | 527 ms | 0 |
| Fri 15 | 0 | 0.0 | 499 ms | 0 |
| Fri 17 | 0 | 0.0 | 596 ms | 0 |
| Fri 19 | 0 | 0.0 | 574 ms | 0 |
| Fri 20 | 0 | 0.0 | 577 ms | 0 |
| Fri 22 | 0 | 0.0 | — | 0 |
| Sat 00 | 0 | 0.0 | 1005 ms | 0 |
| Sat 01 | 0 | 0.0 | 497 ms | 0 |
| Sat 03 | 0 | 0.0 | 513 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 ALUXE 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 ALUXE goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send ALUXE alerts to Slack, Discord or a webhook — free.
ALUXE is listed in our Cloud & developer category and checked at aluxe.com. ALUXE 亞立詩鑽石提供頂級求婚鑽石戒指、結婚對戒,鑽石項鍊、耳環、手鍊等高級珠寶。嚴選鑽石的品質,搭配多樣化的品牌設計風格,以最高規格的專屬訂製、打造平易近人的價格。
ALUXE publishes an official status page at status.aluxe.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong 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: 567 ms average, 470–1005 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 ALUXE incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
567 ms on average over the last 24 hours (470–1005 ms).
Yes, at https://status.aluxe.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 ALUXE here at once, the problem is on ALUXE'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 ALUXE. 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.