Incidents 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/783447 Wed, 10 Dec 2025 04:12:23 -0000 https://status.veebor.dev/incident/783447#5882ef171b66b4ea2af3b6b38d75f7c5659e0a7026d44bad1db22540ac7c0a5f Veebor Track Service and Veebor Password Service recovered. https://status.veebor.dev/incident/783447 Wed, 10 Dec 2025 04:12:23 -0000 https://status.veebor.dev/incident/783447#5882ef171b66b4ea2af3b6b38d75f7c5659e0a7026d44bad1db22540ac7c0a5f 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 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 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 ping routing service (alx) recovered. https://status.veebor.dev/incident/780979 Fri, 05 Dec 2025 21:15:11 -0000 https://status.veebor.dev/incident/780979#04eb9867e106e950d06b50265d0347d4098c11e059c65e684484ed921778c235 Shapy Backend Service recovered. https://status.veebor.dev/incident/780979 Fri, 05 Dec 2025 21:10:51 -0000 https://status.veebor.dev/incident/780979#ca56eb6d2e68b3187aaf327866ed18fac21cd63d69ac76a5beb113358f474086 ping routing service (alx) and Shapy Backend Service went down. https://status.veebor.dev/incident/780979 Fri, 05 Dec 2025 21:10:51 -0000 https://status.veebor.dev/incident/780979#ca56eb6d2e68b3187aaf327866ed18fac21cd63d69ac76a5beb113358f474086 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 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 Veebor Password Service went down. https://status.veebor.dev/incident/768470 Tue, 18 Nov 2025 12:57:31 -0000 https://status.veebor.dev/incident/768470#d50eef8b3c219d2b65d1e10746a390f6ff79a525638c53619c839ab0b9f5e73a Shapy Backend Service recovered. https://status.veebor.dev/incident/768470 Tue, 18 Nov 2025 12:46:05 -0000 https://status.veebor.dev/incident/768470#7d5db5cd50715c12f9ee86c24e0835f40a28119a9f0e28eba58ab478ee3ff26a 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 Veebor Portfolio Website recovered. https://status.veebor.dev/incident/768470 Tue, 18 Nov 2025 11:59:47 -0000 https://status.veebor.dev/incident/768470#ae580c9651d34b4bbac93b26c53bc1a8e292614a6ef65c50fe4895f7f1c5ca06 Shapy Backend Service went down. https://status.veebor.dev/incident/768470 Tue, 18 Nov 2025 11:47:19 -0000 https://status.veebor.dev/incident/768470#1a6f8036119d2099688ff7815ea62a4e563b058367d50822161449dab65275fe 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 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 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 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 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 Veebor Storage Service went down. https://status.veebor.dev/incident/761811 Mon, 10 Nov 2025 23:57:48 -0000 https://status.veebor.dev/incident/761811#7f5b9b9b2cb1151c071e09d65e1506963ef143c325635e863063dbf03d90c67d Shapy Backend Service recovered. https://status.veebor.dev/incident/761811 Mon, 10 Nov 2025 23:57:21 -0000 https://status.veebor.dev/incident/761811#20f7186414c32a684a5e48e990f28af25502c0bd8a5bdb75bcd012bd66738074 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 Veebor Git Service, Veebor Track Service, and Veebor Password Service recovered. https://status.veebor.dev/incident/761811 Mon, 10 Nov 2025 23:56:34 -0000 https://status.veebor.dev/incident/761811#52c3c51d3eb9b1cdc32e572c27ca3048a677113782795a199d25d424fbea93c7 Veebor Git Service, Veebor Track Service, and Veebor Password Service recovered. https://status.veebor.dev/incident/761811 Mon, 10 Nov 2025 23:56:34 -0000 https://status.veebor.dev/incident/761811#52c3c51d3eb9b1cdc32e572c27ca3048a677113782795a199d25d424fbea93c7 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 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 Veebor Git Service and Shapy Backend Service went down. https://status.veebor.dev/incident/761811 Mon, 10 Nov 2025 23:38:31 -0000 https://status.veebor.dev/incident/761811#a53b11e50fc43a7d5668fe1be9fb2c5e47c7adc2853c3683afb7c5269bda9439 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 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 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 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 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 Veebor Track Service and Veebor Password Service recovered. https://status.veebor.dev/incident/759864 Fri, 07 Nov 2025 12:53:41 -0000 https://status.veebor.dev/incident/759864#9efdc2758416f2a3bac5f5c047f991f4231ba3eb321c17c4a1d55f06f4af072d 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 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 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 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 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 ping routing service (alx) recovered. https://status.veebor.dev/incident/759864 Fri, 07 Nov 2025 11:54:47 -0000 https://status.veebor.dev/incident/759864#1f28de426b69a0e36fbcb96b54cd303391f2f4e7e604371e83ea19b7679847f8 Shapy Backend Service recovered. https://status.veebor.dev/incident/759864 Fri, 07 Nov 2025 11:49:32 -0000 https://status.veebor.dev/incident/759864#be4f1f8be6e45cf50056f205aecacc681e3ff2a5e15f9eddae98f3a35d2b8447 ping routing service (alx) went down. https://status.veebor.dev/incident/759864 Fri, 07 Nov 2025 11:47:22 -0000 https://status.veebor.dev/incident/759864#23a1ea8f3c829a04e5bc058d81409116e497ffd62a7e219ce51da4b93d8efa6c Shapy Backend Service went down. https://status.veebor.dev/incident/758502 Wed, 05 Nov 2025 13:26:15 -0000 https://status.veebor.dev/incident/758502#edad5aa93c21ee9d1caf7bd70553645908ec8968145e2e4ca3ed23c7b738d6dd 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 Veebor Storage Service went down. https://status.veebor.dev/incident/742575 Mon, 13 Oct 2025 09:20:05 -0000 https://status.veebor.dev/incident/742575#85f50836164a03fbcd2ac65726fc6b0dd6c18967d0ae2536f6ded323ca06a67d Shapy Backend Service recovered. https://status.veebor.dev/incident/742575 Mon, 13 Oct 2025 09:19:12 -0000 https://status.veebor.dev/incident/742575#2c6a6d4dfe3652d997a1ceee45547c321155a05a6abd97899febe0d748c1cc7b ping routing service (alx) recovered. https://status.veebor.dev/incident/742575 Mon, 13 Oct 2025 09:16:07 -0000 https://status.veebor.dev/incident/742575#05717225263fe8b086228c48b1e4cd2d6af397161f827afd917dbe991a3b0b4b Shapy Backend Service went down. https://status.veebor.dev/incident/742575 Mon, 13 Oct 2025 09:14:15 -0000 https://status.veebor.dev/incident/742575#596ca43564f46715b70c9c13b3990f164b1e8150e969db911d2411507d19b015 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 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 Veebor Track Service and Veebor Password Service recovered. https://status.veebor.dev/incident/742575 Mon, 13 Oct 2025 08:48:43 -0000 https://status.veebor.dev/incident/742575#8140466e01f7d1c7c61ef93f2d34bcefd10425aac7f3e48dbee6ac453533cc82 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 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 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 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 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 Veebor Password Service went down. https://status.veebor.dev/incident/738780 Mon, 06 Oct 2025 20:43:22 -0000 https://status.veebor.dev/incident/738780#d9a819266f74447177f6f737d193daa404d78ba7e5deba7dcf714bc2cdca7729 Shapy Backend Service recovered. https://status.veebor.dev/incident/738780 Mon, 06 Oct 2025 20:41:22 -0000 https://status.veebor.dev/incident/738780#ef0a5dcddb27d23315d03abc3050f2c042cd24eae44b9b44c0636e78ea1878ea 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 Veebor Monitoring Service went down. https://status.veebor.dev/incident/738780 Mon, 06 Oct 2025 20:32:27 -0000 https://status.veebor.dev/incident/738780#de58cf5568d4136982be3a30ab19b15b32166e29ee524488afbd93453f4cd32c Shapy Backend Service went down. https://status.veebor.dev/incident/719043 Mon, 08 Sep 2025 10:00:00 -0000 https://status.veebor.dev/incident/719043#f6c7a1c2772fc503f38fa9074a10f2377f6b0afd6e31b2ec5143f77d7fe5a326 Our ISP fixed the upstream issue https://status.veebor.dev/incident/719043 Mon, 08 Sep 2025 10:00:00 -0000 https://status.veebor.dev/incident/719043#f6c7a1c2772fc503f38fa9074a10f2377f6b0afd6e31b2ec5143f77d7fe5a326 Our ISP fixed the upstream issue https://status.veebor.dev/incident/719043 Mon, 08 Sep 2025 10:00:00 -0000 https://status.veebor.dev/incident/719043#f6c7a1c2772fc503f38fa9074a10f2377f6b0afd6e31b2ec5143f77d7fe5a326 Our ISP fixed the upstream issue https://status.veebor.dev/incident/719043 Mon, 08 Sep 2025 10:00:00 -0000 https://status.veebor.dev/incident/719043#f6c7a1c2772fc503f38fa9074a10f2377f6b0afd6e31b2ec5143f77d7fe5a326 Our ISP fixed the upstream issue https://status.veebor.dev/incident/719043 Mon, 08 Sep 2025 10:00:00 -0000 https://status.veebor.dev/incident/719043#f6c7a1c2772fc503f38fa9074a10f2377f6b0afd6e31b2ec5143f77d7fe5a326 Our ISP fixed the upstream issue https://status.veebor.dev/incident/719043 Mon, 08 Sep 2025 10:00:00 -0000 https://status.veebor.dev/incident/719043#f6c7a1c2772fc503f38fa9074a10f2377f6b0afd6e31b2ec5143f77d7fe5a326 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 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 16:50:00 -0000 https://status.veebor.dev/incident/719043#e05ad30657418f3555b3ce72ae924c95a939fbb949db0aac8c48b2fdd171ba4f 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 16:50:00 -0000 https://status.veebor.dev/incident/719043#e05ad30657418f3555b3ce72ae924c95a939fbb949db0aac8c48b2fdd171ba4f 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 16:50:00 -0000 https://status.veebor.dev/incident/719043#e05ad30657418f3555b3ce72ae924c95a939fbb949db0aac8c48b2fdd171ba4f 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 16:50:00 -0000 https://status.veebor.dev/incident/719043#e05ad30657418f3555b3ce72ae924c95a939fbb949db0aac8c48b2fdd171ba4f 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 16:50:00 -0000 https://status.veebor.dev/incident/719043#e05ad30657418f3555b3ce72ae924c95a939fbb949db0aac8c48b2fdd171ba4f 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 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 Veebor Git Service and Shapy Backend Service went down. https://status.veebor.dev/incident/719043 Fri, 05 Sep 2025 15:29:48 -0000 https://status.veebor.dev/incident/719043#f9e65c153e7ac3c466572934f8d72a20252af1446180cb08ed3a3734c2afd96a 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 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 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 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 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 Veebor Storage Service went down. https://status.veebor.dev/incident/701864 Thu, 07 Aug 2025 07:42:20 -0000 https://status.veebor.dev/incident/701864#ea111c3ae4d0b8d6c58fd60ba2e350abd02b2bcdcac4acdb8fd91c6744db717b Shapy Backend Service recovered. https://status.veebor.dev/incident/701864 Thu, 07 Aug 2025 07:40:58 -0000 https://status.veebor.dev/incident/701864#0e4c2911daf8d8220acc2385fee253b2d08509d4b3a855fdf00262f4c3400445 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 Veebor Track Service and Veebor Password Service recovered. https://status.veebor.dev/incident/701864 Thu, 07 Aug 2025 07:40:53 -0000 https://status.veebor.dev/incident/701864#914d4035b6f62848bd6dfddcb98d3503e99def99fd22734be570b1717fcee997 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 Veebor Monitoring Service recovered. https://status.veebor.dev/incident/701864 Thu, 07 Aug 2025 06:10:38 -0000 https://status.veebor.dev/incident/701864#fe57d061656a04e91986dbb5c13ff7a8a145ff98cba3ffa81f87f2a17c6e125b Shapy Backend Service went down. https://status.veebor.dev/incident/701864 Thu, 07 Aug 2025 06:09:31 -0000 https://status.veebor.dev/incident/701864#65115bae560c993495c9c31d9bbe538eb509dc138844a72b70b8b7607a76949e Veebor Git Service and Veebor Track Service went down. https://status.veebor.dev/incident/701864 Thu, 07 Aug 2025 06:09:31 -0000 https://status.veebor.dev/incident/701864#65115bae560c993495c9c31d9bbe538eb509dc138844a72b70b8b7607a76949e 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 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 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 ping routing service (alx) recovered. https://status.veebor.dev/incident/701276 Wed, 06 Aug 2025 09:05:53 -0000 https://status.veebor.dev/incident/701276#6303c4d0dcc5ea58e1c0403ae625e9320ab8b18d44c4e97c46903107b54a92ab Shapy Backend Service recovered. https://status.veebor.dev/incident/701276 Wed, 06 Aug 2025 09:02:00 -0000 https://status.veebor.dev/incident/701276#e1a43b0bf4d34d214bfb589ed9f5aa29362cfc91bade821c67dbd2b68843f829 ping routing service (alx) went down. https://status.veebor.dev/incident/701276 Wed, 06 Aug 2025 09:01:34 -0000 https://status.veebor.dev/incident/701276#c7231ffe2abb7216f01482a21be84c9e43742e04a0d5685b376a4843aeabb488 Shapy Backend Service went down. https://status.veebor.dev/incident/700371 Tue, 05 Aug 2025 00:32:21 -0000 https://status.veebor.dev/incident/700371#367d5dbfe2a17fcdb62aaa31ea492db8fa62ba2c0a02eb5028cc233e337ca3b5 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 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 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 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 ping routing service (alx) recovered. https://status.veebor.dev/incident/668329 Thu, 31 Jul 2025 09:27:58 -0000 https://status.veebor.dev/incident/668329#6428ae8f31d45ac95df6c1783bae516d5462f33dd7dc2d15eb2dd725d3934d66 Shapy Backend Service recovered. https://status.veebor.dev/incident/668329 Thu, 31 Jul 2025 09:24:05 -0000 https://status.veebor.dev/incident/668329#c661c2ea023e93ec2397aa1fc6e54b2dfd1071ac9d9ec12a2c95a3a99dc811c5 ping routing service (alx) went down. https://status.veebor.dev/incident/668329 Thu, 31 Jul 2025 09:23:41 -0000 https://status.veebor.dev/incident/668329#18b753ec5fda215127270392850dad76fa6bb91b70bf93df4b2639faaf24983c Shapy Backend Service went down. https://status.veebor.dev/incident/626677 Sun, 27 Jul 2025 17:59:03 -0000 https://status.veebor.dev/incident/626677#7b4d0bc07624d176e478668f051b7df812ee8ef3d179b1f891457e02c946af51 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 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 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 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 Veebor Track Service and Veebor Password Service recovered. https://status.veebor.dev/incident/624202 Wed, 23 Jul 2025 22:25:20 -0000 https://status.veebor.dev/incident/624202#e047c2c2737b38514a9e5782ffaf34787780a614a744c0121a10b418684739fd 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 ping routing service (alx) recovered. https://status.veebor.dev/incident/624202 Wed, 23 Jul 2025 22:23:37 -0000 https://status.veebor.dev/incident/624202#8d7c5ba0651e26c98898ae983f1094272d3558c904ec5252da6d8b9dea21f875 Shapy Backend Service recovered. https://status.veebor.dev/incident/624202 Wed, 23 Jul 2025 22:20:59 -0000 https://status.veebor.dev/incident/624202#74e7fefc0cdaba1ad483ffb85d47d1e6674ff4d2526f7f95a8fdaa0291c1c34a 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 ping routing service (alx) and Veebor Password Service went down. https://status.veebor.dev/incident/624202 Wed, 23 Jul 2025 22:19:43 -0000 https://status.veebor.dev/incident/624202#ecbab73bc652698ffd019dc7d8fd4041de31ca208abc16671d8f40e982815482 ping routing service (alx) and Veebor Password Service went down. https://status.veebor.dev/incident/624202 Wed, 23 Jul 2025 22:19:31 -0000 https://status.veebor.dev/incident/624202#c428056879008aa244dc432e24f360f8f602f82e0c2a3e9366119cc2323977d7 Shapy Backend Service went down. https://status.veebor.dev/incident/624202 Wed, 23 Jul 2025 01:38:16 -0000 https://status.veebor.dev/incident/624202#64398af38ac449ee34ddb824bed769c49d4ba13d40d78d7632e5ac8566f5da47 Veebor Track Service and Veebor Password Service recovered. https://status.veebor.dev/incident/624202 Wed, 23 Jul 2025 01:38:16 -0000 https://status.veebor.dev/incident/624202#64398af38ac449ee34ddb824bed769c49d4ba13d40d78d7632e5ac8566f5da47 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 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 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 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 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 Veebor Track Service recovered. https://status.veebor.dev/incident/626131 Fri, 04 Jul 2025 17:30:02 -0000 https://status.veebor.dev/incident/626131#f1361078de854eb5b2a8bfc40a4a8ce9c5ea620d15e20c2ec1b60d9881e79f9f Maintenance completed https://status.veebor.dev/incident/626131 Fri, 04 Jul 2025 17:30:02 -0000 https://status.veebor.dev/incident/626131#f1361078de854eb5b2a8bfc40a4a8ce9c5ea620d15e20c2ec1b60d9881e79f9f Maintenance completed https://status.veebor.dev/incident/626131 Fri, 04 Jul 2025 17:30:02 -0000 https://status.veebor.dev/incident/626131#f1361078de854eb5b2a8bfc40a4a8ce9c5ea620d15e20c2ec1b60d9881e79f9f Maintenance completed https://status.veebor.dev/incident/626131 Fri, 04 Jul 2025 17:30:02 -0000 https://status.veebor.dev/incident/626131#f1361078de854eb5b2a8bfc40a4a8ce9c5ea620d15e20c2ec1b60d9881e79f9f Maintenance completed https://status.veebor.dev/incident/626131 Fri, 04 Jul 2025 17:30:02 -0000 https://status.veebor.dev/incident/626131#f1361078de854eb5b2a8bfc40a4a8ce9c5ea620d15e20c2ec1b60d9881e79f9f Maintenance completed https://status.veebor.dev/incident/614190 Fri, 04 Jul 2025 17:27:39 -0000 https://status.veebor.dev/incident/614190#af87f2445cc43da357f4351ded95e8990bcd26707818d0cd78d492dadd73cdf9 Veebor Git Service and Veebor Password Service recovered. https://status.veebor.dev/incident/614190 Fri, 04 Jul 2025 17:27:39 -0000 https://status.veebor.dev/incident/614190#af87f2445cc43da357f4351ded95e8990bcd26707818d0cd78d492dadd73cdf9 Veebor Git Service and Veebor Password Service recovered. https://status.veebor.dev/incident/614190 Fri, 04 Jul 2025 17:25:23 -0000 https://status.veebor.dev/incident/614190#1af70b31acbf7b7de8a47456d367e75fac00a5d02b2ba78b2f90ac4f13245348 Shapy Backend Service recovered. https://status.veebor.dev/incident/614190 Fri, 04 Jul 2025 13:25:12 -0000 https://status.veebor.dev/incident/614190#776f76ce98ed456b35bad4b39e79af1c0890884e30655b429358fdb4cb4c516b Shapy Backend Service went down. https://status.veebor.dev/incident/614190 Fri, 04 Jul 2025 13:23:28 -0000 https://status.veebor.dev/incident/614190#9adcbbb3a6e5a0ee008d0ecb55e4832778235b43cfaf1425b1e0725e7547ea37 Veebor Git Service and Veebor Track Service went down. https://status.veebor.dev/incident/614190 Fri, 04 Jul 2025 13:23:28 -0000 https://status.veebor.dev/incident/614190#9adcbbb3a6e5a0ee008d0ecb55e4832778235b43cfaf1425b1e0725e7547ea37 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 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 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 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 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 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 Veebor Track Service and Veebor Password Service recovered. https://status.veebor.dev/incident/614190 Fri, 04 Jul 2025 11:48:25 -0000 https://status.veebor.dev/incident/614190#785cce8362784915bcdf9c3f5974c0e641e247223f246185fc5060c2cff2f35e 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 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 Veebor Password Service went down. https://status.veebor.dev/incident/626131 Fri, 04 Jul 2025 11:30:02 -0000 https://status.veebor.dev/incident/626131#cb1e9359ce91553d7d3c9eae3d7ef7de3f97f98bdc11dd7c93ca72d0d0bb9ea8 New server @ ALX https://status.veebor.dev/incident/626131 Fri, 04 Jul 2025 11:30:02 -0000 https://status.veebor.dev/incident/626131#cb1e9359ce91553d7d3c9eae3d7ef7de3f97f98bdc11dd7c93ca72d0d0bb9ea8 New server @ ALX https://status.veebor.dev/incident/626131 Fri, 04 Jul 2025 11:30:02 -0000 https://status.veebor.dev/incident/626131#cb1e9359ce91553d7d3c9eae3d7ef7de3f97f98bdc11dd7c93ca72d0d0bb9ea8 New server @ ALX https://status.veebor.dev/incident/626131 Fri, 04 Jul 2025 11:30:02 -0000 https://status.veebor.dev/incident/626131#cb1e9359ce91553d7d3c9eae3d7ef7de3f97f98bdc11dd7c93ca72d0d0bb9ea8 New server @ ALX https://status.veebor.dev/incident/626131 Fri, 04 Jul 2025 11:30:02 -0000 https://status.veebor.dev/incident/626131#cb1e9359ce91553d7d3c9eae3d7ef7de3f97f98bdc11dd7c93ca72d0d0bb9ea8 New server @ ALX https://status.veebor.dev/incident/600687 Wed, 11 Jun 2025 06:38:07 -0000 https://status.veebor.dev/incident/600687#929faf7cbc77e5d4fa5a96ce8a73f0767c34e85a06e8711e5c5edb6ed0dd5bfd 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 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 Veebor Track Service and Veebor Password Service recovered. https://status.veebor.dev/incident/573390 Tue, 20 May 2025 22:36:10 -0000 https://status.veebor.dev/incident/573390#649db9c568a84980aba791d6e86f3d1f8f3fef431628e54652a76d107d46353f 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 ping routing service (alx) recovered. https://status.veebor.dev/incident/573390 Tue, 20 May 2025 22:34:32 -0000 https://status.veebor.dev/incident/573390#319f2e32867868ffa3adc374cf48071719c8eef75fa3b992efdd3f5be148e33d Shapy Backend Service recovered. https://status.veebor.dev/incident/573390 Tue, 20 May 2025 22:33:59 -0000 https://status.veebor.dev/incident/573390#7a5842de32fa3679583911ddbb3baa6852b8eb1f9d32c8e881b25343b0ad1f1d 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 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 Veebor Git Service and Shapy Backend Service went down. https://status.veebor.dev/incident/573390 Tue, 20 May 2025 22:30:07 -0000 https://status.veebor.dev/incident/573390#7f9c497f08c4ea0736559ef26baa9f3ab13e41e3f997d4a27a5a611fc28bef01 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 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 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 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 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 ping routing service (alx) and Shapy Backend Service recovered. https://status.veebor.dev/incident/529293 Sun, 16 Mar 2025 23:58:15 -0000 https://status.veebor.dev/incident/529293#314869e2c1d877cd8df22d56e4c8c45435a67bc1a4fd311153f80e70fba5f44e 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 Veebor Git Service, Veebor Track Service, and Veebor Password Service recovered. https://status.veebor.dev/incident/529293 Sun, 16 Mar 2025 23:56:55 -0000 https://status.veebor.dev/incident/529293#9cc157b78d3120b60891a10c8228b94958db0c77628aa2437d0eb5ad9b38e861 Veebor Git Service, Veebor Track Service, and Veebor Password Service recovered. https://status.veebor.dev/incident/529293 Sun, 16 Mar 2025 23:56:55 -0000 https://status.veebor.dev/incident/529293#9cc157b78d3120b60891a10c8228b94958db0c77628aa2437d0eb5ad9b38e861 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 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 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 Veebor Password Service and Shapy Backend Service went down. https://status.veebor.dev/incident/529293 Sun, 16 Mar 2025 23:39:35 -0000 https://status.veebor.dev/incident/529293#d2c5696a4c067d323d59debfd56c81c7fdd39b79e046040cf74e83a8d0259b27 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 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 ping routing service (alx) and Shapy Backend Service recovered. https://status.veebor.dev/incident/528727 Sat, 15 Mar 2025 16:45:16 -0000 https://status.veebor.dev/incident/528727#9177abcc8bc785ccac1cfdd4d9cce42782a79d33ec0280fd214d39c98a0cc7f5 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 Veebor Git Service, Veebor Track Service, and Veebor Password Service recovered. https://status.veebor.dev/incident/528727 Sat, 15 Mar 2025 16:43:58 -0000 https://status.veebor.dev/incident/528727#ed681736607c12d62cb08b8a8156275a2a5f2400151c534c4b34f08bd05cb9bb Veebor Git Service, Veebor Track Service, and Veebor Password Service recovered. https://status.veebor.dev/incident/528727 Sat, 15 Mar 2025 16:43:58 -0000 https://status.veebor.dev/incident/528727#ed681736607c12d62cb08b8a8156275a2a5f2400151c534c4b34f08bd05cb9bb 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 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 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 Veebor Password Service went down. https://status.veebor.dev/incident/528727 Sat, 15 Mar 2025 16:38:44 -0000 https://status.veebor.dev/incident/528727#dabcb3cacb766673e24cc3f0dca2c49e71cf9822dcacc737f88b28e89f4bb7f4 Shapy Backend Service went down. https://status.veebor.dev/incident/528727 Sat, 15 Mar 2025 16:37:56 -0000 https://status.veebor.dev/incident/528727#6e013e0d712d4c619c0555abbe276a94f19c59a1cfb8a20befcd82f7a1d759bd 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 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 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 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 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 ping routing service (alx) and Shapy Backend Service recovered. https://status.veebor.dev/incident/514572 Tue, 18 Feb 2025 01:36:12 -0000 https://status.veebor.dev/incident/514572#e5bfa071afe761b89af987d046a0cfe023bc2d1ed7a871d1d65656acd5fa7700 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 Veebor Git Service, Veebor Track Service, and Veebor Password Service recovered. https://status.veebor.dev/incident/514572 Tue, 18 Feb 2025 01:35:37 -0000 https://status.veebor.dev/incident/514572#7ccf0380629fed06fe2a710d01c7758080e69a79355f9a6ca519641f5d3c5221 Veebor Git Service, Veebor Track Service, and Veebor Password Service recovered. https://status.veebor.dev/incident/514572 Tue, 18 Feb 2025 01:35:37 -0000 https://status.veebor.dev/incident/514572#7ccf0380629fed06fe2a710d01c7758080e69a79355f9a6ca519641f5d3c5221 Veebor Git Service, Veebor Track Service, and Veebor Password Service recovered. https://status.veebor.dev/incident/514572 Tue, 18 Feb 2025 01:20:47 -0000 https://status.veebor.dev/incident/514572#35679a072d7e470bf648afa8b0c3153ea4255a7f1c68d83620232903dbe3d06f Shapy Backend Service went down. https://status.veebor.dev/incident/514572 Tue, 18 Feb 2025 01:20:09 -0000 https://status.veebor.dev/incident/514572#b2e430e744218465820a0a12556d5acd2e9af0851f9eb0858aa8c805777af039 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 ping routing service (alx) and Veebor Track Service went down. https://status.veebor.dev/incident/514572 Tue, 18 Feb 2025 01:19:30 -0000 https://status.veebor.dev/incident/514572#d42fb46dd673aea6584a0ba83d472e5c5cfdfb0fa104909b6a400c0b7bc73cdd 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 Veebor Password Service went down. https://status.veebor.dev/incident/512367 Thu, 13 Feb 2025 14:09:45 -0000 https://status.veebor.dev/incident/512367#8fc3412f4ee99bad5c9a94ec613263a0a62d8c08b8c8d4b443bda3ff4ed164d1 Veebor Git Service, Veebor Track Service, and Veebor Password Service recovered. https://status.veebor.dev/incident/512367 Thu, 13 Feb 2025 14:09:45 -0000 https://status.veebor.dev/incident/512367#8fc3412f4ee99bad5c9a94ec613263a0a62d8c08b8c8d4b443bda3ff4ed164d1 Veebor Git Service, Veebor Track Service, and Veebor Password Service recovered. https://status.veebor.dev/incident/512367 Thu, 13 Feb 2025 14:09:45 -0000 https://status.veebor.dev/incident/512367#8fc3412f4ee99bad5c9a94ec613263a0a62d8c08b8c8d4b443bda3ff4ed164d1 Veebor Git Service, Veebor Track Service, and Veebor Password Service recovered. https://status.veebor.dev/incident/512367 Thu, 13 Feb 2025 14:03:50 -0000 https://status.veebor.dev/incident/512367#33b1ecd6be9f953ec9685ba1a5a44975451b6bcacd67c8d3e4faf99c7eb44765 Veebor Git Service went down. https://status.veebor.dev/incident/512367 Thu, 13 Feb 2025 14:02:52 -0000 https://status.veebor.dev/incident/512367#4980f32b528eb38fadefd979fd3b7b5778070db39e4746edfd58d72e5d3df234 Veebor Track Service went down. https://status.veebor.dev/incident/512367 Thu, 13 Feb 2025 14:01:14 -0000 https://status.veebor.dev/incident/512367#03f3ae07620f48e533920e31e60dd4eedd44eb2492ab36f7cfdea0ef5dbebdcc Veebor Password Service went down. https://status.veebor.dev/incident/509489 Sat, 08 Feb 2025 12:00:59 -0000 https://status.veebor.dev/incident/509489#ba1bb342d3b5eb8402c567091661fe2c101c9f3264a712259194fc83aa8779e0 Maintenance completed https://status.veebor.dev/incident/509489 Sat, 08 Feb 2025 12:00:59 -0000 https://status.veebor.dev/incident/509489#ba1bb342d3b5eb8402c567091661fe2c101c9f3264a712259194fc83aa8779e0 Maintenance completed https://status.veebor.dev/incident/509489 Sat, 08 Feb 2025 12:00:59 -0000 https://status.veebor.dev/incident/509489#ba1bb342d3b5eb8402c567091661fe2c101c9f3264a712259194fc83aa8779e0 Maintenance completed https://status.veebor.dev/incident/509489 Sat, 08 Feb 2025 12:00:59 -0000 https://status.veebor.dev/incident/509489#ba1bb342d3b5eb8402c567091661fe2c101c9f3264a712259194fc83aa8779e0 Maintenance completed https://status.veebor.dev/incident/509489 Sat, 08 Feb 2025 11:30:59 -0000 https://status.veebor.dev/incident/509489#01b15a5bff72babb2cb55580329a52ff0648184e19f22c19b49cc48714ab3ed1 Upgrades https://status.veebor.dev/incident/509489 Sat, 08 Feb 2025 11:30:59 -0000 https://status.veebor.dev/incident/509489#01b15a5bff72babb2cb55580329a52ff0648184e19f22c19b49cc48714ab3ed1 Upgrades https://status.veebor.dev/incident/509489 Sat, 08 Feb 2025 11:30:59 -0000 https://status.veebor.dev/incident/509489#01b15a5bff72babb2cb55580329a52ff0648184e19f22c19b49cc48714ab3ed1 Upgrades https://status.veebor.dev/incident/509489 Sat, 08 Feb 2025 11:30:59 -0000 https://status.veebor.dev/incident/509489#01b15a5bff72babb2cb55580329a52ff0648184e19f22c19b49cc48714ab3ed1 Upgrades https://status.veebor.dev/incident/508377 Mon, 03 Feb 2025 12:00:38 -0000 https://status.veebor.dev/incident/508377#5906a50cf9f9d17529c5b4845aea559c4a6d727d5dd771d5d8e4dc141d103818 Maintenance completed https://status.veebor.dev/incident/508377 Mon, 03 Feb 2025 12:00:38 -0000 https://status.veebor.dev/incident/508377#5906a50cf9f9d17529c5b4845aea559c4a6d727d5dd771d5d8e4dc141d103818 Maintenance completed https://status.veebor.dev/incident/508377 Mon, 03 Feb 2025 12:00:38 -0000 https://status.veebor.dev/incident/508377#5906a50cf9f9d17529c5b4845aea559c4a6d727d5dd771d5d8e4dc141d103818 Maintenance completed https://status.veebor.dev/incident/508377 Mon, 03 Feb 2025 12:00:38 -0000 https://status.veebor.dev/incident/508377#5906a50cf9f9d17529c5b4845aea559c4a6d727d5dd771d5d8e4dc141d103818 Maintenance completed https://status.veebor.dev/incident/508377 Mon, 03 Feb 2025 11:30:38 -0000 https://status.veebor.dev/incident/508377#7df1b7ae0a829263174164c2d199a12290853dd35a321f1da1eb3d6d3723acc8 Hardware upgrades https://status.veebor.dev/incident/508377 Mon, 03 Feb 2025 11:30:38 -0000 https://status.veebor.dev/incident/508377#7df1b7ae0a829263174164c2d199a12290853dd35a321f1da1eb3d6d3723acc8 Hardware upgrades https://status.veebor.dev/incident/508377 Mon, 03 Feb 2025 11:30:38 -0000 https://status.veebor.dev/incident/508377#7df1b7ae0a829263174164c2d199a12290853dd35a321f1da1eb3d6d3723acc8 Hardware upgrades https://status.veebor.dev/incident/508377 Mon, 03 Feb 2025 11:30:38 -0000 https://status.veebor.dev/incident/508377#7df1b7ae0a829263174164c2d199a12290853dd35a321f1da1eb3d6d3723acc8 Hardware upgrades https://status.veebor.dev/incident/508375 Mon, 03 Feb 2025 10:30:12 -0000 https://status.veebor.dev/incident/508375#8ab7d76ab2f0c9e77504a04b6de813b0676f41ee68ef967e1814a517f2e0ff29 Maintenance completed https://status.veebor.dev/incident/508375 Mon, 03 Feb 2025 10:30:12 -0000 https://status.veebor.dev/incident/508375#8ab7d76ab2f0c9e77504a04b6de813b0676f41ee68ef967e1814a517f2e0ff29 Maintenance completed https://status.veebor.dev/incident/508375 Mon, 03 Feb 2025 10:30:12 -0000 https://status.veebor.dev/incident/508375#8ab7d76ab2f0c9e77504a04b6de813b0676f41ee68ef967e1814a517f2e0ff29 Maintenance completed https://status.veebor.dev/incident/508375 Mon, 03 Feb 2025 10:30:12 -0000 https://status.veebor.dev/incident/508375#8ab7d76ab2f0c9e77504a04b6de813b0676f41ee68ef967e1814a517f2e0ff29 Maintenance completed https://status.veebor.dev/incident/508375 Mon, 03 Feb 2025 10:00:12 -0000 https://status.veebor.dev/incident/508375#032361f383be956239b83d4002de1891086f5c900430e5c109b5645ab8d87f53 Hardware upgrades https://status.veebor.dev/incident/508375 Mon, 03 Feb 2025 10:00:12 -0000 https://status.veebor.dev/incident/508375#032361f383be956239b83d4002de1891086f5c900430e5c109b5645ab8d87f53 Hardware upgrades https://status.veebor.dev/incident/508375 Mon, 03 Feb 2025 10:00:12 -0000 https://status.veebor.dev/incident/508375#032361f383be956239b83d4002de1891086f5c900430e5c109b5645ab8d87f53 Hardware upgrades https://status.veebor.dev/incident/508375 Mon, 03 Feb 2025 10:00:12 -0000 https://status.veebor.dev/incident/508375#032361f383be956239b83d4002de1891086f5c900430e5c109b5645ab8d87f53 Hardware upgrades https://status.veebor.dev/incident/443512 Sat, 12 Oct 2024 16:15:00 -0000 https://status.veebor.dev/incident/443512#f41e6077f8bac8338384b99a5f2ab5f752cda016bad13284ce150c81022a8b38 Maintenance completed https://status.veebor.dev/incident/443512 Sat, 12 Oct 2024 16:15:00 -0000 https://status.veebor.dev/incident/443512#f41e6077f8bac8338384b99a5f2ab5f752cda016bad13284ce150c81022a8b38 Maintenance completed https://status.veebor.dev/incident/443512 Sat, 12 Oct 2024 16:15:00 -0000 https://status.veebor.dev/incident/443512#f41e6077f8bac8338384b99a5f2ab5f752cda016bad13284ce150c81022a8b38 Maintenance completed https://status.veebor.dev/incident/443512 Sat, 12 Oct 2024 16:00:00 -0000 https://status.veebor.dev/incident/443512#8727bff0087f98bcd8159b6b0ce62d22aff8d1555ab6de4618268bf46f0833b4 Update systems https://status.veebor.dev/incident/443512 Sat, 12 Oct 2024 16:00:00 -0000 https://status.veebor.dev/incident/443512#8727bff0087f98bcd8159b6b0ce62d22aff8d1555ab6de4618268bf46f0833b4 Update systems https://status.veebor.dev/incident/443512 Sat, 12 Oct 2024 16:00:00 -0000 https://status.veebor.dev/incident/443512#8727bff0087f98bcd8159b6b0ce62d22aff8d1555ab6de4618268bf46f0833b4 Update systems https://status.veebor.dev/incident/396777 Thu, 11 Jul 2024 14:00:00 -0000 https://status.veebor.dev/incident/396777#6117f7ca6b044ca83dc04b7a6700fb3df182499df5c2a936d79e79f45b509ed3 Maintenance completed https://status.veebor.dev/incident/396777 Thu, 11 Jul 2024 14:00:00 -0000 https://status.veebor.dev/incident/396777#6117f7ca6b044ca83dc04b7a6700fb3df182499df5c2a936d79e79f45b509ed3 Maintenance completed https://status.veebor.dev/incident/396777 Thu, 11 Jul 2024 14:00:00 -0000 https://status.veebor.dev/incident/396777#6117f7ca6b044ca83dc04b7a6700fb3df182499df5c2a936d79e79f45b509ed3 Maintenance completed https://status.veebor.dev/incident/396777 Thu, 11 Jul 2024 12:00:00 -0000 https://status.veebor.dev/incident/396777#ffa36712712c53ff00476e56430cb9145ee468a173109eb56618c8500a162a8f Upgrade ALX-1 hardware https://status.veebor.dev/incident/396777 Thu, 11 Jul 2024 12:00:00 -0000 https://status.veebor.dev/incident/396777#ffa36712712c53ff00476e56430cb9145ee468a173109eb56618c8500a162a8f Upgrade ALX-1 hardware https://status.veebor.dev/incident/396777 Thu, 11 Jul 2024 12:00:00 -0000 https://status.veebor.dev/incident/396777#ffa36712712c53ff00476e56430cb9145ee468a173109eb56618c8500a162a8f Upgrade ALX-1 hardware https://status.veebor.dev/incident/393518 Fri, 05 Jul 2024 01:20:00 -0000 https://status.veebor.dev/incident/393518#95a8b4c20219ec255b3a76de28bd843beac3b0471a681ed5b361d04d96aa20c6 Maintenance completed https://status.veebor.dev/incident/393518 Fri, 05 Jul 2024 01:20:00 -0000 https://status.veebor.dev/incident/393518#95a8b4c20219ec255b3a76de28bd843beac3b0471a681ed5b361d04d96aa20c6 Maintenance completed https://status.veebor.dev/incident/393518 Fri, 05 Jul 2024 01:20:00 -0000 https://status.veebor.dev/incident/393518#95a8b4c20219ec255b3a76de28bd843beac3b0471a681ed5b361d04d96aa20c6 Maintenance completed https://status.veebor.dev/incident/393518 Fri, 05 Jul 2024 00:55:00 -0000 https://status.veebor.dev/incident/393518#36cba7d9b5f1b27c2382662b7b1a46254a5869f5440ba21b7891306057a4605e Reboot systems https://status.veebor.dev/incident/393518 Fri, 05 Jul 2024 00:55:00 -0000 https://status.veebor.dev/incident/393518#36cba7d9b5f1b27c2382662b7b1a46254a5869f5440ba21b7891306057a4605e Reboot systems https://status.veebor.dev/incident/393518 Fri, 05 Jul 2024 00:55:00 -0000 https://status.veebor.dev/incident/393518#36cba7d9b5f1b27c2382662b7b1a46254a5869f5440ba21b7891306057a4605e Reboot systems https://status.veebor.dev/incident/366777 Wed, 08 May 2024 23:00:00 -0000 https://status.veebor.dev/incident/366777#1a768ca61c36ad507e0def9dc61ce00b5bd1dd22575c13a5d5fae22626c4b086 Maintenance completed https://status.veebor.dev/incident/366777 Wed, 08 May 2024 23:00:00 -0000 https://status.veebor.dev/incident/366777#1a768ca61c36ad507e0def9dc61ce00b5bd1dd22575c13a5d5fae22626c4b086 Maintenance completed https://status.veebor.dev/incident/366777 Wed, 08 May 2024 23:00:00 -0000 https://status.veebor.dev/incident/366777#1a768ca61c36ad507e0def9dc61ce00b5bd1dd22575c13a5d5fae22626c4b086 Maintenance completed https://status.veebor.dev/incident/366777 Wed, 08 May 2024 22:45:00 -0000 https://status.veebor.dev/incident/366777#04c5b66bd6816dd3d0f15a1f22f6c3d1591ace23862841f14a79498d2c6433b6 Update Proxmox https://status.veebor.dev/incident/366777 Wed, 08 May 2024 22:45:00 -0000 https://status.veebor.dev/incident/366777#04c5b66bd6816dd3d0f15a1f22f6c3d1591ace23862841f14a79498d2c6433b6 Update Proxmox https://status.veebor.dev/incident/366777 Wed, 08 May 2024 22:45:00 -0000 https://status.veebor.dev/incident/366777#04c5b66bd6816dd3d0f15a1f22f6c3d1591ace23862841f14a79498d2c6433b6 Update Proxmox https://status.veebor.dev/incident/360699 Thu, 25 Apr 2024 14:30:00 -0000 https://status.veebor.dev/incident/360699#d94f97473e90de071a9a11b3286fd93bb345073cd6013e35891931b073607204 Maintenance completed https://status.veebor.dev/incident/360699 Thu, 25 Apr 2024 13:55:00 -0000 https://status.veebor.dev/incident/360699#faf609d6bb161330f16eeb563f5a693f5d62e35908af9a5164f37c2600026638 Migrate pass.veebor.dev to an in-house container in ALX region https://status.veebor.dev/incident/360608 Thu, 25 Apr 2024 10:30:00 -0000 https://status.veebor.dev/incident/360608#fe9cd1da0fb4c15981662d0d87d27c38d2ad475aa32a90036bf5745f0720f257 Maintenance completed https://status.veebor.dev/incident/360608 Thu, 25 Apr 2024 10:30:00 -0000 https://status.veebor.dev/incident/360608#fe9cd1da0fb4c15981662d0d87d27c38d2ad475aa32a90036bf5745f0720f257 Maintenance completed https://status.veebor.dev/incident/360608 Thu, 25 Apr 2024 10:00:00 -0000 https://status.veebor.dev/incident/360608#b22971acc751f3b77d53e9cc6687b63e14f1045fc1de472e4be9d76618288633 Proxmox + GitLab update https://status.veebor.dev/incident/360608 Thu, 25 Apr 2024 10:00:00 -0000 https://status.veebor.dev/incident/360608#b22971acc751f3b77d53e9cc6687b63e14f1045fc1de472e4be9d76618288633 Proxmox + GitLab update