Incidents reported on status page for Velar | Health https://status.velar.com/ https://d1lppblt9t2x15.cloudfront.net/logos/56da679825dc14f719b08ff046924931.png https://status.velar.com/ en https://status.velar.com/ Fri, 03 Apr 2026 00:13:27 +0000 https://status.velar.com/#74a401112ad0245297e546c43364b7ea1252abb3694e3611a6e600f85f4c4fbd Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 02 Apr 2026 23:40:27 +0000 https://status.velar.com/#74a401112ad0245297e546c43364b7ea1252abb3694e3611a6e600f85f4c4fbd Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 02 Apr 2026 23:34:16 +0000 https://status.velar.com/#955bb5a2255fc21d353fc7fbffc99f242fcccc79c85dc129299782cf2127b52b Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 02 Apr 2026 23:28:20 +0000 https://status.velar.com/#955bb5a2255fc21d353fc7fbffc99f242fcccc79c85dc129299782cf2127b52b Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 02 Apr 2026 23:22:24 +0000 https://status.velar.com/#a87e9553e18b2f5d69cc27609d0e943ad19bea3acdbf6ae83f09f9d236543313 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 02 Apr 2026 23:07:18 +0000 https://status.velar.com/#a87e9553e18b2f5d69cc27609d0e943ad19bea3acdbf6ae83f09f9d236543313 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 02 Apr 2026 22:58:20 +0000 https://status.velar.com/#66821d645acb2d0c75b085eb0b0a926f7d443e747c1b101f38754958b3502ca8 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 02 Apr 2026 21:40:21 +0000 https://status.velar.com/#66821d645acb2d0c75b085eb0b0a926f7d443e747c1b101f38754958b3502ca8 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 02 Apr 2026 21:25:20 +0000 https://status.velar.com/#3f9c6e15301c5f8b455e42e1a3e7b84cbeeb36f89e726501978cc0d497c7946d Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 02 Apr 2026 21:22:19 +0000 https://status.velar.com/#3f9c6e15301c5f8b455e42e1a3e7b84cbeeb36f89e726501978cc0d497c7946d Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 02 Apr 2026 21:04:21 +0000 https://status.velar.com/#c635e839029291e17a0bd811f1f22dc614527cf7a54aa8063320c8a8bfe3ad5a Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 02 Apr 2026 20:58:21 +0000 https://status.velar.com/#c635e839029291e17a0bd811f1f22dc614527cf7a54aa8063320c8a8bfe3ad5a Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 02 Apr 2026 20:31:30 +0000 https://status.velar.com/#adaf736b92d1eacfd1fcef2882d30836fd8ea0cddb3d67502e660c247402d7d2 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 02 Apr 2026 19:25:24 +0000 https://status.velar.com/#adaf736b92d1eacfd1fcef2882d30836fd8ea0cddb3d67502e660c247402d7d2 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 02 Apr 2026 19:19:35 +0000 https://status.velar.com/#ba6b6d420dc13894da834365ceda5c598e559321d4b48948022062a3cfaa211b Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 02 Apr 2026 19:16:20 +0000 https://status.velar.com/#ba6b6d420dc13894da834365ceda5c598e559321d4b48948022062a3cfaa211b Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 02 Apr 2026 19:07:26 +0000 https://status.velar.com/#cffe03d6b61288fcc47b89080125d8875c70591618b2985090e50b19120168ae Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 02 Apr 2026 18:49:25 +0000 https://status.velar.com/#cffe03d6b61288fcc47b89080125d8875c70591618b2985090e50b19120168ae Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 02 Apr 2026 18:37:20 +0000 https://status.velar.com/#bc1b0f72ecb02cac194ea53184a1bf552bf307634aa4b51ac6e113a8a6d7d0d5 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 02 Apr 2026 18:07:31 +0000 https://status.velar.com/#bc1b0f72ecb02cac194ea53184a1bf552bf307634aa4b51ac6e113a8a6d7d0d5 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 02 Apr 2026 17:55:29 +0000 https://status.velar.com/#8b710e09b649de6f0348d3ff52aff66f12bd5b1ada5d14a36049204e9468530e Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 02 Apr 2026 16:07:24 +0000 https://status.velar.com/#8b710e09b649de6f0348d3ff52aff66f12bd5b1ada5d14a36049204e9468530e Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 02 Apr 2026 15:58:22 +0000 https://status.velar.com/#ccb0fa95d2cb7a5664ba9aec220293d9c6feb11f47990e22dfa28449873badc1 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 02 Apr 2026 15:55:21 +0000 https://status.velar.com/#ccb0fa95d2cb7a5664ba9aec220293d9c6feb11f47990e22dfa28449873badc1 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 02 Apr 2026 15:40:21 +0000 https://status.velar.com/#93a98590f2a32eb603ce857a91eaa738fbf45be1c31e2b704ec4fe8fdf6eb33c Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 02 Apr 2026 14:07:24 +0000 https://status.velar.com/#93a98590f2a32eb603ce857a91eaa738fbf45be1c31e2b704ec4fe8fdf6eb33c Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 02 Apr 2026 13:58:15 +0000 https://status.velar.com/#04668804ab86a798846b4f6d411be1292a1574e777ae7d0c6f25b1f67f643055 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 02 Apr 2026 13:46:25 +0000 https://status.velar.com/#04668804ab86a798846b4f6d411be1292a1574e777ae7d0c6f25b1f67f643055 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 02 Apr 2026 13:40:23 +0000 https://status.velar.com/#8769f191678fdce668baaa9972dfe31a83ad087c5b9537850a91ba10ca9b8c10 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 02 Apr 2026 13:01:19 +0000 https://status.velar.com/#8769f191678fdce668baaa9972dfe31a83ad087c5b9537850a91ba10ca9b8c10 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 02 Apr 2026 12:52:16 +0000 https://status.velar.com/#6813ae10e39f96d07e68798bb081a313a3e5915771555d8a3ae50eb609496503 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 02 Apr 2026 12:46:20 +0000 https://status.velar.com/#6813ae10e39f96d07e68798bb081a313a3e5915771555d8a3ae50eb609496503 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 02 Apr 2026 12:31:29 +0000 https://status.velar.com/#6011633675119ed6406b4e41f3e427f29d2ef617462a5ca53364306e18440a73 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 02 Apr 2026 12:25:22 +0000 https://status.velar.com/#6011633675119ed6406b4e41f3e427f29d2ef617462a5ca53364306e18440a73 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 02 Apr 2026 12:19:34 +0000 https://status.velar.com/#0ee03c951d333dfa477672bf8cd32afb815ea371d8ff2110928d3288c2bfeb00 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 02 Apr 2026 12:07:28 +0000 https://status.velar.com/#0ee03c951d333dfa477672bf8cd32afb815ea371d8ff2110928d3288c2bfeb00 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 02 Apr 2026 12:01:24 +0000 https://status.velar.com/#8984a75af1f5c1996abf05d5b16a87a64db06c900a877561824d4e330d1ef5d9 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 02 Apr 2026 11:31:20 +0000 https://status.velar.com/#8984a75af1f5c1996abf05d5b16a87a64db06c900a877561824d4e330d1ef5d9 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 02 Apr 2026 11:13:30 +0000 https://status.velar.com/#97ad066665a77e22728620e350f3e4f78cdaa29ae6e73942e7eb5c63242d3d9d Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 02 Apr 2026 10:34:31 +0000 https://status.velar.com/#97ad066665a77e22728620e350f3e4f78cdaa29ae6e73942e7eb5c63242d3d9d Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 02 Apr 2026 10:28:26 +0000 https://status.velar.com/#5e26726688e994fd554906eee715d0b3e5fbba80e31e066892389e6f8f1bbafd Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 02 Apr 2026 10:16:21 +0000 https://status.velar.com/#5e26726688e994fd554906eee715d0b3e5fbba80e31e066892389e6f8f1bbafd Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 02 Apr 2026 10:10:24 +0000 https://status.velar.com/#6d865b3c5fa55951fa9688579aa727fe3dac0b61e89edee03c1388497a82c88a Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 02 Apr 2026 09:55:19 +0000 https://status.velar.com/#6d865b3c5fa55951fa9688579aa727fe3dac0b61e89edee03c1388497a82c88a Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 02 Apr 2026 09:46:20 +0000 https://status.velar.com/#c96de729f78f18ae35f04a27ab302a9364868addb971803c97c6763059468406 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 02 Apr 2026 09:28:21 +0000 https://status.velar.com/#c96de729f78f18ae35f04a27ab302a9364868addb971803c97c6763059468406 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 02 Apr 2026 09:22:30 +0000 https://status.velar.com/#27d377c074d618d0dc9c86d0d1997cb67047eb4ea0e09aab0c579b1580dadaac Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 02 Apr 2026 08:34:19 +0000 https://status.velar.com/#27d377c074d618d0dc9c86d0d1997cb67047eb4ea0e09aab0c579b1580dadaac Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 02 Apr 2026 08:28:20 +0000 https://status.velar.com/#5df3b6cb2f393174e63b341655dee028f608ba57579637c5fed9395740acd9d6 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 02 Apr 2026 07:31:22 +0000 https://status.velar.com/#5df3b6cb2f393174e63b341655dee028f608ba57579637c5fed9395740acd9d6 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 02 Apr 2026 07:22:19 +0000 https://status.velar.com/#2a320080ca56c39cb4161ea4733019d830507d7754d0c604b929f3b0c3c948dd Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 02 Apr 2026 06:01:21 +0000 https://status.velar.com/#2a320080ca56c39cb4161ea4733019d830507d7754d0c604b929f3b0c3c948dd Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 02 Apr 2026 05:55:24 +0000 https://status.velar.com/#0dd563c3fcaa24f8e9ed1dff113e4110a340193397ba8a14f222888162886e20 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 02 Apr 2026 04:58:19 +0000 https://status.velar.com/#0dd563c3fcaa24f8e9ed1dff113e4110a340193397ba8a14f222888162886e20 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 02 Apr 2026 04:46:30 +0000 https://status.velar.com/#3dd1648914f8cc19b6425db1afe3bbf4da47258826ceb7b563112db54d65084a Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 02 Apr 2026 03:58:21 +0000 https://status.velar.com/#3dd1648914f8cc19b6425db1afe3bbf4da47258826ceb7b563112db54d65084a Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 02 Apr 2026 03:43:32 +0000 https://status.velar.com/#48ba3eee3576d311c097055afff5ebe51d4e0135ec275abdf3d1c2a35d8f3bab Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 02 Apr 2026 02:58:27 +0000 https://status.velar.com/#48ba3eee3576d311c097055afff5ebe51d4e0135ec275abdf3d1c2a35d8f3bab Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 02 Apr 2026 02:52:22 +0000 https://status.velar.com/#92ad6622b84d5670f6c48636ed5a9df74ba53d4eecfa361985d397e627806ea6 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 02 Apr 2026 02:19:26 +0000 https://status.velar.com/#92ad6622b84d5670f6c48636ed5a9df74ba53d4eecfa361985d397e627806ea6 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 02 Apr 2026 02:16:21 +0000 https://status.velar.com/#e8ef47e934e5b5c53a9a0b73dc6b5a38c34da9e9970e2d0dc115a3ff7132e060 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 02 Apr 2026 02:10:21 +0000 https://status.velar.com/#e8ef47e934e5b5c53a9a0b73dc6b5a38c34da9e9970e2d0dc115a3ff7132e060 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 02 Apr 2026 02:04:21 +0000 https://status.velar.com/#e74456b1415771aafa2e5fbcaff117209880275c50ba354eb37fdb10710d6b03 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 02 Apr 2026 01:52:22 +0000 https://status.velar.com/#e74456b1415771aafa2e5fbcaff117209880275c50ba354eb37fdb10710d6b03 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 02 Apr 2026 01:46:23 +0000 https://status.velar.com/#5673662498cbc3323fcd806c9088450069420bc974f616c1c4ddbc01c71f6163 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 02 Apr 2026 01:16:19 +0000 https://status.velar.com/#5673662498cbc3323fcd806c9088450069420bc974f616c1c4ddbc01c71f6163 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 02 Apr 2026 01:10:22 +0000 https://status.velar.com/#5ef436c055e3332332e5d5a1af19af156bccf2f982f423807246d33259347abb Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 02 Apr 2026 00:40:21 +0000 https://status.velar.com/#5ef436c055e3332332e5d5a1af19af156bccf2f982f423807246d33259347abb Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 02 Apr 2026 00:34:23 +0000 https://status.velar.com/#db210b137c5e6fcdae476e6425aa23d5a0d8616e10bd6afb0f8040358deb4dc1 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 02 Apr 2026 00:25:18 +0000 https://status.velar.com/#db210b137c5e6fcdae476e6425aa23d5a0d8616e10bd6afb0f8040358deb4dc1 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 02 Apr 2026 00:16:19 +0000 https://status.velar.com/#bd0b50f8e9944dd4824ec25b19efd3fd2c5898d2ccbd2da1ee658fb83c2f60f2 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 02 Apr 2026 00:04:20 +0000 https://status.velar.com/#bd0b50f8e9944dd4824ec25b19efd3fd2c5898d2ccbd2da1ee658fb83c2f60f2 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 23:55:20 +0000 https://status.velar.com/#d99d5e462c534dc38fdcac28075a571c158c5f0311edf631e0c0a78e5a97344f Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 23:31:34 +0000 https://status.velar.com/#d99d5e462c534dc38fdcac28075a571c158c5f0311edf631e0c0a78e5a97344f Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 23:22:27 +0000 https://status.velar.com/#109140cd7a2a21dfde731201ea1abf3d92c69c75ac7ea882937603fcec43172b Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 23:10:20 +0000 https://status.velar.com/#109140cd7a2a21dfde731201ea1abf3d92c69c75ac7ea882937603fcec43172b Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 22:55:32 +0000 https://status.velar.com/#8b10a70f80699a8da514365aae573da28c69c4498d07c40477faed62c1fb6da7 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 22:01:19 +0000 https://status.velar.com/#8b10a70f80699a8da514365aae573da28c69c4498d07c40477faed62c1fb6da7 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 21:52:30 +0000 https://status.velar.com/#28d26f5c064517b54588f3d585c0fea8518a349fa3fc3894e54ec5b5df33072d Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 21:43:31 +0000 https://status.velar.com/#28d26f5c064517b54588f3d585c0fea8518a349fa3fc3894e54ec5b5df33072d Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 21:22:22 +0000 https://status.velar.com/#37233f841011b0c39fc69372c51c050f8e9802d46c1aca0676f0c364b38f1669 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 21:19:26 +0000 https://status.velar.com/#37233f841011b0c39fc69372c51c050f8e9802d46c1aca0676f0c364b38f1669 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 21:13:21 +0000 https://status.velar.com/#7287cf4a30501a50d8eb0e01d6e125cb7d79d0f89bf8a0c672c9a792c7f7522c Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 20:52:25 +0000 https://status.velar.com/#7287cf4a30501a50d8eb0e01d6e125cb7d79d0f89bf8a0c672c9a792c7f7522c Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 20:37:23 +0000 https://status.velar.com/#041388051fd7a51e78210ffbd544d566f35938e702af565b8871da269be3272d Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 20:25:19 +0000 https://status.velar.com/#041388051fd7a51e78210ffbd544d566f35938e702af565b8871da269be3272d Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 20:19:26 +0000 https://status.velar.com/#653fa08e15e04cc4825f19a9c95dd8ca44f97b7023a95596b095ee974198d0fb Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 17:52:27 +0000 https://status.velar.com/#653fa08e15e04cc4825f19a9c95dd8ca44f97b7023a95596b095ee974198d0fb Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 17:43:20 +0000 https://status.velar.com/#3f86dc1cec5b3cfe29a3576898746c8094de4801c367acd3e6707115e453ccf8 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 17:31:26 +0000 https://status.velar.com/#3f86dc1cec5b3cfe29a3576898746c8094de4801c367acd3e6707115e453ccf8 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 17:28:19 +0000 https://status.velar.com/#93e86ae50afcf942c02d6162debba714ec78de8783d3ef95ae252fe1123816ed Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 17:22:28 +0000 https://status.velar.com/#93e86ae50afcf942c02d6162debba714ec78de8783d3ef95ae252fe1123816ed Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 17:16:31 +0000 https://status.velar.com/#bad4c948e8938abd00ec79c258a0a4933c1f4550c43c540e4f36bb7a0fbb46b9 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 16:58:21 +0000 https://status.velar.com/#bad4c948e8938abd00ec79c258a0a4933c1f4550c43c540e4f36bb7a0fbb46b9 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 16:37:21 +0000 https://status.velar.com/#e85d59122550ac2f90529e3b123778c5f89ecd4e0e53fdf31ce115e75725f553 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 16:34:26 +0000 https://status.velar.com/#e85d59122550ac2f90529e3b123778c5f89ecd4e0e53fdf31ce115e75725f553 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 16:10:23 +0000 https://status.velar.com/#6d7304a05b30a96aa197c2fb0d558fceb011e1272f0264ee9b088f0febdd6ece Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 15:58:24 +0000 https://status.velar.com/#6d7304a05b30a96aa197c2fb0d558fceb011e1272f0264ee9b088f0febdd6ece Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 15:28:23 +0000 https://status.velar.com/#2b53157d3ba0ae321401a9efbc5cc7f81a0a36314b4eeede557a9768da91432b Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 15:07:17 +0000 https://status.velar.com/#2b53157d3ba0ae321401a9efbc5cc7f81a0a36314b4eeede557a9768da91432b Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 14:28:20 +0000 https://status.velar.com/#ac722c1ed836df72dd9ce8badd7993f2428733983a292cb10a0cca138ee33332 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 14:04:20 +0000 https://status.velar.com/#ac722c1ed836df72dd9ce8badd7993f2428733983a292cb10a0cca138ee33332 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 13:46:28 +0000 https://status.velar.com/#1c3795cb320ee3abd0f097f4cef08517d57c10f7f5006db5cadfc1ce4baed2ca Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 13:37:20 +0000 https://status.velar.com/#1c3795cb320ee3abd0f097f4cef08517d57c10f7f5006db5cadfc1ce4baed2ca Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 13:19:36 +0000 https://status.velar.com/#c50420d35a7d25ac60f06a778044ea3b1905f61c36e5f8c1b1094bf2dd6d3473 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 12:37:19 +0000 https://status.velar.com/#c50420d35a7d25ac60f06a778044ea3b1905f61c36e5f8c1b1094bf2dd6d3473 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 12:07:23 +0000 https://status.velar.com/#e8f75aa2ab6a646c7b1ccc754bdedfb2d5676de4b2d114f1e6be38d7e63544e2 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 11:46:22 +0000 https://status.velar.com/#e8f75aa2ab6a646c7b1ccc754bdedfb2d5676de4b2d114f1e6be38d7e63544e2 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 11:19:26 +0000 https://status.velar.com/#7c32d1836927c6e7d0c1109f1e6d6f4e97ac913b9f6dc49a2ec9acfc2c563e38 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 11:16:20 +0000 https://status.velar.com/#7c32d1836927c6e7d0c1109f1e6d6f4e97ac913b9f6dc49a2ec9acfc2c563e38 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 10:58:24 +0000 https://status.velar.com/#b2fd595d2d43ede2640ebd96837d3e43a055b33d1178770f35e74ba07ff00de5 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 10:46:20 +0000 https://status.velar.com/#b2fd595d2d43ede2640ebd96837d3e43a055b33d1178770f35e74ba07ff00de5 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 10:40:24 +0000 https://status.velar.com/#cb8af4a08f7254118e5be39c3fb182e40e982e73fbb3556d70bffff901d0c9d2 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 10:34:26 +0000 https://status.velar.com/#cb8af4a08f7254118e5be39c3fb182e40e982e73fbb3556d70bffff901d0c9d2 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 10:16:16 +0000 https://status.velar.com/#29df147314c95f82ff16116ea54f544b80903cfe68d16608147a9bd1d59d49da Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 10:04:23 +0000 https://status.velar.com/#29df147314c95f82ff16116ea54f544b80903cfe68d16608147a9bd1d59d49da Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 09:46:23 +0000 https://status.velar.com/#fb3c0fe37c0c4bc188904aed96cf728f97a04f45b1cccb95f9326edda235f836 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 09:40:16 +0000 https://status.velar.com/#fb3c0fe37c0c4bc188904aed96cf728f97a04f45b1cccb95f9326edda235f836 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 09:10:23 +0000 https://status.velar.com/#a47d9de5f321e3bfa6f5e7c19b44a428cd7eeb6f42304f013cc56c06d1d69056 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 09:04:16 +0000 https://status.velar.com/#a47d9de5f321e3bfa6f5e7c19b44a428cd7eeb6f42304f013cc56c06d1d69056 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 08:58:20 +0000 https://status.velar.com/#425542e37bbd70aa2193e91a3d088e71f8bf9e910359cda46885e77441dcfe7b Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 08:55:21 +0000 https://status.velar.com/#425542e37bbd70aa2193e91a3d088e71f8bf9e910359cda46885e77441dcfe7b Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 08:25:22 +0000 https://status.velar.com/#7cf4b7caf3cf2bfeeac07c41f67ac4cfcabd098ae9a0a612d1223af08ce5b381 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 08:22:19 +0000 https://status.velar.com/#7cf4b7caf3cf2bfeeac07c41f67ac4cfcabd098ae9a0a612d1223af08ce5b381 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 07:22:25 +0000 https://status.velar.com/#cbb78cd2a78b08e806a0277990f77ccf896296125800ec3f7003e653d9f99cb6 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 07:13:23 +0000 https://status.velar.com/#cbb78cd2a78b08e806a0277990f77ccf896296125800ec3f7003e653d9f99cb6 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 07:01:29 +0000 https://status.velar.com/#5dcf2f03bb62d373f9a446dfd124af7c3d08c13d97caaeabcf3f2f715456578c Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 06:58:22 +0000 https://status.velar.com/#5dcf2f03bb62d373f9a446dfd124af7c3d08c13d97caaeabcf3f2f715456578c Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 06:28:25 +0000 https://status.velar.com/#500d0b817741d58e30427026abadcd6957fcce3cc5bf220cfc9f290f7450dfc7 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 06:04:14 +0000 https://status.velar.com/#500d0b817741d58e30427026abadcd6957fcce3cc5bf220cfc9f290f7450dfc7 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 05:52:23 +0000 https://status.velar.com/#775307c97e27613a793858e30d2c83ed4e2ecc5ef2c3558eb07c0572c2d9458a Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 05:46:25 +0000 https://status.velar.com/#775307c97e27613a793858e30d2c83ed4e2ecc5ef2c3558eb07c0572c2d9458a Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 05:31:25 +0000 https://status.velar.com/#7b2998a9a8e9d4313b51b23f9bdc23f66200434a95d32ed995bb0b10fa8724ce Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 05:28:16 +0000 https://status.velar.com/#7b2998a9a8e9d4313b51b23f9bdc23f66200434a95d32ed995bb0b10fa8724ce Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 05:10:25 +0000 https://status.velar.com/#c9a6d9978b75cfa6bae32f247e5c8dc2e968e92c6844d28e0876339b5f639e83 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 05:04:21 +0000 https://status.velar.com/#c9a6d9978b75cfa6bae32f247e5c8dc2e968e92c6844d28e0876339b5f639e83 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 04:52:19 +0000 https://status.velar.com/#8faa9521cced70c6df893f12d663f9121a712f739dff6ccf65706b8682677c1d Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 04:49:22 +0000 https://status.velar.com/#8faa9521cced70c6df893f12d663f9121a712f739dff6ccf65706b8682677c1d Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 04:43:22 +0000 https://status.velar.com/#78badb7b46268bdec41b43497eeeef81dfdd8e00df7d019c643c48a3498f840b Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 04:37:26 +0000 https://status.velar.com/#78badb7b46268bdec41b43497eeeef81dfdd8e00df7d019c643c48a3498f840b Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 04:04:23 +0000 https://status.velar.com/#8fe472ac2d7231f7a02f98b5b9103c58227f5b12a7fdee97545572ccb15b44df Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 03:58:24 +0000 https://status.velar.com/#8fe472ac2d7231f7a02f98b5b9103c58227f5b12a7fdee97545572ccb15b44df Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 03:40:21 +0000 https://status.velar.com/#e7b60d9ec4c5a93b811cc85b5c006808f15a4357425f3fdf4fd9757c02e5ddeb Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 03:31:20 +0000 https://status.velar.com/#e7b60d9ec4c5a93b811cc85b5c006808f15a4357425f3fdf4fd9757c02e5ddeb Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 03:10:26 +0000 https://status.velar.com/#e4335ac5f1ec75d90914e475521a9a37d011e9cd56b7231644cec2ff008c8d36 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 02:43:19 +0000 https://status.velar.com/#e4335ac5f1ec75d90914e475521a9a37d011e9cd56b7231644cec2ff008c8d36 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 02:31:26 +0000 https://status.velar.com/#3552855f52f792f65f1db504e800a252d4eaf2ac7e62a4fa9696726514526eb7 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 02:13:27 +0000 https://status.velar.com/#3552855f52f792f65f1db504e800a252d4eaf2ac7e62a4fa9696726514526eb7 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 01:31:23 +0000 https://status.velar.com/#8c22c10823af9411a3dbcee6d59312d1d900a28009873995bda351d93a67f221 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 01:28:24 +0000 https://status.velar.com/#8c22c10823af9411a3dbcee6d59312d1d900a28009873995bda351d93a67f221 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 01:22:27 +0000 https://status.velar.com/#7a700b1312f57d3bbc1baee8a41edbc43c0305e707ad7a863ad38ab78ef06210 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 01:04:24 +0000 https://status.velar.com/#7a700b1312f57d3bbc1baee8a41edbc43c0305e707ad7a863ad38ab78ef06210 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 01 Apr 2026 00:37:23 +0000 https://status.velar.com/#162e7597aabe33ea424780398a9db70c011316b1c239cef67eacda796d38ea3c Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 01 Apr 2026 00:19:21 +0000 https://status.velar.com/#162e7597aabe33ea424780398a9db70c011316b1c239cef67eacda796d38ea3c Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 31 Mar 2026 23:52:26 +0000 https://status.velar.com/#441dda81ba0714c4663534a9c167ceba992d21e2a9d3c98ef47ff4b28a482744 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 31 Mar 2026 23:49:29 +0000 https://status.velar.com/#441dda81ba0714c4663534a9c167ceba992d21e2a9d3c98ef47ff4b28a482744 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 31 Mar 2026 20:07:23 +0000 https://status.velar.com/#a8463abb34d334ca32c7316b489c44ad680d4054ef9bb5a4e1a4d6d81a731e8f Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 31 Mar 2026 20:04:21 +0000 https://status.velar.com/#a8463abb34d334ca32c7316b489c44ad680d4054ef9bb5a4e1a4d6d81a731e8f Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 31 Mar 2026 03:46:27 +0000 https://status.velar.com/#f6af3f6dc2c08ae7c2cddd78c9e01fbe4e50ef6d20864fbb7ffdba984bb21d7d Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 31 Mar 2026 03:43:22 +0000 https://status.velar.com/#f6af3f6dc2c08ae7c2cddd78c9e01fbe4e50ef6d20864fbb7ffdba984bb21d7d Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 30 Mar 2026 20:58:27 +0000 https://status.velar.com/#7312bb2e9b5849246ca40818eceb9e621644ac42898026d5c3981721f267fee7 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 30 Mar 2026 20:52:21 +0000 https://status.velar.com/#7312bb2e9b5849246ca40818eceb9e621644ac42898026d5c3981721f267fee7 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 29 Mar 2026 19:34:25 +0000 https://status.velar.com/#0a4a79b7aa5cbbee6ade434109bf4f82f807dac7b18d7c2c0ee17c805652b110 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 29 Mar 2026 19:28:19 +0000 https://status.velar.com/#0a4a79b7aa5cbbee6ade434109bf4f82f807dac7b18d7c2c0ee17c805652b110 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 29 Mar 2026 17:31:19 +0000 https://status.velar.com/#3789dad6e6da9ea70ac6b8a7c89ef59efe3d226baf5e2a7f139a6b8e68aeb0de Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 29 Mar 2026 17:28:21 +0000 https://status.velar.com/#3789dad6e6da9ea70ac6b8a7c89ef59efe3d226baf5e2a7f139a6b8e68aeb0de Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 28 Mar 2026 02:25:23 +0000 https://status.velar.com/#7d95235bed776f02701cfcdaff3ffa30fb1974a10bc336a057c32fde17ac94e9 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 28 Mar 2026 02:22:19 +0000 https://status.velar.com/#7d95235bed776f02701cfcdaff3ffa30fb1974a10bc336a057c32fde17ac94e9 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 26 Mar 2026 20:52:23 +0000 https://status.velar.com/#00203f01ac8969a117abf8b89394a74e58913a42e2e5c2674077ed376da83f77 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 26 Mar 2026 20:49:28 +0000 https://status.velar.com/#00203f01ac8969a117abf8b89394a74e58913a42e2e5c2674077ed376da83f77 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 26 Mar 2026 16:19:31 +0000 https://status.velar.com/#53e86257a8ff12ba64ae80f4bf9efd9fc98e2cbb0c7c5ea8ad012df33017fc45 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 26 Mar 2026 16:13:20 +0000 https://status.velar.com/#53e86257a8ff12ba64ae80f4bf9efd9fc98e2cbb0c7c5ea8ad012df33017fc45 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 26 Mar 2026 12:34:19 +0000 https://status.velar.com/#4d9b7b08ded726544a0fe3280a33ed89a3a565ba305152ba00fea3c8d8f031cb Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 26 Mar 2026 12:31:24 +0000 https://status.velar.com/#4d9b7b08ded726544a0fe3280a33ed89a3a565ba305152ba00fea3c8d8f031cb Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 26 Mar 2026 07:16:24 +0000 https://status.velar.com/#66c00b7c9d16e5e047033bdade47f730006421ca0abdd2ae38dd0d41c35cf3f4 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 26 Mar 2026 07:13:18 +0000 https://status.velar.com/#66c00b7c9d16e5e047033bdade47f730006421ca0abdd2ae38dd0d41c35cf3f4 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 26 Mar 2026 00:37:20 +0000 https://status.velar.com/#b3d656c6c1282a52d4159dc614cfbef01b35c0ff42347aad98f64e830c81ab37 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 26 Mar 2026 00:34:20 +0000 https://status.velar.com/#b3d656c6c1282a52d4159dc614cfbef01b35c0ff42347aad98f64e830c81ab37 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 25 Mar 2026 20:58:22 +0000 https://status.velar.com/#ccf6ee9b4f8517b5c334ac86955ba151b59b6b83d1d9bbc07a8847050871c4cf Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 25 Mar 2026 20:52:30 +0000 https://status.velar.com/#ccf6ee9b4f8517b5c334ac86955ba151b59b6b83d1d9bbc07a8847050871c4cf Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 25 Mar 2026 18:07:24 +0000 https://status.velar.com/#b35daf53097e85fb72a456d7b26a053eb198de88c62a3dd0447b452de461805b Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 25 Mar 2026 18:04:22 +0000 https://status.velar.com/#b35daf53097e85fb72a456d7b26a053eb198de88c62a3dd0447b452de461805b Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 25 Mar 2026 17:25:21 +0000 https://status.velar.com/#35546a23b0662598ebe0a41bec1ef01c9a9ba1b908e303a85a2d59f5babee3bb Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 25 Mar 2026 17:16:27 +0000 https://status.velar.com/#35546a23b0662598ebe0a41bec1ef01c9a9ba1b908e303a85a2d59f5babee3bb Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 25 Mar 2026 17:07:22 +0000 https://status.velar.com/#b5182e4ce756655cf3d4db91eed9cef5e95a37cbbfa2fa4f9a608e1105aa8aba Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 25 Mar 2026 17:04:20 +0000 https://status.velar.com/#b5182e4ce756655cf3d4db91eed9cef5e95a37cbbfa2fa4f9a608e1105aa8aba Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 25 Mar 2026 03:16:21 +0000 https://status.velar.com/#838f3e80346ba62a1d1c83dff3fc0e30fe4e94aa2c88457d0d31b4c3ef428e5c Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 25 Mar 2026 03:13:23 +0000 https://status.velar.com/#838f3e80346ba62a1d1c83dff3fc0e30fe4e94aa2c88457d0d31b4c3ef428e5c Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 25 Mar 2026 02:43:25 +0000 https://status.velar.com/#a95e18187ebade65f736e2372b22f9ddb74f722130ab4937b473b6312aac4b07 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 25 Mar 2026 02:40:18 +0000 https://status.velar.com/#a95e18187ebade65f736e2372b22f9ddb74f722130ab4937b473b6312aac4b07 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 25 Mar 2026 02:28:22 +0000 https://status.velar.com/#093a6cb3b20c55b169367810920f15981619f3bb96130c8c1d87a68f6893c3c1 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 25 Mar 2026 02:22:19 +0000 https://status.velar.com/#093a6cb3b20c55b169367810920f15981619f3bb96130c8c1d87a68f6893c3c1 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 25 Mar 2026 00:40:23 +0000 https://status.velar.com/#2094df9b5a8a2e7770f519e03d9b611b11bb8cc0e7161e40a4d177a70323507d Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 25 Mar 2026 00:37:26 +0000 https://status.velar.com/#2094df9b5a8a2e7770f519e03d9b611b11bb8cc0e7161e40a4d177a70323507d Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 25 Mar 2026 00:01:25 +0000 https://status.velar.com/#2ce5b43a5e732d8aaa94221feec8424b38db5eaebba2a43573500ae37bed36a4 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 24 Mar 2026 23:58:19 +0000 https://status.velar.com/#2ce5b43a5e732d8aaa94221feec8424b38db5eaebba2a43573500ae37bed36a4 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 24 Mar 2026 20:07:24 +0000 https://status.velar.com/#9676ed1fae49d3c172641c18db08423e02b2216b73dbf4f3c852a1dd49bec7f4 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 24 Mar 2026 20:04:21 +0000 https://status.velar.com/#9676ed1fae49d3c172641c18db08423e02b2216b73dbf4f3c852a1dd49bec7f4 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 24 Mar 2026 05:16:29 +0000 https://status.velar.com/#61bf1f3ed61f88e1059b3d85b8204707a620376eaae14ce740e6677c625223aa Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 24 Mar 2026 05:13:21 +0000 https://status.velar.com/#61bf1f3ed61f88e1059b3d85b8204707a620376eaae14ce740e6677c625223aa Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 24 Mar 2026 04:16:25 +0000 https://status.velar.com/#8bdde484d76ad9e3c85dbd97d6e71c42bb487fa5a98428bb0254da23ba439f5c Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 24 Mar 2026 04:13:25 +0000 https://status.velar.com/#8bdde484d76ad9e3c85dbd97d6e71c42bb487fa5a98428bb0254da23ba439f5c Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 23 Mar 2026 23:07:20 +0000 https://status.velar.com/#e39865ee690cc98e864d7dfa06252293ba0dbccf498df803573ca3cdeef0bc33 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 23 Mar 2026 23:04:18 +0000 https://status.velar.com/#e39865ee690cc98e864d7dfa06252293ba0dbccf498df803573ca3cdeef0bc33 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 23 Mar 2026 21:19:23 +0000 https://status.velar.com/#022d6f531215f73dd2bedd22db9f7d1ee0203efed065712a64bb27447016b93c Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 23 Mar 2026 21:13:23 +0000 https://status.velar.com/#022d6f531215f73dd2bedd22db9f7d1ee0203efed065712a64bb27447016b93c Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 23 Mar 2026 13:10:21 +0000 https://status.velar.com/#bf822eb4f456c4115aba1732cdabe7ea83f00f237957e6a8ca30791baf4b7471 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 23 Mar 2026 13:07:25 +0000 https://status.velar.com/#bf822eb4f456c4115aba1732cdabe7ea83f00f237957e6a8ca30791baf4b7471 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 23 Mar 2026 08:22:19 +0000 https://status.velar.com/#fba356e4fb2206896702c557a9c947982513b695179766c6fd531ce2b5d44639 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 23 Mar 2026 08:13:25 +0000 https://status.velar.com/#fba356e4fb2206896702c557a9c947982513b695179766c6fd531ce2b5d44639 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 23 Mar 2026 06:22:26 +0000 https://status.velar.com/#2e47237f4dde1843251f870fd4c4fc082b0c9189cfd18355ab46827a9794c02d Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 23 Mar 2026 06:19:22 +0000 https://status.velar.com/#2e47237f4dde1843251f870fd4c4fc082b0c9189cfd18355ab46827a9794c02d Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 23 Mar 2026 04:10:19 +0000 https://status.velar.com/#bb615a6e73581c7a3994488882b7c1c9b6692bc459e631a8927f7ae455a1bbaf Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 23 Mar 2026 04:07:21 +0000 https://status.velar.com/#bb615a6e73581c7a3994488882b7c1c9b6692bc459e631a8927f7ae455a1bbaf Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 22 Mar 2026 20:58:19 +0000 https://status.velar.com/#d7c8df0e4d02e1ba4178f6a44ebd3259788860333e40e82e7420349f133df78e Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 22 Mar 2026 20:52:27 +0000 https://status.velar.com/#d7c8df0e4d02e1ba4178f6a44ebd3259788860333e40e82e7420349f133df78e Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 22 Mar 2026 20:31:22 +0000 https://status.velar.com/#b9550fddc8c9b775cdf6eefa6984b0b67a8f3b6224af800fc2065b22fc2e374d Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 22 Mar 2026 20:16:27 +0000 https://status.velar.com/#b9550fddc8c9b775cdf6eefa6984b0b67a8f3b6224af800fc2065b22fc2e374d Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 22 Mar 2026 16:46:16 +0000 https://status.velar.com/#08afe6472a4a7d51aa885bcf2c975e0bfb232d74235792efa0709cf3f5dd0589 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 22 Mar 2026 16:43:17 +0000 https://status.velar.com/#08afe6472a4a7d51aa885bcf2c975e0bfb232d74235792efa0709cf3f5dd0589 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 22 Mar 2026 15:46:24 +0000 https://status.velar.com/#2f7be4c9cd38aa4f23b39ed7f1c9091b5bcd0781e276a8576f8ecea361eebcc7 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 22 Mar 2026 15:34:19 +0000 https://status.velar.com/#2f7be4c9cd38aa4f23b39ed7f1c9091b5bcd0781e276a8576f8ecea361eebcc7 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 22 Mar 2026 00:28:25 +0000 https://status.velar.com/#d51b73f003c63358c779c796c1a9e66a6101c3a98e33e3aa0de3511677ffbc20 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 22 Mar 2026 00:22:23 +0000 https://status.velar.com/#d51b73f003c63358c779c796c1a9e66a6101c3a98e33e3aa0de3511677ffbc20 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 21 Mar 2026 20:40:17 +0000 https://status.velar.com/#78793bb4a1a718265e5713a52cbc04f408e621392e9dc2f6f0ecad34c77ecd04 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 21 Mar 2026 20:37:28 +0000 https://status.velar.com/#78793bb4a1a718265e5713a52cbc04f408e621392e9dc2f6f0ecad34c77ecd04 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 21 Mar 2026 18:10:27 +0000 https://status.velar.com/#e9df0697340d29a7e558005ba2a7326a34989c21b98c1eba828c5f9affa5e96d Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 21 Mar 2026 18:07:20 +0000 https://status.velar.com/#e9df0697340d29a7e558005ba2a7326a34989c21b98c1eba828c5f9affa5e96d Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 21 Mar 2026 17:19:25 +0000 https://status.velar.com/#b0f8da663a16921e43a6b56d625ae369493c8fc102a96f4997db1f7ae15f9803 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 21 Mar 2026 17:16:27 +0000 https://status.velar.com/#b0f8da663a16921e43a6b56d625ae369493c8fc102a96f4997db1f7ae15f9803 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 21 Mar 2026 17:01:26 +0000 https://status.velar.com/#b7bb592485907096db7be75153aa6527e6ba2603a3b0d0644d37d39e4f8caf31 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 21 Mar 2026 16:52:24 +0000 https://status.velar.com/#b7bb592485907096db7be75153aa6527e6ba2603a3b0d0644d37d39e4f8caf31 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 21 Mar 2026 16:46:18 +0000 https://status.velar.com/#3bedeedc24f90436de95fe225a110dfe0732cc3be42088a1531b56daf1bc7edb Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 21 Mar 2026 16:43:21 +0000 https://status.velar.com/#3bedeedc24f90436de95fe225a110dfe0732cc3be42088a1531b56daf1bc7edb Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 21 Mar 2026 15:40:23 +0000 https://status.velar.com/#7cc2272b1b8097782513534545a7e2dfffd1c14187f88bd5bfcfc3c276dc4282 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 21 Mar 2026 15:37:26 +0000 https://status.velar.com/#7cc2272b1b8097782513534545a7e2dfffd1c14187f88bd5bfcfc3c276dc4282 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 21 Mar 2026 14:55:25 +0000 https://status.velar.com/#e1a83b5f12165f5bb4c55d9cb12a8a4af321d5d2b810bd80956e8fdd145e7553 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 21 Mar 2026 14:52:25 +0000 https://status.velar.com/#e1a83b5f12165f5bb4c55d9cb12a8a4af321d5d2b810bd80956e8fdd145e7553 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 21 Mar 2026 11:58:19 +0000 https://status.velar.com/#44a1f4af6e1d9a491583fe53d77a69d242aa029cd6a551660d66fd4c5caf8f8b Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 21 Mar 2026 11:55:26 +0000 https://status.velar.com/#44a1f4af6e1d9a491583fe53d77a69d242aa029cd6a551660d66fd4c5caf8f8b Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 21 Mar 2026 11:49:32 +0000 https://status.velar.com/#8b14272fc0081c6c1454a1ae5b58f3c3b54c7a1a0f8dced92dd36e6f8f3a729c Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 21 Mar 2026 11:34:24 +0000 https://status.velar.com/#8b14272fc0081c6c1454a1ae5b58f3c3b54c7a1a0f8dced92dd36e6f8f3a729c Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 21 Mar 2026 07:40:22 +0000 https://status.velar.com/#df92205c4e767e5bab2ae43a2de9f6336b5430e1a806032c62657b68c625630e Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 21 Mar 2026 07:37:29 +0000 https://status.velar.com/#df92205c4e767e5bab2ae43a2de9f6336b5430e1a806032c62657b68c625630e Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 21 Mar 2026 06:19:27 +0000 https://status.velar.com/#e4274f2f2388c154909874be79bb932d369919b82dd2c26508f1f8bea4b9a3ef Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 21 Mar 2026 06:16:17 +0000 https://status.velar.com/#e4274f2f2388c154909874be79bb932d369919b82dd2c26508f1f8bea4b9a3ef Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 21 Mar 2026 05:28:25 +0000 https://status.velar.com/#30a3cc19796c335010723f36ee305f4a67ba5f6fb2b832fe679c8b4b51166bfd Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 21 Mar 2026 05:25:25 +0000 https://status.velar.com/#30a3cc19796c335010723f36ee305f4a67ba5f6fb2b832fe679c8b4b51166bfd Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 21 Mar 2026 05:22:18 +0000 https://status.velar.com/#5b3062ea201889088437b87294d578d3fbd8997d3f7cc443086b80d5fbd3e2d7 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 21 Mar 2026 05:19:23 +0000 https://status.velar.com/#5b3062ea201889088437b87294d578d3fbd8997d3f7cc443086b80d5fbd3e2d7 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 21 Mar 2026 04:07:22 +0000 https://status.velar.com/#678b914c6d8d28b20b3c633749c4ccf6174bf0ed9e8afe3df84f1828fceb6e8d Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 21 Mar 2026 03:58:24 +0000 https://status.velar.com/#678b914c6d8d28b20b3c633749c4ccf6174bf0ed9e8afe3df84f1828fceb6e8d Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 21 Mar 2026 03:52:16 +0000 https://status.velar.com/#9e0dabae2128827e2f58c1ad31c5140cbc98f33f24a014c44c02108950256d45 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 21 Mar 2026 03:49:19 +0000 https://status.velar.com/#9e0dabae2128827e2f58c1ad31c5140cbc98f33f24a014c44c02108950256d45 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 21 Mar 2026 00:31:26 +0000 https://status.velar.com/#28712e56565cebe8099e3e370287fa4c49843e5a75bd3cb87459fa3b9b241cb5 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 21 Mar 2026 00:28:24 +0000 https://status.velar.com/#28712e56565cebe8099e3e370287fa4c49843e5a75bd3cb87459fa3b9b241cb5 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 20 Mar 2026 19:16:21 +0000 https://status.velar.com/#ef9623efc3d770fb7a2d7cc7ad91f12bdefe420e21ccf6bcd2ade7e4258664fa Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 20 Mar 2026 19:10:22 +0000 https://status.velar.com/#ef9623efc3d770fb7a2d7cc7ad91f12bdefe420e21ccf6bcd2ade7e4258664fa Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 20 Mar 2026 18:43:23 +0000 https://status.velar.com/#7a9f6f646d25e3b09c5e2a8aa041bed2c8c116cf12907bdee79cc7067cbaa6c6 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 20 Mar 2026 18:34:16 +0000 https://status.velar.com/#7a9f6f646d25e3b09c5e2a8aa041bed2c8c116cf12907bdee79cc7067cbaa6c6 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 20 Mar 2026 06:07:17 +0000 https://status.velar.com/#24b63ec8322cf26d2c2bb230f148fd458263550f7f396d4e2f09b77cce1c9ca8 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 20 Mar 2026 05:58:19 +0000 https://status.velar.com/#24b63ec8322cf26d2c2bb230f148fd458263550f7f396d4e2f09b77cce1c9ca8 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 20 Mar 2026 04:49:29 +0000 https://status.velar.com/#7d6a118419f42ba6621f424571fddc73b056205a9f2590e246180ffcd86fd58a Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 20 Mar 2026 04:46:18 +0000 https://status.velar.com/#7d6a118419f42ba6621f424571fddc73b056205a9f2590e246180ffcd86fd58a Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 20 Mar 2026 04:37:29 +0000 https://status.velar.com/#3883f91c2fb370153b98077c59a7802b614faf99d08673773b0e34199e1453f5 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 20 Mar 2026 04:34:21 +0000 https://status.velar.com/#3883f91c2fb370153b98077c59a7802b614faf99d08673773b0e34199e1453f5 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 20 Mar 2026 04:13:25 +0000 https://status.velar.com/#24c0e28578c5e664010918e616dc5a5b5e9c01f84544752f56e8d8ffd704e0d0 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 20 Mar 2026 04:10:17 +0000 https://status.velar.com/#24c0e28578c5e664010918e616dc5a5b5e9c01f84544752f56e8d8ffd704e0d0 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 20 Mar 2026 03:10:25 +0000 https://status.velar.com/#624e8326713928753db5c3a7586404b2b71e3f5e54ab035902ea6c86a670a9dc Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 20 Mar 2026 03:07:20 +0000 https://status.velar.com/#624e8326713928753db5c3a7586404b2b71e3f5e54ab035902ea6c86a670a9dc Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 20 Mar 2026 02:43:25 +0000 https://status.velar.com/#dfb6723827859491c6c3c58fda314697dc341e1ddc2a6b0d37a1aad4df2cb360 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 20 Mar 2026 02:40:19 +0000 https://status.velar.com/#dfb6723827859491c6c3c58fda314697dc341e1ddc2a6b0d37a1aad4df2cb360 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 19 Mar 2026 21:34:19 +0000 https://status.velar.com/#4fe70b215602b08d718a89c2b967505d23e952294992ec46a63a6e238a21f7cc Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 19 Mar 2026 21:31:23 +0000 https://status.velar.com/#4fe70b215602b08d718a89c2b967505d23e952294992ec46a63a6e238a21f7cc Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 19 Mar 2026 19:31:26 +0000 https://status.velar.com/#22b8ad1f059a7bf277048ed28d04adca09230e53805d464fe3487ae681e9ca39 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 19 Mar 2026 19:28:17 +0000 https://status.velar.com/#22b8ad1f059a7bf277048ed28d04adca09230e53805d464fe3487ae681e9ca39 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 19 Mar 2026 16:43:23 +0000 https://status.velar.com/#310ecfa54257bbd48d0b9299c82d08f91598ffb1766c1256198454ba75e83af1 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 19 Mar 2026 16:40:24 +0000 https://status.velar.com/#310ecfa54257bbd48d0b9299c82d08f91598ffb1766c1256198454ba75e83af1 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 19 Mar 2026 15:19:25 +0000 https://status.velar.com/#0785bb8b7fadbfce9bbf37b404f377dd624608f207546b26aae9d58102323052 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 19 Mar 2026 15:16:26 +0000 https://status.velar.com/#0785bb8b7fadbfce9bbf37b404f377dd624608f207546b26aae9d58102323052 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 19 Mar 2026 15:07:25 +0000 https://status.velar.com/#36e3184326cc6919ce0ac7c8d4f421f80239ba23cc97a1d57751bc9584ed28b8 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 19 Mar 2026 15:01:25 +0000 https://status.velar.com/#36e3184326cc6919ce0ac7c8d4f421f80239ba23cc97a1d57751bc9584ed28b8 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 19 Mar 2026 14:16:22 +0000 https://status.velar.com/#7d8c7a19c010c39ffb5b60469cba98549386ebcf1c10673e8c5f0220059dff67 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 19 Mar 2026 14:13:30 +0000 https://status.velar.com/#7d8c7a19c010c39ffb5b60469cba98549386ebcf1c10673e8c5f0220059dff67 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 19 Mar 2026 13:55:22 +0000 https://status.velar.com/#911fd66ad97c909009e71b79a8a761d1544723c06cbef257c1f608fcccffc5c1 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 19 Mar 2026 13:52:23 +0000 https://status.velar.com/#911fd66ad97c909009e71b79a8a761d1544723c06cbef257c1f608fcccffc5c1 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 19 Mar 2026 12:28:21 +0000 https://status.velar.com/#c00fb818a3d469d1bcdb5e813dfa5bce1eb4773059a41f277996fbce13a3c0fb Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 19 Mar 2026 12:22:21 +0000 https://status.velar.com/#c00fb818a3d469d1bcdb5e813dfa5bce1eb4773059a41f277996fbce13a3c0fb Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 19 Mar 2026 10:49:25 +0000 https://status.velar.com/#9f23297d370b9571b4cf374a29cf9a31f7228a9d6eaf417c6f9cdef508d055df Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 19 Mar 2026 10:46:17 +0000 https://status.velar.com/#9f23297d370b9571b4cf374a29cf9a31f7228a9d6eaf417c6f9cdef508d055df Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 19 Mar 2026 07:22:23 +0000 https://status.velar.com/#51df6d209ee2275050e73573ff3f251dc5dc0b97155ec1cefd3dd4cc6780c523 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 19 Mar 2026 07:19:18 +0000 https://status.velar.com/#51df6d209ee2275050e73573ff3f251dc5dc0b97155ec1cefd3dd4cc6780c523 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 19 Mar 2026 06:40:23 +0000 https://status.velar.com/#9f1f156dcdfc117836f021f3f195a065ae7a60c700edee21e907b30468d64f2c Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 19 Mar 2026 06:28:22 +0000 https://status.velar.com/#9f1f156dcdfc117836f021f3f195a065ae7a60c700edee21e907b30468d64f2c Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 19 Mar 2026 03:01:27 +0000 https://status.velar.com/#b1fb2e7ae47c90641b4936a41853c80646d009bdfc39d5640ab8a9265334a36b Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 19 Mar 2026 02:58:19 +0000 https://status.velar.com/#b1fb2e7ae47c90641b4936a41853c80646d009bdfc39d5640ab8a9265334a36b Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 19 Mar 2026 01:40:23 +0000 https://status.velar.com/#33da69d52f81c5079ec2fd76b681fe8145ad8e62a46a7d399fd64cac180cdc70 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 19 Mar 2026 01:37:29 +0000 https://status.velar.com/#33da69d52f81c5079ec2fd76b681fe8145ad8e62a46a7d399fd64cac180cdc70 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 18 Mar 2026 20:40:19 +0000 https://status.velar.com/#11a3f17936e7b1a6128fdbeed9d4ad21ae840428071eb5cf54cf99b09340cbad Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 18 Mar 2026 20:37:27 +0000 https://status.velar.com/#11a3f17936e7b1a6128fdbeed9d4ad21ae840428071eb5cf54cf99b09340cbad Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 18 Mar 2026 17:52:23 +0000 https://status.velar.com/#3715c5189cb2dc0a64d968beb2ccfd3f3773a29afc3638bd025c011a9add6a19 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 18 Mar 2026 17:49:28 +0000 https://status.velar.com/#3715c5189cb2dc0a64d968beb2ccfd3f3773a29afc3638bd025c011a9add6a19 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 18 Mar 2026 10:25:26 +0000 https://status.velar.com/#2369a37410d69cdee90cfaa7f079b8dfd0d79ae9e196243093e6f501f7befce6 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 18 Mar 2026 10:22:25 +0000 https://status.velar.com/#2369a37410d69cdee90cfaa7f079b8dfd0d79ae9e196243093e6f501f7befce6 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 18 Mar 2026 02:22:20 +0000 https://status.velar.com/#f9f51d9a3068a0d2ac5c4a595427a37b80499c6913e217d2d5bc23ed1b5680fc Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 18 Mar 2026 02:19:30 +0000 https://status.velar.com/#f9f51d9a3068a0d2ac5c4a595427a37b80499c6913e217d2d5bc23ed1b5680fc Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 18 Mar 2026 02:16:22 +0000 https://status.velar.com/#55836f0ff5f757d9769e6e7b36d41862d5ff15173a5b10c691c581a24e455069 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 18 Mar 2026 02:13:28 +0000 https://status.velar.com/#55836f0ff5f757d9769e6e7b36d41862d5ff15173a5b10c691c581a24e455069 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 17 Mar 2026 23:37:27 +0000 https://status.velar.com/#336988b64b0ce89dcd476a1aad7931f513ecad7ad84cd74ab6a2cc8604cf709b Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 17 Mar 2026 23:34:23 +0000 https://status.velar.com/#336988b64b0ce89dcd476a1aad7931f513ecad7ad84cd74ab6a2cc8604cf709b Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 17 Mar 2026 19:49:26 +0000 https://status.velar.com/#1ae9c9fb2a62e41205601d077a53c83953a20337ac936d0b961b6b9eebf98f78 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 17 Mar 2026 19:46:18 +0000 https://status.velar.com/#1ae9c9fb2a62e41205601d077a53c83953a20337ac936d0b961b6b9eebf98f78 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 17 Mar 2026 10:25:25 +0000 https://status.velar.com/#0864bf58c48c435e0c4e6938c00edd9b6765e5944f43b94cbaca7da87c4b9b62 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 17 Mar 2026 10:22:24 +0000 https://status.velar.com/#0864bf58c48c435e0c4e6938c00edd9b6765e5944f43b94cbaca7da87c4b9b62 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 16 Mar 2026 23:07:23 +0000 https://status.velar.com/#38deded3f059315848794a9179ede4eef6b44dc0a5b068d5790b65452024ee9c Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 16 Mar 2026 23:04:24 +0000 https://status.velar.com/#38deded3f059315848794a9179ede4eef6b44dc0a5b068d5790b65452024ee9c Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 16 Mar 2026 22:34:24 +0000 https://status.velar.com/#0e7ed009e8492aad0f0d18640263b851f3cc98fe51f0b26a147d3d8dc9a160fa Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 16 Mar 2026 22:31:22 +0000 https://status.velar.com/#0e7ed009e8492aad0f0d18640263b851f3cc98fe51f0b26a147d3d8dc9a160fa Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 16 Mar 2026 16:07:21 +0000 https://status.velar.com/#2c61a294923c3533e0ac97673164cc8b1020b7f515980c72d2d671a5ce2e90b8 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 16 Mar 2026 16:04:22 +0000 https://status.velar.com/#2c61a294923c3533e0ac97673164cc8b1020b7f515980c72d2d671a5ce2e90b8 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 15 Mar 2026 21:46:23 +0000 https://status.velar.com/#1cacba2a7382aeacc5333deaa8c9f07868ba738a171597b441fdd97a218c43ed Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 15 Mar 2026 21:43:19 +0000 https://status.velar.com/#1cacba2a7382aeacc5333deaa8c9f07868ba738a171597b441fdd97a218c43ed Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 14 Mar 2026 20:49:24 +0000 https://status.velar.com/#0aab1cf5a0facdc545a47946c07d95f4527dac724ff9732d5af8919316810901 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 14 Mar 2026 20:40:22 +0000 https://status.velar.com/#0aab1cf5a0facdc545a47946c07d95f4527dac724ff9732d5af8919316810901 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 14 Mar 2026 20:35:15 +0000 https://status.velar.com/#289d7cc1b1564e8e4452baedc44223d9b8dfbb7742351afedfc9cb9fd45f38c5 api.velar.co recovered https://status.velar.com/ Sat, 14 Mar 2026 20:32:12 +0000 https://status.velar.com/#289d7cc1b1564e8e4452baedc44223d9b8dfbb7742351afedfc9cb9fd45f38c5 api.velar.co went down https://status.velar.com/ Sat, 14 Mar 2026 15:37:27 +0000 https://status.velar.com/#eda9410cf918e062d78fe1db1bc545b52330acdbdbb7b15b949fd1556d630019 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 14 Mar 2026 15:34:36 +0000 https://status.velar.com/#eda9410cf918e062d78fe1db1bc545b52330acdbdbb7b15b949fd1556d630019 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 13 Mar 2026 23:28:23 +0000 https://status.velar.com/#41ba69512ea0b80fb9986b10adc37bd5f4da986033259827347ddad111f3a9ae Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 13 Mar 2026 23:25:26 +0000 https://status.velar.com/#41ba69512ea0b80fb9986b10adc37bd5f4da986033259827347ddad111f3a9ae Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 12 Mar 2026 23:31:24 +0000 https://status.velar.com/#3c01d258c529ed24067577bae98e4e83c6051b3469fdbf395bf41458919170dd Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 12 Mar 2026 23:28:24 +0000 https://status.velar.com/#3c01d258c529ed24067577bae98e4e83c6051b3469fdbf395bf41458919170dd Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 11 Mar 2026 17:43:43 +0000 https://status.velar.com/#a813b2b6305507147a7f33d606b7ca610d8566c7d769270dd96e500d70f8a8c5 bridge.velar.com recovered https://status.velar.com/ Wed, 11 Mar 2026 17:40:34 +0000 https://status.velar.com/#a813b2b6305507147a7f33d606b7ca610d8566c7d769270dd96e500d70f8a8c5 bridge.velar.com went down https://status.velar.com/ Wed, 11 Mar 2026 10:43:46 +0000 https://status.velar.com/#9d3bc01c19709e73c3df6451277a0f4bc19ac4fda544286d80e1e626eccda6b8 bridge.velar.com recovered https://status.velar.com/ Wed, 11 Mar 2026 10:40:46 +0000 https://status.velar.com/#9d3bc01c19709e73c3df6451277a0f4bc19ac4fda544286d80e1e626eccda6b8 bridge.velar.com went down https://status.velar.com/ Wed, 11 Mar 2026 09:39:53 +0000 https://status.velar.com/#1cf87f55e462f97626c61e9f5a3ef011ec97b4c706b49d1d75f1e1549401d1be Web App (app.velar.com) recovered https://status.velar.com/ Wed, 11 Mar 2026 09:33:54 +0000 https://status.velar.com/#1cf87f55e462f97626c61e9f5a3ef011ec97b4c706b49d1d75f1e1549401d1be Web App (app.velar.com) went down https://status.velar.com/ Tue, 10 Mar 2026 15:25:34 +0000 https://status.velar.com/#da1a3c40036069c3ed7fea4df712a60f4d2da0ceaa47ca201bbf519646062f47 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 10 Mar 2026 15:22:31 +0000 https://status.velar.com/#da1a3c40036069c3ed7fea4df712a60f4d2da0ceaa47ca201bbf519646062f47 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 10 Mar 2026 12:58:31 +0000 https://status.velar.com/#46669bf593ec1ff647e3a6f2dbf1d90fcf013f2e11a1d262bcd3e1b554c51651 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 10 Mar 2026 12:55:22 +0000 https://status.velar.com/#46669bf593ec1ff647e3a6f2dbf1d90fcf013f2e11a1d262bcd3e1b554c51651 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 10 Mar 2026 12:22:30 +0000 https://status.velar.com/#0474d5213fb58d7d144d7890ebcb4ee7f29705ebf4cb9e6a5c6b5daed596a6fa Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 10 Mar 2026 12:19:22 +0000 https://status.velar.com/#0474d5213fb58d7d144d7890ebcb4ee7f29705ebf4cb9e6a5c6b5daed596a6fa Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 10 Mar 2026 08:43:23 +0000 https://status.velar.com/#0765797db95049f84b1c1a14600dcfe9648e77e9a6cff333e2881178a1be720f Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 10 Mar 2026 08:40:15 +0000 https://status.velar.com/#0765797db95049f84b1c1a14600dcfe9648e77e9a6cff333e2881178a1be720f Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 10 Mar 2026 00:13:19 +0000 https://status.velar.com/#4571b1a340aed78a0333ca8d0bc294a37a5f3ff4663c29e458701e3bdbdf9de5 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 10 Mar 2026 00:07:20 +0000 https://status.velar.com/#4571b1a340aed78a0333ca8d0bc294a37a5f3ff4663c29e458701e3bdbdf9de5 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 09 Mar 2026 21:46:26 +0000 https://status.velar.com/#e696df3ec45512c00550a7e8bb54b67dfbdc0179eb3e3cec000aa7194fd1dd09 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 09 Mar 2026 21:37:25 +0000 https://status.velar.com/#e696df3ec45512c00550a7e8bb54b67dfbdc0179eb3e3cec000aa7194fd1dd09 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 08 Mar 2026 17:28:21 +0000 https://status.velar.com/#e6b3781c557a657bc7464cd96fdd0dc94fb69f00d86e301f852fcf1de6629f41 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 08 Mar 2026 17:25:25 +0000 https://status.velar.com/#e6b3781c557a657bc7464cd96fdd0dc94fb69f00d86e301f852fcf1de6629f41 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 08 Mar 2026 12:28:20 +0000 https://status.velar.com/#5abf7081328117eee46c4dd1c0b00712324264d3569c485ea01249188979b496 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 08 Mar 2026 12:25:27 +0000 https://status.velar.com/#5abf7081328117eee46c4dd1c0b00712324264d3569c485ea01249188979b496 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 08 Mar 2026 06:16:26 +0000 https://status.velar.com/#19b95f2f2d5b0c4209d07380fb53e910019446b212d4aba24dc1976195a79a12 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 08 Mar 2026 06:07:18 +0000 https://status.velar.com/#19b95f2f2d5b0c4209d07380fb53e910019446b212d4aba24dc1976195a79a12 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 08 Mar 2026 05:13:40 +0000 https://status.velar.com/#90b4fd8bf45934d6cef85b8961b05e8a9ac15793e5d6bfedec5ca3e436454245 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 08 Mar 2026 05:10:25 +0000 https://status.velar.com/#90b4fd8bf45934d6cef85b8961b05e8a9ac15793e5d6bfedec5ca3e436454245 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 08 Mar 2026 03:10:26 +0000 https://status.velar.com/#c0d265963b9432e83c3eddc3f3b17fffc952a6143812a3334e1cd40c02ea1cc7 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 08 Mar 2026 03:07:16 +0000 https://status.velar.com/#c0d265963b9432e83c3eddc3f3b17fffc952a6143812a3334e1cd40c02ea1cc7 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 22:58:24 +0000 https://status.velar.com/#fa0880dde53396275feae3f8872fedf87bf71b9a098e2b17c1f7de1147670d8a Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 22:55:17 +0000 https://status.velar.com/#fa0880dde53396275feae3f8872fedf87bf71b9a098e2b17c1f7de1147670d8a Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 17:40:24 +0000 https://status.velar.com/#3a381b11ecb1c82e751793e511f571011c82cb311c546a60367405aaf89e8833 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 17:34:25 +0000 https://status.velar.com/#3a381b11ecb1c82e751793e511f571011c82cb311c546a60367405aaf89e8833 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 17:32:20 +0000 https://status.velar.com/#9d60fa56411de94ddce38ce0fafa09ad4e988a48208ac0a5684c38de8da4d30b api.velar.co recovered https://status.velar.com/ Sat, 07 Mar 2026 17:29:14 +0000 https://status.velar.com/#9d60fa56411de94ddce38ce0fafa09ad4e988a48208ac0a5684c38de8da4d30b api.velar.co went down https://status.velar.com/ Sat, 07 Mar 2026 17:28:20 +0000 https://status.velar.com/#850e418166c9cb3489cec373097e842b710a07ebf0c1c038fffd8cc5edf97de3 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 17:04:24 +0000 https://status.velar.com/#850e418166c9cb3489cec373097e842b710a07ebf0c1c038fffd8cc5edf97de3 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 16:46:22 +0000 https://status.velar.com/#e5288cd91c040b1a87d3303ee564bd175648498898037d994c432a756b40558a Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 16:40:23 +0000 https://status.velar.com/#e5288cd91c040b1a87d3303ee564bd175648498898037d994c432a756b40558a Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 16:10:19 +0000 https://status.velar.com/#09eef76a11e6f1ab608cd70a53c20bce35011e5c85684b3d876907c35a9f607a Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 16:04:22 +0000 https://status.velar.com/#09eef76a11e6f1ab608cd70a53c20bce35011e5c85684b3d876907c35a9f607a Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 15:58:25 +0000 https://status.velar.com/#1af25dc4c9ffc7b067e3f32f9429447a46b3366656af291c22fdeaf98db76b52 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 15:55:25 +0000 https://status.velar.com/#1af25dc4c9ffc7b067e3f32f9429447a46b3366656af291c22fdeaf98db76b52 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 15:46:25 +0000 https://status.velar.com/#94724ee7303a8f4bd3e78d7051ede2d2b72abbed78045dc3c8b14fc057653219 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 15:43:18 +0000 https://status.velar.com/#94724ee7303a8f4bd3e78d7051ede2d2b72abbed78045dc3c8b14fc057653219 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 15:31:26 +0000 https://status.velar.com/#0fa414b83dd84ec720950eb0ddaedbd54c6ae4da530ca5b10228a89c6eb9aa47 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 15:25:28 +0000 https://status.velar.com/#0fa414b83dd84ec720950eb0ddaedbd54c6ae4da530ca5b10228a89c6eb9aa47 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 15:16:26 +0000 https://status.velar.com/#579c28393b7e69b8da9bc7cfb4b61ff330a829ed56cea41c8c6a71949a4b09a5 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 15:10:25 +0000 https://status.velar.com/#579c28393b7e69b8da9bc7cfb4b61ff330a829ed56cea41c8c6a71949a4b09a5 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 14:43:25 +0000 https://status.velar.com/#3cc7c8e88ce8eef1dd853a38593d0bcb64c94544fa5eca25a55f339facfff70f Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 14:41:13 +0000 https://status.velar.com/#03d8eca145d4a3de9d3e6f9c91d8978b9b75d425e055ad1de4cb8bc4168934ab api.velar.co recovered https://status.velar.com/ Sat, 07 Mar 2026 14:38:10 +0000 https://status.velar.com/#03d8eca145d4a3de9d3e6f9c91d8978b9b75d425e055ad1de4cb8bc4168934ab api.velar.co went down https://status.velar.com/ Sat, 07 Mar 2026 14:34:24 +0000 https://status.velar.com/#3cc7c8e88ce8eef1dd853a38593d0bcb64c94544fa5eca25a55f339facfff70f Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 14:31:18 +0000 https://status.velar.com/#83524259091db9f201bde762485923be6af0deb6627a4b21dad3a41a429844a2 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 14:28:21 +0000 https://status.velar.com/#83524259091db9f201bde762485923be6af0deb6627a4b21dad3a41a429844a2 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 14:22:22 +0000 https://status.velar.com/#83918cdfd6251cd36fe3b22fc6c0661b617ff888c7c3ce5976d908a3f1eacee3 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 13:49:25 +0000 https://status.velar.com/#83918cdfd6251cd36fe3b22fc6c0661b617ff888c7c3ce5976d908a3f1eacee3 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 13:40:17 +0000 https://status.velar.com/#86f523b4e69c9c915c68cc84bd0ed50c6953c521eee5cdfb30c8aa43c72f7bf8 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 13:28:25 +0000 https://status.velar.com/#86f523b4e69c9c915c68cc84bd0ed50c6953c521eee5cdfb30c8aa43c72f7bf8 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 13:19:22 +0000 https://status.velar.com/#29a89090415f1dfd05728570a001a71b890db0b521a6bb5d0ec8a6acdcb8ab63 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 12:52:23 +0000 https://status.velar.com/#29a89090415f1dfd05728570a001a71b890db0b521a6bb5d0ec8a6acdcb8ab63 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 12:34:20 +0000 https://status.velar.com/#a0693360b9a9ce506ec61f99d867dd288ce3a42e684c82aa61c2d67fb24871f6 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 12:25:37 +0000 https://status.velar.com/#a0693360b9a9ce506ec61f99d867dd288ce3a42e684c82aa61c2d67fb24871f6 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 12:01:25 +0000 https://status.velar.com/#a5d8db4aba3486c1733c9b642125a3563196b5ef36ad7ea334ed6ab834ad385e Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 11:34:25 +0000 https://status.velar.com/#a5d8db4aba3486c1733c9b642125a3563196b5ef36ad7ea334ed6ab834ad385e Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 11:10:26 +0000 https://status.velar.com/#3d400ec9b91736353ef44ce440275ca6efe4454acb248b01c36fe20e970ae103 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 10:28:22 +0000 https://status.velar.com/#3d400ec9b91736353ef44ce440275ca6efe4454acb248b01c36fe20e970ae103 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 10:22:24 +0000 https://status.velar.com/#f7a0fed82e6c1b4d469213e107ef7fe0239058c1e23d71cf2f48267222e53fd4 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 09:22:24 +0000 https://status.velar.com/#f7a0fed82e6c1b4d469213e107ef7fe0239058c1e23d71cf2f48267222e53fd4 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 09:04:20 +0000 https://status.velar.com/#42dc196a435d07258b8bd74a1a1e1904114b6e0487bfb3cd5ce3d59b61b9d653 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 08:58:19 +0000 https://status.velar.com/#42dc196a435d07258b8bd74a1a1e1904114b6e0487bfb3cd5ce3d59b61b9d653 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 08:43:21 +0000 https://status.velar.com/#174554c975a54e06ade58b2dfe08e45b259b7523661b3af6fbc7cbe777427614 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 08:37:24 +0000 https://status.velar.com/#174554c975a54e06ade58b2dfe08e45b259b7523661b3af6fbc7cbe777427614 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 08:28:19 +0000 https://status.velar.com/#c7ec37ed72602d8b88edfefead8f615c91af38a258c2feee2700a802c1ccd746 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 08:13:25 +0000 https://status.velar.com/#c7ec37ed72602d8b88edfefead8f615c91af38a258c2feee2700a802c1ccd746 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 07:58:24 +0000 https://status.velar.com/#ec732ab42eaf31d41bdc0fbf4fc3baa7dc9c3e41753f9abf7a629506589619bf Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 07:10:21 +0000 https://status.velar.com/#ec732ab42eaf31d41bdc0fbf4fc3baa7dc9c3e41753f9abf7a629506589619bf Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 06:58:27 +0000 https://status.velar.com/#1acd554f6c38fe14b07fe5cc16c88619ef2120f9db5ca7ee855dc67bde2b443b Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 06:46:25 +0000 https://status.velar.com/#1acd554f6c38fe14b07fe5cc16c88619ef2120f9db5ca7ee855dc67bde2b443b Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 06:43:18 +0000 https://status.velar.com/#64608a52468ddd45bf36155ddf9fc16132106c31c9e03a12918b96f7c4d6caf9 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 06:40:22 +0000 https://status.velar.com/#64608a52468ddd45bf36155ddf9fc16132106c31c9e03a12918b96f7c4d6caf9 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 06:34:24 +0000 https://status.velar.com/#6c4d4bf5e6046d2d681b399a7c517cc9d04293c2c7d0e2cf7de5f9cda74767df Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 06:28:22 +0000 https://status.velar.com/#6c4d4bf5e6046d2d681b399a7c517cc9d04293c2c7d0e2cf7de5f9cda74767df Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 06:19:27 +0000 https://status.velar.com/#e415cf4fe957ecb9d2b50608886895e765130baadc2b849d85636541f0b87f3c Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 06:10:53 +0000 https://status.velar.com/#e415cf4fe957ecb9d2b50608886895e765130baadc2b849d85636541f0b87f3c Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 05:58:22 +0000 https://status.velar.com/#294ed790e6f2b51073bfb5e19befb2327c4798454b51278049597c59684b643e Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 05:40:23 +0000 https://status.velar.com/#294ed790e6f2b51073bfb5e19befb2327c4798454b51278049597c59684b643e Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 05:31:18 +0000 https://status.velar.com/#4224b278f0a9d32f5f9a81e2fadd2665389361c19a6fcef825a1ea640e36a5bc Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 05:22:20 +0000 https://status.velar.com/#4224b278f0a9d32f5f9a81e2fadd2665389361c19a6fcef825a1ea640e36a5bc Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 05:16:21 +0000 https://status.velar.com/#0857621d19628d68461f69571112c6c7d7904436951bb23285c4aafa1c630f56 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 05:13:25 +0000 https://status.velar.com/#0857621d19628d68461f69571112c6c7d7904436951bb23285c4aafa1c630f56 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 05:07:28 +0000 https://status.velar.com/#5ca2d636b33b29ca4309ae4c18544f8efadd13d95f34e12ec125a64979d035eb Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 04:55:19 +0000 https://status.velar.com/#5ca2d636b33b29ca4309ae4c18544f8efadd13d95f34e12ec125a64979d035eb Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 04:46:20 +0000 https://status.velar.com/#f4216eacdf689ba587f6df2b5e643c03367d33bd8479effbe608a255cd1e43a6 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 04:04:22 +0000 https://status.velar.com/#f4216eacdf689ba587f6df2b5e643c03367d33bd8479effbe608a255cd1e43a6 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 03:34:20 +0000 https://status.velar.com/#db5f26978a7b96c4e06c07bdeb014f6c1df260a79b678e4312fd666641c46184 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 03:25:27 +0000 https://status.velar.com/#db5f26978a7b96c4e06c07bdeb014f6c1df260a79b678e4312fd666641c46184 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 03:19:25 +0000 https://status.velar.com/#15dfefa14793cf362069d3f09a94b5c288273588621625973941751926ab0010 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 02:37:21 +0000 https://status.velar.com/#15dfefa14793cf362069d3f09a94b5c288273588621625973941751926ab0010 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 02:31:15 +0000 https://status.velar.com/#d33cfd8dab1cdfa6a1548c021636e60bc4f76106c8db868a168252eb9916b1d4 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 02:13:24 +0000 https://status.velar.com/#d33cfd8dab1cdfa6a1548c021636e60bc4f76106c8db868a168252eb9916b1d4 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 01:52:23 +0000 https://status.velar.com/#246b3caaf00c8ba4bad159493b4c93ed84a18637b4c1d4c5b3283c9294282412 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 01:46:19 +0000 https://status.velar.com/#246b3caaf00c8ba4bad159493b4c93ed84a18637b4c1d4c5b3283c9294282412 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 01:28:22 +0000 https://status.velar.com/#94dee900089c1d5b99c8850d8304e1b411148d2377dfe6714d21817f144e71f3 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 01:25:23 +0000 https://status.velar.com/#94dee900089c1d5b99c8850d8304e1b411148d2377dfe6714d21817f144e71f3 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 01:19:15 +0000 https://status.velar.com/#cda4413a35470e676f3057bf79231e13f7baf62b54d2fad20a446ccf54f8be42 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 01:16:22 +0000 https://status.velar.com/#cda4413a35470e676f3057bf79231e13f7baf62b54d2fad20a446ccf54f8be42 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 00:58:27 +0000 https://status.velar.com/#4dce0f9de99144e84e700443adf7f460b2f96fab6ae79868207bd5d7eaea1960 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 00:55:27 +0000 https://status.velar.com/#4dce0f9de99144e84e700443adf7f460b2f96fab6ae79868207bd5d7eaea1960 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 00:34:21 +0000 https://status.velar.com/#b093396fb343a70408bd81fe1554ef11de032e6151c172c6c138aad25d882a6e Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 00:28:21 +0000 https://status.velar.com/#b093396fb343a70408bd81fe1554ef11de032e6151c172c6c138aad25d882a6e Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 07 Mar 2026 00:07:20 +0000 https://status.velar.com/#5de17e5b9ad319571cd60509a2d3bf4633bb0b0e605a29889b609753ccd1cf9b Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 07 Mar 2026 00:04:19 +0000 https://status.velar.com/#5de17e5b9ad319571cd60509a2d3bf4633bb0b0e605a29889b609753ccd1cf9b Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 23:52:20 +0000 https://status.velar.com/#3e32d11b8abbac6f8b46c49414b497b77d662752d75318e8edfecc0bc926bbfa Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 23:28:23 +0000 https://status.velar.com/#3e32d11b8abbac6f8b46c49414b497b77d662752d75318e8edfecc0bc926bbfa Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 23:22:21 +0000 https://status.velar.com/#e41a0a7b618aae0f8c8af3807d05a98ce5aa184675881352a7210ca3a3ef26ec Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 23:19:25 +0000 https://status.velar.com/#e41a0a7b618aae0f8c8af3807d05a98ce5aa184675881352a7210ca3a3ef26ec Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 23:16:21 +0000 https://status.velar.com/#e73f8796d0b955381e913ff57b5b3db3ecc3d949d90d4fc796c4380e43a4dcab Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 22:58:24 +0000 https://status.velar.com/#e73f8796d0b955381e913ff57b5b3db3ecc3d949d90d4fc796c4380e43a4dcab Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 22:19:17 +0000 https://status.velar.com/#483602bd0a99329f8037ce6e3314b76329005164339d8e72ab7864858527e758 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 22:07:26 +0000 https://status.velar.com/#483602bd0a99329f8037ce6e3314b76329005164339d8e72ab7864858527e758 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 22:01:24 +0000 https://status.velar.com/#68767cbb466108d8f597e5caf368b10f677361f10d4588d8159200f55de59d9b Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 21:55:27 +0000 https://status.velar.com/#68767cbb466108d8f597e5caf368b10f677361f10d4588d8159200f55de59d9b Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 21:46:24 +0000 https://status.velar.com/#81b4e13ec0cbf5405d0bd15a0e46e7c4d1c87316ba209232a804144a1fc7a41b Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 21:40:21 +0000 https://status.velar.com/#81b4e13ec0cbf5405d0bd15a0e46e7c4d1c87316ba209232a804144a1fc7a41b Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 21:34:21 +0000 https://status.velar.com/#e306c298200768bd4993c2678e4fd56c7b7ce167184dd305caeb6dd938197617 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 21:28:22 +0000 https://status.velar.com/#e306c298200768bd4993c2678e4fd56c7b7ce167184dd305caeb6dd938197617 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 20:52:23 +0000 https://status.velar.com/#10a97aa072ec5d3d082a1456da16bb6e1c8b6aadeac00d9c2e986d7425b1c05d Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 20:43:23 +0000 https://status.velar.com/#10a97aa072ec5d3d082a1456da16bb6e1c8b6aadeac00d9c2e986d7425b1c05d Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 20:22:21 +0000 https://status.velar.com/#ea6d7db476d220903ce848e714ed254568a20e913ea6b3ef335cba5c1ca9d37c Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 20:10:25 +0000 https://status.velar.com/#ea6d7db476d220903ce848e714ed254568a20e913ea6b3ef335cba5c1ca9d37c Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 19:40:24 +0000 https://status.velar.com/#2fa1dbc937f8aaa81f3c2917d9ba65011b801e31d879873f970c1682c56a1a9b Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 19:28:25 +0000 https://status.velar.com/#2fa1dbc937f8aaa81f3c2917d9ba65011b801e31d879873f970c1682c56a1a9b Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 19:22:24 +0000 https://status.velar.com/#919a810f480a3e337de7deaad001f1bfef0a0bb75f88e8a8b0ee545f2b90c6ec Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 19:19:15 +0000 https://status.velar.com/#919a810f480a3e337de7deaad001f1bfef0a0bb75f88e8a8b0ee545f2b90c6ec Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 19:13:24 +0000 https://status.velar.com/#5d6e3d385c5911e20ad7c3ba88972736df449ce51cfba852fdf94fc02d18e3f1 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 19:07:25 +0000 https://status.velar.com/#5d6e3d385c5911e20ad7c3ba88972736df449ce51cfba852fdf94fc02d18e3f1 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 19:01:26 +0000 https://status.velar.com/#57dd7f86f9bff829368a4ab2d5426f802a8b4e41fe641d0bbcb5dbf98ff583be Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 18:52:23 +0000 https://status.velar.com/#57dd7f86f9bff829368a4ab2d5426f802a8b4e41fe641d0bbcb5dbf98ff583be Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 18:46:24 +0000 https://status.velar.com/#1de317116c381a3e122bd82a4dfa60cefed5ea3ec252d0847dda86bae8bbdb25 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 18:19:26 +0000 https://status.velar.com/#1de317116c381a3e122bd82a4dfa60cefed5ea3ec252d0847dda86bae8bbdb25 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 18:13:23 +0000 https://status.velar.com/#dcbab24becb2c36afbbecda6a72bf9d05eb6bb7978dd97b886b551d39d5a2530 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 17:55:23 +0000 https://status.velar.com/#dcbab24becb2c36afbbecda6a72bf9d05eb6bb7978dd97b886b551d39d5a2530 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 17:31:21 +0000 https://status.velar.com/#c7099e810c6363c7ac12d57dabdcd2d6af3811945f119b8e1474dc92873aa921 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 17:13:24 +0000 https://status.velar.com/#c7099e810c6363c7ac12d57dabdcd2d6af3811945f119b8e1474dc92873aa921 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 16:25:24 +0000 https://status.velar.com/#bae3d473c8e0aa8e5b38718a1d8f1d40fcb2fdce6ec9d6111ec6583cf0375f48 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 16:16:21 +0000 https://status.velar.com/#bae3d473c8e0aa8e5b38718a1d8f1d40fcb2fdce6ec9d6111ec6583cf0375f48 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 16:04:23 +0000 https://status.velar.com/#759fdb15802c6d2eb5c1fa4ee45adce1e08a7cd5197d03d94d92e887f690d230 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 15:52:25 +0000 https://status.velar.com/#759fdb15802c6d2eb5c1fa4ee45adce1e08a7cd5197d03d94d92e887f690d230 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 15:43:20 +0000 https://status.velar.com/#caf7bdb54f037831c37579a879aabad3ac2b4a054e0382314f951152cce63e8b Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 15:40:22 +0000 https://status.velar.com/#caf7bdb54f037831c37579a879aabad3ac2b4a054e0382314f951152cce63e8b Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 15:19:26 +0000 https://status.velar.com/#0c9275037cb832dbcb14fb3ef4744d68f5072fd4c0bc781d8d86bad10f00d5bd Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 15:16:54 +0000 https://status.velar.com/#0c9275037cb832dbcb14fb3ef4744d68f5072fd4c0bc781d8d86bad10f00d5bd Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 15:01:28 +0000 https://status.velar.com/#c95aad3fb0d5ae2643f84626e336d6df52d4c41ad49b3fbbc4cd47e2568ad657 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 14:58:23 +0000 https://status.velar.com/#c95aad3fb0d5ae2643f84626e336d6df52d4c41ad49b3fbbc4cd47e2568ad657 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 14:28:23 +0000 https://status.velar.com/#139ca7abb94c9e2b99fec79479315484d30c163aa96c6ac5e34354b51c6593ee Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 14:13:27 +0000 https://status.velar.com/#139ca7abb94c9e2b99fec79479315484d30c163aa96c6ac5e34354b51c6593ee Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 14:01:31 +0000 https://status.velar.com/#e98a938d919c8cc8cb052faeca364d4e2cf2d21b087dd0c901b1c9f3a2f80fe6 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 13:52:20 +0000 https://status.velar.com/#e98a938d919c8cc8cb052faeca364d4e2cf2d21b087dd0c901b1c9f3a2f80fe6 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 13:40:22 +0000 https://status.velar.com/#31e7e1a972fd17e46031930ff74928288eb98d0e45bd6465b01647e61bc05e61 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 13:37:27 +0000 https://status.velar.com/#31e7e1a972fd17e46031930ff74928288eb98d0e45bd6465b01647e61bc05e61 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 13:31:28 +0000 https://status.velar.com/#05446a06debe9d517c7be36b80ab948ee34c917e1c30c6d9200c5028040cce3d Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 13:16:18 +0000 https://status.velar.com/#05446a06debe9d517c7be36b80ab948ee34c917e1c30c6d9200c5028040cce3d Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 12:46:28 +0000 https://status.velar.com/#b4860aca5baf618586048975f1a69051d01dfc0071624d32f0c433e0e38b6241 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 12:25:24 +0000 https://status.velar.com/#b4860aca5baf618586048975f1a69051d01dfc0071624d32f0c433e0e38b6241 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 12:19:25 +0000 https://status.velar.com/#90cd63e40e4535e2c94c2972b8ce5f3e9dbe2624bb6151a12ea1d5cab4d469ab Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 12:16:25 +0000 https://status.velar.com/#90cd63e40e4535e2c94c2972b8ce5f3e9dbe2624bb6151a12ea1d5cab4d469ab Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 11:49:26 +0000 https://status.velar.com/#2806477cefb7e8fbb7cd0d5c57f163d4139c838961e086eac26997d59fad4cc5 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 11:40:35 +0000 https://status.velar.com/#2806477cefb7e8fbb7cd0d5c57f163d4139c838961e086eac26997d59fad4cc5 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 11:31:15 +0000 https://status.velar.com/#f4243bd796b57171057f497c4bc715860a5571b5c5955e44ae96605b98bd86c9 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 11:25:24 +0000 https://status.velar.com/#f4243bd796b57171057f497c4bc715860a5571b5c5955e44ae96605b98bd86c9 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 11:16:22 +0000 https://status.velar.com/#bb70e4ef87ba7ad1bc1ebd4d523b325b0f626665267c3b57ad243a1ab9c29734 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 10:58:25 +0000 https://status.velar.com/#bb70e4ef87ba7ad1bc1ebd4d523b325b0f626665267c3b57ad243a1ab9c29734 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 10:28:23 +0000 https://status.velar.com/#6272595a9acc51ab0cb5b57ced9c4e7e7568748676051b5f0e83a033792477a5 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 10:25:22 +0000 https://status.velar.com/#6272595a9acc51ab0cb5b57ced9c4e7e7568748676051b5f0e83a033792477a5 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 10:19:18 +0000 https://status.velar.com/#e5955655b36fd6d71dfa26c1149a1c06ac777f7c2e05ae501fa8f42bc1766503 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 10:13:27 +0000 https://status.velar.com/#e5955655b36fd6d71dfa26c1149a1c06ac777f7c2e05ae501fa8f42bc1766503 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 09:25:25 +0000 https://status.velar.com/#16f0e379b5ab90afaf9e40f32e779861f2ea8505b46cc1e9387fe32c1dcaa615 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 09:16:24 +0000 https://status.velar.com/#16f0e379b5ab90afaf9e40f32e779861f2ea8505b46cc1e9387fe32c1dcaa615 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 09:07:19 +0000 https://status.velar.com/#a27f42aaffbc3acb8927edcd9ffbc23ca656c3e6f80423d907b80391d4a305e1 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 08:25:24 +0000 https://status.velar.com/#a27f42aaffbc3acb8927edcd9ffbc23ca656c3e6f80423d907b80391d4a305e1 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 08:10:24 +0000 https://status.velar.com/#d8b84a86bbe7bc363994eea2f7822e2528e357e0e55090c5adceda6331e29cc2 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 08:07:19 +0000 https://status.velar.com/#d8b84a86bbe7bc363994eea2f7822e2528e357e0e55090c5adceda6331e29cc2 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 07:55:20 +0000 https://status.velar.com/#1fb844a08db572ce3cf7ad7661228675476b57c94d667f91bbb0615c18b9622c Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 07:52:22 +0000 https://status.velar.com/#1fb844a08db572ce3cf7ad7661228675476b57c94d667f91bbb0615c18b9622c Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 07:19:15 +0000 https://status.velar.com/#523d513345338378b33721376ade394c42849e8ac99a08d65569fd37d0ce5edb Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 06:46:26 +0000 https://status.velar.com/#523d513345338378b33721376ade394c42849e8ac99a08d65569fd37d0ce5edb Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 06:37:24 +0000 https://status.velar.com/#bcd837f802c3739119fa8aa471a379961ff63ab57d262dcc4b9bb4393bb29ba5 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 05:40:22 +0000 https://status.velar.com/#bcd837f802c3739119fa8aa471a379961ff63ab57d262dcc4b9bb4393bb29ba5 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 05:22:21 +0000 https://status.velar.com/#574ccccbbacca715547110ce3987987ed74eae22185a0feda20afed27151090a Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 05:16:22 +0000 https://status.velar.com/#574ccccbbacca715547110ce3987987ed74eae22185a0feda20afed27151090a Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 05:07:16 +0000 https://status.velar.com/#e8f5f8525b1ccb2cc0d416c50da28940ab3d53e9060abb4549f61963f7d788ff Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 04:55:15 +0000 https://status.velar.com/#e8f5f8525b1ccb2cc0d416c50da28940ab3d53e9060abb4549f61963f7d788ff Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 04:31:18 +0000 https://status.velar.com/#e35982f9d1b429117f92f1042cfc71fd632a48ca9ef40a64f2c19db15504e5fb Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 04:13:23 +0000 https://status.velar.com/#e35982f9d1b429117f92f1042cfc71fd632a48ca9ef40a64f2c19db15504e5fb Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 04:01:23 +0000 https://status.velar.com/#c65ee9f85620e63ff86fbddc3f09766c7d4d16de7030357eba84f19cdc7113d6 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 03:43:25 +0000 https://status.velar.com/#c65ee9f85620e63ff86fbddc3f09766c7d4d16de7030357eba84f19cdc7113d6 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 03:40:20 +0000 https://status.velar.com/#3b272cac1d291a8991d4e61b77962b00bdc775f66dfdf91c412396672ebedfd2 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 03:37:23 +0000 https://status.velar.com/#3b272cac1d291a8991d4e61b77962b00bdc775f66dfdf91c412396672ebedfd2 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 03:07:25 +0000 https://status.velar.com/#4984ae22d06ceb306e9121bbb4222932888d16159189bf75b47cdb068a13ec27 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 02:40:23 +0000 https://status.velar.com/#4984ae22d06ceb306e9121bbb4222932888d16159189bf75b47cdb068a13ec27 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 02:34:26 +0000 https://status.velar.com/#b2096c2f187f265a989592a9a6110abb3fde78b6120e55f6b8db9dffa6aa8cb7 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 02:04:23 +0000 https://status.velar.com/#b2096c2f187f265a989592a9a6110abb3fde78b6120e55f6b8db9dffa6aa8cb7 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 01:49:25 +0000 https://status.velar.com/#6bf434a04ae3300c5a27a673242728c9591f711a73015456ebf79e33cee08802 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 01:34:29 +0000 https://status.velar.com/#6bf434a04ae3300c5a27a673242728c9591f711a73015456ebf79e33cee08802 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 01:28:24 +0000 https://status.velar.com/#9df86d987302c5e01ac84b9baac2ea9eff775f2611aee646772206eba1deec64 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 01:25:24 +0000 https://status.velar.com/#9df86d987302c5e01ac84b9baac2ea9eff775f2611aee646772206eba1deec64 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 01:19:27 +0000 https://status.velar.com/#d80b1d24b563333d98cf0c1ce287033b7d62a7192718b1e0f1d2ae1d95f33056 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 01:16:23 +0000 https://status.velar.com/#d80b1d24b563333d98cf0c1ce287033b7d62a7192718b1e0f1d2ae1d95f33056 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 01:10:22 +0000 https://status.velar.com/#ee774c0937fe452f053b49bb0c4d323e309e0b4ec2246258a9f24ef0883569eb Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 00:40:22 +0000 https://status.velar.com/#ee774c0937fe452f053b49bb0c4d323e309e0b4ec2246258a9f24ef0883569eb Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 00:34:22 +0000 https://status.velar.com/#88c563a76118b54d78960a8ec4a903ed5e2ad5c8165de4975d71f922b461624f Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 00:28:19 +0000 https://status.velar.com/#88c563a76118b54d78960a8ec4a903ed5e2ad5c8165de4975d71f922b461624f Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 00:22:25 +0000 https://status.velar.com/#e80ee71554c7cd76c5cf535bd70af1dc74501deb16e77e00cdb4004275d8038a Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 06 Mar 2026 00:10:27 +0000 https://status.velar.com/#e80ee71554c7cd76c5cf535bd70af1dc74501deb16e77e00cdb4004275d8038a Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 06 Mar 2026 00:01:24 +0000 https://status.velar.com/#7beaa7433f43fa9f3f3711ad4fdfca418fa97b97238f32b13ed9169cfc5e11ff Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 05 Mar 2026 23:43:19 +0000 https://status.velar.com/#7beaa7433f43fa9f3f3711ad4fdfca418fa97b97238f32b13ed9169cfc5e11ff Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 05 Mar 2026 23:34:27 +0000 https://status.velar.com/#bda6f023c8ce1c4c376a94d3ff8733aa417274467fbbfce50b38c769c1c1c221 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 05 Mar 2026 22:52:20 +0000 https://status.velar.com/#bda6f023c8ce1c4c376a94d3ff8733aa417274467fbbfce50b38c769c1c1c221 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 05 Mar 2026 22:46:19 +0000 https://status.velar.com/#1ea883b3608e8e4411a42d3b31b0844251972027d3ff3e9aa3ee241e29b24d05 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 05 Mar 2026 22:10:23 +0000 https://status.velar.com/#1ea883b3608e8e4411a42d3b31b0844251972027d3ff3e9aa3ee241e29b24d05 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 05 Mar 2026 21:52:24 +0000 https://status.velar.com/#adf5508a856c7aa7c2a6acae9b553d916ede1c7b52bfca3bad8d13e0ef2c305f Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 05 Mar 2026 21:34:20 +0000 https://status.velar.com/#adf5508a856c7aa7c2a6acae9b553d916ede1c7b52bfca3bad8d13e0ef2c305f Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 05 Mar 2026 21:25:23 +0000 https://status.velar.com/#d30ee3e1086d927f1cc69d64319daf0a6c24c8e4037a0a5bf994b685239dc847 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 05 Mar 2026 21:07:26 +0000 https://status.velar.com/#d30ee3e1086d927f1cc69d64319daf0a6c24c8e4037a0a5bf994b685239dc847 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 05 Mar 2026 20:55:24 +0000 https://status.velar.com/#80c70569d01685a42c9754cd959c152cde6cb590c44b7bb6f70fd143ad7f38c2 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 05 Mar 2026 20:49:25 +0000 https://status.velar.com/#80c70569d01685a42c9754cd959c152cde6cb590c44b7bb6f70fd143ad7f38c2 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 05 Mar 2026 20:37:23 +0000 https://status.velar.com/#e166873d281fa9ac1bd5ac623d9fb71cadc6283efd1f73e650dd440f4f305eca Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 05 Mar 2026 20:28:19 +0000 https://status.velar.com/#e166873d281fa9ac1bd5ac623d9fb71cadc6283efd1f73e650dd440f4f305eca Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 05 Mar 2026 20:07:19 +0000 https://status.velar.com/#25210646243ab549f81f9a8d6d0e315ba7bbe96a5ab581c5e1996ae63039327d Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 05 Mar 2026 19:37:28 +0000 https://status.velar.com/#25210646243ab549f81f9a8d6d0e315ba7bbe96a5ab581c5e1996ae63039327d Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 05 Mar 2026 19:28:26 +0000 https://status.velar.com/#0b337413286fa91f7c2756ac388585099864d635caae0870d2390f3c0d65a2c3 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 05 Mar 2026 18:49:23 +0000 https://status.velar.com/#0b337413286fa91f7c2756ac388585099864d635caae0870d2390f3c0d65a2c3 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 05 Mar 2026 18:43:27 +0000 https://status.velar.com/#c11f96f021c6cf4281249120ddcdb546dee7e8801d288e583d071e1f7571e26f Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 05 Mar 2026 18:40:22 +0000 https://status.velar.com/#c11f96f021c6cf4281249120ddcdb546dee7e8801d288e583d071e1f7571e26f Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 05 Mar 2026 18:22:25 +0000 https://status.velar.com/#fd790f5fd869c5adb607c94b329420cfd2ed56a39288eaef1b3db9d52f819f4b Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 05 Mar 2026 18:04:19 +0000 https://status.velar.com/#fd790f5fd869c5adb607c94b329420cfd2ed56a39288eaef1b3db9d52f819f4b Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 05 Mar 2026 17:46:22 +0000 https://status.velar.com/#21c0229b09e6c1f18ef8d24da28de554ba6605275cfca38a416d23719cbe5101 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 05 Mar 2026 17:37:24 +0000 https://status.velar.com/#21c0229b09e6c1f18ef8d24da28de554ba6605275cfca38a416d23719cbe5101 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 05 Mar 2026 17:19:25 +0000 https://status.velar.com/#89d5a5f57cdf854d01b51fe7a8573deb9957908f6d1d99703f54685a93427331 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 05 Mar 2026 17:01:23 +0000 https://status.velar.com/#89d5a5f57cdf854d01b51fe7a8573deb9957908f6d1d99703f54685a93427331 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 05 Mar 2026 16:43:30 +0000 https://status.velar.com/#6c0738fa4822178060fda70cba60724fc90292272a769637d54fdb32a6e96949 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 05 Mar 2026 16:25:25 +0000 https://status.velar.com/#6c0738fa4822178060fda70cba60724fc90292272a769637d54fdb32a6e96949 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 05 Mar 2026 15:22:26 +0000 https://status.velar.com/#db747ca7f3788f10f2b06385f4c23615716b423963333ae3bb9d407aae54e545 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 05 Mar 2026 15:19:16 +0000 https://status.velar.com/#db747ca7f3788f10f2b06385f4c23615716b423963333ae3bb9d407aae54e545 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 05 Mar 2026 14:49:30 +0000 https://status.velar.com/#a309e64a7521f86afb80cca46a772451a4e79a3a7718db9512f272eec9ff363c Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 05 Mar 2026 14:37:21 +0000 https://status.velar.com/#a309e64a7521f86afb80cca46a772451a4e79a3a7718db9512f272eec9ff363c Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 05 Mar 2026 14:04:22 +0000 https://status.velar.com/#8bcdf4d31aac3ad12cda8cafa837a21561a99f0584f7aa7b7da8a0b7daad0b90 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 05 Mar 2026 13:55:26 +0000 https://status.velar.com/#8bcdf4d31aac3ad12cda8cafa837a21561a99f0584f7aa7b7da8a0b7daad0b90 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 05 Mar 2026 13:31:20 +0000 https://status.velar.com/#dfc6dcc6d97138080988d7318c5ee6795a7689b1af95b0e15772dfb815276b13 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 05 Mar 2026 13:25:23 +0000 https://status.velar.com/#dfc6dcc6d97138080988d7318c5ee6795a7689b1af95b0e15772dfb815276b13 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 05 Mar 2026 13:01:31 +0000 https://status.velar.com/#61b89f58da0daae3cbfe432f69a9951b570b72cab2b673685e5c7e36cdaac10c Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 05 Mar 2026 12:49:20 +0000 https://status.velar.com/#61b89f58da0daae3cbfe432f69a9951b570b72cab2b673685e5c7e36cdaac10c Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 05 Mar 2026 12:04:20 +0000 https://status.velar.com/#48d5e09880ec0f99061bfed9d56b0573cc2b6592fcde09afe0b89181a7d449f6 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 05 Mar 2026 11:55:24 +0000 https://status.velar.com/#48d5e09880ec0f99061bfed9d56b0573cc2b6592fcde09afe0b89181a7d449f6 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 05 Mar 2026 11:25:22 +0000 https://status.velar.com/#1f66133051ee2eae43a7b78d5a77339a86e0f5761a633333d425f38a5712cf78 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 05 Mar 2026 11:10:29 +0000 https://status.velar.com/#1f66133051ee2eae43a7b78d5a77339a86e0f5761a633333d425f38a5712cf78 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 05 Mar 2026 11:01:23 +0000 https://status.velar.com/#7770708ee7f06a455595614e20f9dfe25b64db0ee5d1c78e1c344106c0c7660d Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 05 Mar 2026 10:55:34 +0000 https://status.velar.com/#7770708ee7f06a455595614e20f9dfe25b64db0ee5d1c78e1c344106c0c7660d Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 05 Mar 2026 10:52:19 +0000 https://status.velar.com/#8bc7552f8e5778ca473b460e5befc25a528e1f8a302a383b0f4b3bec9ba50876 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 05 Mar 2026 09:52:18 +0000 https://status.velar.com/#8bc7552f8e5778ca473b460e5befc25a528e1f8a302a383b0f4b3bec9ba50876 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 05 Mar 2026 08:01:25 +0000 https://status.velar.com/#3fba2043d1dd640e0d21f8a7b69b74b9107b21a6cb12c3f8b7a17353f7c28d19 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 05 Mar 2026 07:55:26 +0000 https://status.velar.com/#3fba2043d1dd640e0d21f8a7b69b74b9107b21a6cb12c3f8b7a17353f7c28d19 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 05 Mar 2026 07:25:26 +0000 https://status.velar.com/#a5f871515c09006f7c406f2835ea401a7b871ee8917f2f1d571d8a7f198277f4 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 05 Mar 2026 07:10:19 +0000 https://status.velar.com/#a5f871515c09006f7c406f2835ea401a7b871ee8917f2f1d571d8a7f198277f4 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 05 Mar 2026 06:49:22 +0000 https://status.velar.com/#dfa62b11a4d917ecac4c648b875a8a48e0dfb117aab8fb5245734aa725283602 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 05 Mar 2026 06:40:21 +0000 https://status.velar.com/#dfa62b11a4d917ecac4c648b875a8a48e0dfb117aab8fb5245734aa725283602 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 05 Mar 2026 06:10:26 +0000 https://status.velar.com/#0bef01738aedd67dd0b44ab003be81b73c77cb2dcd2f55f1f479150a797c8aef Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 05 Mar 2026 05:55:22 +0000 https://status.velar.com/#0bef01738aedd67dd0b44ab003be81b73c77cb2dcd2f55f1f479150a797c8aef Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 05 Mar 2026 04:37:30 +0000 https://status.velar.com/#eb0d78937f579e2109beed2ed6c596509fbe8331fffd4e682ed4f7b25023bc70 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 05 Mar 2026 04:34:26 +0000 https://status.velar.com/#eb0d78937f579e2109beed2ed6c596509fbe8331fffd4e682ed4f7b25023bc70 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 05 Mar 2026 03:43:26 +0000 https://status.velar.com/#040ea9ceffadaf01b0c3ca37f9fafa8a4e4a9371815e24d75ca8ee876746db71 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 05 Mar 2026 03:40:20 +0000 https://status.velar.com/#040ea9ceffadaf01b0c3ca37f9fafa8a4e4a9371815e24d75ca8ee876746db71 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 05 Mar 2026 03:22:26 +0000 https://status.velar.com/#7753b2cf713f6b0719821d6709e57a1d4738e26aaa0a308f7f6b2557816d011c Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 05 Mar 2026 03:13:22 +0000 https://status.velar.com/#7753b2cf713f6b0719821d6709e57a1d4738e26aaa0a308f7f6b2557816d011c Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 05 Mar 2026 02:49:26 +0000 https://status.velar.com/#51e58226c7a77fa2925a387da5abe67b1f69763d991f528405c474bb3e8fcb34 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 05 Mar 2026 02:43:17 +0000 https://status.velar.com/#51e58226c7a77fa2925a387da5abe67b1f69763d991f528405c474bb3e8fcb34 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 05 Mar 2026 02:07:20 +0000 https://status.velar.com/#e9718c220ac86810fdd4f43fcd633e2f6e30516e85408f85cc2d2a83f4b10d8b Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 05 Mar 2026 02:04:21 +0000 https://status.velar.com/#e9718c220ac86810fdd4f43fcd633e2f6e30516e85408f85cc2d2a83f4b10d8b Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 05 Mar 2026 01:46:23 +0000 https://status.velar.com/#b9cd06c369e7ac1116300e351a2e5bd8d6ab68786c20b272dec19c36b5906cc0 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 05 Mar 2026 01:43:21 +0000 https://status.velar.com/#b9cd06c369e7ac1116300e351a2e5bd8d6ab68786c20b272dec19c36b5906cc0 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 05 Mar 2026 01:28:22 +0000 https://status.velar.com/#c324d91eb45e7030779de5be91e8e6379ffd38af4db77906e709dec14b51a2d7 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 05 Mar 2026 01:16:27 +0000 https://status.velar.com/#c324d91eb45e7030779de5be91e8e6379ffd38af4db77906e709dec14b51a2d7 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 05 Mar 2026 00:58:29 +0000 https://status.velar.com/#e9ca1914af8d6fc8f7e88274e0b4707cfbc208c5fabb791f8052a247371310e2 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 05 Mar 2026 00:37:23 +0000 https://status.velar.com/#e9ca1914af8d6fc8f7e88274e0b4707cfbc208c5fabb791f8052a247371310e2 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 05 Mar 2026 00:19:20 +0000 https://status.velar.com/#db62a60897e96e9d22f2f1b9ebfe566038d2b0b8c7b021d09e600eac4131dc54 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 05 Mar 2026 00:16:21 +0000 https://status.velar.com/#db62a60897e96e9d22f2f1b9ebfe566038d2b0b8c7b021d09e600eac4131dc54 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 05 Mar 2026 00:01:26 +0000 https://status.velar.com/#b14e3678d7eb79697713f75f5dcf575e51c38ccab68dd051e94147458f92a89e Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 04 Mar 2026 23:52:22 +0000 https://status.velar.com/#b14e3678d7eb79697713f75f5dcf575e51c38ccab68dd051e94147458f92a89e Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 04 Mar 2026 23:16:19 +0000 https://status.velar.com/#1b1f1ab3cf7192c082dc7a615d0ad42da47a3c46b1b71c6a81b84df98887a880 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 04 Mar 2026 23:04:21 +0000 https://status.velar.com/#1b1f1ab3cf7192c082dc7a615d0ad42da47a3c46b1b71c6a81b84df98887a880 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 04 Mar 2026 22:55:23 +0000 https://status.velar.com/#4a0c8fbdc2876b9f0ab3ab9053a4c2f16f62a8ddef767eceffd604df8456ca15 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 04 Mar 2026 22:43:23 +0000 https://status.velar.com/#4a0c8fbdc2876b9f0ab3ab9053a4c2f16f62a8ddef767eceffd604df8456ca15 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 04 Mar 2026 22:31:17 +0000 https://status.velar.com/#dd742853cef91dafcbded8185abc49cb8deab5825d856fde3933a4c24877a43c Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 04 Mar 2026 22:07:25 +0000 https://status.velar.com/#dd742853cef91dafcbded8185abc49cb8deab5825d856fde3933a4c24877a43c Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 04 Mar 2026 21:46:28 +0000 https://status.velar.com/#ce9006731ea1f77d14c9fd545a594a6305efc8042d57c0ce126466231fbe12e0 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 04 Mar 2026 21:43:26 +0000 https://status.velar.com/#ce9006731ea1f77d14c9fd545a594a6305efc8042d57c0ce126466231fbe12e0 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 04 Mar 2026 21:13:20 +0000 https://status.velar.com/#7fd25e184bd6abf2abafe74fecc954dd89813c126a40edc30610227341d144ed Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 04 Mar 2026 20:40:19 +0000 https://status.velar.com/#7fd25e184bd6abf2abafe74fecc954dd89813c126a40edc30610227341d144ed Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 04 Mar 2026 19:55:26 +0000 https://status.velar.com/#f304651bc2197fcf5c67dea8d2073fcaf25f793a239e1a48ae5d1c7fa92bd3c4 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 04 Mar 2026 19:40:19 +0000 https://status.velar.com/#f304651bc2197fcf5c67dea8d2073fcaf25f793a239e1a48ae5d1c7fa92bd3c4 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 04 Mar 2026 19:22:22 +0000 https://status.velar.com/#7e9e8c4a9ecba477dab6d02f09d16a38508a34eec73fa8610214ac972c0afc31 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 04 Mar 2026 19:10:27 +0000 https://status.velar.com/#7e9e8c4a9ecba477dab6d02f09d16a38508a34eec73fa8610214ac972c0afc31 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 04 Mar 2026 18:28:21 +0000 https://status.velar.com/#e7be81c23300c56f90931b2341df851501d26692e0b04e50d0146e792c79197c Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 04 Mar 2026 17:40:20 +0000 https://status.velar.com/#e7be81c23300c56f90931b2341df851501d26692e0b04e50d0146e792c79197c Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 04 Mar 2026 17:34:25 +0000 https://status.velar.com/#cdbef3eb768e89255c62b8b3f607a3865722084761280a99edd5efd5f6c6c258 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 04 Mar 2026 17:25:27 +0000 https://status.velar.com/#cdbef3eb768e89255c62b8b3f607a3865722084761280a99edd5efd5f6c6c258 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 04 Mar 2026 17:19:23 +0000 https://status.velar.com/#5f4495fb08279669549b07e9550c3c5f1a656ce27c3a46983b8127347e635747 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 04 Mar 2026 16:37:25 +0000 https://status.velar.com/#5f4495fb08279669549b07e9550c3c5f1a656ce27c3a46983b8127347e635747 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 04 Mar 2026 15:52:23 +0000 https://status.velar.com/#fef8b8f43f2d5a3c78ee16126601a2fdd0469c68bb3472edcc959345cdb26d5e Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 04 Mar 2026 15:46:26 +0000 https://status.velar.com/#fef8b8f43f2d5a3c78ee16126601a2fdd0469c68bb3472edcc959345cdb26d5e Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 04 Mar 2026 15:31:25 +0000 https://status.velar.com/#e04da91c328a8e3082e6837e2f3b595c84b6824c867137b84bf1758b5a2db68d Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 04 Mar 2026 15:28:21 +0000 https://status.velar.com/#e04da91c328a8e3082e6837e2f3b595c84b6824c867137b84bf1758b5a2db68d Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 04 Mar 2026 14:31:23 +0000 https://status.velar.com/#005d144f47f03c2d5db44111163d9a5d4cfc2642fc5c89f83876532d422d3158 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 04 Mar 2026 14:04:22 +0000 https://status.velar.com/#005d144f47f03c2d5db44111163d9a5d4cfc2642fc5c89f83876532d422d3158 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 04 Mar 2026 13:19:25 +0000 https://status.velar.com/#5c8b3f907d0931478f8552899d782731e708b91f3105cab5c6ecf3da383fdea6 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 04 Mar 2026 13:10:21 +0000 https://status.velar.com/#5c8b3f907d0931478f8552899d782731e708b91f3105cab5c6ecf3da383fdea6 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 04 Mar 2026 12:40:20 +0000 https://status.velar.com/#e873e3dde305fd70123e4919072def3eab4dcfb4ffdf599b37d374a195797541 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 04 Mar 2026 12:23:14 +0000 https://status.velar.com/#e873e3dde305fd70123e4919072def3eab4dcfb4ffdf599b37d374a195797541 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 04 Mar 2026 12:19:18 +0000 https://status.velar.com/#08b13e9254698640d3ea17b40f1d195a8395988f3617e75b1f4ee4ff57884f1c Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 04 Mar 2026 12:16:16 +0000 https://status.velar.com/#08b13e9254698640d3ea17b40f1d195a8395988f3617e75b1f4ee4ff57884f1c Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 04 Mar 2026 11:58:21 +0000 https://status.velar.com/#dd2577f32ff8f936bcf2fff51b946262e3eb0e863f9e750b75a196437b5c2169 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 04 Mar 2026 11:52:22 +0000 https://status.velar.com/#dd2577f32ff8f936bcf2fff51b946262e3eb0e863f9e750b75a196437b5c2169 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 04 Mar 2026 11:46:29 +0000 https://status.velar.com/#915875c9dfa6bb71c56e1bf1f4a85972da77cee18e62572af7463e9aa0920b82 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 04 Mar 2026 11:22:21 +0000 https://status.velar.com/#915875c9dfa6bb71c56e1bf1f4a85972da77cee18e62572af7463e9aa0920b82 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 04 Mar 2026 11:10:23 +0000 https://status.velar.com/#b07c9608c5255767f1f8f25aebe7a3de08ba05fa514f620166f4e8bb0029b4b9 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 04 Mar 2026 09:40:23 +0000 https://status.velar.com/#b07c9608c5255767f1f8f25aebe7a3de08ba05fa514f620166f4e8bb0029b4b9 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 04 Mar 2026 09:34:20 +0000 https://status.velar.com/#49543739914037243be3e6cd2eaa1bf1c38569aac1250cc40f3d17e3acd894ff Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 04 Mar 2026 08:52:30 +0000 https://status.velar.com/#49543739914037243be3e6cd2eaa1bf1c38569aac1250cc40f3d17e3acd894ff Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 04 Mar 2026 08:46:26 +0000 https://status.velar.com/#98e4b536bbb076917fe07fe11bafa436387f49e47a2d445a11f10064e5792a0e Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 04 Mar 2026 08:40:18 +0000 https://status.velar.com/#98e4b536bbb076917fe07fe11bafa436387f49e47a2d445a11f10064e5792a0e Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 04 Mar 2026 08:31:23 +0000 https://status.velar.com/#25cd2ec64d4c9590e0d9792a140e14aa27b7c4e12e7c9d188758a23e403a81e1 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 04 Mar 2026 08:25:23 +0000 https://status.velar.com/#25cd2ec64d4c9590e0d9792a140e14aa27b7c4e12e7c9d188758a23e403a81e1 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 04 Mar 2026 08:07:19 +0000 https://status.velar.com/#9ec623a8349ee9f6bd2944958621642b9e0e6e774c6baedb347d12fe2b2c0d88 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 04 Mar 2026 07:07:29 +0000 https://status.velar.com/#9ec623a8349ee9f6bd2944958621642b9e0e6e774c6baedb347d12fe2b2c0d88 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 04 Mar 2026 06:37:26 +0000 https://status.velar.com/#0e0f5af14aa47a2f1d731e64e42c3036125fb0c8febe3fdf9947d974f7d6a348 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 04 Mar 2026 06:34:20 +0000 https://status.velar.com/#0e0f5af14aa47a2f1d731e64e42c3036125fb0c8febe3fdf9947d974f7d6a348 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 04 Mar 2026 05:22:21 +0000 https://status.velar.com/#24281543edc04683d7a8d2b2892f65e0648902dbf34863f72204b609b5609f35 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 04 Mar 2026 05:13:40 +0000 https://status.velar.com/#24281543edc04683d7a8d2b2892f65e0648902dbf34863f72204b609b5609f35 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 04 Mar 2026 04:37:25 +0000 https://status.velar.com/#a8cdfebf79155aef96e779cd9df4fcf6cd136b1b730d0acc6cc308a24f1d2b12 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 04 Mar 2026 04:28:27 +0000 https://status.velar.com/#a8cdfebf79155aef96e779cd9df4fcf6cd136b1b730d0acc6cc308a24f1d2b12 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 04 Mar 2026 04:22:26 +0000 https://status.velar.com/#432e099d3f88878d2eec6e4e50acdbebd8051eda91ec2936dcc4842c928cc165 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 04 Mar 2026 04:16:17 +0000 https://status.velar.com/#432e099d3f88878d2eec6e4e50acdbebd8051eda91ec2936dcc4842c928cc165 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 04 Mar 2026 03:04:19 +0000 https://status.velar.com/#fae5f5c34e363487c8c9f0ba5ba292cb64f68ba5e8ba946c93cbaeb0396f32e9 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 04 Mar 2026 02:49:23 +0000 https://status.velar.com/#fae5f5c34e363487c8c9f0ba5ba292cb64f68ba5e8ba946c93cbaeb0396f32e9 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 04 Mar 2026 02:13:24 +0000 https://status.velar.com/#717595261430a6abff7c0d27ccd0f68f5b64be782a45900ebc45d73b64877327 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 04 Mar 2026 02:07:27 +0000 https://status.velar.com/#717595261430a6abff7c0d27ccd0f68f5b64be782a45900ebc45d73b64877327 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 04 Mar 2026 01:25:30 +0000 https://status.velar.com/#df41b6d3a6e3e598cdb117eaade7855c9d157b649e6b1a2e8930c8d96ff4daf1 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 04 Mar 2026 00:49:27 +0000 https://status.velar.com/#df41b6d3a6e3e598cdb117eaade7855c9d157b649e6b1a2e8930c8d96ff4daf1 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 04 Mar 2026 00:37:23 +0000 https://status.velar.com/#46da5b7824588699b46875a486dc358dd552df131fbde3ecd17a495ab7a7a56c Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 03 Mar 2026 23:52:19 +0000 https://status.velar.com/#46da5b7824588699b46875a486dc358dd552df131fbde3ecd17a495ab7a7a56c Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 03 Mar 2026 23:04:19 +0000 https://status.velar.com/#94d31c2f16ac667ecf29ca79d97a02d545432af37ce5d52202d0860d17929776 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 03 Mar 2026 23:01:27 +0000 https://status.velar.com/#94d31c2f16ac667ecf29ca79d97a02d545432af37ce5d52202d0860d17929776 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 03 Mar 2026 22:34:23 +0000 https://status.velar.com/#e811e57b4dcfa2de2dfaae9abd76b5c08d4e7140c4a30ce5c7ef0d0ca7dc31f9 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 03 Mar 2026 22:31:27 +0000 https://status.velar.com/#e811e57b4dcfa2de2dfaae9abd76b5c08d4e7140c4a30ce5c7ef0d0ca7dc31f9 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 03 Mar 2026 21:16:29 +0000 https://status.velar.com/#78fa9ae1b4500f431178276493c9966a19a01a3494cffc98ad6e50e83aa94c23 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 03 Mar 2026 21:13:29 +0000 https://status.velar.com/#78fa9ae1b4500f431178276493c9966a19a01a3494cffc98ad6e50e83aa94c23 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 03 Mar 2026 21:04:20 +0000 https://status.velar.com/#4e371d56ac033862164f55babf93355619fa5506595e79196679c1488c3f03e6 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 03 Mar 2026 20:37:26 +0000 https://status.velar.com/#4e371d56ac033862164f55babf93355619fa5506595e79196679c1488c3f03e6 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 03 Mar 2026 19:58:28 +0000 https://status.velar.com/#881f448a7addce040644ff5dcaf03e74223ba795eb47f07de897f8904ba3d90d Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 03 Mar 2026 19:49:26 +0000 https://status.velar.com/#881f448a7addce040644ff5dcaf03e74223ba795eb47f07de897f8904ba3d90d Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 03 Mar 2026 19:40:22 +0000 https://status.velar.com/#3a4a3eeed1549a13b6a16e71bfee326619fccc091db2def74e7a2439be9af651 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 03 Mar 2026 19:07:26 +0000 https://status.velar.com/#3a4a3eeed1549a13b6a16e71bfee326619fccc091db2def74e7a2439be9af651 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 03 Mar 2026 18:28:23 +0000 https://status.velar.com/#6e9bc58b39536473ab6a09227ac9bedcae6a666658aef5c11a3a4c8dac7c2e13 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 03 Mar 2026 18:25:24 +0000 https://status.velar.com/#6e9bc58b39536473ab6a09227ac9bedcae6a666658aef5c11a3a4c8dac7c2e13 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 03 Mar 2026 17:01:24 +0000 https://status.velar.com/#2fb80d811ff37dd384ef1bf9e404dcac2ad96d2060e7a387064994213a5a98ad Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 03 Mar 2026 16:58:28 +0000 https://status.velar.com/#2fb80d811ff37dd384ef1bf9e404dcac2ad96d2060e7a387064994213a5a98ad Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 03 Mar 2026 16:07:28 +0000 https://status.velar.com/#c53d942152480d8e6f2e25b21917bf01343d7d0d86fc22c82fbc11de456c82b4 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 03 Mar 2026 15:34:22 +0000 https://status.velar.com/#c53d942152480d8e6f2e25b21917bf01343d7d0d86fc22c82fbc11de456c82b4 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 03 Mar 2026 14:31:22 +0000 https://status.velar.com/#32e8bb64c3ad1e0da38bbc5b18108bf4600894be98cdcbec5d382d29909b16c3 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 03 Mar 2026 14:25:24 +0000 https://status.velar.com/#32e8bb64c3ad1e0da38bbc5b18108bf4600894be98cdcbec5d382d29909b16c3 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 03 Mar 2026 14:19:24 +0000 https://status.velar.com/#33ae496dd69a950d52d90b72e2602073c1deda628977d53d64d72b27667defad Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 03 Mar 2026 14:04:19 +0000 https://status.velar.com/#33ae496dd69a950d52d90b72e2602073c1deda628977d53d64d72b27667defad Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 03 Mar 2026 13:31:25 +0000 https://status.velar.com/#24f0e18db33decedc6195be06d96b3320d99294eacaf70b591cb17316bb08ec8 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 03 Mar 2026 13:19:21 +0000 https://status.velar.com/#24f0e18db33decedc6195be06d96b3320d99294eacaf70b591cb17316bb08ec8 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 03 Mar 2026 11:31:22 +0000 https://status.velar.com/#c8e575992b9fedb3e77740ee29a6ecadd24546331588c36c1106be03729a11ae Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 03 Mar 2026 11:01:23 +0000 https://status.velar.com/#c8e575992b9fedb3e77740ee29a6ecadd24546331588c36c1106be03729a11ae Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 03 Mar 2026 10:52:23 +0000 https://status.velar.com/#d64b2986988c74017bdd3a1531e82cebbdd8175df1567d60d8cbaa2771a1eb81 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 03 Mar 2026 10:34:29 +0000 https://status.velar.com/#d64b2986988c74017bdd3a1531e82cebbdd8175df1567d60d8cbaa2771a1eb81 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 03 Mar 2026 10:10:23 +0000 https://status.velar.com/#19cd29bc18a37fd065835d55970910aa902d3dde7b1c213d6fbfdab72e2ff3a8 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 03 Mar 2026 10:07:29 +0000 https://status.velar.com/#19cd29bc18a37fd065835d55970910aa902d3dde7b1c213d6fbfdab72e2ff3a8 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 03 Mar 2026 09:46:26 +0000 https://status.velar.com/#c55e349baca76b73f60b8d9577026008e9f5b8d19876084ff9a1a25abe9e7645 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 03 Mar 2026 09:13:22 +0000 https://status.velar.com/#c55e349baca76b73f60b8d9577026008e9f5b8d19876084ff9a1a25abe9e7645 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 03 Mar 2026 09:01:28 +0000 https://status.velar.com/#16463b30e2ee93fa8c9501c1b137c4eb6e94955bc835747bf73de9a7cea118d5 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 03 Mar 2026 08:43:23 +0000 https://status.velar.com/#16463b30e2ee93fa8c9501c1b137c4eb6e94955bc835747bf73de9a7cea118d5 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 03 Mar 2026 08:22:20 +0000 https://status.velar.com/#f3276bb62c2175b5f446a591d25ed2930ed0792d9b2d7b86271a471101cfee75 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 03 Mar 2026 08:04:17 +0000 https://status.velar.com/#f3276bb62c2175b5f446a591d25ed2930ed0792d9b2d7b86271a471101cfee75 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 03 Mar 2026 06:55:19 +0000 https://status.velar.com/#bd6499e88a208d803db6383e1dee3fdd2176f1555842b1296efcdb593936d579 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 03 Mar 2026 06:46:29 +0000 https://status.velar.com/#bd6499e88a208d803db6383e1dee3fdd2176f1555842b1296efcdb593936d579 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 03 Mar 2026 05:52:19 +0000 https://status.velar.com/#9e523cd7af27a5effc13381e1733e89ed486f490af7f36cc1ca040b5f3c0ea1d Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 03 Mar 2026 04:52:19 +0000 https://status.velar.com/#9e523cd7af27a5effc13381e1733e89ed486f490af7f36cc1ca040b5f3c0ea1d Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 03 Mar 2026 04:40:22 +0000 https://status.velar.com/#7e7b02784830fdf828821d5e7ce3a86b289645a362014276144ccb3b8f1643f7 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 03 Mar 2026 03:43:19 +0000 https://status.velar.com/#7e7b02784830fdf828821d5e7ce3a86b289645a362014276144ccb3b8f1643f7 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 03 Mar 2026 03:25:23 +0000 https://status.velar.com/#c69f1471e2571495f8890c56f54164d02ceb557375662d12fc94a420b66926ee Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 03 Mar 2026 03:13:21 +0000 https://status.velar.com/#c69f1471e2571495f8890c56f54164d02ceb557375662d12fc94a420b66926ee Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 03 Mar 2026 02:49:22 +0000 https://status.velar.com/#fcc47f94ee8aaca2c200f2727288963652e140ff55dccfb746a2361eb5577536 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 03 Mar 2026 02:31:18 +0000 https://status.velar.com/#fcc47f94ee8aaca2c200f2727288963652e140ff55dccfb746a2361eb5577536 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 03 Mar 2026 02:19:21 +0000 https://status.velar.com/#9e5472829de57dd785ed9938bbfac310fe0ddd207008cd8dfe9e699653d952d0 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 03 Mar 2026 01:31:21 +0000 https://status.velar.com/#9e5472829de57dd785ed9938bbfac310fe0ddd207008cd8dfe9e699653d952d0 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 02 Mar 2026 23:01:27 +0000 https://status.velar.com/#41b7211fa02a70b7ab5a74cca8a12564f9c3f18d9a96bc1d83a59ba902af5ad8 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 02 Mar 2026 22:58:28 +0000 https://status.velar.com/#41b7211fa02a70b7ab5a74cca8a12564f9c3f18d9a96bc1d83a59ba902af5ad8 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 02 Mar 2026 22:37:24 +0000 https://status.velar.com/#2651055496d26b69f8dab33cba4d5da7cc7c58b014ca938acd7bc7a6bdb22b5d Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 02 Mar 2026 22:34:25 +0000 https://status.velar.com/#2651055496d26b69f8dab33cba4d5da7cc7c58b014ca938acd7bc7a6bdb22b5d Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 02 Mar 2026 22:19:20 +0000 https://status.velar.com/#818eed1d5f82f03f3bd612616913d8f7ae75df9004ea12f26b41422b55afbe1c Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 02 Mar 2026 22:04:23 +0000 https://status.velar.com/#818eed1d5f82f03f3bd612616913d8f7ae75df9004ea12f26b41422b55afbe1c Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 02 Mar 2026 21:40:29 +0000 https://status.velar.com/#04a4afe5c928c8b7a9b2d7e69533ee2f8aba50db776a5defd9065acd17c7ee9d Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 02 Mar 2026 21:37:23 +0000 https://status.velar.com/#04a4afe5c928c8b7a9b2d7e69533ee2f8aba50db776a5defd9065acd17c7ee9d Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 02 Mar 2026 21:28:18 +0000 https://status.velar.com/#ecf6b26188cb1289fdadcf595a187f779265bf8a8f053a814a00419b1df02122 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 02 Mar 2026 21:07:17 +0000 https://status.velar.com/#ecf6b26188cb1289fdadcf595a187f779265bf8a8f053a814a00419b1df02122 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 02 Mar 2026 20:55:23 +0000 https://status.velar.com/#2c3943b1621b4e7ec7b6c20b976ee4cb20c5e70b23b42d8c3906dbd49a7a03a6 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 02 Mar 2026 19:46:24 +0000 https://status.velar.com/#2c3943b1621b4e7ec7b6c20b976ee4cb20c5e70b23b42d8c3906dbd49a7a03a6 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 02 Mar 2026 18:43:21 +0000 https://status.velar.com/#c9d293417d329fe8b36ba0c7ad0e6ee7ed484ca9144aa5c26e2ff654d3c22741 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 02 Mar 2026 18:31:23 +0000 https://status.velar.com/#c9d293417d329fe8b36ba0c7ad0e6ee7ed484ca9144aa5c26e2ff654d3c22741 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 02 Mar 2026 18:13:24 +0000 https://status.velar.com/#4c48b61e248ff98fbd6819f1f8fd10e6b2c3551b3276cae4e3bacb421124c1d2 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 02 Mar 2026 18:07:20 +0000 https://status.velar.com/#4c48b61e248ff98fbd6819f1f8fd10e6b2c3551b3276cae4e3bacb421124c1d2 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 02 Mar 2026 16:37:27 +0000 https://status.velar.com/#9c5967e8857bfc0b5523cf55f3a526d6189b56bff0bda6d5e8efdceced72d295 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 02 Mar 2026 15:16:21 +0000 https://status.velar.com/#9c5967e8857bfc0b5523cf55f3a526d6189b56bff0bda6d5e8efdceced72d295 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 02 Mar 2026 14:07:26 +0000 https://status.velar.com/#0d1ac45415b212c18f2c1dd2fda1965e2ae51536f8afa19da5ae63f2e4c9ed0a Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 02 Mar 2026 13:55:22 +0000 https://status.velar.com/#0d1ac45415b212c18f2c1dd2fda1965e2ae51536f8afa19da5ae63f2e4c9ed0a Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 02 Mar 2026 13:37:23 +0000 https://status.velar.com/#83977fb4b74c8381e2cec9040469b066c5d1c18e64a9cd1808421c166649f28c Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 02 Mar 2026 13:28:22 +0000 https://status.velar.com/#83977fb4b74c8381e2cec9040469b066c5d1c18e64a9cd1808421c166649f28c Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 02 Mar 2026 13:13:26 +0000 https://status.velar.com/#9c6539092845dacce94312341e31379e595e42c76ce5cef92ce4a90a1298199e Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 02 Mar 2026 12:46:27 +0000 https://status.velar.com/#9c6539092845dacce94312341e31379e595e42c76ce5cef92ce4a90a1298199e Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 02 Mar 2026 12:40:20 +0000 https://status.velar.com/#4b15f5eed04fa02c755d25ccf86ffcf67e42fc96cbb81f5f6daab9a6514a6a1d Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 02 Mar 2026 12:28:19 +0000 https://status.velar.com/#4b15f5eed04fa02c755d25ccf86ffcf67e42fc96cbb81f5f6daab9a6514a6a1d Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 02 Mar 2026 12:10:27 +0000 https://status.velar.com/#1fd83176537ef9b209e506a1b3580008b0adc2ce43189b026fbcffaad0ad8b51 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 02 Mar 2026 12:07:21 +0000 https://status.velar.com/#1fd83176537ef9b209e506a1b3580008b0adc2ce43189b026fbcffaad0ad8b51 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 02 Mar 2026 12:01:25 +0000 https://status.velar.com/#f7527397b7b5c261443cc67aff519e7b0606cd34ab11a1219be020b028d62c2d Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 02 Mar 2026 11:55:27 +0000 https://status.velar.com/#f7527397b7b5c261443cc67aff519e7b0606cd34ab11a1219be020b028d62c2d Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 02 Mar 2026 11:07:26 +0000 https://status.velar.com/#e740390a8b99f9617693fc5d77188a48fd2b5142cd95192fee05883b3557ae24 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 02 Mar 2026 10:37:24 +0000 https://status.velar.com/#e740390a8b99f9617693fc5d77188a48fd2b5142cd95192fee05883b3557ae24 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 02 Mar 2026 10:13:24 +0000 https://status.velar.com/#4af140526b13b2b55c251089fe4a8f25ab264866050017a4984b2d0cc315cb64 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 02 Mar 2026 09:52:19 +0000 https://status.velar.com/#4af140526b13b2b55c251089fe4a8f25ab264866050017a4984b2d0cc315cb64 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 02 Mar 2026 09:01:26 +0000 https://status.velar.com/#cfc74242692c43d47cd004e890e0d2cbc29482fa72eaa79b7597fd530058bac2 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 02 Mar 2026 08:49:22 +0000 https://status.velar.com/#cfc74242692c43d47cd004e890e0d2cbc29482fa72eaa79b7597fd530058bac2 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 02 Mar 2026 08:28:23 +0000 https://status.velar.com/#fe441d390498a77752dbda6afe1ee7dbc306452c38cac682e9394d085483f17d Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 02 Mar 2026 08:22:25 +0000 https://status.velar.com/#fe441d390498a77752dbda6afe1ee7dbc306452c38cac682e9394d085483f17d Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 02 Mar 2026 07:28:22 +0000 https://status.velar.com/#079bb5caf52f0d0bd0f48dd19dfafed6d0415e5ce2a29324c3aff6f29538e867 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 02 Mar 2026 07:25:22 +0000 https://status.velar.com/#079bb5caf52f0d0bd0f48dd19dfafed6d0415e5ce2a29324c3aff6f29538e867 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 02 Mar 2026 07:16:20 +0000 https://status.velar.com/#26192135caf97cc9078451cf1c48e41d5dbe1fe1b89c9eab00d196d7889d8bbb Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 02 Mar 2026 06:55:27 +0000 https://status.velar.com/#26192135caf97cc9078451cf1c48e41d5dbe1fe1b89c9eab00d196d7889d8bbb Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 02 Mar 2026 06:16:18 +0000 https://status.velar.com/#ad4298007c8e87349576f59f3e1c8b42070dd9039362683dcfe4b9aac26830b3 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 02 Mar 2026 05:52:20 +0000 https://status.velar.com/#ad4298007c8e87349576f59f3e1c8b42070dd9039362683dcfe4b9aac26830b3 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 02 Mar 2026 04:49:25 +0000 https://status.velar.com/#cc72f41597dac25322973f2ffe59b8b9fd054104355db3d0c34434bd1ea51b95 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 02 Mar 2026 04:40:20 +0000 https://status.velar.com/#cc72f41597dac25322973f2ffe59b8b9fd054104355db3d0c34434bd1ea51b95 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 02 Mar 2026 04:19:19 +0000 https://status.velar.com/#f9188cc95315c57a45cd3f900b4adcb1582f27bea88504db54a24d8a6d2f6bfd Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 02 Mar 2026 03:31:23 +0000 https://status.velar.com/#f9188cc95315c57a45cd3f900b4adcb1582f27bea88504db54a24d8a6d2f6bfd Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 02 Mar 2026 02:37:19 +0000 https://status.velar.com/#91009b3ef0088e5f6ed991dffa7b8b2ef0a3eb4aaa2b5d85f659ef490c983259 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 02 Mar 2026 02:04:16 +0000 https://status.velar.com/#91009b3ef0088e5f6ed991dffa7b8b2ef0a3eb4aaa2b5d85f659ef490c983259 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 02 Mar 2026 01:52:22 +0000 https://status.velar.com/#08695bc2ab6859098303fd615c1bf93f37bc23da58ab016612fb9bf6f0569be1 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 02 Mar 2026 01:46:19 +0000 https://status.velar.com/#08695bc2ab6859098303fd615c1bf93f37bc23da58ab016612fb9bf6f0569be1 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 02 Mar 2026 01:31:27 +0000 https://status.velar.com/#4fb60af3675b6896ddbbf556453b99da5a08af47958ccc9ef186b79ef4e9ce07 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 02 Mar 2026 01:28:18 +0000 https://status.velar.com/#4fb60af3675b6896ddbbf556453b99da5a08af47958ccc9ef186b79ef4e9ce07 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 01 Mar 2026 23:31:22 +0000 https://status.velar.com/#8abce910b3c858ae8837f6e5598a1b49304ca6b45b8ee4706b38013419d85c23 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 01 Mar 2026 23:28:21 +0000 https://status.velar.com/#8abce910b3c858ae8837f6e5598a1b49304ca6b45b8ee4706b38013419d85c23 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 01 Mar 2026 23:22:23 +0000 https://status.velar.com/#3dc01fb4d5c2a333a997f286020a978995609af89488dc1e2d289a5120988c87 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 01 Mar 2026 23:13:22 +0000 https://status.velar.com/#3dc01fb4d5c2a333a997f286020a978995609af89488dc1e2d289a5120988c87 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 01 Mar 2026 20:34:28 +0000 https://status.velar.com/#d2590869b67464a9e5544663bb8f815fc8d306b4a6d557278c3c16bc1d6b7e33 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 01 Mar 2026 20:01:29 +0000 https://status.velar.com/#d2590869b67464a9e5544663bb8f815fc8d306b4a6d557278c3c16bc1d6b7e33 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 01 Mar 2026 19:31:26 +0000 https://status.velar.com/#1fa666ebacd8356f30ff533dcc334e18483fe928ddd5a1893253c127b2576474 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 01 Mar 2026 19:04:22 +0000 https://status.velar.com/#1fa666ebacd8356f30ff533dcc334e18483fe928ddd5a1893253c127b2576474 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 01 Mar 2026 18:46:26 +0000 https://status.velar.com/#a4d9ddffc89f8a1c66a5a3bab0e21b20cd2111f6418d1b901eda964c025291d3 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 01 Mar 2026 18:16:16 +0000 https://status.velar.com/#a4d9ddffc89f8a1c66a5a3bab0e21b20cd2111f6418d1b901eda964c025291d3 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 01 Mar 2026 17:58:20 +0000 https://status.velar.com/#4fa77d2518769c56f792d383e2760b76a2e0fb99cd577ae17a1c789407bfbf84 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 01 Mar 2026 17:52:20 +0000 https://status.velar.com/#4fa77d2518769c56f792d383e2760b76a2e0fb99cd577ae17a1c789407bfbf84 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 01 Mar 2026 16:49:26 +0000 https://status.velar.com/#c5e7288aa33768f936d20504f9e1c2da1d35a4e30159db6b54131dd5acd56199 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 01 Mar 2026 16:37:24 +0000 https://status.velar.com/#c5e7288aa33768f936d20504f9e1c2da1d35a4e30159db6b54131dd5acd56199 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 01 Mar 2026 16:10:22 +0000 https://status.velar.com/#63b777fb6ae59efab65e73cb10513dba516173f3f7090526b44181bcf1f1457a Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 01 Mar 2026 16:04:17 +0000 https://status.velar.com/#63b777fb6ae59efab65e73cb10513dba516173f3f7090526b44181bcf1f1457a Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 01 Mar 2026 14:25:25 +0000 https://status.velar.com/#a1e255c09fb60aef729716a9bcc97e83d3547d536ef26c42531771f5d38115b7 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 01 Mar 2026 13:25:26 +0000 https://status.velar.com/#a1e255c09fb60aef729716a9bcc97e83d3547d536ef26c42531771f5d38115b7 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 01 Mar 2026 13:16:20 +0000 https://status.velar.com/#e8e507a2daa08897fd02d0d2eec7c32744e68561c5c2c4862ce1cd59f3fb0546 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 01 Mar 2026 13:04:22 +0000 https://status.velar.com/#e8e507a2daa08897fd02d0d2eec7c32744e68561c5c2c4862ce1cd59f3fb0546 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 01 Mar 2026 12:52:18 +0000 https://status.velar.com/#4f15afb091336810635a172751b110eb4253d492303302380367f5e271eabbe3 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 01 Mar 2026 12:43:28 +0000 https://status.velar.com/#4f15afb091336810635a172751b110eb4253d492303302380367f5e271eabbe3 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 01 Mar 2026 12:04:22 +0000 https://status.velar.com/#2731b064aa17f8e4816d09415662ca920ba74fb664eed4a775f60d2cf70f778e Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 01 Mar 2026 12:01:25 +0000 https://status.velar.com/#2731b064aa17f8e4816d09415662ca920ba74fb664eed4a775f60d2cf70f778e Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 01 Mar 2026 11:31:24 +0000 https://status.velar.com/#bc7128fc811ec57d3d9ded8cd6e2901b98f899d5873569499d18ddf960c412ec Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 01 Mar 2026 11:01:29 +0000 https://status.velar.com/#bc7128fc811ec57d3d9ded8cd6e2901b98f899d5873569499d18ddf960c412ec Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 01 Mar 2026 10:52:21 +0000 https://status.velar.com/#11234aaea1b54131a479adfdbe4aa51ae6aad2ed89d5a5ceedfae20d14cee73d Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 01 Mar 2026 10:28:24 +0000 https://status.velar.com/#11234aaea1b54131a479adfdbe4aa51ae6aad2ed89d5a5ceedfae20d14cee73d Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 01 Mar 2026 10:07:29 +0000 https://status.velar.com/#64368f2751f17c078685f8b87bc7c1abbeae5bd8af181224614421b61d4dd5d1 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 01 Mar 2026 09:52:26 +0000 https://status.velar.com/#64368f2751f17c078685f8b87bc7c1abbeae5bd8af181224614421b61d4dd5d1 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 01 Mar 2026 08:28:23 +0000 https://status.velar.com/#7830270774431e2bd008410522684750026419da2c2f3df91a5846c5d479ca19 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 01 Mar 2026 08:25:26 +0000 https://status.velar.com/#7830270774431e2bd008410522684750026419da2c2f3df91a5846c5d479ca19 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 01 Mar 2026 07:55:24 +0000 https://status.velar.com/#2080fb0972e1da56f61c95206ba352ba23328e731d9d3da6d06c5005954c0c0a Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 01 Mar 2026 07:37:23 +0000 https://status.velar.com/#2080fb0972e1da56f61c95206ba352ba23328e731d9d3da6d06c5005954c0c0a Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 01 Mar 2026 07:13:26 +0000 https://status.velar.com/#634455a1b7f1746ef99f914f573aaaff999c9b868f3b2c7b0789a4617abb95f5 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 01 Mar 2026 05:46:25 +0000 https://status.velar.com/#634455a1b7f1746ef99f914f573aaaff999c9b868f3b2c7b0789a4617abb95f5 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 01 Mar 2026 05:31:23 +0000 https://status.velar.com/#17d0aa4dd64f9110e10778ca052f031af3d81b71810173250411b1c4c391f910 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 01 Mar 2026 04:46:22 +0000 https://status.velar.com/#17d0aa4dd64f9110e10778ca052f031af3d81b71810173250411b1c4c391f910 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 01 Mar 2026 03:34:23 +0000 https://status.velar.com/#b8fbe6f977c6dce82f4dde01cf7a42b4c4d62bd78fddb67f3812b7aa871da3d7 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 01 Mar 2026 03:31:20 +0000 https://status.velar.com/#b8fbe6f977c6dce82f4dde01cf7a42b4c4d62bd78fddb67f3812b7aa871da3d7 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 01 Mar 2026 02:46:24 +0000 https://status.velar.com/#e6ac23e3c832e75eb9130cb0e968cd1aeed8f4b7e4ed45aa3e597b87e6c75fb8 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 01 Mar 2026 02:34:23 +0000 https://status.velar.com/#e6ac23e3c832e75eb9130cb0e968cd1aeed8f4b7e4ed45aa3e597b87e6c75fb8 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 01 Mar 2026 01:49:27 +0000 https://status.velar.com/#89575619d04adfcfbedbf0aaefeec55fa5bceacafb7bf1d841ec47ece199b9af Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 01 Mar 2026 01:19:23 +0000 https://status.velar.com/#89575619d04adfcfbedbf0aaefeec55fa5bceacafb7bf1d841ec47ece199b9af Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 01 Mar 2026 01:01:21 +0000 https://status.velar.com/#4f3aa5f4a45e22c773b16cbfcdfe49c5277181435da5c3fcc58ed40598a4f16d Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 01 Mar 2026 00:46:29 +0000 https://status.velar.com/#4f3aa5f4a45e22c773b16cbfcdfe49c5277181435da5c3fcc58ed40598a4f16d Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 28 Feb 2026 23:31:20 +0000 https://status.velar.com/#ce0525a1c5cddaf9f0037fe52f6fed72c65a672c8cb16010faa1e6b6cbe621da Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 28 Feb 2026 23:19:19 +0000 https://status.velar.com/#ce0525a1c5cddaf9f0037fe52f6fed72c65a672c8cb16010faa1e6b6cbe621da Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 28 Feb 2026 23:04:25 +0000 https://status.velar.com/#353e12f12a2a50bf9a279c63a76737239d75f99bad48d8478244fca69d9dbbc7 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 28 Feb 2026 22:58:28 +0000 https://status.velar.com/#353e12f12a2a50bf9a279c63a76737239d75f99bad48d8478244fca69d9dbbc7 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 28 Feb 2026 22:52:18 +0000 https://status.velar.com/#0478c32925701c1a4ffb320bb1da6a6bbb1d98dbae019d89f52895fc2659dee6 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 28 Feb 2026 22:49:24 +0000 https://status.velar.com/#0478c32925701c1a4ffb320bb1da6a6bbb1d98dbae019d89f52895fc2659dee6 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 28 Feb 2026 21:13:28 +0000 https://status.velar.com/#fbad91d27861ce3db874a62770bc4225c9f855c74d2c372f9d68a4de15149c6a Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 28 Feb 2026 20:49:21 +0000 https://status.velar.com/#fbad91d27861ce3db874a62770bc4225c9f855c74d2c372f9d68a4de15149c6a Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 28 Feb 2026 19:55:20 +0000 https://status.velar.com/#ab0976fe6aefd7b2d62e01d52657c1d553774467390d6e7d95e8e2ed581fa73e Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 28 Feb 2026 19:16:18 +0000 https://status.velar.com/#ab0976fe6aefd7b2d62e01d52657c1d553774467390d6e7d95e8e2ed581fa73e Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 28 Feb 2026 19:07:21 +0000 https://status.velar.com/#89d607af6d654c3616b0cebe10122d2ea539ad662f07de8e177a8ed22e52c5bc Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 28 Feb 2026 18:19:21 +0000 https://status.velar.com/#89d607af6d654c3616b0cebe10122d2ea539ad662f07de8e177a8ed22e52c5bc Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 28 Feb 2026 17:31:23 +0000 https://status.velar.com/#f5274f928d597f2ab4bc6b7d7660c8efef3775e34c7a180fe4a017151eae207e Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 28 Feb 2026 17:10:35 +0000 https://status.velar.com/#f5274f928d597f2ab4bc6b7d7660c8efef3775e34c7a180fe4a017151eae207e Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 28 Feb 2026 17:08:11 +0000 https://status.velar.com/#db837077aebfb0f7ac6c1709173c0a78effb5840fe7b6bfed6ece5ccb439242e api.velar.co recovered https://status.velar.com/ Sat, 28 Feb 2026 17:05:18 +0000 https://status.velar.com/#db837077aebfb0f7ac6c1709173c0a78effb5840fe7b6bfed6ece5ccb439242e api.velar.co went down https://status.velar.com/ Sat, 28 Feb 2026 16:07:25 +0000 https://status.velar.com/#3da668526192fff5c66e57cc42024aa876f7c7bc69c6a749c5ef601c449662d2 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 28 Feb 2026 16:04:25 +0000 https://status.velar.com/#3da668526192fff5c66e57cc42024aa876f7c7bc69c6a749c5ef601c449662d2 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 28 Feb 2026 07:40:20 +0000 https://status.velar.com/#1ef2f683c27accdf4333dd93e55938b51a292faba6e02726be54fa789bf081dd Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 28 Feb 2026 07:37:25 +0000 https://status.velar.com/#1ef2f683c27accdf4333dd93e55938b51a292faba6e02726be54fa789bf081dd Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 27 Feb 2026 23:07:20 +0000 https://status.velar.com/#36d574c23091b20f6f2c1da3c1be89f199fa4b36abc53fd830522cac840a171a Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 27 Feb 2026 23:04:23 +0000 https://status.velar.com/#36d574c23091b20f6f2c1da3c1be89f199fa4b36abc53fd830522cac840a171a Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 27 Feb 2026 22:22:27 +0000 https://status.velar.com/#bae1e712eec24a9359985f0510b15a74c66059d846b2f34f1e617f5f42a9f52e Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 27 Feb 2026 22:19:19 +0000 https://status.velar.com/#bae1e712eec24a9359985f0510b15a74c66059d846b2f34f1e617f5f42a9f52e Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 27 Feb 2026 21:52:25 +0000 https://status.velar.com/#087ee4c764068b644b86f7d090cb747aaee7e6dcd20baaf745a1981a6bee9efa Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 27 Feb 2026 21:49:25 +0000 https://status.velar.com/#087ee4c764068b644b86f7d090cb747aaee7e6dcd20baaf745a1981a6bee9efa Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 27 Feb 2026 14:40:23 +0000 https://status.velar.com/#d15566a16918a1b6a1218bf8cca78aad99bbf7cf1987ae28f82cb0e42ed62563 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 27 Feb 2026 14:37:24 +0000 https://status.velar.com/#d15566a16918a1b6a1218bf8cca78aad99bbf7cf1987ae28f82cb0e42ed62563 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 24 Feb 2026 00:34:21 +0000 https://status.velar.com/#6e0581a07a300b2b0634ddcd379278f6dcdf10dfdb9e4e953c3ea4f37c81128a Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 24 Feb 2026 00:31:21 +0000 https://status.velar.com/#6e0581a07a300b2b0634ddcd379278f6dcdf10dfdb9e4e953c3ea4f37c81128a Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 23 Feb 2026 00:13:29 +0000 https://status.velar.com/#524f07482268577330af2f4d15c6784c819ef643ff7d0e923329e11814bcfd5f Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 23 Feb 2026 00:04:16 +0000 https://status.velar.com/#524f07482268577330af2f4d15c6784c819ef643ff7d0e923329e11814bcfd5f Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 22 Feb 2026 23:44:11 +0000 https://status.velar.com/#36f41912d5e72b814391e633a807e7d945a06968c46ea1ebac283bb7ce154314 api.velar.co recovered https://status.velar.com/ Sun, 22 Feb 2026 23:38:53 +0000 https://status.velar.com/#36f41912d5e72b814391e633a807e7d945a06968c46ea1ebac283bb7ce154314 api.velar.co went down https://status.velar.com/ Sun, 22 Feb 2026 23:35:42 +0000 https://status.velar.com/#7fa2d42711fb1e10a5046369f4fbec6ee9971bf0a0c7af7c2508a80da8194ab8 Gateway (gateway.velar.network) recovered https://status.velar.com/ Sun, 22 Feb 2026 23:32:42 +0000 https://status.velar.com/#7fa2d42711fb1e10a5046369f4fbec6ee9971bf0a0c7af7c2508a80da8194ab8 Gateway (gateway.velar.network) went down https://status.velar.com/ Sun, 22 Feb 2026 22:52:20 +0000 https://status.velar.com/#b9ff04670babdc687eea62e72c23ba0f5b231c1a688c94b8898a2ec91041128f Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 22 Feb 2026 22:10:21 +0000 https://status.velar.com/#b9ff04670babdc687eea62e72c23ba0f5b231c1a688c94b8898a2ec91041128f Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 22 Feb 2026 19:58:25 +0000 https://status.velar.com/#bc91d6ff968d3df7740087f21cf2b9bd6e960de4bea5652aae8fab93f66b9619 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 22 Feb 2026 19:49:23 +0000 https://status.velar.com/#bc91d6ff968d3df7740087f21cf2b9bd6e960de4bea5652aae8fab93f66b9619 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 22 Feb 2026 19:10:20 +0000 https://status.velar.com/#5ff780dd21d5daeae0e8ae749c5320d6128692072ed21f036ba36c1dcb392ac3 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 22 Feb 2026 18:52:22 +0000 https://status.velar.com/#5ff780dd21d5daeae0e8ae749c5320d6128692072ed21f036ba36c1dcb392ac3 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 22 Feb 2026 18:40:23 +0000 https://status.velar.com/#d0f287c1be7d763ecfc56a5caa467a044afd11920cb430c880dd156acff0bbf5 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 22 Feb 2026 18:22:24 +0000 https://status.velar.com/#d0f287c1be7d763ecfc56a5caa467a044afd11920cb430c880dd156acff0bbf5 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 22 Feb 2026 16:43:19 +0000 https://status.velar.com/#f58c70ba622f6337c171db922783a6f76f975c30d39143aaee18fad2d4cca045 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 22 Feb 2026 16:40:21 +0000 https://status.velar.com/#f58c70ba622f6337c171db922783a6f76f975c30d39143aaee18fad2d4cca045 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 22 Feb 2026 11:13:26 +0000 https://status.velar.com/#078e6cf625fe330696a4c113e9630e62b944917b88419023a065e10e2a9b4c4b Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 22 Feb 2026 11:01:23 +0000 https://status.velar.com/#078e6cf625fe330696a4c113e9630e62b944917b88419023a065e10e2a9b4c4b Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 22 Feb 2026 04:07:28 +0000 https://status.velar.com/#32b6761d371802808c97b05e0f69bcf2d907a91fc4b6d59aeef44c8371c2c81a Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 22 Feb 2026 03:46:22 +0000 https://status.velar.com/#32b6761d371802808c97b05e0f69bcf2d907a91fc4b6d59aeef44c8371c2c81a Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 22 Feb 2026 02:49:25 +0000 https://status.velar.com/#f9ab7a283b9556ca5a0938403aada6ab801981fb69c94238ef86ce48821aacc1 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 22 Feb 2026 02:34:26 +0000 https://status.velar.com/#f9ab7a283b9556ca5a0938403aada6ab801981fb69c94238ef86ce48821aacc1 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 22 Feb 2026 01:52:21 +0000 https://status.velar.com/#032ab11a3b3fe15dbd15c13d917ad6242f2cbed725eae6e89005e873989ac24c Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 22 Feb 2026 01:46:22 +0000 https://status.velar.com/#032ab11a3b3fe15dbd15c13d917ad6242f2cbed725eae6e89005e873989ac24c Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 22 Feb 2026 00:01:26 +0000 https://status.velar.com/#adc2649a533644039db34f1f50e0f9b82867269fc019a79e48fea8a46cc3911c Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 21 Feb 2026 23:07:19 +0000 https://status.velar.com/#adc2649a533644039db34f1f50e0f9b82867269fc019a79e48fea8a46cc3911c Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 21 Feb 2026 22:19:27 +0000 https://status.velar.com/#f6bc43109de67d80b0b2c70b4ae081d9f19ba7a16320de385aa3fdeaa3127c6d Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 21 Feb 2026 22:07:29 +0000 https://status.velar.com/#f6bc43109de67d80b0b2c70b4ae081d9f19ba7a16320de385aa3fdeaa3127c6d Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 21 Feb 2026 21:43:24 +0000 https://status.velar.com/#4fc50e35885c73c8377b72fe35ed53613400a68a2f7410981d83f718784dd25d Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 21 Feb 2026 21:28:19 +0000 https://status.velar.com/#4fc50e35885c73c8377b72fe35ed53613400a68a2f7410981d83f718784dd25d Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 21 Feb 2026 20:04:21 +0000 https://status.velar.com/#00d9b4823b3b95fb31720fc17e531393fa63f58c16f6d4144dd9ca9daa0eace2 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 21 Feb 2026 19:52:18 +0000 https://status.velar.com/#00d9b4823b3b95fb31720fc17e531393fa63f58c16f6d4144dd9ca9daa0eace2 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 21 Feb 2026 16:19:19 +0000 https://status.velar.com/#c560cc70482988caec30ba59e3b546673e462dbde38a1ce6c389d65bcc4343ff Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 21 Feb 2026 15:43:40 +0000 https://status.velar.com/#c560cc70482988caec30ba59e3b546673e462dbde38a1ce6c389d65bcc4343ff Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 21 Feb 2026 12:07:27 +0000 https://status.velar.com/#e2976a49080d23a4a96ec4a852f4c876d346660667831e9b799dd786a245e1dc Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 21 Feb 2026 11:58:20 +0000 https://status.velar.com/#e2976a49080d23a4a96ec4a852f4c876d346660667831e9b799dd786a245e1dc Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 21 Feb 2026 03:31:27 +0000 https://status.velar.com/#261cbf1cbb3cc723dfaf365d899131828ace23f86cdc57cc8ac8db019d512897 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 21 Feb 2026 03:28:20 +0000 https://status.velar.com/#261cbf1cbb3cc723dfaf365d899131828ace23f86cdc57cc8ac8db019d512897 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 21 Feb 2026 03:07:19 +0000 https://status.velar.com/#65eac00f3e0de4cc433ba93b48f9eeb4893b70e143360bc5e77f0d9b09b91b9e Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 21 Feb 2026 02:52:20 +0000 https://status.velar.com/#65eac00f3e0de4cc433ba93b48f9eeb4893b70e143360bc5e77f0d9b09b91b9e Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 21 Feb 2026 01:28:21 +0000 https://status.velar.com/#6e65471b2152f5a2a7be0ad7c5629245a1579fb9f9bfc426740ef27787e1a82f Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 21 Feb 2026 01:25:28 +0000 https://status.velar.com/#6e65471b2152f5a2a7be0ad7c5629245a1579fb9f9bfc426740ef27787e1a82f Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 21 Feb 2026 00:28:25 +0000 https://status.velar.com/#57005f75742a1846cb7645525d74393665d95fbb2733496abaecec6de7f90cb5 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 21 Feb 2026 00:16:21 +0000 https://status.velar.com/#57005f75742a1846cb7645525d74393665d95fbb2733496abaecec6de7f90cb5 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 20 Feb 2026 21:04:17 +0000 https://status.velar.com/#1b0101208dd3b374c4fe64997a23e6355113542e198392780167c50449e00274 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 20 Feb 2026 20:37:28 +0000 https://status.velar.com/#1b0101208dd3b374c4fe64997a23e6355113542e198392780167c50449e00274 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 20 Feb 2026 19:52:21 +0000 https://status.velar.com/#16f53d4c6b59ecf02d2ea77acccaa23b5c55c62ab5be24e9ea77ede2fb8d3c4a Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 20 Feb 2026 19:37:20 +0000 https://status.velar.com/#16f53d4c6b59ecf02d2ea77acccaa23b5c55c62ab5be24e9ea77ede2fb8d3c4a Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 20 Feb 2026 19:01:23 +0000 https://status.velar.com/#9ebe74e8d848a6ec5d4a2d5ab54663960113563642b6944602e59e97df2b0e02 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 20 Feb 2026 18:10:26 +0000 https://status.velar.com/#9ebe74e8d848a6ec5d4a2d5ab54663960113563642b6944602e59e97df2b0e02 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 20 Feb 2026 17:58:23 +0000 https://status.velar.com/#b943c8ca392c6d18d7b8a665433aea32851b5182139a467f9f9c9128aaed681f Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 20 Feb 2026 17:55:27 +0000 https://status.velar.com/#b943c8ca392c6d18d7b8a665433aea32851b5182139a467f9f9c9128aaed681f Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 20 Feb 2026 17:19:25 +0000 https://status.velar.com/#d914b06f64b42ec91ef7657b2859aca717edb28c86afab51a5e2c9f1cb4e4065 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 20 Feb 2026 16:40:23 +0000 https://status.velar.com/#d914b06f64b42ec91ef7657b2859aca717edb28c86afab51a5e2c9f1cb4e4065 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 20 Feb 2026 16:10:19 +0000 https://status.velar.com/#2627a4353c9e1395984df92689f7f4dec348e763bea05610746336d54e309fa8 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 20 Feb 2026 16:01:22 +0000 https://status.velar.com/#2627a4353c9e1395984df92689f7f4dec348e763bea05610746336d54e309fa8 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 20 Feb 2026 15:10:28 +0000 https://status.velar.com/#dca44d899f5ff30b99a52700c4dd0668d38c31a1fdc07ed964af77ed1a0088b9 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 20 Feb 2026 14:28:19 +0000 https://status.velar.com/#dca44d899f5ff30b99a52700c4dd0668d38c31a1fdc07ed964af77ed1a0088b9 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 20 Feb 2026 14:19:20 +0000 https://status.velar.com/#41dbae77065e8de924004384e3680a8e12e0bfca38e1a47fbba0a0c9da2e432a Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 20 Feb 2026 13:52:16 +0000 https://status.velar.com/#41dbae77065e8de924004384e3680a8e12e0bfca38e1a47fbba0a0c9da2e432a Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 20 Feb 2026 13:43:24 +0000 https://status.velar.com/#87ffd8411c4d35ceeb4ba45dada2da3106ffd0d020b538883e84dbd4c2a32868 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 20 Feb 2026 13:16:16 +0000 https://status.velar.com/#87ffd8411c4d35ceeb4ba45dada2da3106ffd0d020b538883e84dbd4c2a32868 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 20 Feb 2026 12:07:21 +0000 https://status.velar.com/#a0318b375d1e244659877b9efe63d89db7bdfe80e615f8c9fb8762ad109c9be0 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 20 Feb 2026 11:46:22 +0000 https://status.velar.com/#a0318b375d1e244659877b9efe63d89db7bdfe80e615f8c9fb8762ad109c9be0 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 20 Feb 2026 11:34:28 +0000 https://status.velar.com/#931f5ea88a084c55441cc05f0956a0f4c38963f4c466a7fa830790b597debaac Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 20 Feb 2026 11:13:25 +0000 https://status.velar.com/#931f5ea88a084c55441cc05f0956a0f4c38963f4c466a7fa830790b597debaac Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 20 Feb 2026 11:07:25 +0000 https://status.velar.com/#a2767a1e5438fdf34c981b0a238e4579014d0b7a851bf15dc6a960f7339453cf Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 20 Feb 2026 10:28:22 +0000 https://status.velar.com/#a2767a1e5438fdf34c981b0a238e4579014d0b7a851bf15dc6a960f7339453cf Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 20 Feb 2026 10:19:23 +0000 https://status.velar.com/#87fb26134430d328c45ed1dc3476c8983807158e051014abca11e890a8ebc402 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 20 Feb 2026 09:58:27 +0000 https://status.velar.com/#87fb26134430d328c45ed1dc3476c8983807158e051014abca11e890a8ebc402 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 20 Feb 2026 09:49:29 +0000 https://status.velar.com/#129314beb2f0a092df65457ad0725e5e0a60cdb2ce61b8a3f1c49cface80039c Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 20 Feb 2026 09:28:24 +0000 https://status.velar.com/#129314beb2f0a092df65457ad0725e5e0a60cdb2ce61b8a3f1c49cface80039c Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 20 Feb 2026 07:52:21 +0000 https://status.velar.com/#6de9a2b4bdaa7b873b8c6b829442547b186f0274616962b80220f9625c5af4a9 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 20 Feb 2026 05:55:25 +0000 https://status.velar.com/#6de9a2b4bdaa7b873b8c6b829442547b186f0274616962b80220f9625c5af4a9 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 20 Feb 2026 05:16:23 +0000 https://status.velar.com/#78eb918f169f85c84023cdc87f6f386a9706c00bbcf7d398d2d178b50a3939b2 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 20 Feb 2026 05:07:19 +0000 https://status.velar.com/#78eb918f169f85c84023cdc87f6f386a9706c00bbcf7d398d2d178b50a3939b2 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 20 Feb 2026 04:52:15 +0000 https://status.velar.com/#6d35cb7575a7a91402ba3dfdf8255b5e31368c9a669a13b5d0c188f2c469d40f Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 20 Feb 2026 04:43:20 +0000 https://status.velar.com/#6d35cb7575a7a91402ba3dfdf8255b5e31368c9a669a13b5d0c188f2c469d40f Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 20 Feb 2026 04:07:19 +0000 https://status.velar.com/#9b6f396f9ff0a40d3e5b3ea5caa342fd8901706b5f6554b4eea6f6a754672f94 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 20 Feb 2026 03:34:20 +0000 https://status.velar.com/#9b6f396f9ff0a40d3e5b3ea5caa342fd8901706b5f6554b4eea6f6a754672f94 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 20 Feb 2026 03:22:23 +0000 https://status.velar.com/#0f5b86e63b66926c004a23994e9de9b5782b517b272d25df673bacfafbcc220f Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 20 Feb 2026 03:16:20 +0000 https://status.velar.com/#0f5b86e63b66926c004a23994e9de9b5782b517b272d25df673bacfafbcc220f Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 20 Feb 2026 02:22:21 +0000 https://status.velar.com/#19351ab7e608650f0fe1b7295dfbb7d47ffcb5b158d0971984fa6a898f112d34 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 20 Feb 2026 02:19:19 +0000 https://status.velar.com/#19351ab7e608650f0fe1b7295dfbb7d47ffcb5b158d0971984fa6a898f112d34 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 20 Feb 2026 01:52:19 +0000 https://status.velar.com/#15abd8542ed7dded2d2ff29383e0601fd8094f9a69fad3eb6c34923b22e7bf58 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 20 Feb 2026 01:25:27 +0000 https://status.velar.com/#15abd8542ed7dded2d2ff29383e0601fd8094f9a69fad3eb6c34923b22e7bf58 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 20 Feb 2026 01:04:23 +0000 https://status.velar.com/#3148c07cc936ade0dab2a803df76bc194e0edd38c57737df7846179de08cda22 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 20 Feb 2026 00:34:23 +0000 https://status.velar.com/#3148c07cc936ade0dab2a803df76bc194e0edd38c57737df7846179de08cda22 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 20 Feb 2026 00:10:24 +0000 https://status.velar.com/#73a0355b3ff0dd7354c0b31d9507e8997aad3a51d0bd0b5fc91d5751fb519097 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 20 Feb 2026 00:01:26 +0000 https://status.velar.com/#73a0355b3ff0dd7354c0b31d9507e8997aad3a51d0bd0b5fc91d5751fb519097 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 19 Feb 2026 23:31:20 +0000 https://status.velar.com/#45195685566aca57b9573f927ef7ae72452b16a03b921f5c922fbe0da4cd1eed Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 19 Feb 2026 23:13:26 +0000 https://status.velar.com/#45195685566aca57b9573f927ef7ae72452b16a03b921f5c922fbe0da4cd1eed Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 19 Feb 2026 22:40:22 +0000 https://status.velar.com/#6f1dd092495d27ab1eeaffc1159e0b9893fcf449e3dd3947de25bc272f8965e1 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 19 Feb 2026 22:34:24 +0000 https://status.velar.com/#6f1dd092495d27ab1eeaffc1159e0b9893fcf449e3dd3947de25bc272f8965e1 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 19 Feb 2026 22:10:21 +0000 https://status.velar.com/#427386641ad43142cb2c2f2fd5847cc3beead86efd4dfdca89f6900da26c8e87 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 19 Feb 2026 22:04:21 +0000 https://status.velar.com/#427386641ad43142cb2c2f2fd5847cc3beead86efd4dfdca89f6900da26c8e87 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 19 Feb 2026 20:46:22 +0000 https://status.velar.com/#077a7451054877c2cf2722624f044091aa5e70095526a526d5ed16e735aa57b4 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 19 Feb 2026 20:43:21 +0000 https://status.velar.com/#077a7451054877c2cf2722624f044091aa5e70095526a526d5ed16e735aa57b4 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 19 Feb 2026 20:31:19 +0000 https://status.velar.com/#e3abda75dd012550770dc7b48c77ca900629eb0304fe1c95a978eb21608c1466 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 19 Feb 2026 19:37:24 +0000 https://status.velar.com/#e3abda75dd012550770dc7b48c77ca900629eb0304fe1c95a978eb21608c1466 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 19 Feb 2026 19:25:27 +0000 https://status.velar.com/#ed973f0e3dd429cd77d3e571ab72ace08bc27e0fff9f4b6b4b9db7d573ae061e Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 19 Feb 2026 19:10:19 +0000 https://status.velar.com/#ed973f0e3dd429cd77d3e571ab72ace08bc27e0fff9f4b6b4b9db7d573ae061e Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 19 Feb 2026 18:58:22 +0000 https://status.velar.com/#d1c171ba031f3f419b4012b7f9931fe6fb845eec53b894478339c4128a8920f1 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 19 Feb 2026 18:01:27 +0000 https://status.velar.com/#d1c171ba031f3f419b4012b7f9931fe6fb845eec53b894478339c4128a8920f1 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 19 Feb 2026 17:31:25 +0000 https://status.velar.com/#dbc6a83eadcea7c8192c1e10f1f90251235ac998587b390bcf68a4586702a200 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 19 Feb 2026 16:49:26 +0000 https://status.velar.com/#dbc6a83eadcea7c8192c1e10f1f90251235ac998587b390bcf68a4586702a200 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 19 Feb 2026 16:37:25 +0000 https://status.velar.com/#05344e741c380ca7164d9a2447b7362990a415ccb02696502d7de683105c78d3 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 19 Feb 2026 16:34:24 +0000 https://status.velar.com/#05344e741c380ca7164d9a2447b7362990a415ccb02696502d7de683105c78d3 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 19 Feb 2026 16:13:27 +0000 https://status.velar.com/#d95daa64a070821aa1745e953c3571e2e33611241e051748734075e36da54057 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 19 Feb 2026 15:31:24 +0000 https://status.velar.com/#d95daa64a070821aa1745e953c3571e2e33611241e051748734075e36da54057 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 19 Feb 2026 14:34:26 +0000 https://status.velar.com/#7e7c72d6193271a4dfcd0e8e31fcafa79ab32c6f27ea617ca86aa94587863ffd Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 19 Feb 2026 13:55:24 +0000 https://status.velar.com/#7e7c72d6193271a4dfcd0e8e31fcafa79ab32c6f27ea617ca86aa94587863ffd Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 19 Feb 2026 13:46:22 +0000 https://status.velar.com/#5ee6b8310c9c53e1564e11e2f49daae5182519f8d52a28ef93c49aceacd281d5 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 19 Feb 2026 13:37:36 +0000 https://status.velar.com/#5ee6b8310c9c53e1564e11e2f49daae5182519f8d52a28ef93c49aceacd281d5 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 19 Feb 2026 13:31:22 +0000 https://status.velar.com/#08e0d1ec8d5464419bb131cd4e8aa09ce53255caa802b235ff46d92bafc102c4 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 19 Feb 2026 13:22:23 +0000 https://status.velar.com/#08e0d1ec8d5464419bb131cd4e8aa09ce53255caa802b235ff46d92bafc102c4 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 19 Feb 2026 13:10:19 +0000 https://status.velar.com/#8350ec3b1f02dc3d50a17813f6b9ac145d19e5121fd9eef853ba1ede3a568c9a Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 19 Feb 2026 13:01:24 +0000 https://status.velar.com/#8350ec3b1f02dc3d50a17813f6b9ac145d19e5121fd9eef853ba1ede3a568c9a Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 19 Feb 2026 11:10:21 +0000 https://status.velar.com/#2f1ac917f93b32bdd3fb284159a9efdb67ff405af383e98e54f81256b766582c Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 19 Feb 2026 11:01:18 +0000 https://status.velar.com/#2f1ac917f93b32bdd3fb284159a9efdb67ff405af383e98e54f81256b766582c Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 19 Feb 2026 10:31:23 +0000 https://status.velar.com/#5cd8df4e2d2d0b2ec9f5a145931566a070247a46150e033abd66f926436121c4 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 19 Feb 2026 10:19:26 +0000 https://status.velar.com/#5cd8df4e2d2d0b2ec9f5a145931566a070247a46150e033abd66f926436121c4 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 19 Feb 2026 10:10:20 +0000 https://status.velar.com/#7523a6177c94f86d5bfb62e84afdf90c89a2f8b002d28b59b3fc3a1abd3ce26e Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 19 Feb 2026 09:58:21 +0000 https://status.velar.com/#7523a6177c94f86d5bfb62e84afdf90c89a2f8b002d28b59b3fc3a1abd3ce26e Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 19 Feb 2026 09:13:21 +0000 https://status.velar.com/#899b7bb3f07fa96cfe1c1c99cf2b5f5c3d73084d92a2c62af8c232c3f313f9e4 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 19 Feb 2026 08:55:24 +0000 https://status.velar.com/#899b7bb3f07fa96cfe1c1c99cf2b5f5c3d73084d92a2c62af8c232c3f313f9e4 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 19 Feb 2026 08:43:22 +0000 https://status.velar.com/#3a481e6928d0ca791237e5e5246dbc7bbe5118e322b4ff1ae3e61df360ac2d7d Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 19 Feb 2026 08:34:26 +0000 https://status.velar.com/#3a481e6928d0ca791237e5e5246dbc7bbe5118e322b4ff1ae3e61df360ac2d7d Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 19 Feb 2026 08:28:17 +0000 https://status.velar.com/#46f60ceb1b0b773d48b9e34479e34c528ea2620db8203826a17180777b6a63fe Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 19 Feb 2026 08:22:22 +0000 https://status.velar.com/#46f60ceb1b0b773d48b9e34479e34c528ea2620db8203826a17180777b6a63fe Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 19 Feb 2026 04:19:22 +0000 https://status.velar.com/#b775ea2a052301e414471245d131da30c94db627c9546584ade7f8b12ad00b2e Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 19 Feb 2026 04:10:22 +0000 https://status.velar.com/#b775ea2a052301e414471245d131da30c94db627c9546584ade7f8b12ad00b2e Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 19 Feb 2026 03:04:16 +0000 https://status.velar.com/#831e7f53706deaaca0bbcebb17877c5e9a7b3b2d776be2277f59a63da1d4754e Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 19 Feb 2026 03:01:24 +0000 https://status.velar.com/#831e7f53706deaaca0bbcebb17877c5e9a7b3b2d776be2277f59a63da1d4754e Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 19 Feb 2026 02:22:24 +0000 https://status.velar.com/#8b53f2fdfcf0423ee52f01c450b573fa9a0a3ac3fecf254424315f7b9c5e86dd Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 19 Feb 2026 02:01:21 +0000 https://status.velar.com/#8b53f2fdfcf0423ee52f01c450b573fa9a0a3ac3fecf254424315f7b9c5e86dd Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 18 Feb 2026 22:19:24 +0000 https://status.velar.com/#5fceeb67d86d7427d64f19fa55f7b90c61cbf3e8bd3bae2d26a95beabfe39a8f Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 18 Feb 2026 22:13:28 +0000 https://status.velar.com/#5fceeb67d86d7427d64f19fa55f7b90c61cbf3e8bd3bae2d26a95beabfe39a8f Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 18 Feb 2026 21:40:19 +0000 https://status.velar.com/#ca4a686fc0b0ce6f6f681fc80ba0820e8c80a9308ab872af2046a4bba0e896d3 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 18 Feb 2026 21:34:21 +0000 https://status.velar.com/#ca4a686fc0b0ce6f6f681fc80ba0820e8c80a9308ab872af2046a4bba0e896d3 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 18 Feb 2026 21:25:20 +0000 https://status.velar.com/#9374c244bec14c0ff9bbe9c8b211e340fc15a6921e404252f317fcd3b5872802 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 18 Feb 2026 21:10:26 +0000 https://status.velar.com/#9374c244bec14c0ff9bbe9c8b211e340fc15a6921e404252f317fcd3b5872802 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 18 Feb 2026 20:58:24 +0000 https://status.velar.com/#221ec678dc393d855ffe4aa27211ccda083f5467e5202e18c09db1b0787d6748 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 18 Feb 2026 20:07:26 +0000 https://status.velar.com/#221ec678dc393d855ffe4aa27211ccda083f5467e5202e18c09db1b0787d6748 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 18 Feb 2026 19:52:15 +0000 https://status.velar.com/#9aba6179fd37fef46d011dc5633e7e5888fc0cd043630c3c51b1d680e980794e Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 18 Feb 2026 19:34:23 +0000 https://status.velar.com/#9aba6179fd37fef46d011dc5633e7e5888fc0cd043630c3c51b1d680e980794e Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 18 Feb 2026 18:46:24 +0000 https://status.velar.com/#c8e91826864a8408b561737c2a49a093a0e3deacaec2901500ccbfce3b0eb692 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 18 Feb 2026 18:40:29 +0000 https://status.velar.com/#c8e91826864a8408b561737c2a49a093a0e3deacaec2901500ccbfce3b0eb692 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 18 Feb 2026 18:34:22 +0000 https://status.velar.com/#546736d941cac7ebc4ac0389b36a254e383ddbcecd77451ba330bbe15eaf62e8 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 18 Feb 2026 18:13:22 +0000 https://status.velar.com/#546736d941cac7ebc4ac0389b36a254e383ddbcecd77451ba330bbe15eaf62e8 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 18 Feb 2026 17:28:17 +0000 https://status.velar.com/#ae3b2515da80b422f3ee0e1035259bb2857d61c3b63b6558bdb40bbcdae4ed24 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 18 Feb 2026 17:25:28 +0000 https://status.velar.com/#ae3b2515da80b422f3ee0e1035259bb2857d61c3b63b6558bdb40bbcdae4ed24 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 18 Feb 2026 17:22:20 +0000 https://status.velar.com/#4e0efe5db463ec373d619c19091871d7a8d8cc513b62f88ec7431800dee536a7 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 18 Feb 2026 17:04:21 +0000 https://status.velar.com/#4e0efe5db463ec373d619c19091871d7a8d8cc513b62f88ec7431800dee536a7 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 18 Feb 2026 14:58:23 +0000 https://status.velar.com/#6acbdec7880b841caacc102583159688d313e142df188cf1fd458db43eb033d3 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 18 Feb 2026 14:04:16 +0000 https://status.velar.com/#6acbdec7880b841caacc102583159688d313e142df188cf1fd458db43eb033d3 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 18 Feb 2026 13:43:22 +0000 https://status.velar.com/#14ebb578f1357e3f782f36ba67337e2c11f1ae6a037825d937a2b61b2125064c Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 18 Feb 2026 13:34:24 +0000 https://status.velar.com/#14ebb578f1357e3f782f36ba67337e2c11f1ae6a037825d937a2b61b2125064c Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 18 Feb 2026 12:52:21 +0000 https://status.velar.com/#14f4ecb97ed8ebfcc421cb87d79b07890918fe63049f9fd112251fe48a9c2431 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 18 Feb 2026 12:40:26 +0000 https://status.velar.com/#14f4ecb97ed8ebfcc421cb87d79b07890918fe63049f9fd112251fe48a9c2431 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 18 Feb 2026 11:25:28 +0000 https://status.velar.com/#c7c99d792b4f8f889084583a703098247c83d84a40a3773331e38e439aeba089 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 18 Feb 2026 10:46:19 +0000 https://status.velar.com/#c7c99d792b4f8f889084583a703098247c83d84a40a3773331e38e439aeba089 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 18 Feb 2026 10:37:31 +0000 https://status.velar.com/#136536a448a3119b64bc5178b9eb7e064b764ef6a4b1e5114e0f55bfd91bace4 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 18 Feb 2026 10:31:24 +0000 https://status.velar.com/#136536a448a3119b64bc5178b9eb7e064b764ef6a4b1e5114e0f55bfd91bace4 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 18 Feb 2026 09:58:24 +0000 https://status.velar.com/#d36e4cef4fe00e2b43ad9cfa06444a1b7fcfb432d33cbdcac42cc582ec5f494a Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 18 Feb 2026 09:40:20 +0000 https://status.velar.com/#d36e4cef4fe00e2b43ad9cfa06444a1b7fcfb432d33cbdcac42cc582ec5f494a Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 18 Feb 2026 09:10:25 +0000 https://status.velar.com/#ae9082d8035a571a76cb64bdf634b4e2e0b50d28ada804893d1b672e424cc768 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 18 Feb 2026 08:58:20 +0000 https://status.velar.com/#ae9082d8035a571a76cb64bdf634b4e2e0b50d28ada804893d1b672e424cc768 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 18 Feb 2026 08:28:17 +0000 https://status.velar.com/#e7a7ec85c29e3dab7c0195253e280cada16511265b6e29b95fd5fd6e16d714f0 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 18 Feb 2026 07:10:21 +0000 https://status.velar.com/#e7a7ec85c29e3dab7c0195253e280cada16511265b6e29b95fd5fd6e16d714f0 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 18 Feb 2026 06:19:27 +0000 https://status.velar.com/#fc14a2f082de38143ee008727035160e9534a4f51d18be84fe2fad47a5249128 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 18 Feb 2026 06:04:17 +0000 https://status.velar.com/#fc14a2f082de38143ee008727035160e9534a4f51d18be84fe2fad47a5249128 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 18 Feb 2026 04:28:23 +0000 https://status.velar.com/#81c1a78d22eb27c2a7c7a44d17cda3b0853af19ab0851434570f12c51046f6e6 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 18 Feb 2026 04:25:27 +0000 https://status.velar.com/#81c1a78d22eb27c2a7c7a44d17cda3b0853af19ab0851434570f12c51046f6e6 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 18 Feb 2026 04:10:23 +0000 https://status.velar.com/#43ad06283e59d18a91cc558bd25ef5e24b026651634ce94730ac4da0c17b071a Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 18 Feb 2026 04:01:30 +0000 https://status.velar.com/#43ad06283e59d18a91cc558bd25ef5e24b026651634ce94730ac4da0c17b071a Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 18 Feb 2026 03:22:23 +0000 https://status.velar.com/#6cafe9090cb530879188e488080290701bca9b48f7290dae761fabafecec4972 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 18 Feb 2026 02:34:24 +0000 https://status.velar.com/#6cafe9090cb530879188e488080290701bca9b48f7290dae761fabafecec4972 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 18 Feb 2026 02:28:16 +0000 https://status.velar.com/#c5bdf82ea7d512389b860102547b592cd68290fca3673e19c9484399df219543 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 18 Feb 2026 02:10:19 +0000 https://status.velar.com/#c5bdf82ea7d512389b860102547b592cd68290fca3673e19c9484399df219543 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 18 Feb 2026 01:58:24 +0000 https://status.velar.com/#f3329427040a538951aaa2f5334d0f03ad5d077516965a7fbb88d75b601e4114 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 18 Feb 2026 01:43:21 +0000 https://status.velar.com/#f3329427040a538951aaa2f5334d0f03ad5d077516965a7fbb88d75b601e4114 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 17 Feb 2026 22:22:26 +0000 https://status.velar.com/#0a52e2e5d8a3aeba52b0a7c27a0731ca5e927cade78c497523ba7fb2a6f27434 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 17 Feb 2026 22:04:23 +0000 https://status.velar.com/#0a52e2e5d8a3aeba52b0a7c27a0731ca5e927cade78c497523ba7fb2a6f27434 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 17 Feb 2026 20:22:40 +0000 https://status.velar.com/#3990569e815e47d46f1c2c9e5cd289d1ffa3591440db6dec10877713e3a7eb77 bridge.velar.com recovered https://status.velar.com/ Tue, 17 Feb 2026 20:18:11 +0000 https://status.velar.com/#d9df35257bea56c4c539d7081a0aca0af19c3dde74562aaa820b56d089fec28c Web App (perpdex.velar.com) recovered https://status.velar.com/ Tue, 17 Feb 2026 20:15:57 +0000 https://status.velar.com/#9bcea34632dcb8b28e5b59f36060c63a77614ef085ad9858e68a37caf1313416 Web App (app.velar.com) recovered https://status.velar.com/ Tue, 17 Feb 2026 20:15:54 +0000 https://status.velar.com/#b8b5609d99278d1d93c0e44d243accb7148d390ab2d7a265d4e8a1374b7195dd velar.com recovered https://status.velar.com/ Tue, 17 Feb 2026 20:15:24 +0000 https://status.velar.com/#d9df35257bea56c4c539d7081a0aca0af19c3dde74562aaa820b56d089fec28c Web App (perpdex.velar.com) went down https://status.velar.com/ Tue, 17 Feb 2026 20:13:39 +0000 https://status.velar.com/#3990569e815e47d46f1c2c9e5cd289d1ffa3591440db6dec10877713e3a7eb77 bridge.velar.com went down https://status.velar.com/ Tue, 17 Feb 2026 20:13:16 +0000 https://status.velar.com/#b8b5609d99278d1d93c0e44d243accb7148d390ab2d7a265d4e8a1374b7195dd velar.com went down https://status.velar.com/ Tue, 17 Feb 2026 20:10:22 +0000 https://status.velar.com/#0a5faa45d721d0db38182419e136cab4cfe8ecee1d80c78288cba583bd8d95a3 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 17 Feb 2026 20:10:14 +0000 https://status.velar.com/#9bcea34632dcb8b28e5b59f36060c63a77614ef085ad9858e68a37caf1313416 Web App (app.velar.com) went down https://status.velar.com/ Tue, 17 Feb 2026 20:07:39 +0000 https://status.velar.com/#0a5faa45d721d0db38182419e136cab4cfe8ecee1d80c78288cba583bd8d95a3 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 17 Feb 2026 20:04:19 +0000 https://status.velar.com/#cac8ef624500d8a00e73c3d680e9d9b627c2cac58753146d5c2cd189cc43ec78 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 17 Feb 2026 18:37:25 +0000 https://status.velar.com/#cac8ef624500d8a00e73c3d680e9d9b627c2cac58753146d5c2cd189cc43ec78 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 17 Feb 2026 18:28:17 +0000 https://status.velar.com/#eb2c6e921398198850cb2854549c0744496766d8dde9f3955c3a28fbac71e5bb Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 17 Feb 2026 18:01:24 +0000 https://status.velar.com/#eb2c6e921398198850cb2854549c0744496766d8dde9f3955c3a28fbac71e5bb Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 17 Feb 2026 17:31:21 +0000 https://status.velar.com/#7205244ec32bd0046fd0c5ce2cc9275b79e93224b4e0787c08e91e5809b26c75 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 17 Feb 2026 17:22:21 +0000 https://status.velar.com/#7205244ec32bd0046fd0c5ce2cc9275b79e93224b4e0787c08e91e5809b26c75 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 17 Feb 2026 16:52:18 +0000 https://status.velar.com/#bc469718d6b4b81ef54422ff601311710cc3c4be8ef87c27d38dad62f3907f68 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 17 Feb 2026 15:58:21 +0000 https://status.velar.com/#bc469718d6b4b81ef54422ff601311710cc3c4be8ef87c27d38dad62f3907f68 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 17 Feb 2026 13:28:18 +0000 https://status.velar.com/#06eca616b15b9c99ce9ce513fb2f37252a1ae4bf52fdf78bc575c42aed8b27c8 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 17 Feb 2026 13:22:23 +0000 https://status.velar.com/#06eca616b15b9c99ce9ce513fb2f37252a1ae4bf52fdf78bc575c42aed8b27c8 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 17 Feb 2026 12:46:24 +0000 https://status.velar.com/#c63caa7c80f1d63c86f5a26b442d75547f9e0ad43eeed1cdbc25d0fcb018e29d Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 17 Feb 2026 11:40:15 +0000 https://status.velar.com/#c63caa7c80f1d63c86f5a26b442d75547f9e0ad43eeed1cdbc25d0fcb018e29d Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 17 Feb 2026 11:22:23 +0000 https://status.velar.com/#448f0f75e116b680f1515b099300a6c14a77da2c90919dec37f9be163347a55f Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 17 Feb 2026 11:04:22 +0000 https://status.velar.com/#448f0f75e116b680f1515b099300a6c14a77da2c90919dec37f9be163347a55f Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 17 Feb 2026 10:34:22 +0000 https://status.velar.com/#863c8a8dc10bf5bf379b4c94e15faf10d18a63df04c488bf897fd7598b991dc1 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 17 Feb 2026 10:25:21 +0000 https://status.velar.com/#863c8a8dc10bf5bf379b4c94e15faf10d18a63df04c488bf897fd7598b991dc1 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 17 Feb 2026 10:16:16 +0000 https://status.velar.com/#db84e2e524c060c784f271b4ab33e5ef9e57fd070ba0bb32a07df1233ab481f7 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 17 Feb 2026 09:58:18 +0000 https://status.velar.com/#db84e2e524c060c784f271b4ab33e5ef9e57fd070ba0bb32a07df1233ab481f7 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 17 Feb 2026 06:40:17 +0000 https://status.velar.com/#5d01b8d3c736af9d910f9d70265a4849cbcf32def78ccabdacaf471c0decb95a Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 17 Feb 2026 06:19:18 +0000 https://status.velar.com/#5d01b8d3c736af9d910f9d70265a4849cbcf32def78ccabdacaf471c0decb95a Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 17 Feb 2026 04:40:27 +0000 https://status.velar.com/#cb214fc643dba21f7d1fafdcac86943ccab69e9b9692cbc3a56b7ae96deac75d Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 17 Feb 2026 04:37:38 +0000 https://status.velar.com/#cb214fc643dba21f7d1fafdcac86943ccab69e9b9692cbc3a56b7ae96deac75d Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 17 Feb 2026 03:37:24 +0000 https://status.velar.com/#80b7840d1325826bbf5e047a86c9447d146754030ec0a5939eaffeaa1871e948 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 17 Feb 2026 03:25:27 +0000 https://status.velar.com/#80b7840d1325826bbf5e047a86c9447d146754030ec0a5939eaffeaa1871e948 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 17 Feb 2026 01:28:22 +0000 https://status.velar.com/#876b5606e4857909f4b5f6bd72a56aa39306c6be4974f31b2cdb9863975f3975 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 17 Feb 2026 01:16:14 +0000 https://status.velar.com/#876b5606e4857909f4b5f6bd72a56aa39306c6be4974f31b2cdb9863975f3975 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 16 Feb 2026 20:13:29 +0000 https://status.velar.com/#80b570515ea428a2e860d556eb85fcd5145e251d8c5d04969e739735d0de4591 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 16 Feb 2026 20:01:19 +0000 https://status.velar.com/#80b570515ea428a2e860d556eb85fcd5145e251d8c5d04969e739735d0de4591 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 16 Feb 2026 19:13:24 +0000 https://status.velar.com/#99fd28abfa50d346c2002ae84e7df26f6bc14bc2f17b97079c1decafb35d9213 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 16 Feb 2026 19:07:19 +0000 https://status.velar.com/#99fd28abfa50d346c2002ae84e7df26f6bc14bc2f17b97079c1decafb35d9213 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 16 Feb 2026 15:25:27 +0000 https://status.velar.com/#d707c63bcf901eedab717baf63e65eb8986acef72f5c081833efae3d475784c5 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 16 Feb 2026 14:58:25 +0000 https://status.velar.com/#d707c63bcf901eedab717baf63e65eb8986acef72f5c081833efae3d475784c5 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 16 Feb 2026 13:31:26 +0000 https://status.velar.com/#4f3514731f9f92d7d8473eff5b9078b2c2fd6b29ebcd3d48968abc9f5416a56e Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 16 Feb 2026 13:25:21 +0000 https://status.velar.com/#4f3514731f9f92d7d8473eff5b9078b2c2fd6b29ebcd3d48968abc9f5416a56e Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 16 Feb 2026 13:01:28 +0000 https://status.velar.com/#9bf52edceb0dcff8311fe02f09ba3a037a9bdc3bc557267ead2f44d812fe3022 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 16 Feb 2026 12:40:14 +0000 https://status.velar.com/#9bf52edceb0dcff8311fe02f09ba3a037a9bdc3bc557267ead2f44d812fe3022 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 16 Feb 2026 05:31:23 +0000 https://status.velar.com/#b38eda8ab2b91490b9eabf661ad0667d262156e6ca7a3f315fe53d50dc2d5bac Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 16 Feb 2026 05:28:18 +0000 https://status.velar.com/#b38eda8ab2b91490b9eabf661ad0667d262156e6ca7a3f315fe53d50dc2d5bac Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 16 Feb 2026 04:10:18 +0000 https://status.velar.com/#5a767dc2b3b55aaf74c10f6b16e0561689f95452dc4a3a8cb26d16d8f267a2fd Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 16 Feb 2026 03:58:20 +0000 https://status.velar.com/#5a767dc2b3b55aaf74c10f6b16e0561689f95452dc4a3a8cb26d16d8f267a2fd Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 15 Feb 2026 20:10:20 +0000 https://status.velar.com/#c17c35638d8d547bdff73539306ce35f5584b310c70723e9a047b962edd202f8 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 15 Feb 2026 20:07:25 +0000 https://status.velar.com/#c17c35638d8d547bdff73539306ce35f5584b310c70723e9a047b962edd202f8 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 15 Feb 2026 18:55:23 +0000 https://status.velar.com/#574e7b0a890e2c870bc2874666d6edb2d02bff84bd7cc2586d2025124b55a2e5 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 15 Feb 2026 18:52:19 +0000 https://status.velar.com/#574e7b0a890e2c870bc2874666d6edb2d02bff84bd7cc2586d2025124b55a2e5 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 15 Feb 2026 16:25:25 +0000 https://status.velar.com/#868c36e9bd6972d9f08503a502aa3c9580b6abac55ed5f00bd2e7d45dae5b9fc Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 15 Feb 2026 16:16:14 +0000 https://status.velar.com/#868c36e9bd6972d9f08503a502aa3c9580b6abac55ed5f00bd2e7d45dae5b9fc Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 15 Feb 2026 15:07:19 +0000 https://status.velar.com/#4ce92223efeff4c7a95d6ebeffac714361e919ce021991a242df66a5d6548454 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 15 Feb 2026 15:01:26 +0000 https://status.velar.com/#4ce92223efeff4c7a95d6ebeffac714361e919ce021991a242df66a5d6548454 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 15 Feb 2026 10:40:18 +0000 https://status.velar.com/#67a1afb6f53438cf0aa2de69624aee531970d871381cbe29b73d464f5364b1d1 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 15 Feb 2026 10:16:25 +0000 https://status.velar.com/#67a1afb6f53438cf0aa2de69624aee531970d871381cbe29b73d464f5364b1d1 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 15 Feb 2026 03:31:24 +0000 https://status.velar.com/#645ffef97f5516b6c5c67cac56ac1ffe44f8479dce8d495799f9742e28b054b2 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 15 Feb 2026 03:28:16 +0000 https://status.velar.com/#645ffef97f5516b6c5c67cac56ac1ffe44f8479dce8d495799f9742e28b054b2 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 15 Feb 2026 01:22:22 +0000 https://status.velar.com/#2a192175af5f63563cb8b24b0aa118dd6fbcc43485c9a47747bd6e5546e98576 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 15 Feb 2026 01:13:20 +0000 https://status.velar.com/#2a192175af5f63563cb8b24b0aa118dd6fbcc43485c9a47747bd6e5546e98576 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 15 Feb 2026 00:23:13 +0000 https://status.velar.com/#c28ecb62ce99d9e21a33a0a11ef24e665a4c17b9db8fedc909e68e2e0c8653d1 api.velar.co recovered https://status.velar.com/ Sun, 15 Feb 2026 00:17:27 +0000 https://status.velar.com/#c28ecb62ce99d9e21a33a0a11ef24e665a4c17b9db8fedc909e68e2e0c8653d1 api.velar.co went down https://status.velar.com/ Sat, 14 Feb 2026 22:07:18 +0000 https://status.velar.com/#3fbcc16eb349255267a3e1e5fd7ad96bb515ae187007d1ff7769945a5ed59715 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 14 Feb 2026 21:58:17 +0000 https://status.velar.com/#3fbcc16eb349255267a3e1e5fd7ad96bb515ae187007d1ff7769945a5ed59715 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 14 Feb 2026 20:25:23 +0000 https://status.velar.com/#ac8ad6544b5b7b6a2244fe5d0f28dde4cc03ea00a1479adbf386f5d3e70f61fd Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 14 Feb 2026 20:22:23 +0000 https://status.velar.com/#ac8ad6544b5b7b6a2244fe5d0f28dde4cc03ea00a1479adbf386f5d3e70f61fd Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 14 Feb 2026 19:04:19 +0000 https://status.velar.com/#755078d98234282993865b3b658eb2ca17deecc3a8ff9d98a2f3e6eef6d41f7f Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 14 Feb 2026 19:01:24 +0000 https://status.velar.com/#755078d98234282993865b3b658eb2ca17deecc3a8ff9d98a2f3e6eef6d41f7f Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 14 Feb 2026 18:16:22 +0000 https://status.velar.com/#807e54d6c2abb7fb27ab920df0ae1446ed1c61fc8b5980e61e4128ac66d86c77 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 14 Feb 2026 18:10:26 +0000 https://status.velar.com/#807e54d6c2abb7fb27ab920df0ae1446ed1c61fc8b5980e61e4128ac66d86c77 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 14 Feb 2026 17:55:19 +0000 https://status.velar.com/#bee37e078390de04cf4838032e822463bf284ef9f0f5ab5a1a372e5fb51745f8 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 14 Feb 2026 17:40:17 +0000 https://status.velar.com/#bee37e078390de04cf4838032e822463bf284ef9f0f5ab5a1a372e5fb51745f8 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 14 Feb 2026 16:52:17 +0000 https://status.velar.com/#dca5b2e6400fa684679c4525b12ff41207dbfbe2a948c68faf7abf1b9bcb8f1a Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 14 Feb 2026 16:49:22 +0000 https://status.velar.com/#dca5b2e6400fa684679c4525b12ff41207dbfbe2a948c68faf7abf1b9bcb8f1a Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 14 Feb 2026 16:10:20 +0000 https://status.velar.com/#0c9647c5b18945571e75f8f78d38cf2c04a6593c191a0b5e31b850273f87777c Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 14 Feb 2026 16:07:25 +0000 https://status.velar.com/#0c9647c5b18945571e75f8f78d38cf2c04a6593c191a0b5e31b850273f87777c Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sat, 14 Feb 2026 11:22:18 +0000 https://status.velar.com/#e5d0797a7f76d152293dcdf37766e163a90c4a020f9782384f27ca29ae861c52 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sat, 14 Feb 2026 11:13:26 +0000 https://status.velar.com/#e5d0797a7f76d152293dcdf37766e163a90c4a020f9782384f27ca29ae861c52 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 13 Feb 2026 20:04:17 +0000 https://status.velar.com/#cfbb02098627fea65a1d889f7e339cf8805686ec069857c52ad457ed6610951a Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 13 Feb 2026 20:01:31 +0000 https://status.velar.com/#cfbb02098627fea65a1d889f7e339cf8805686ec069857c52ad457ed6610951a Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 13 Feb 2026 11:31:28 +0000 https://status.velar.com/#7891a3b86044b8cfb350f748f1128a301778cc0ad57fe6ad7c48535d88a5407a Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 13 Feb 2026 11:22:20 +0000 https://status.velar.com/#7891a3b86044b8cfb350f748f1128a301778cc0ad57fe6ad7c48535d88a5407a Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 13 Feb 2026 09:58:20 +0000 https://status.velar.com/#408d7f1ed82cc66b484ab2bb06f85a1190f608833f42e71a594e6fc24938d52e Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 13 Feb 2026 09:55:16 +0000 https://status.velar.com/#408d7f1ed82cc66b484ab2bb06f85a1190f608833f42e71a594e6fc24938d52e Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Fri, 13 Feb 2026 01:22:23 +0000 https://status.velar.com/#bda07d6ad44e3c7a1da1b1445f3ee2a8b39415b28b488e840a53387480d1b9ac Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Fri, 13 Feb 2026 01:16:15 +0000 https://status.velar.com/#bda07d6ad44e3c7a1da1b1445f3ee2a8b39415b28b488e840a53387480d1b9ac Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 12 Feb 2026 23:13:25 +0000 https://status.velar.com/#2244415c5e398155c54eb3fb6286fa43bea77459c5e53c8d054d161b4678e84f Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 12 Feb 2026 23:10:20 +0000 https://status.velar.com/#2244415c5e398155c54eb3fb6286fa43bea77459c5e53c8d054d161b4678e84f Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 12 Feb 2026 21:43:26 +0000 https://status.velar.com/#42bbedc342d27818c3cfb5bd7863688872a912f77396320be031adb0bca80612 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 12 Feb 2026 21:40:14 +0000 https://status.velar.com/#42bbedc342d27818c3cfb5bd7863688872a912f77396320be031adb0bca80612 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 12 Feb 2026 16:46:25 +0000 https://status.velar.com/#4af304887858b47d919bdf0b7fa25cd5cce602092c5b591732b4f7e30f473fb1 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 12 Feb 2026 16:34:17 +0000 https://status.velar.com/#4af304887858b47d919bdf0b7fa25cd5cce602092c5b591732b4f7e30f473fb1 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 12 Feb 2026 14:40:29 +0000 https://status.velar.com/#adc60d6f411d23246d4174f4b3cc13c1abee760deb718579d01df6bdaa69d5d9 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 12 Feb 2026 14:34:21 +0000 https://status.velar.com/#adc60d6f411d23246d4174f4b3cc13c1abee760deb718579d01df6bdaa69d5d9 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 12 Feb 2026 06:46:21 +0000 https://status.velar.com/#8d7024a74fda1c8c083823a09c49f9bca1cdf24ccafcb0759967b652a0f9186b Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Thu, 12 Feb 2026 06:40:29 +0000 https://status.velar.com/#8d7024a74fda1c8c083823a09c49f9bca1cdf24ccafcb0759967b652a0f9186b Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 11 Feb 2026 23:40:19 +0000 https://status.velar.com/#252e6ce4bc919cb4f0726844788fdddb407607f2464325317704ac6dfb742d75 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 11 Feb 2026 23:34:21 +0000 https://status.velar.com/#252e6ce4bc919cb4f0726844788fdddb407607f2464325317704ac6dfb742d75 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 11 Feb 2026 22:46:21 +0000 https://status.velar.com/#c511acfc799f093ac769e11fa65dd940df2588b867bdb9fd6810e5e46ff079fa Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 11 Feb 2026 22:40:17 +0000 https://status.velar.com/#c511acfc799f093ac769e11fa65dd940df2588b867bdb9fd6810e5e46ff079fa Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 11 Feb 2026 20:10:20 +0000 https://status.velar.com/#cd398acd0df91ddb96bb777a9acb7cd0c06d88e02c9a1e9090b863dfc1d8f1c4 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 11 Feb 2026 20:07:30 +0000 https://status.velar.com/#cd398acd0df91ddb96bb777a9acb7cd0c06d88e02c9a1e9090b863dfc1d8f1c4 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 11 Feb 2026 19:04:15 +0000 https://status.velar.com/#716f332ab9e8ff54c080346ea154020841e112db41f8d583904520579643e4a9 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 11 Feb 2026 18:58:17 +0000 https://status.velar.com/#716f332ab9e8ff54c080346ea154020841e112db41f8d583904520579643e4a9 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 11 Feb 2026 12:46:19 +0000 https://status.velar.com/#8962882b35ed4742958b6aebfc5e90b1eca29902c7953803a2492c459a8612b4 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Wed, 11 Feb 2026 12:43:23 +0000 https://status.velar.com/#8962882b35ed4742958b6aebfc5e90b1eca29902c7953803a2492c459a8612b4 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Wed, 11 Feb 2026 12:25:49 +0000 https://status.velar.com/#355998720d9fe0e4775575ef74b89818235d36d612aff20e0151fcf125a23f78 bridge.velar.com recovered https://status.velar.com/ Wed, 11 Feb 2026 12:18:54 +0000 https://status.velar.com/#a4a18eb453894c5e951f2d767f88c21e8b5f9bd73e8a03b23634afd5610a573f Web App (app.velar.com) recovered https://status.velar.com/ Wed, 11 Feb 2026 12:16:33 +0000 https://status.velar.com/#355998720d9fe0e4775575ef74b89818235d36d612aff20e0151fcf125a23f78 bridge.velar.com went down https://status.velar.com/ Wed, 11 Feb 2026 12:10:51 +0000 https://status.velar.com/#a4a18eb453894c5e951f2d767f88c21e8b5f9bd73e8a03b23634afd5610a573f Web App (app.velar.com) went down https://status.velar.com/ Tue, 10 Feb 2026 13:37:30 +0000 https://status.velar.com/#64bb1b3c091236ac9573d7ebadf955157c74ef06c2699947db12f03a5b316822 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 10 Feb 2026 13:28:26 +0000 https://status.velar.com/#64bb1b3c091236ac9573d7ebadf955157c74ef06c2699947db12f03a5b316822 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 10 Feb 2026 08:37:27 +0000 https://status.velar.com/#80e9a59e4583b0673ae3aec1e583c7855a6da7ed9237bf4897a3fdca900a7612 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 10 Feb 2026 08:34:25 +0000 https://status.velar.com/#80e9a59e4583b0673ae3aec1e583c7855a6da7ed9237bf4897a3fdca900a7612 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 10 Feb 2026 07:10:20 +0000 https://status.velar.com/#cc6d296df2fa2ea4a8d5e8a0ce029ef1c1ba9afb69a0b2b221e9a8181406cc43 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 10 Feb 2026 07:04:18 +0000 https://status.velar.com/#cc6d296df2fa2ea4a8d5e8a0ce029ef1c1ba9afb69a0b2b221e9a8181406cc43 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Tue, 10 Feb 2026 02:10:21 +0000 https://status.velar.com/#9679d0d6f5b5a2dae0d44267e2e753f46da1c19cbb57cc360f2e3cc74f6c4c65 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Tue, 10 Feb 2026 02:08:03 +0000 https://status.velar.com/#9679d0d6f5b5a2dae0d44267e2e753f46da1c19cbb57cc360f2e3cc74f6c4c65 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 09 Feb 2026 11:43:27 +0000 https://status.velar.com/#99d1c19c432dfb396cba2e0a0bb75575d3556c75350586439c9a5d4347e544bc Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 09 Feb 2026 11:40:24 +0000 https://status.velar.com/#99d1c19c432dfb396cba2e0a0bb75575d3556c75350586439c9a5d4347e544bc Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Mon, 09 Feb 2026 11:10:26 +0000 https://status.velar.com/#7e0d9eab5495835541b5540d9fc4e3c11a9caea1a60ec7f9dfebe5683b678eb2 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Mon, 09 Feb 2026 11:04:24 +0000 https://status.velar.com/#7e0d9eab5495835541b5540d9fc4e3c11a9caea1a60ec7f9dfebe5683b678eb2 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 08 Feb 2026 16:10:19 +0000 https://status.velar.com/#7c1f961db8517f9e97d805b307f9b66017e5b5ecbc33746071f2481749150fea Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 08 Feb 2026 15:52:22 +0000 https://status.velar.com/#7c1f961db8517f9e97d805b307f9b66017e5b5ecbc33746071f2481749150fea Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 08 Feb 2026 09:49:26 +0000 https://status.velar.com/#c4727f46b30df443bea696d03d128b559a23afb9452de79000bc53204d217181 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 08 Feb 2026 09:37:25 +0000 https://status.velar.com/#c4727f46b30df443bea696d03d128b559a23afb9452de79000bc53204d217181 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Sun, 08 Feb 2026 06:10:28 +0000 https://status.velar.com/#b05646755c7db2cae35fda943dcd052d596f44231c748085e607b40115f3dfa6 Gateway (perpdex-api.velar.network) recovered https://status.velar.com/ Sun, 08 Feb 2026 06:04:24 +0000 https://status.velar.com/#b05646755c7db2cae35fda943dcd052d596f44231c748085e607b40115f3dfa6 Gateway (perpdex-api.velar.network) went down https://status.velar.com/ Thu, 05 Feb 2026 09:08:15 +0000 https://status.velar.com/#3b9e512f814bff6eadcc87370658f1dea67f39468bd0a587622c80b8e465362b api.velar.co recovered https://status.velar.com/ Thu, 05 Feb 2026 09:05:19 +0000 https://status.velar.com/#3b9e512f814bff6eadcc87370658f1dea67f39468bd0a587622c80b8e465362b api.velar.co went down https://status.velar.com/ Tue, 03 Feb 2026 19:51:53 +0000 https://status.velar.com/#e730f2f32c0877d43189c883586802b0554a3f59a2a824174d2d1046d486a167 Web App (app.velar.com) recovered https://status.velar.com/ Tue, 03 Feb 2026 19:49:12 +0000 https://status.velar.com/#e730f2f32c0877d43189c883586802b0554a3f59a2a824174d2d1046d486a167 Web App (app.velar.com) went down