UptimusJuicefs statusUptimusJuicefs status
No — Juicefs is operational.
Last checked Sep 6, 01:24 AM UTC
Operational
Current status
100.00%
Known uptime
70
Monitored components
The service was operational. The official source currently reports no active incidents or maintenance windows.
0 outage reports in the last 24 hours.
No community outage reports have been submitted for this service in the last 24 hours.
0Share your thoughts about Juicefs
Be the first to comment!
Official component health and availability history.
70 tracked components
90 days ago → Today
Geographic clusters from community-submitted reports.
Official updates and resolved service disruptions.
May 13, 2019 02:15 +08 Investigating - Recieved alarm on disrupted service in for Asia regions (Singapore). May 13, 2019 02:26 +08 Resolved - Restarted those instanses and add more memory, the service was fully recovered.
Started May 12, 2019, 06:26 PM UTC · Resolved May 12, 2019, 06:26 PM UTC
May 15, 2018 21:08 +08 Investigating - Two of the three meta service for UCloud North failed, which caused service outage. May 15, 2018 21:38 +08 Resolved - - Apply for new available zone E and distribute meta services in zone B, D, E to reduce the outage chance. - Lower the alarm threshold to detect failure sooner
Started May 15, 2018, 01:38 PM UTC · Resolved May 15, 2018, 01:38 PM UTC
February 18, 2018 12:08 +08 Investigating - Two of the three meta services failed to accept new connections. No syslog for past 20 hours. February 18, 2018 12:55 +08 Resolved - - Reboot node to recover - Rollback recent changes in syslog configuration
Uptimus monitors Juicefs through its official status source and normalizes published incidents, maintenance windows and component health into one consistent service status.
This page currently includes 70 monitored components, 7 indexed incidents, 0 maintenance windows and 1 days of known history.
Uptimus is an independent monitoring service and is not affiliated with Juicefs. A healthy status does not guarantee that every user, device or region is unaffected.
Get notified when Juicefs or one of its monitored components reports a major outage or another critical service disruption. Alerts can be routed through the notification channels enabled for your workspace, including email, push and configured integrations. The available history contains 7 indexed incidents, giving each alert context beyond the current status. A recent indexed incident was “Outrage in Asia Regions”.
Get notified about degraded performance, partial impact and smaller incidents that do not represent a complete outage. Uptimus currently tracks 70 Juicefs components: JuiceFS Regions - AWS (Asia Pacific - Hongkong), JuiceFS Regions - AWS (Asia Pacific - Mumbai), JuiceFS Regions - AWS (Asia Pacific - Seoul), JuiceFS Regions - AWS (Asia Pacific - Singapore). Alerts can be routed through the notification channels enabled for your workspace, including email, push and configured integrations.
Downdetector public pages are led by user reports. Uptimus combines community activity with official provider incidents, maintenance windows and component health when the source publishes them.
| Comparison criteria | Uptimus | Downdetector |
|---|---|---|
| Community outage reports for Juicefs |
Started Feb 18, 2018, 04:55 AM UTC · Resolved Feb 18, 2018, 04:55 AM UTC
January 22, 2018 20:42 +08 Investigating - Out of memory when rotating changelog to disk. It causes slow response in election and finally losing leader. January 22, 2018 20:54 +08 Resolved - - Increase memory - Adjust alarm threshold for memory
Started Jan 22, 2018, 12:54 PM UTC · Resolved Jan 22, 2018, 12:54 PM UTC
November 17, 2017 04:16 +08 Investigating - 12:18 Received alarm about disruption of JuiceFS metadata service in UCloud beijing region. Investigation started. 12:20 Saw that two follower nodes can't replay change log from leader, kept restarting. 12:23 Restarted the previous leader. 12:26 Service is fully recovered, back to normal. 13:30 Find the bug that cause the failure of applying. 20:30 Deployed the bugfix. November 17, 2017 04:26 +08 Resolved - This is caused by a bug introduced in 4.2.2, which have a slightly different logic to apply change log, that introduce different internal result and fail the checksum. The bug was fixed and deployed.
Started Nov 16, 2017, 08:26 PM UTC · Resolved Nov 16, 2017, 08:26 PM UTC
July 3, 2017 14:30 +08 Scheduled - Deploy a new release with huge performance improvements. July 3, 2017 14:30 +08 Active - 6:30 Deployed to Aliyun HK region, 6:40 Start to deploy to all regions. July 3, 2017 14:50 +08 Completed - 6:50 Deployed to all regions successfully.
Started Jul 3, 2017, 06:50 AM UTC · Resolved Jul 3, 2017, 06:50 AM UTC
May 16, 2017 14:12 +08 Investigating - 6:14 Got a report that JuiceFS in AWS Beijing region is slow, timeout to connect to metadata service. 6:16 Start investigating. We realized that a node from UCloud Beijing region is elected as active to serve requests from AWS Beijing. The egress of AWS Beijing region is slow and dropping packets. 6:30 The egress of AWS Beijing is back to normal. May 16, 2017 14:30 +08 Resolved - 13:34 All the node for AWS Beijing are moved to AWS Beijing to make sure that slowness of egress will not degrade the performance of JuiceFS. We also double check all other regions to make sure that the metadata service is access within the same region for better performance.
Started May 16, 2017, 06:30 AM UTC · Resolved May 16, 2017, 06:30 AM UTC
| Included |
| Adaptive baseline that separates isolated reports from wider disruption | Included | Included |
|---|
| 24-hour report activity and regional outage view | Included | Included |
|---|
| One workspace for websites, provider status pages, Steam games and Android apps and games | Included | Separate product |
|---|
| Email, push and webhook alerts from the same workspace | Included | Separate product |
|---|
| Official incident updates and status timeline for Juicefs | Included | User-report led |
|---|
| Component health and maintenance windows kept separate | Included | Limited on public pages |
|---|
Rate this service
No reviews yet
Discover other popular services and their current status
