8 major incidents detected for Knowji. View live status dashboard →
On 2026-05-11 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Knowji. The incident has been resolved after approximately 22h 0m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-08 at 03:18 UTC, DownForAI monitoring detected a significant service issue affecting Knowji. The incident has been resolved after approximately 71h 42m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-05 at 03:12 UTC, DownForAI monitoring detected a significant service issue affecting Knowji. The incident has been resolved after approximately 71h 48m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-02 at 03:18 UTC, DownForAI monitoring detected a significant service issue affecting Knowji. The incident has been resolved after approximately 71h 41m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-04-29 at 03:12 UTC, DownForAI monitoring detected a significant service issue affecting Knowji. The incident has been resolved after approximately 71h 48m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-04-26 at 03:06 UTC, DownForAI monitoring detected a significant service issue affecting Knowji. The incident has been resolved after approximately 71h 54m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-04-23 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Knowji. The incident has been resolved after approximately 72h 0m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-04-20 at 05:06 UTC, DownForAI monitoring detected a significant service issue affecting Knowji. The incident has been resolved after approximately 69h 54m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.