Incidents and maintenance reported on status page for Veebor S.r.l. https://status.veebor.dev/ https://d1lppblt9t2x15.cloudfront.net/logos/eee319deb262c07d45439cfc4c5b2704.png https://status.veebor.dev/ en https://status.veebor.dev/incident/1078979 Thu, 01 Oct 2026 06:49:21 -0000 https://status.veebor.dev/incident/1078979#72a183e79232f4253f790914b65fbbe27362842019cb4bedbf6d3d351d00d72b Incident Veebor Main Website recovered. https://status.veebor.dev/incident/1078979 Thu, 01 Oct 2026 06:29:44 -0000 https://status.veebor.dev/incident/1078979#1de3e73678e0fe39e6f468c21b58b070fecc45d4b7efe7c81317ed33816e4496 Incident Veebor Main Website went down. https://status.veebor.dev/incident/1078574 Wed, 30 Sep 2026 23:40:22 -0000 https://status.veebor.dev/incident/1078574#22f1b7bd6265a5f9b4ea7eafe44c09ffd70998c5cc22af95119a6981b8fa9a53 Incident Veebor Main Website recovered. https://status.veebor.dev/incident/1078574 Wed, 30 Sep 2026 23:32:25 -0000 https://status.veebor.dev/incident/1078574#e46fbc21a0c261694b736691e1d88aa526da99799f13bef7cfaae87da270236a Incident Veebor Main Website went down. https://status.veebor.dev/incident/1078574 Wed, 30 Sep 2026 19:19:14 -0000 https://status.veebor.dev/incident/1078574#a402b4922500d12308b5028f4425874e43677324b748813f4ec060883a5c7d7c Incident Veebor Main Website recovered. https://status.veebor.dev/incident/1078574 Wed, 30 Sep 2026 19:14:46 -0000 https://status.veebor.dev/incident/1078574#0001b07d81ac2d98fad7b7c52f792cf344edc54ecf5c90b208c7ed0796d92f99 Incident Veebor Main Website went down. https://status.veebor.dev/incident/1076988 Tue, 29 Sep 2026 07:52:49 -0000 https://status.veebor.dev/incident/1076988#0e6153aa410629c686155a1b85793b10ac0c18dacb5ca6ef09df32341679d849 Incident Veebor Main Website recovered. https://status.veebor.dev/incident/1076988 Tue, 29 Sep 2026 07:44:43 -0000 https://status.veebor.dev/incident/1076988#97bd444f51f5d1f4f3c1095e5d922d8f5bd3f327c135f19ecb1f674d0fcd559a Incident Veebor Main Website went down. https://status.veebor.dev/incident/1075632 Sun, 27 Sep 2026 20:01:14 -0000 https://status.veebor.dev/incident/1075632#1d180845fad41b2c19d0bd84569d2e1387d0084905b0a48308ed6781d41f212c Incident Veebor Main Website recovered. https://status.veebor.dev/incident/1075632 Sun, 27 Sep 2026 19:56:51 -0000 https://status.veebor.dev/incident/1075632#9e31aceb4b4eb9b27a221dbe6c2665f17bac81ab35def2a2155904231acdc7a2 Incident Veebor Main Website went down. https://status.veebor.dev/incident/1072890 Thu, 24 Sep 2026 10:01:22 -0000 https://status.veebor.dev/incident/1072890#4016d9327811684a7c27357b958352cfd907fa38317ce2d021fd8380b5f196f5 Incident Veebor Main Website recovered. https://status.veebor.dev/incident/1072890 Thu, 24 Sep 2026 09:54:52 -0000 https://status.veebor.dev/incident/1072890#4a03708f70a38925b58aa309b6ca6d66a618bc8011a67627e5a5297fe209a5be Incident Veebor Main Website went down. https://status.veebor.dev/incident/1070468 Mon, 21 Sep 2026 16:05:30 -0000 https://status.veebor.dev/incident/1070468#44e6b2f5203faa32e807b5f91ff6a5f546fa5c824cc84b3af97088f92cb9f911 Incident Veebor Main Website recovered. https://status.veebor.dev/incident/1070468 Mon, 21 Sep 2026 15:56:36 -0000 https://status.veebor.dev/incident/1070468#2613a30fff00e6fe7effd2544f608aa1ca1753ce9b2b8e1bc44af3a3fe8afc9e Incident Veebor Main Website went down. https://status.veebor.dev/incident/1069648 Sun, 20 Sep 2026 19:16:23 -0000 https://status.veebor.dev/incident/1069648#ec2487c9ab34858e0ac480b6d72a618fe24b02b46a644b4a5c779f4ab171bd66 Incident Veebor Storage Service recovered. https://status.veebor.dev/incident/1069648 Sun, 20 Sep 2026 19:08:47 -0000 https://status.veebor.dev/incident/1069648#3827abb6324c4d2373604c3724a1a2d6f249fd25fb323bc843623ded817067cb Incident Veebor Storage Service went down. https://status.veebor.dev/incident/1062162 Sun, 13 Sep 2026 22:40:23 -0000 https://status.veebor.dev/incident/1062162#04ff4d92e3147c91553035261ca83ec91e8a84498feefe3316c56c6036040eb9 Incident Veebor Main Website recovered. https://status.veebor.dev/incident/1062162 Sun, 13 Sep 2026 22:36:13 -0000 https://status.veebor.dev/incident/1062162#7aaf3d091587a78939446b9ef3fe052ae329d782f3a21ab9fdd44be58217fc04 Incident Veebor Main Website went down. https://status.veebor.dev/incident/1056588 Tue, 08 Sep 2026 08:11:13 -0000 https://status.veebor.dev/incident/1056588#bfce34277f963bf4adad3a84c3a8a8ee2ca10d70b9a1382e4aaec5f6596a04d2 Incident Veebor Password Service recovered. https://status.veebor.dev/incident/1056588 Tue, 08 Sep 2026 08:10:48 -0000 https://status.veebor.dev/incident/1056588#b2d747fc477ff5a0067b1ee00ad5552195b32ffd77c5a11d60d14ec3f2a1563d Incident ping routing service (alx) and Veebor Track Service recovered. https://status.veebor.dev/incident/1056588 Tue, 08 Sep 2026 08:06:25 -0000 https://status.veebor.dev/incident/1056588#de1ece122b4a54b07d28584f2b73ef00ecc431030cbc6302dc8e208ef5993f17 Incident Veebor Track Service went down. https://status.veebor.dev/incident/1056588 Tue, 08 Sep 2026 08:05:52 -0000 https://status.veebor.dev/incident/1056588#ff8362ef1ee0d5e4a8ca6eb8b7af59ff6f4d5e892174c289fc0ea7380465a45b Incident ping routing service (alx) went down. https://status.veebor.dev/incident/1056588 Tue, 08 Sep 2026 08:05:12 -0000 https://status.veebor.dev/incident/1056588#12204e8611883bfbc30bf37ea34182c81f8fd3f80b6260f7fe49b7f1effb0ecf Incident Veebor Password Service went down. https://status.veebor.dev/incident/1006542 Sun, 09 Aug 2026 22:43:18 -0000 https://status.veebor.dev/incident/1006542#7db649e2bb68338ec0dbe09656be677dee2b02bb0d94941cbb82e767f0f5c52f Incident Veebor Main Website recovered. https://status.veebor.dev/incident/1006542 Sun, 09 Aug 2026 22:38:48 -0000 https://status.veebor.dev/incident/1006542#271ffec859e7bdbdd5d204efd32ee92003cceb4c276eb71e877ba42efaad0005 Incident Veebor Main Website went down. https://status.veebor.dev/incident/979461 Sun, 26 Jul 2026 23:58:12 -0000 https://status.veebor.dev/incident/979461#90a46df2ec384f04873e9c8efd7d171f15d8f40f72436d96e314472d833c9ec9 Incident Veebor Storage Service recovered. https://status.veebor.dev/incident/979461 Sun, 26 Jul 2026 23:50:39 -0000 https://status.veebor.dev/incident/979461#87d46915cfbddce2120de1ecbe96d8fed0db9736f81f142edec196c5a1abe1ad Incident Veebor Storage Service went down. https://status.veebor.dev/incident/979461 Sun, 26 Jul 2026 19:25:52 -0000 https://status.veebor.dev/incident/979461#3b55768de04f2835df8c0ee212cab7f41fda31187587ccdd4049bfc2da2d9a97 Incident Veebor Storage Service recovered. https://status.veebor.dev/incident/979461 Sun, 26 Jul 2026 19:12:00 -0000 https://status.veebor.dev/incident/979461#c8a07b1fbafe54f94de11caa916e3e7815d02ad4272f4a470ce2362959655a15 Incident Veebor Storage Service went down. https://status.veebor.dev/incident/972090 Tue, 21 Jul 2026 21:52:11 -0000 https://status.veebor.dev/incident/972090#1481ffe069b3d4dd21d3bcbf7872b4127bc091249527b425409bc8d678155214 Incident Veebor Main Website recovered. https://status.veebor.dev/incident/972090 Tue, 21 Jul 2026 21:48:00 -0000 https://status.veebor.dev/incident/972090#31b37d414daa8e4fc808885e0f9bcbcc6675a076bfd22ad79a70fcd39d2823dc Incident Veebor Main Website went down. https://status.veebor.dev/incident/965183 Wed, 15 Jul 2026 22:16:15 -0000 https://status.veebor.dev/incident/965183#9001628774b17d3cd9289e93499070e1ef30c4d2728b3a38afb4015f5dda786b Incident Veebor Main Website recovered. https://status.veebor.dev/incident/965183 Wed, 15 Jul 2026 22:02:39 -0000 https://status.veebor.dev/incident/965183#d81df574f572343619b97bf10f7fa93d4d368ad872ff32912f90feb3d1cb7faf Incident Veebor Main Website went down. https://status.veebor.dev/incident/949144 Thu, 09 Jul 2026 22:46:24 -0000 https://status.veebor.dev/incident/949144#8932ab2aced626c4f17eaeb420d54686056f2a160eed4277739c1c989289829d Incident Veebor Main Website recovered. https://status.veebor.dev/incident/949144 Thu, 09 Jul 2026 22:41:36 -0000 https://status.veebor.dev/incident/949144#1f71bcde364e98d547ed652e3a595ebf0043ecc03f718c94d5289c4d1d3d083a Incident Veebor Main Website went down. https://status.veebor.dev/incident/944261 Sun, 05 Jul 2026 22:13:12 -0000 https://status.veebor.dev/incident/944261#c6ab89509400523a50b5a142e33fb05947810d0565f51285fa7096d182d7d2bb Incident Veebor Main Website recovered. https://status.veebor.dev/incident/944261 Sun, 05 Jul 2026 22:02:30 -0000 https://status.veebor.dev/incident/944261#ea3773944b1030ab083a7f4fa3b086bdacf5c48d8c26544a87d812a417fc50ea Incident Veebor Main Website went down. https://status.veebor.dev/incident/939901 Tue, 30 Jun 2026 23:58:30 -0000 https://status.veebor.dev/incident/939901#c8af0ea0b1d1d950fa1c339247519adc87d86816f81166453746d1d6b8c23c4f Incident Veebor Password Service recovered. https://status.veebor.dev/incident/939901 Tue, 30 Jun 2026 23:53:19 -0000 https://status.veebor.dev/incident/939901#5de1b558b83e973fc66297f6cfe03371b0b1820d4fd9d4663652aabef8d16dd8 Incident Veebor Password Service went down. https://status.veebor.dev/incident/900158 Tue, 19 May 2026 23:25:29 -0000 https://status.veebor.dev/incident/900158#9bdba63ed356a233bb5f17199bcaf58b1942f056791aec3098597fddeff657f0 Incident ping routing service (alx), Veebor Git Service, Veebor Track Service, and 1 other resource recovered. https://status.veebor.dev/incident/900158 Tue, 19 May 2026 23:24:46 -0000 https://status.veebor.dev/incident/900158#974b704231cfd0bbd2ef66bd8ab5f87e9b5a18d07ab82d67e7e169f18cc439eb Incident Veebor Monitoring Service recovered. https://status.veebor.dev/incident/900158 Tue, 19 May 2026 23:15:40 -0000 https://status.veebor.dev/incident/900158#07f4f34673508b55281e80a3651ddd0db5f9b8e8601b0d538503e2aee18ea74e Incident Veebor Monitoring Service went down. https://status.veebor.dev/incident/900158 Tue, 19 May 2026 23:13:38 -0000 https://status.veebor.dev/incident/900158#aac3e1f2af53b331ccc0daf165c3836d921e8d84212a7d02364d5c2fb3a98a17 Incident Veebor Git Service went down. https://status.veebor.dev/incident/900158 Tue, 19 May 2026 23:12:23 -0000 https://status.veebor.dev/incident/900158#7f24504b6cbcc311cd49150ec620c6f6ae6492d6830c69f426b5ec7a0a497ee0 Incident Veebor Track Service went down. https://status.veebor.dev/incident/900158 Tue, 19 May 2026 23:11:43 -0000 https://status.veebor.dev/incident/900158#9d2f57dff7986cc36f674751cc29f67273ad9cb27d725fa0173df5389400d80e Incident ping routing service (alx) went down. https://status.veebor.dev/incident/900158 Tue, 19 May 2026 23:11:00 -0000 https://status.veebor.dev/incident/900158#2ba886216b1e709d5d78d77a0c9b8c39c18c706e067e1a5b72004624ac081152 Incident Veebor Password Service went down. https://status.veebor.dev/incident/898223 Sun, 17 May 2026 23:49:11 -0000 https://status.veebor.dev/incident/898223#afb2e70ccd14bb14f32a4f0f2cf7a9cf74ffa7f8e7e95f8793225418bc989a5c Incident Veebor Main Website recovered. https://status.veebor.dev/incident/898223 Sun, 17 May 2026 23:45:12 -0000 https://status.veebor.dev/incident/898223#6da1de9369e9a7d0e93cf7cf5c2bb4a36c32e95023a4d728f5f6423c319bb605 Incident Veebor Main Website went down. https://status.veebor.dev/incident/892836 Wed, 13 May 2026 22:58:47 -0000 https://status.veebor.dev/incident/892836#c71535692a40034fa80fa56df546a3125a35333fe02ecdd4e4e759257dbe3a4a Incident Veebor Git Service recovered. https://status.veebor.dev/incident/892836 Wed, 13 May 2026 22:58:21 -0000 https://status.veebor.dev/incident/892836#995de6365dac019e4e56b5e1754ade7afcd937f0fc85fd6bba8479cbc4fee1d1 Incident ping routing service (alx), Veebor Track Service, and Veebor Password Service recovered. https://status.veebor.dev/incident/892836 Wed, 13 May 2026 22:58:00 -0000 https://status.veebor.dev/incident/892836#ecd94f7f826be98016e7cefcda3830f17302e0901397dd0dd2ae0cdea97a7247 Incident Veebor Monitoring Service recovered. https://status.veebor.dev/incident/892836 Wed, 13 May 2026 22:43:36 -0000 https://status.veebor.dev/incident/892836#eccbdfb910f02856ec5d02d57725f0eabe10cc379029bd677c8f7968adba2809 Incident Veebor Git Service went down. https://status.veebor.dev/incident/892836 Wed, 13 May 2026 22:42:33 -0000 https://status.veebor.dev/incident/892836#dacf8f21498fce788d1436476d354c18988661f5ff5f4feb6aaaaea38f4e7651 Incident Veebor Monitoring Service went down. https://status.veebor.dev/incident/892836 Wed, 13 May 2026 22:42:06 -0000 https://status.veebor.dev/incident/892836#6f891f7b52ad10a1ff6a23f14086b9584aef896b5965d1dc7b8cc7a42351986e Incident Veebor Track Service went down. https://status.veebor.dev/incident/892836 Wed, 13 May 2026 22:41:41 -0000 https://status.veebor.dev/incident/892836#1e162629d4cb88725862567ca68c2b7b1f3e23e539303ea6ef2c3496c094fba1 Incident ping routing service (alx) went down. https://status.veebor.dev/incident/892836 Wed, 13 May 2026 22:41:12 -0000 https://status.veebor.dev/incident/892836#df272d6b32a650675c47ab67040c1b8d35252d8e7084ff524e4c485aaec6a7fa Incident Veebor Password Service went down and Veebor Git Service recovered. https://status.veebor.dev/incident/892836 Tue, 12 May 2026 22:27:09 -0000 https://status.veebor.dev/incident/892836#55711b28293e7ad675d05863fe4b352d17f76da223236db279526b9760a3bfad Incident Veebor Git Service went down. https://status.veebor.dev/incident/892836 Tue, 12 May 2026 19:25:13 -0000 https://status.veebor.dev/incident/892836#65353f56c6baaccb42cfe508e2166619bad68cefea6dd7b439b8a9d16f2695b9 Incident Veebor Main Website recovered. https://status.veebor.dev/incident/892836 Mon, 11 May 2026 07:02:38 -0000 https://status.veebor.dev/incident/892836#32db32bf8e8b511f0482ddec8535275169095070b5e6d2e7d213eb7de5ac9f8f Incident Veebor Main Website went down. https://status.veebor.dev/incident/888524 Tue, 05 May 2026 22:34:34 -0000 https://status.veebor.dev/incident/888524#87fe5ca29acd9d78222fc0ac6b6b283ab2e2451c1ad43bb013f9f978372e1b2f Incident Veebor Storage Service recovered. https://status.veebor.dev/incident/888524 Tue, 05 May 2026 21:05:25 -0000 https://status.veebor.dev/incident/888524#18f1b19584677df25b20c7242ded64bb01dc976f03f07affd63eddd6fba6332a Incident Veebor Storage Service went down. https://status.veebor.dev/incident/883259 Thu, 30 Apr 2026 04:52:23 -0000 https://status.veebor.dev/incident/883259#b81d169f93c42c3500ae031722544d2b62e8f23c045feb91c191faef21a03038 Incident Veebor Main Website recovered. https://status.veebor.dev/incident/883259 Wed, 29 Apr 2026 14:41:15 -0000 https://status.veebor.dev/incident/883259#e8735ecbaa9f989347b6fdd3487a3ff3ec14cb9aca2bdd4bce285f6f2b3a229e Incident Veebor Main Website went down. https://status.veebor.dev/incident/870370 Mon, 13 Apr 2026 06:16:16 -0000 https://status.veebor.dev/incident/870370#5b7b680babc9975ccda8f2227ae8dfd7f512f1806e96add1291c6aa9d7006ec0 Incident Veebor Storage Service recovered. https://status.veebor.dev/incident/870370 Mon, 13 Apr 2026 06:11:32 -0000 https://status.veebor.dev/incident/870370#513267fca2c5cb43e71b571b027b7f4eec139f1a1b7ef9348b01b80fe3d34fe0 Incident Veebor Storage Service went down. https://status.veebor.dev/incident/851087 Tue, 17 Mar 2026 08:22:15 -0000 https://status.veebor.dev/incident/851087#71af96632bcb66ad801378b860270eeed6f98b0bb0ac6efc5386a5c0255ed17a Incident Veebor Storage Service recovered. https://status.veebor.dev/incident/851087 Tue, 17 Mar 2026 08:17:31 -0000 https://status.veebor.dev/incident/851087#ca4aa96f31eafe2edf6b0359a24803229372a94df04b1a34f0441975c725d211 Incident Veebor Storage Service went down. https://status.veebor.dev/incident/850204 Mon, 16 Mar 2026 06:58:21 -0000 https://status.veebor.dev/incident/850204#c4f697fcc39b61e810eed0ad861cf13fa1d4b5496e4bc6c9df50d5b0c9202a08 Incident Veebor Storage Service recovered. https://status.veebor.dev/incident/850204 Mon, 16 Mar 2026 06:43:10 -0000 https://status.veebor.dev/incident/850204#4e782d2517468e8f8f2ab53e1b55e56720b3e064a6c00229c53f2bef1910e815 Incident Veebor Storage Service went down. https://status.veebor.dev/incident/838422 Tue, 03 Mar 2026 01:22:37 -0000 https://status.veebor.dev/incident/838422#36da2aace3ef885fd6e45496c562e07ef229a725979f684ec92e3cf581b45449 Incident ping routing service (alx), Veebor Git Service, Veebor Track Service, and 1 other resource recovered. https://status.veebor.dev/incident/838422 Tue, 03 Mar 2026 01:21:43 -0000 https://status.veebor.dev/incident/838422#d6afc309c41545f97cc10385088f8b4cd1f7acc7e60a1a14138f51bdabbf3b62 Incident Veebor Monitoring Service recovered. https://status.veebor.dev/incident/838422 Tue, 03 Mar 2026 00:46:59 -0000 https://status.veebor.dev/incident/838422#183ae033bbd74c464536c6cda4d61b50a272c22d012ea2fcfcf73ee3477e7112 Incident Veebor Git Service went down. https://status.veebor.dev/incident/838422 Tue, 03 Mar 2026 00:45:31 -0000 https://status.veebor.dev/incident/838422#23a1da19188caf8c2307f2c69246ea4d636d45dd1f92bf7c6de99c279fb5ad02 Incident Veebor Monitoring Service went down. https://status.veebor.dev/incident/838422 Tue, 03 Mar 2026 00:45:15 -0000 https://status.veebor.dev/incident/838422#a53d2e7721a7f07a82cca0f6eab41694c4adfa762ece7c86aeb4c5e31598c279 Incident Veebor Track Service went down. https://status.veebor.dev/incident/838422 Tue, 03 Mar 2026 00:44:54 -0000 https://status.veebor.dev/incident/838422#fb23232faba17dfecb9c60667e1bbe26a5eca7f6703353490122bb8becb227c6 Incident ping routing service (alx) went down. https://status.veebor.dev/incident/838422 Tue, 03 Mar 2026 00:44:02 -0000 https://status.veebor.dev/incident/838422#e1b540dd5c7e2356bdd632affd5fd76a756dee2c895c49307f962ed582b92279 Incident Veebor Password Service went down. https://status.veebor.dev/incident/834179 Thu, 26 Feb 2026 17:43:36 -0000 https://status.veebor.dev/incident/834179#7f2411109cb2b64b28db23c672d4d45ccf589dff395c985bd9693dbbdaa3b204 Incident Veebor Git Service recovered. https://status.veebor.dev/incident/834179 Thu, 26 Feb 2026 17:35:48 -0000 https://status.veebor.dev/incident/834179#b1418aff4b19d80969bd95760c0907552630b8acec6007b7fed36bb0c8a06e26 Incident Veebor Git Service went down. https://status.veebor.dev/incident/834179 Thu, 26 Feb 2026 16:10:31 -0000 https://status.veebor.dev/incident/834179#a8a2b1fc0d9182b0697df1139b7e1e66a05e29c1afdc899709dbc13c3afe68fa Incident Veebor Password Service recovered. https://status.veebor.dev/incident/834179 Thu, 26 Feb 2026 15:59:29 -0000 https://status.veebor.dev/incident/834179#aa9321bd859dcef65cb53008e566c345ed0a4780c729a84e5f1329b8109f0dae Incident Veebor Password Service went down. https://status.veebor.dev/incident/834179 Thu, 26 Feb 2026 14:16:36 -0000 https://status.veebor.dev/incident/834179#022d6d1bc5ba2404ce2f8571a626f472dfdf4e527e22bc63f9d84b836946e915 Incident Veebor Password Service recovered. https://status.veebor.dev/incident/834179 Thu, 26 Feb 2026 14:05:27 -0000 https://status.veebor.dev/incident/834179#709bc6219c3209b9ea0075ecebd1e36b0ee300cef50976de0d40a5a3449cd81e Incident Veebor Password Service went down. https://status.veebor.dev/incident/819705 Fri, 06 Feb 2026 06:19:17 -0000 https://status.veebor.dev/incident/819705#93c83c241dea999f46e4fcebcdeb1612b64d9810cdc1fad200cf40b416436970 Incident Veebor Storage Service recovered. https://status.veebor.dev/incident/819705 Fri, 06 Feb 2026 06:14:29 -0000 https://status.veebor.dev/incident/819705#19f7ad75ccc8a6c262d7ed530051692c64b131c5dda787bedd5df6a18d0be4ff Incident Veebor Storage Service went down. https://status.veebor.dev/incident/819045 Thu, 05 Feb 2026 07:28:31 -0000 https://status.veebor.dev/incident/819045#c1185de3cab4da0688d208d7029e107d58f659b0e2ba2cc35cace86ffbc7edcd Incident Veebor Storage Service recovered. https://status.veebor.dev/incident/819045 Thu, 05 Feb 2026 07:13:19 -0000 https://status.veebor.dev/incident/819045#5979657fcb0e57be6cf630a5e145418db374360c48670425c9b034475a08b491 Incident Veebor Storage Service went down. https://status.veebor.dev/incident/813893 Wed, 28 Jan 2026 23:46:20 -0000 https://status.veebor.dev/incident/813893#86fa38449adeca4d96798f377d8da15541f444ea1970e9a07b747745932bc182 Incident Veebor Storage Service recovered. https://status.veebor.dev/incident/813893 Wed, 28 Jan 2026 23:36:12 -0000 https://status.veebor.dev/incident/813893#c7d5a5a3f389a052cebbd4c895ce6dc1ab2f0bd7a876151018c4fdd1d7807f36 Incident Veebor Storage Service went down. https://status.veebor.dev/incident/813893 Wed, 28 Jan 2026 23:19:21 -0000 https://status.veebor.dev/incident/813893#f7321e45411c376f1d8b1d887c94e4fba63f261bf7987515ad18aa4f7109a6da Incident Veebor Storage Service recovered. https://status.veebor.dev/incident/813893 Wed, 28 Jan 2026 23:13:10 -0000 https://status.veebor.dev/incident/813893#ade9d5edebfc90766f71ab6e5a9e9abfe9be28fb9ddc358815c0235e68ccacbc Incident Veebor Storage Service went down. https://status.veebor.dev/incident/808507 Wed, 21 Jan 2026 00:04:54 -0000 https://status.veebor.dev/incident/808507#9a747a800d99edd5502a16ddedd62cbc6873b866ef2aaf330c79c717c2c2143e Incident Veebor Git Service recovered. https://status.veebor.dev/incident/808507 Wed, 21 Jan 2026 00:04:27 -0000 https://status.veebor.dev/incident/808507#b3f50bc58281e2cca24c0338702f60f67ee4c5ed555e8986420b4f08bb399111 Incident ping routing service (alx), Veebor Track Service, and Veebor Password Service recovered. https://status.veebor.dev/incident/808507 Wed, 21 Jan 2026 00:03:40 -0000 https://status.veebor.dev/incident/808507#64af66961be0ea67df618074f05254e501c1edf53590b55a9e828d81e7f46953 Incident Veebor Monitoring Service recovered. https://status.veebor.dev/incident/808507 Tue, 20 Jan 2026 23:46:33 -0000 https://status.veebor.dev/incident/808507#a74c2d4a0eb944ebec8b59715a2f04ea0a001583173d3509aac2d51c0a7ecaec Incident Veebor Git Service went down. https://status.veebor.dev/incident/808507 Tue, 20 Jan 2026 23:45:31 -0000 https://status.veebor.dev/incident/808507#a06e5f0e459eef9a6a38d0fbca62fa3ee055c10c1cae04eb642e80af68025390 Incident Veebor Monitoring Service went down. https://status.veebor.dev/incident/808507 Tue, 20 Jan 2026 23:45:15 -0000 https://status.veebor.dev/incident/808507#6d97fd4fed4137f717f3379da5742e36cae3f1bc0f2b8b3705b17dd6d972d88a Incident Veebor Track Service went down. https://status.veebor.dev/incident/808507 Tue, 20 Jan 2026 23:44:44 -0000 https://status.veebor.dev/incident/808507#17abb60fd20ff2422731075ff946fe65d58ef1e436c8d8134ec2330c0dd1e987 Incident ping routing service (alx) went down. https://status.veebor.dev/incident/808507 Tue, 20 Jan 2026 23:43:59 -0000 https://status.veebor.dev/incident/808507#0b0cd26d5ddc6bef0ad6934be30935dca8dbe7ba7e501411f602e85dd18c0af8 Incident Veebor Password Service went down. https://status.veebor.dev/incident/796590 Wed, 31 Dec 2025 11:25:36 -0000 https://status.veebor.dev/incident/796590#4ad47dce9d4321b85574abb32dd4f8c80294cdc6b34975715f81a6218570070c Incident Veebor Git Service and Veebor Password Service recovered. https://status.veebor.dev/incident/796590 Wed, 31 Dec 2025 11:25:25 -0000 https://status.veebor.dev/incident/796590#7544a5f2efcd75da8af4635d07ceb3601071fdbca12391b832bdc276f479f4ff Incident ping routing service (alx) and Veebor Track Service recovered. https://status.veebor.dev/incident/796590 Wed, 31 Dec 2025 11:22:38 -0000 https://status.veebor.dev/incident/796590#76c38b224504dcb16fbd1f050a86c8982f7c42f64dcca2f902e6fb2c5d56c42b Incident Veebor Git Service went down. https://status.veebor.dev/incident/796590 Wed, 31 Dec 2025 11:21:03 -0000 https://status.veebor.dev/incident/796590#90cd22cbbbc2836a0e470cfec2e838d55f18b7fb7aa8ad542c0642a0501e1ea1 Incident Veebor Track Service went down. https://status.veebor.dev/incident/796590 Wed, 31 Dec 2025 11:20:46 -0000 https://status.veebor.dev/incident/796590#3776eefe64330fc40038aa0bd9bd3660adc1b23866922bdfb36f6e170d8656e4 Incident ping routing service (alx) went down. https://status.veebor.dev/incident/796590 Wed, 31 Dec 2025 11:20:01 -0000 https://status.veebor.dev/incident/796590#afc31dd38900fb2d0cad758209082c163b90171173938f58e11d039459ed0a66 Incident Veebor Password Service went down. https://status.veebor.dev/incident/795167 Sun, 28 Dec 2025 16:31:31 -0000 https://status.veebor.dev/incident/795167#af7d2d96ce59410bb38909ca6b689d0e02b80782ed1ebb34c32e4ec81e30b707 Incident Veebor Track Service and Veebor Password Service recovered. https://status.veebor.dev/incident/795167 Sun, 28 Dec 2025 16:31:08 -0000 https://status.veebor.dev/incident/795167#cf19423ee3fcc83350d2358c5ad35675edae208e1b9c513411d227f9f5168791 Incident Veebor Git Service recovered. https://status.veebor.dev/incident/795167 Sun, 28 Dec 2025 16:30:44 -0000 https://status.veebor.dev/incident/795167#d6ef9711859149a7d88d3948be6f811d1bc07bb1df10de4ed8e2fae150235129 Incident Veebor Git Service went down and Veebor Monitoring Service recovered. https://status.veebor.dev/incident/795167 Sun, 28 Dec 2025 16:11:27 -0000 https://status.veebor.dev/incident/795167#8a88f9fcf1cae05ad8f9ccf2f1451374077afebb9f0dd63e8e53df18856dfeab Incident Veebor Track Service went down. https://status.veebor.dev/incident/795167 Sun, 28 Dec 2025 16:10:35 -0000 https://status.veebor.dev/incident/795167#38242f14311b8fed65e1414749d30b89614c894de8148876ddca340e7dfc3e55 Incident Veebor Password Service and Veebor Monitoring Service went down. https://status.veebor.dev/incident/795167 Sun, 28 Dec 2025 15:05:04 -0000 https://status.veebor.dev/incident/795167#d50143db21e626c530d4580a34eb9b171fb9df936e98d4cb874b0165e1d386ee Incident Veebor Git Service recovered. https://status.veebor.dev/incident/795167 Sun, 28 Dec 2025 15:04:43 -0000 https://status.veebor.dev/incident/795167#667400380ee08f53efc3b7e4306de56899aed06c970114ff1094454c7621d269 Incident Veebor Track Service recovered. https://status.veebor.dev/incident/795167 Sun, 28 Dec 2025 15:01:25 -0000 https://status.veebor.dev/incident/795167#32a08a3590017d696380e917ba230335d9439790fadf70d7e27c8d6ad97c3d6b Incident Veebor Password Service recovered. https://status.veebor.dev/incident/795167 Sun, 28 Dec 2025 15:00:57 -0000 https://status.veebor.dev/incident/795167#7908fe4d7fb0b82c78cd5342d02bbebf733451e8140bc88a624655ac1de56470 Incident Veebor Monitoring Service recovered. https://status.veebor.dev/incident/795167 Sun, 28 Dec 2025 14:53:36 -0000 https://status.veebor.dev/incident/795167#05c465f0c670db6959506c9ebdf2bce8581f69572fb206dc6df5abacff5ce572 Incident Veebor Git Service and Veebor Track Service went down. https://status.veebor.dev/incident/795167 Sun, 28 Dec 2025 14:52:48 -0000 https://status.veebor.dev/incident/795167#2e2cfccbc8f63fda93e676f863d3deb8199b06db6d4e53ac4f81297d588e9d74 Incident Veebor Monitoring Service went down. https://status.veebor.dev/incident/795167 Sun, 28 Dec 2025 14:52:22 -0000 https://status.veebor.dev/incident/795167#98666ca44bc37791d813e736b503af6e1d7aabc12874936acb2006a7d2cda329 Incident Veebor Password Service went down. https://status.veebor.dev/incident/786314 Sun, 14 Dec 2025 16:40:32 -0000 https://status.veebor.dev/incident/786314#ed706022bd102d844b05e2dbc050ba450a22c2d5ca2e18b53ebedb09005275b7 Incident Veebor Track Service recovered. https://status.veebor.dev/incident/786314 Sun, 14 Dec 2025 16:36:28 -0000 https://status.veebor.dev/incident/786314#2a622ca981861b054a158662472e4537aa0f72183264aad5392f2a87d7e91411 Incident Veebor Track Service went down. https://status.veebor.dev/incident/783447 Wed, 10 Dec 2025 04:12:23 -0000 https://status.veebor.dev/incident/783447#5882ef171b66b4ea2af3b6b38d75f7c5659e0a7026d44bad1db22540ac7c0a5f Incident Veebor Track Service and Veebor Password Service recovered. https://status.veebor.dev/incident/783447 Wed, 10 Dec 2025 04:08:05 -0000 https://status.veebor.dev/incident/783447#e49376c86d9dc1e03c0b1f5d3e5c4df47a06ea73b660c6eb80d9214a110b35da Incident Veebor Track Service went down. https://status.veebor.dev/incident/783447 Wed, 10 Dec 2025 04:06:56 -0000 https://status.veebor.dev/incident/783447#4cf6799b551d0c15f426ab32c5d82e39ae39589d8b916fe6b96e3dae3d02eec4 Incident Veebor Password Service went down. https://status.veebor.dev/incident/780979 Fri, 05 Dec 2025 21:15:31 -0000 https://status.veebor.dev/incident/780979#b0af614e56cb3c698750326202010bc7a9eb826aacd63896dfdb05cff41e1ac4 Incident ping routing service (alx) recovered. https://status.veebor.dev/incident/780979 Fri, 05 Dec 2025 21:10:51 -0000 https://status.veebor.dev/incident/780979#ca56eb6d2e68b3187aaf327866ed18fac21cd63d69ac76a5beb113358f474086 Incident ping routing service (alx) and Shapy Backend Service went down. https://status.veebor.dev/incident/779842 Thu, 04 Dec 2025 21:25:31 -0000 https://status.veebor.dev/incident/779842#08c973fbd0b059a71805ace4d0f223416f9d772642cba5b688e7e78e6f143ccd Incident Veebor Password Service recovered. https://status.veebor.dev/incident/779842 Thu, 04 Dec 2025 21:19:16 -0000 https://status.veebor.dev/incident/779842#bcf84323300105a15346346fde27cf43e110718b8769b5ba7d4c25de158da78d Incident Veebor Password Service went down. https://status.veebor.dev/incident/768470 Tue, 18 Nov 2025 12:46:05 -0000 https://status.veebor.dev/incident/768470#7d5db5cd50715c12f9ee86c24e0835f40a28119a9f0e28eba58ab478ee3ff26a Incident Veebor Password Service recovered. https://status.veebor.dev/incident/768470 Tue, 18 Nov 2025 12:38:18 -0000 https://status.veebor.dev/incident/768470#fcbbb11fd7f500bbb8e64e3c45fa54cce6aeb206e2240e1b3bcfb48295fbbf0e Incident Veebor Portfolio Website recovered. https://status.veebor.dev/incident/768470 Tue, 18 Nov 2025 11:47:19 -0000 https://status.veebor.dev/incident/768470#1a6f8036119d2099688ff7815ea62a4e563b058367d50822161449dab65275fe Incident Veebor Portfolio Website went down. https://status.veebor.dev/incident/768470 Tue, 18 Nov 2025 11:38:53 -0000 https://status.veebor.dev/incident/768470#1cc0eb5021faea9021317a3581996022b9d28d3fb07fddd1f005b4d5a5c51afb Incident Veebor Password Service went down. https://status.veebor.dev/incident/763655 Thu, 13 Nov 2025 08:13:55 -0000 https://status.veebor.dev/incident/763655#8dd8a4f370b2a8361544004dcaa196c7531ba2f319006dda8af348d1051ae2ca Incident Veebor Storage Service recovered. https://status.veebor.dev/incident/763655 Thu, 13 Nov 2025 08:08:59 -0000 https://status.veebor.dev/incident/763655#a249f7e3e32a7555ca7eaa6bd830cf783bff650769af5a325414e90f049cb150 Incident Veebor Storage Service went down. https://status.veebor.dev/incident/762760 Wed, 12 Nov 2025 08:39:42 -0000 https://status.veebor.dev/incident/762760#4c5a3c125dbaae437562a5de88c1065144a67db4d25a46ca36b241871fd42799 Incident Veebor Storage Service recovered. https://status.veebor.dev/incident/762760 Wed, 12 Nov 2025 08:27:24 -0000 https://status.veebor.dev/incident/762760#3b8b42d99614321fcca6263071b48d219ab11fdf4be1408e2b3af2b0d497311d Incident Veebor Storage Service went down. https://status.veebor.dev/incident/761811 Mon, 10 Nov 2025 23:57:21 -0000 https://status.veebor.dev/incident/761811#20f7186414c32a684a5e48e990f28af25502c0bd8a5bdb75bcd012bd66738074 Incident ping routing service (alx) recovered. https://status.veebor.dev/incident/761811 Mon, 10 Nov 2025 23:56:34 -0000 https://status.veebor.dev/incident/761811#52c3c51d3eb9b1cdc32e572c27ca3048a677113782795a199d25d424fbea93c7 Incident Veebor Git Service, Veebor Track Service, and Veebor Password Service recovered. https://status.veebor.dev/incident/761811 Mon, 10 Nov 2025 23:55:32 -0000 https://status.veebor.dev/incident/761811#8fc2cf1129d6f4678de6538eee8139f69ab7ae3326e1cfdc3160650be703ec12 Incident Veebor Monitoring Service recovered. https://status.veebor.dev/incident/761811 Mon, 10 Nov 2025 23:38:31 -0000 https://status.veebor.dev/incident/761811#a53b11e50fc43a7d5668fe1be9fb2c5e47c7adc2853c3683afb7c5269bda9439 Incident Veebor Git Service and Shapy Backend Service went down. https://status.veebor.dev/incident/761811 Mon, 10 Nov 2025 23:37:51 -0000 https://status.veebor.dev/incident/761811#e6fac940647458c7444cd5e32d3a42b253a6a6d082380ffbfab86c68fda33cdd Incident ping routing service (alx) went down. https://status.veebor.dev/incident/761811 Mon, 10 Nov 2025 23:37:30 -0000 https://status.veebor.dev/incident/761811#8a84e470374728502261c4912915a217fa66ac78f0ab0b1c18505fb706ddbd0c Incident Veebor Monitoring Service went down. https://status.veebor.dev/incident/761811 Mon, 10 Nov 2025 23:37:06 -0000 https://status.veebor.dev/incident/761811#40cd86801bd78871c1a2531fb8e4e56b52d24538e556639dbcf9f0d7f1f9b0bc Incident Veebor Track Service went down. https://status.veebor.dev/incident/761811 Mon, 10 Nov 2025 23:36:09 -0000 https://status.veebor.dev/incident/761811#060f61853019c8c827c0757c41badfc82617733c2f211ac0e51b11328187a32c Incident Veebor Password Service went down. https://status.veebor.dev/incident/759864 Fri, 07 Nov 2025 12:53:41 -0000 https://status.veebor.dev/incident/759864#9efdc2758416f2a3bac5f5c047f991f4231ba3eb321c17c4a1d55f06f4af072d Incident Veebor Track Service and Veebor Password Service recovered. https://status.veebor.dev/incident/759864 Fri, 07 Nov 2025 12:51:40 -0000 https://status.veebor.dev/incident/759864#6eeebb0d6c1e476e91e8617209d828b90ee0fd041445e49c8eae5667f4351fe8 Incident ping routing service (alx) recovered. https://status.veebor.dev/incident/759864 Fri, 07 Nov 2025 12:46:55 -0000 https://status.veebor.dev/incident/759864#9f9905472b3980f583b22f2b494c95eb391cea680811ce65b1dc5d7243a004ef Incident ping routing service (alx) went down. https://status.veebor.dev/incident/759864 Fri, 07 Nov 2025 12:46:14 -0000 https://status.veebor.dev/incident/759864#4d9bf4ad9d8848905e8e86a64a246db6ecbd95a9a7dbea4cac67565249fb2152 Incident Veebor Track Service went down. https://status.veebor.dev/incident/759864 Fri, 07 Nov 2025 12:45:05 -0000 https://status.veebor.dev/incident/759864#a3c196ddf687d8fc416fb64e55afd230d773ad58f26f12e2008e0e25e02be9ed Incident Veebor Password Service went down. https://status.veebor.dev/incident/759864 Fri, 07 Nov 2025 11:57:15 -0000 https://status.veebor.dev/incident/759864#9833da9d93c2f42e7b1a9880ddcc37e4af05b3ef0c4cbd9c9567104869f9f897 Incident ping routing service (alx) recovered. https://status.veebor.dev/incident/759864 Fri, 07 Nov 2025 11:49:32 -0000 https://status.veebor.dev/incident/759864#be4f1f8be6e45cf50056f205aecacc681e3ff2a5e15f9eddae98f3a35d2b8447 Incident ping routing service (alx) went down. https://status.veebor.dev/incident/758502 Wed, 05 Nov 2025 13:26:15 -0000 https://status.veebor.dev/incident/758502#edad5aa93c21ee9d1caf7bd70553645908ec8968145e2e4ca3ed23c7b738d6dd Incident Veebor Storage Service recovered. https://status.veebor.dev/incident/758502 Wed, 05 Nov 2025 13:03:07 -0000 https://status.veebor.dev/incident/758502#193721d61261a7358dfc38527ad251bf50edafb23113261f159bb60f22c41dc6 Incident Veebor Storage Service went down. https://status.veebor.dev/incident/742575 Mon, 13 Oct 2025 09:19:12 -0000 https://status.veebor.dev/incident/742575#2c6a6d4dfe3652d997a1ceee45547c321155a05a6abd97899febe0d748c1cc7b Incident ping routing service (alx) recovered. https://status.veebor.dev/incident/742575 Mon, 13 Oct 2025 09:14:15 -0000 https://status.veebor.dev/incident/742575#596ca43564f46715b70c9c13b3990f164b1e8150e969db911d2411507d19b015 Incident ping routing service (alx) went down. https://status.veebor.dev/incident/742575 Mon, 13 Oct 2025 08:48:43 -0000 https://status.veebor.dev/incident/742575#176942cc2c2115c1e36bc5b10e4f2f80f4407a4e864fbc74bb07b64685fee161 Incident ping routing service (alx) recovered. https://status.veebor.dev/incident/742575 Mon, 13 Oct 2025 08:48:43 -0000 https://status.veebor.dev/incident/742575#8140466e01f7d1c7c61ef93f2d34bcefd10425aac7f3e48dbee6ac453533cc82 Incident Veebor Track Service and Veebor Password Service recovered. https://status.veebor.dev/incident/742575 Mon, 13 Oct 2025 08:48:16 -0000 https://status.veebor.dev/incident/742575#46322df982561a07162b241e97ad6c79fe3ab0bd3184fb85e57f94777904f3f0 Incident Veebor Monitoring Service recovered. https://status.veebor.dev/incident/742575 Mon, 13 Oct 2025 08:44:59 -0000 https://status.veebor.dev/incident/742575#c856c0f7d9fdde562db6b394d9af6fd9fd704acd3a6dbc362412831dce4fe37b Incident Veebor Monitoring Service went down. https://status.veebor.dev/incident/742575 Mon, 13 Oct 2025 08:44:44 -0000 https://status.veebor.dev/incident/742575#85850e2ddb33f81dabe8335f337febe31019109cbc32c5fb3329cbe7a23baf8c Incident Veebor Track Service went down. https://status.veebor.dev/incident/742575 Mon, 13 Oct 2025 08:44:20 -0000 https://status.veebor.dev/incident/742575#e504348df53678b29e7e98c08abf0bb3ffbccdf78a76603988ce67ff99f53cc5 Incident ping routing service (alx) went down. https://status.veebor.dev/incident/742575 Mon, 13 Oct 2025 08:43:29 -0000 https://status.veebor.dev/incident/742575#7534dd07a5819a5eb63fffb367414284e463b8cfa63d2f6cd3635f9daba495ea Incident Veebor Password Service went down. https://status.veebor.dev/incident/738780 Mon, 06 Oct 2025 20:41:22 -0000 https://status.veebor.dev/incident/738780#ef0a5dcddb27d23315d03abc3050f2c042cd24eae44b9b44c0636e78ea1878ea Incident Veebor Monitoring Service recovered. https://status.veebor.dev/incident/738780 Mon, 06 Oct 2025 20:33:15 -0000 https://status.veebor.dev/incident/738780#c024658032e0c53b22d9264f0a828d6384071a6196881017517ce9fe465118b9 Incident Veebor Monitoring Service went down. https://status.veebor.dev/incident/719043 Mon, 08 Sep 2025 10:00:00 -0000 https://status.veebor.dev/incident/719043#f6c7a1c2772fc503f38fa9074a10f2377f6b0afd6e31b2ec5143f77d7fe5a326 Incident Our ISP fixed the upstream issue https://status.veebor.dev/incident/719043 Fri, 05 Sep 2025 16:50:00 -0000 https://status.veebor.dev/incident/719043#e05ad30657418f3555b3ce72ae924c95a939fbb949db0aac8c48b2fdd171ba4f Incident We have identified the root cause of the issue with our ISP. Unfortunately, we have to wait for them to address the problem with their infrastructure. https://status.veebor.dev/incident/719043 Fri, 05 Sep 2025 15:31:59 -0000 https://status.veebor.dev/incident/719043#408ad6c9933146c69403c38261f6fe0c08207c03f1ae3a280d5c3b62e106821e Incident Veebor Monitoring Service went down. https://status.veebor.dev/incident/719043 Fri, 05 Sep 2025 15:29:48 -0000 https://status.veebor.dev/incident/719043#f9e65c153e7ac3c466572934f8d72a20252af1446180cb08ed3a3734c2afd96a Incident Veebor Git Service and Shapy Backend Service went down. https://status.veebor.dev/incident/719043 Fri, 05 Sep 2025 15:29:12 -0000 https://status.veebor.dev/incident/719043#aa6b31c1a3d7d907a48ac33b2a88e11b4b72b547553da09eb208371c20c0353b Incident Veebor Track Service went down. https://status.veebor.dev/incident/719043 Fri, 05 Sep 2025 15:28:16 -0000 https://status.veebor.dev/incident/719043#4a87723a2e30358dd75ce678d58a2b21e8daca426b2574bc3cf28cd2c9762c38 Incident ping routing service (alx) went down. https://status.veebor.dev/incident/719043 Fri, 05 Sep 2025 15:27:27 -0000 https://status.veebor.dev/incident/719043#d9a4cbfece7f1bfe76e8bad8874d55ab516504a599cbf7786c804a97968872f5 Incident Veebor Password Service went down. https://status.veebor.dev/incident/712581 Tue, 26 Aug 2025 06:59:27 -0000 https://status.veebor.dev/incident/712581#bebae360f52918dd319f4be0cc68797a8b961a674e1a76dd739cba549f5182a4 Incident Veebor Storage Service recovered. https://status.veebor.dev/incident/712581 Tue, 26 Aug 2025 06:55:04 -0000 https://status.veebor.dev/incident/712581#5ef78ba175b68839228ddfa967bb5559672c534b3dec458f79794a43c2040e5e Incident Veebor Storage Service went down. https://status.veebor.dev/incident/701864 Thu, 07 Aug 2025 07:40:58 -0000 https://status.veebor.dev/incident/701864#0e4c2911daf8d8220acc2385fee253b2d08509d4b3a855fdf00262f4c3400445 Incident Veebor Git Service recovered. https://status.veebor.dev/incident/701864 Thu, 07 Aug 2025 07:40:53 -0000 https://status.veebor.dev/incident/701864#914d4035b6f62848bd6dfddcb98d3503e99def99fd22734be570b1717fcee997 Incident Veebor Track Service and Veebor Password Service recovered. https://status.veebor.dev/incident/701864 Thu, 07 Aug 2025 07:40:33 -0000 https://status.veebor.dev/incident/701864#3398f1bd7bfa18ee7e08c9d044070277febb9939230a4d75078cd3b6f63a4d14 Incident Veebor Monitoring Service recovered. https://status.veebor.dev/incident/701864 Thu, 07 Aug 2025 06:09:31 -0000 https://status.veebor.dev/incident/701864#65115bae560c993495c9c31d9bbe538eb509dc138844a72b70b8b7607a76949e Incident Veebor Git Service and Veebor Track Service went down. https://status.veebor.dev/incident/701864 Thu, 07 Aug 2025 06:08:31 -0000 https://status.veebor.dev/incident/701864#4b446f29face039f896d865f33a89086a9cea89e8710692125c0255399045e81 Incident Veebor Password Service went down. https://status.veebor.dev/incident/701864 Thu, 07 Aug 2025 06:08:12 -0000 https://status.veebor.dev/incident/701864#3f83bc9aa31f27e8203023cbd7b0a45219026bfc090216193445a952728f9c96 Incident Veebor Monitoring Service went down. https://status.veebor.dev/incident/701276 Wed, 06 Aug 2025 09:06:42 -0000 https://status.veebor.dev/incident/701276#2d5cf877a55c5331e7c365109bf0b097c354079bb892d77f8fd051c257194fcf Incident ping routing service (alx) recovered. https://status.veebor.dev/incident/701276 Wed, 06 Aug 2025 09:02:00 -0000 https://status.veebor.dev/incident/701276#e1a43b0bf4d34d214bfb589ed9f5aa29362cfc91bade821c67dbd2b68843f829 Incident ping routing service (alx) went down. https://status.veebor.dev/incident/700371 Tue, 05 Aug 2025 00:32:21 -0000 https://status.veebor.dev/incident/700371#367d5dbfe2a17fcdb62aaa31ea492db8fa62ba2c0a02eb5028cc233e337ca3b5 Incident Veebor Track Service recovered. https://status.veebor.dev/incident/700371 Tue, 05 Aug 2025 00:28:06 -0000 https://status.veebor.dev/incident/700371#324070ec237c6b228c90456d5e8958425b00c8536675e1bc019ccd76b9940108 Incident Veebor Track Service went down. https://status.veebor.dev/incident/668329 Thu, 31 Jul 2025 09:49:47 -0000 https://status.veebor.dev/incident/668329#5d79a9d1441010eb092f48358c0820c7c5099f78ccb3792652163d3c33d7f0d4 Incident ping routing service (alx) recovered. https://status.veebor.dev/incident/668329 Thu, 31 Jul 2025 09:45:05 -0000 https://status.veebor.dev/incident/668329#6b35b0c918284867af0e13228ab67cce097205bb692a0f6f9fd8de3510d1df70 Incident ping routing service (alx) went down. https://status.veebor.dev/incident/668329 Thu, 31 Jul 2025 09:28:49 -0000 https://status.veebor.dev/incident/668329#e662a7bd8a2f3d32e83d3f8400c6d5852d378b99653f3e20d61c5f38db7e495c Incident ping routing service (alx) recovered. https://status.veebor.dev/incident/668329 Thu, 31 Jul 2025 09:24:05 -0000 https://status.veebor.dev/incident/668329#c661c2ea023e93ec2397aa1fc6e54b2dfd1071ac9d9ec12a2c95a3a99dc811c5 Incident ping routing service (alx) went down. https://status.veebor.dev/incident/626677 Sun, 27 Jul 2025 17:59:03 -0000 https://status.veebor.dev/incident/626677#7b4d0bc07624d176e478668f051b7df812ee8ef3d179b1f891457e02c946af51 Incident Veebor Track Service recovered. https://status.veebor.dev/incident/626677 Sun, 27 Jul 2025 17:44:26 -0000 https://status.veebor.dev/incident/626677#30a31cdca5828412f56d5d35051a7d5936be2f77fc963f6addeda799b58099f3 Incident Veebor Track Service went down. https://status.veebor.dev/incident/625885 Fri, 25 Jul 2025 23:38:29 -0000 https://status.veebor.dev/incident/625885#3a35ff88cdc976d2b2065c2cf01a950bbcdaea1e124cee048a748fef0c9f0dac Incident Veebor Main Website recovered. https://status.veebor.dev/incident/625885 Fri, 25 Jul 2025 21:27:40 -0000 https://status.veebor.dev/incident/625885#e287a06ed1fc5341e9cd51c7b75b47535a82c1bb59497e46ea1f97a34296b0a1 Incident Veebor Main Website went down. https://status.veebor.dev/incident/624202 Wed, 23 Jul 2025 22:25:20 -0000 https://status.veebor.dev/incident/624202#e047c2c2737b38514a9e5782ffaf34787780a614a744c0121a10b418684739fd Incident Veebor Track Service and Veebor Password Service recovered. https://status.veebor.dev/incident/624202 Wed, 23 Jul 2025 22:24:29 -0000 https://status.veebor.dev/incident/624202#2090b3dba10f09cfe5316a10296a0fc2369a6a4ec74edb488ae65fba27ab1c92 Incident ping routing service (alx) recovered. https://status.veebor.dev/incident/624202 Wed, 23 Jul 2025 22:20:59 -0000 https://status.veebor.dev/incident/624202#74e7fefc0cdaba1ad483ffb85d47d1e6674ff4d2526f7f95a8fdaa0291c1c34a Incident Veebor Track Service went down. https://status.veebor.dev/incident/624202 Wed, 23 Jul 2025 22:19:43 -0000 https://status.veebor.dev/incident/624202#ecbab73bc652698ffd019dc7d8fd4041de31ca208abc16671d8f40e982815482 Incident ping routing service (alx) and Veebor Password Service went down. https://status.veebor.dev/incident/624202 Wed, 23 Jul 2025 01:38:16 -0000 https://status.veebor.dev/incident/624202#64398af38ac449ee34ddb824bed769c49d4ba13d40d78d7632e5ac8566f5da47 Incident Veebor Track Service and Veebor Password Service recovered. https://status.veebor.dev/incident/624202 Wed, 23 Jul 2025 01:33:58 -0000 https://status.veebor.dev/incident/624202#18f9d4df78a314e85949a68f49dc3b5bec687621ed5e61e148b5795f55783fab Incident Veebor Track Service went down. https://status.veebor.dev/incident/624202 Wed, 23 Jul 2025 01:32:47 -0000 https://status.veebor.dev/incident/624202#c592fb60453d30707e233b0ab95ac45b4d95e79ad3ec39b07f81508bce7f2fbf Incident Veebor Password Service went down. https://status.veebor.dev/incident/615347 Mon, 07 Jul 2025 07:28:55 -0000 https://status.veebor.dev/incident/615347#cd99e33dffad7ab9716363bbf091f765e1ce3110aadb5a0ce8d5bb605e16db8d Incident Veebor Storage Service recovered. https://status.veebor.dev/incident/615347 Mon, 07 Jul 2025 07:24:08 -0000 https://status.veebor.dev/incident/615347#9cf6928fcabc947aebe878188cd32b15540fae66051c85e6c16163d0ec2d6aa2 Incident Veebor Storage Service went down. https://status.veebor.dev/incident/614190 Fri, 04 Jul 2025 23:36:35 -0000 https://status.veebor.dev/incident/614190#2eb40d9178bb37b4a9d0abb0e721531b247c3d1433a33e9fea63be6962fd2fe6 Incident Veebor Track Service recovered. https://status.veebor.dev/incident/614190 Fri, 04 Jul 2025 17:27:39 -0000 https://status.veebor.dev/incident/614190#af87f2445cc43da357f4351ded95e8990bcd26707818d0cd78d492dadd73cdf9 Incident Veebor Git Service and Veebor Password Service recovered. https://status.veebor.dev/incident/614190 Fri, 04 Jul 2025 13:23:28 -0000 https://status.veebor.dev/incident/614190#9adcbbb3a6e5a0ee008d0ecb55e4832778235b43cfaf1425b1e0725e7547ea37 Incident Veebor Git Service and Veebor Track Service went down. https://status.veebor.dev/incident/614190 Fri, 04 Jul 2025 13:22:27 -0000 https://status.veebor.dev/incident/614190#614381c22a96dad5637e63b3d31d239d0c5b3f3bdad9a676beb82a45269a7071 Incident Veebor Password Service went down. https://status.veebor.dev/incident/614190 Fri, 04 Jul 2025 13:16:50 -0000 https://status.veebor.dev/incident/614190#536c8135d3629113a39b4ee06960fa246b1b977df6d018a513b44877e3fbfb5d Incident Veebor Git Service recovered. https://status.veebor.dev/incident/614190 Fri, 04 Jul 2025 13:16:21 -0000 https://status.veebor.dev/incident/614190#18eb8eb81f39e8d2fe051e54abeb2c1d45537a90b567af668e9abb651e28c3b7 Incident Veebor Track Service recovered. https://status.veebor.dev/incident/614190 Fri, 04 Jul 2025 13:07:17 -0000 https://status.veebor.dev/incident/614190#03aa426751efbfaab4a4f109f23bbc2a730bbbf4ca21754ba43cc91169ec3e01 Incident Veebor Git Service went down. https://status.veebor.dev/incident/614190 Fri, 04 Jul 2025 13:06:50 -0000 https://status.veebor.dev/incident/614190#10e3c665a86c58a4380c7b77540007ee3e7bc4f7f3b483dd0a0f7a39f79c4262 Incident Veebor Track Service went down. https://status.veebor.dev/incident/614190 Fri, 04 Jul 2025 11:48:25 -0000 https://status.veebor.dev/incident/614190#785cce8362784915bcdf9c3f5974c0e641e247223f246185fc5060c2cff2f35e Incident Veebor Track Service and Veebor Password Service recovered. https://status.veebor.dev/incident/614190 Fri, 04 Jul 2025 11:44:09 -0000 https://status.veebor.dev/incident/614190#64d362d59eaffdc92c9ea402a9c5bf0e1b42f2896805db4e1b26d97d3292524d Incident Veebor Track Service went down. https://status.veebor.dev/incident/614190 Fri, 04 Jul 2025 11:43:03 -0000 https://status.veebor.dev/incident/614190#c4fa949ecf955e973fcf3e58272845749cb60d83bb923111cd98b6d66e6f8a07 Incident Veebor Password Service went down. https://status.veebor.dev/maintenance/626131 Fri, 04 Jul 2025 11:30:02 -0000 https://status.veebor.dev/incident/626131#cb1e9359ce91553d7d3c9eae3d7ef7de3f97f98bdc11dd7c93ca72d0d0bb9ea8 Maintenance New server @ ALX https://status.veebor.dev/incident/600687 Wed, 11 Jun 2025 06:38:07 -0000 https://status.veebor.dev/incident/600687#929faf7cbc77e5d4fa5a96ce8a73f0767c34e85a06e8711e5c5edb6ed0dd5bfd Incident Veebor Storage Service recovered. https://status.veebor.dev/incident/600687 Wed, 11 Jun 2025 06:25:43 -0000 https://status.veebor.dev/incident/600687#29ae707ad297c1e0ffc4f220f1f7643d9142edbc65552cfa8bba2ae8a211f86b Incident Veebor Storage Service went down. https://status.veebor.dev/incident/573390 Tue, 20 May 2025 22:36:10 -0000 https://status.veebor.dev/incident/573390#649db9c568a84980aba791d6e86f3d1f8f3fef431628e54652a76d107d46353f Incident Veebor Track Service and Veebor Password Service recovered. https://status.veebor.dev/incident/573390 Tue, 20 May 2025 22:35:04 -0000 https://status.veebor.dev/incident/573390#e004c2f95fc43e274cb1967161db89335ce554a5e604e5e340f6580064b7208b Incident ping routing service (alx) recovered. https://status.veebor.dev/incident/573390 Tue, 20 May 2025 22:33:59 -0000 https://status.veebor.dev/incident/573390#7a5842de32fa3679583911ddbb3baa6852b8eb1f9d32c8e881b25343b0ad1f1d Incident Veebor Git Service recovered. https://status.veebor.dev/incident/573390 Tue, 20 May 2025 22:30:18 -0000 https://status.veebor.dev/incident/573390#561951ef1f5a318e91e81e1d795aab4c6ded56aed289bcfdac7dc845d8cb4870 Incident ping routing service (alx) went down. https://status.veebor.dev/incident/573390 Tue, 20 May 2025 22:30:07 -0000 https://status.veebor.dev/incident/573390#7f9c497f08c4ea0736559ef26baa9f3ab13e41e3f997d4a27a5a611fc28bef01 Incident Veebor Git Service and Shapy Backend Service went down. https://status.veebor.dev/incident/573390 Tue, 20 May 2025 22:28:51 -0000 https://status.veebor.dev/incident/573390#a4b11ca925eaf3ad0a899435cabbd52e991a09fd5209b875c6b5858c0b0d5450 Incident Veebor Track Service went down. https://status.veebor.dev/incident/573390 Tue, 20 May 2025 22:27:49 -0000 https://status.veebor.dev/incident/573390#b73192a30da31825f9537a3b8ef9cbe922c287de24f7ea5fbd5ab3e84c207528 Incident Veebor Password Service went down. https://status.veebor.dev/incident/554202 Wed, 30 Apr 2025 06:14:48 -0000 https://status.veebor.dev/incident/554202#cb0b7d807a561443190aea44afd5fd2faf2beadccf5a164908e72ad455d30ad2 Incident Veebor Storage Service recovered. https://status.veebor.dev/incident/554202 Wed, 30 Apr 2025 06:02:07 -0000 https://status.veebor.dev/incident/554202#d868d47a8935eafa9c0c29c9ff0226b840bb3bff25981ce82f5297dd299ba8a9 Incident Veebor Storage Service went down. https://status.veebor.dev/incident/529293 Sun, 16 Mar 2025 23:58:15 -0000 https://status.veebor.dev/incident/529293#314869e2c1d877cd8df22d56e4c8c45435a67bc1a4fd311153f80e70fba5f44e Incident ping routing service (alx) and Shapy Backend Service recovered. https://status.veebor.dev/incident/529293 Sun, 16 Mar 2025 23:56:55 -0000 https://status.veebor.dev/incident/529293#9cc157b78d3120b60891a10c8228b94958db0c77628aa2437d0eb5ad9b38e861 Incident Veebor Git Service, Veebor Track Service, and Veebor Password Service recovered. https://status.veebor.dev/incident/529293 Sun, 16 Mar 2025 23:42:07 -0000 https://status.veebor.dev/incident/529293#6de51d9945ca0b32781c6a9e243d935170c85a82306703963f84a2590c9ff314 Incident Veebor Git Service went down. https://status.veebor.dev/incident/529293 Sun, 16 Mar 2025 23:41:17 -0000 https://status.veebor.dev/incident/529293#de179a49d5cec5148d8c52365df4e2acc5f976c37387c073f0defc5202382563 Incident Veebor Track Service went down. https://status.veebor.dev/incident/529293 Sun, 16 Mar 2025 23:39:35 -0000 https://status.veebor.dev/incident/529293#d2c5696a4c067d323d59debfd56c81c7fdd39b79e046040cf74e83a8d0259b27 Incident Veebor Password Service and Shapy Backend Service went down. https://status.veebor.dev/incident/529293 Sun, 16 Mar 2025 23:38:47 -0000 https://status.veebor.dev/incident/529293#cb609ba38a4d610174abbd90c6ce200f7af75b1db38986df39303f188b87ae42 Incident ping routing service (alx) went down. https://status.veebor.dev/incident/528727 Sat, 15 Mar 2025 16:45:16 -0000 https://status.veebor.dev/incident/528727#9177abcc8bc785ccac1cfdd4d9cce42782a79d33ec0280fd214d39c98a0cc7f5 Incident ping routing service (alx) and Shapy Backend Service recovered. https://status.veebor.dev/incident/528727 Sat, 15 Mar 2025 16:43:58 -0000 https://status.veebor.dev/incident/528727#ed681736607c12d62cb08b8a8156275a2a5f2400151c534c4b34f08bd05cb9bb Incident Veebor Git Service, Veebor Track Service, and Veebor Password Service recovered. https://status.veebor.dev/incident/528727 Sat, 15 Mar 2025 16:41:05 -0000 https://status.veebor.dev/incident/528727#10f9e98c2782316b6891816922ff31dc0a0fa87f34289d9fdf62e4f0759f0b3c Incident Veebor Git Service went down. https://status.veebor.dev/incident/528727 Sat, 15 Mar 2025 16:40:16 -0000 https://status.veebor.dev/incident/528727#0073f230b5bef88a42f5c01b47412f611d7dc0bb2b92bffcf18f50e8588282a2 Incident Veebor Track Service went down. https://status.veebor.dev/incident/528727 Sat, 15 Mar 2025 16:38:57 -0000 https://status.veebor.dev/incident/528727#0cc37273420b825e68920fb6650b60d1f00e84b809ff994630e6af3894ecd198 Incident Veebor Password Service went down. https://status.veebor.dev/incident/528727 Sat, 15 Mar 2025 16:37:56 -0000 https://status.veebor.dev/incident/528727#6e013e0d712d4c619c0555abbe276a94f19c59a1cfb8a20befcd82f7a1d759bd Incident ping routing service (alx) went down. https://status.veebor.dev/incident/525764 Mon, 10 Mar 2025 14:42:14 -0000 https://status.veebor.dev/incident/525764#27d80bf9d79fed84e81f1132f708a382663eab982d54c0f6419afeb24866ae26 Incident ping routing service (alx) recovered. https://status.veebor.dev/incident/525764 Mon, 10 Mar 2025 14:37:47 -0000 https://status.veebor.dev/incident/525764#2e0da3131491d84f91d40cf49dccc48078d03bfdc204eebc4ec9bb1cff789d50 Incident ping routing service (alx) went down. https://status.veebor.dev/incident/519141 Wed, 26 Feb 2025 06:45:22 -0000 https://status.veebor.dev/incident/519141#652adc5981de9a17c6d82ba7f86ff09a54f8eb04d084fd6daca02193986c1330 Incident Veebor Storage Service recovered. https://status.veebor.dev/incident/519141 Wed, 26 Feb 2025 06:27:01 -0000 https://status.veebor.dev/incident/519141#72976c6342e0d5466246970b38b6e478f6174a7903e6b9b7af2747b074b92161 Incident Veebor Storage Service went down. https://status.veebor.dev/incident/514572 Tue, 18 Feb 2025 01:36:12 -0000 https://status.veebor.dev/incident/514572#e5bfa071afe761b89af987d046a0cfe023bc2d1ed7a871d1d65656acd5fa7700 Incident ping routing service (alx) and Shapy Backend Service recovered. https://status.veebor.dev/incident/514572 Tue, 18 Feb 2025 01:35:37 -0000 https://status.veebor.dev/incident/514572#7ccf0380629fed06fe2a710d01c7758080e69a79355f9a6ca519641f5d3c5221 Incident Veebor Git Service, Veebor Track Service, and Veebor Password Service recovered. https://status.veebor.dev/incident/514572 Tue, 18 Feb 2025 01:20:09 -0000 https://status.veebor.dev/incident/514572#b2e430e744218465820a0a12556d5acd2e9af0851f9eb0858aa8c805777af039 Incident Veebor Git Service went down. https://status.veebor.dev/incident/514572 Tue, 18 Feb 2025 01:19:30 -0000 https://status.veebor.dev/incident/514572#d42fb46dd673aea6584a0ba83d472e5c5cfdfb0fa104909b6a400c0b7bc73cdd Incident ping routing service (alx) and Veebor Track Service went down. https://status.veebor.dev/incident/514572 Tue, 18 Feb 2025 01:18:07 -0000 https://status.veebor.dev/incident/514572#ab11d658d11044902aae174cd8d32b217f3bc46245d8659ad498cbc0278205f5 Incident Veebor Password Service went down. https://status.veebor.dev/maintenance/509489 Sat, 08 Feb 2025 11:30:59 -0000 https://status.veebor.dev/incident/509489#01b15a5bff72babb2cb55580329a52ff0648184e19f22c19b49cc48714ab3ed1 Maintenance Upgrades https://status.veebor.dev/maintenance/508377 Mon, 03 Feb 2025 11:30:38 -0000 https://status.veebor.dev/incident/508377#7df1b7ae0a829263174164c2d199a12290853dd35a321f1da1eb3d6d3723acc8 Maintenance Hardware upgrades https://status.veebor.dev/maintenance/508375 Mon, 03 Feb 2025 10:00:12 -0000 https://status.veebor.dev/incident/508375#032361f383be956239b83d4002de1891086f5c900430e5c109b5645ab8d87f53 Maintenance Hardware upgrades https://status.veebor.dev/maintenance/443512 Sat, 12 Oct 2024 15:55:18 -0000 https://status.veebor.dev/incident/443512#8727bff0087f98bcd8159b6b0ce62d22aff8d1555ab6de4618268bf46f0833b4 Maintenance Update systems https://status.veebor.dev/maintenance/396777 Thu, 11 Jul 2024 12:00:00 -0000 https://status.veebor.dev/incident/396777#ffa36712712c53ff00476e56430cb9145ee468a173109eb56618c8500a162a8f Maintenance Upgrade ALX-1 hardware https://status.veebor.dev/maintenance/393518 Thu, 04 Jul 2024 11:01:36 -0000 https://status.veebor.dev/incident/393518#36cba7d9b5f1b27c2382662b7b1a46254a5869f5440ba21b7891306057a4605e Maintenance Reboot systems https://status.veebor.dev/maintenance/366777 Wed, 08 May 2024 22:45:00 -0000 https://status.veebor.dev/incident/366777#04c5b66bd6816dd3d0f15a1f22f6c3d1591ace23862841f14a79498d2c6433b6 Maintenance Update Proxmox https://status.veebor.dev/maintenance/360699 Thu, 25 Apr 2024 13:55:00 -0000 https://status.veebor.dev/incident/360699#faf609d6bb161330f16eeb563f5a693f5d62e35908af9a5164f37c2600026638 Maintenance Migrate pass.veebor.dev to an in-house container in ALX region https://status.veebor.dev/maintenance/360608 Thu, 25 Apr 2024 09:59:36 -0000 https://status.veebor.dev/incident/360608#b22971acc751f3b77d53e9cc6687b63e14f1045fc1de472e4be9d76618288633 Maintenance Proxmox + GitLab update