Incidents reported on status page for NAVQ https://status.navq.dev/ en https://status.navq.dev/ Wed, 11 Feb 2026 05:07:18 +0000 https://status.navq.dev/#329c86e934025f81082b85b5705d79a9eaaafcb0bd8850afdc60e73c2c6c3fe5 NAVQ Website recovered https://status.navq.dev/ Wed, 11 Feb 2026 05:03:51 +0000 https://status.navq.dev/#329c86e934025f81082b85b5705d79a9eaaafcb0bd8850afdc60e73c2c6c3fe5 NAVQ Website went down https://status.navq.dev/ Tue, 03 Feb 2026 04:21:52 +0000 https://status.navq.dev/#6b00125510ea978cc199cb25f223e3801c04ae22057f316439190494f1f9eefe NAVQ Website recovered https://status.navq.dev/ Tue, 03 Feb 2026 04:18:51 +0000 https://status.navq.dev/#6b00125510ea978cc199cb25f223e3801c04ae22057f316439190494f1f9eefe NAVQ Website went down https://status.navq.dev/ Thu, 29 Jan 2026 12:19:01 +0000 https://status.navq.dev/#696805c71a62fd4343eb30bec41d5d92730c6f88c8776447e8be3e8076310297 NAVQ Website recovered https://status.navq.dev/ Thu, 29 Jan 2026 12:15:54 +0000 https://status.navq.dev/#696805c71a62fd4343eb30bec41d5d92730c6f88c8776447e8be3e8076310297 NAVQ Website went down https://status.navq.dev/ Thu, 29 Jan 2026 11:48:49 +0000 https://status.navq.dev/#a645063dcfe525a3ff669db17e101c2ea5a24476f1c0f2663f949fa9249bbf3c NAVQ Website recovered https://status.navq.dev/ Thu, 29 Jan 2026 11:42:59 +0000 https://status.navq.dev/#a645063dcfe525a3ff669db17e101c2ea5a24476f1c0f2663f949fa9249bbf3c NAVQ Website went down https://status.navq.dev/ Thu, 29 Jan 2026 11:24:57 +0000 https://status.navq.dev/#66c69f3d35f64fc65ef4dbb9702481163c08ef23f9d7371fc107acce3e4671b6 NAVQ Website recovered https://status.navq.dev/ Thu, 29 Jan 2026 11:21:46 +0000 https://status.navq.dev/#66c69f3d35f64fc65ef4dbb9702481163c08ef23f9d7371fc107acce3e4671b6 NAVQ Website went down https://status.navq.dev/ Thu, 29 Jan 2026 10:33:48 +0000 https://status.navq.dev/#8700de0c36818d1342a1441b701d071ca6bff23f7f0568385beb4ac2a5dc725e NAVQ Website recovered https://status.navq.dev/ Thu, 29 Jan 2026 10:27:55 +0000 https://status.navq.dev/#8700de0c36818d1342a1441b701d071ca6bff23f7f0568385beb4ac2a5dc725e NAVQ Website went down https://status.navq.dev/ Thu, 29 Jan 2026 10:15:55 +0000 https://status.navq.dev/#9d6a36e02c3218d323183b8aa1772747ef20447e1a42cfa37a493e70ac36e878 NAVQ Website recovered https://status.navq.dev/ Thu, 29 Jan 2026 09:51:53 +0000 https://status.navq.dev/#9d6a36e02c3218d323183b8aa1772747ef20447e1a42cfa37a493e70ac36e878 NAVQ Website went down https://status.navq.dev/ Thu, 08 Jan 2026 04:04:02 +0000 https://status.navq.dev/#7af433ee0a5340f76c9752f23cd6e2c7ca56a94a09cee94a6291816168324787 NAVQ Website recovered https://status.navq.dev/ Thu, 08 Jan 2026 04:00:52 +0000 https://status.navq.dev/#7af433ee0a5340f76c9752f23cd6e2c7ca56a94a09cee94a6291816168324787 NAVQ Website went down https://status.navq.dev/ Mon, 05 Jan 2026 11:04:00 +0000 https://status.navq.dev/#eb38f38da61a3401e5dbc5f8226320f8e4caf2278a461544ea2610faf08cb8a7 NAVQ Website recovered https://status.navq.dev/ Mon, 05 Jan 2026 11:01:55 +0000 https://status.navq.dev/#eb38f38da61a3401e5dbc5f8226320f8e4caf2278a461544ea2610faf08cb8a7 NAVQ Website went down