Incidents | Nava Incidents reported on status page for Nava https://status.navalabs.dev/ en Chain recovered https://status.navalabs.dev/ Thu, 30 Jul 2026 09:05:19 +0000 https://status.navalabs.dev/#f561dd422bc57e4899b1f1ece7afd092e83a8d02f130a8916004e5082a4e12f6 Chain recovered Chain went down https://status.navalabs.dev/ Wed, 29 Jul 2026 17:05:21 +0000 https://status.navalabs.dev/#f561dd422bc57e4899b1f1ece7afd092e83a8d02f130a8916004e5082a4e12f6 Chain went down Explorer recovered https://status.navalabs.dev/ Sun, 05 Jul 2026 23:09:12 +0000 https://status.navalabs.dev/#d249e9426d7963d33f8e0ab16b0612fadc03e33370a7fb24df3ef7076d836888 Explorer recovered Nava API recovered https://status.navalabs.dev/ Sun, 05 Jul 2026 23:06:20 +0000 https://status.navalabs.dev/#b6fb70c0d80e3cd7d6e8269570a300880aa90be3113e6c86b08a62b46869d1a4 Nava API recovered Chain recovered https://status.navalabs.dev/ Sun, 05 Jul 2026 23:05:18 +0000 https://status.navalabs.dev/#465b8546a1b56c8f811f98a96c4182445eb1c7cb7f0f04dc02d42eb3f6e44ff0 Chain recovered Nava API went down https://status.navalabs.dev/ Sun, 05 Jul 2026 15:06:16 +0000 https://status.navalabs.dev/#b6fb70c0d80e3cd7d6e8269570a300880aa90be3113e6c86b08a62b46869d1a4 Nava API went down Chain went down https://status.navalabs.dev/ Sun, 05 Jul 2026 15:05:17 +0000 https://status.navalabs.dev/#465b8546a1b56c8f811f98a96c4182445eb1c7cb7f0f04dc02d42eb3f6e44ff0 Chain went down Explorer went down https://status.navalabs.dev/ Sun, 05 Jul 2026 15:04:06 +0000 https://status.navalabs.dev/#d249e9426d7963d33f8e0ab16b0612fadc03e33370a7fb24df3ef7076d836888 Explorer went down Explorer recovered https://status.navalabs.dev/ Mon, 01 Jun 2026 23:34:17 +0000 https://status.navalabs.dev/#60efa8dc8778cf5b57feef5de8e1a681a7121f0bf9bccf71dec76e8a270a6f7f Explorer recovered Arbiter recovered https://status.navalabs.dev/ Mon, 01 Jun 2026 23:15:52 +0000 https://status.navalabs.dev/#f85f131909bfae38ccb3f8e6457d640e672b7f66f1825b73e6f3f0bb53d3a7d8 Arbiter recovered Nava API recovered https://status.navalabs.dev/ Mon, 01 Jun 2026 23:01:10 +0000 https://status.navalabs.dev/#02b233d85d5f6ac95ba60b2ae97f2a1b733631851530ad43a0585fb9accc3b20 Nava API recovered Chain recovered https://status.navalabs.dev/ Mon, 01 Jun 2026 23:00:25 +0000 https://status.navalabs.dev/#8fb869dd4267f0125b6debb8817bdf2c5e886e32a0bef890ba4e911326c47b71 Chain recovered Arbiter went down https://status.navalabs.dev/ Mon, 01 Jun 2026 22:53:45 +0000 https://status.navalabs.dev/#f85f131909bfae38ccb3f8e6457d640e672b7f66f1825b73e6f3f0bb53d3a7d8 Arbiter went down Nava API went down https://status.navalabs.dev/ Mon, 01 Jun 2026 22:52:05 +0000 https://status.navalabs.dev/#02b233d85d5f6ac95ba60b2ae97f2a1b733631851530ad43a0585fb9accc3b20 Nava API went down Chain went down https://status.navalabs.dev/ Mon, 01 Jun 2026 22:51:18 +0000 https://status.navalabs.dev/#8fb869dd4267f0125b6debb8817bdf2c5e886e32a0bef890ba4e911326c47b71 Chain went down Explorer went down https://status.navalabs.dev/ Mon, 01 Jun 2026 22:49:59 +0000 https://status.navalabs.dev/#60efa8dc8778cf5b57feef5de8e1a681a7121f0bf9bccf71dec76e8a270a6f7f Explorer went down Arbiter recovered https://status.navalabs.dev/ Fri, 29 May 2026 02:10:02 +0000 https://status.navalabs.dev/#076062160e3ff76454680efe9c7ba32ed8d7bdb0d59e842d8ce3f2dda5a27813 Arbiter recovered Arbiter went down https://status.navalabs.dev/ Fri, 29 May 2026 02:08:42 +0000 https://status.navalabs.dev/#076062160e3ff76454680efe9c7ba32ed8d7bdb0d59e842d8ce3f2dda5a27813 Arbiter went down