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