Incidents reported on status page for PPRO.DEV https://status.ppro.dev/ https://d1lppblt9t2x15.cloudfront.net/logos/8f6104f7dd5b9db77b1f2440f08264e3.png https://status.ppro.dev/ en https://status.ppro.dev/incident/359861 Sun, 02 Feb 2025 12:58:48 -0000 https://status.ppro.dev/incident/359861#6da6959cdfa86f13de73026808039997dd94c568333634f880d766798e2545ff BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sun, 02 Feb 2025 12:51:06 -0000 https://status.ppro.dev/incident/359861#009c9d73b561647bdd00b1cd20bebc68f144e308c48db169ce4a2f0ded4db5a5 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 22 Jan 2025 23:21:36 -0000 https://status.ppro.dev/incident/359861#af7cb2d6df46405ed364a86a80e63c76d03c06b4288cd5e7eb800b35fa41b714 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 22 Jan 2025 23:14:22 -0000 https://status.ppro.dev/incident/359861#510bb130265918cbce578c34b68c9d9c68497b1aa20d359e2d1df9cfc3c4882d BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Thu, 26 Dec 2024 11:15:34 -0000 https://status.ppro.dev/incident/359861#91a9b966e730dfb7cc320a87c4b6fbcad7de4957b82fc60e993c4e1cabed7fe5 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Thu, 26 Dec 2024 11:13:54 -0000 https://status.ppro.dev/incident/359861#63d42227d0bb5d419e6f41acee0fc07337ce91656f00984231e1c2692c0b1993 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Thu, 26 Dec 2024 11:08:09 -0000 https://status.ppro.dev/incident/359861#c112b3fc72ab24ef8258314e7d8df8c377b9be8d14b47fd6ba17066b86ddbe9b BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Thu, 26 Dec 2024 11:06:37 -0000 https://status.ppro.dev/incident/359861#b9220a6412db6b3e8b95ffb7bd92386e999d06e2d7c53c6c1af8038b98bfc9bd BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 25 Dec 2024 16:45:05 -0000 https://status.ppro.dev/incident/359861#f75f2604af7978510f23f1fa3151203c86a51793fe78da53a44e600bf84e3d83 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 25 Dec 2024 16:43:47 -0000 https://status.ppro.dev/incident/359861#7431e2982c3fcb960c70fa601279675af5084c58220eddc8620e38562f1b5891 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 25 Dec 2024 14:06:17 -0000 https://status.ppro.dev/incident/359861#a0dfe4dca920a94f5ac03b5927346eb8c322466064d29816e47d61081b03323d BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 25 Dec 2024 14:02:47 -0000 https://status.ppro.dev/incident/359861#13bab4df43324a1c1b30222ce866f691072ed59ae61a20f0b54980e2cf2e59a6 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 16 Dec 2024 09:53:10 -0000 https://status.ppro.dev/incident/359861#362548aa89f5d53e3b4b37145efaa3e4396257f0e9341b3e7cdeeba6611ae0f4 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 16 Dec 2024 09:51:23 -0000 https://status.ppro.dev/incident/359861#2382f31e37913b495ddf8bb199924aabd65cf344381054ceb14342950f80e29a BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 16 Dec 2024 09:45:38 -0000 https://status.ppro.dev/incident/359861#9c2b00c2b8b46da5a1183ada60dc41114db426c75ba799709d1604b249f1c41c BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 16 Dec 2024 09:44:06 -0000 https://status.ppro.dev/incident/359861#ff068e10c7fcc29129c7caa919f6bc90cc1b19c692ecec8a5d5d89bf2837c24d BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 16 Dec 2024 05:47:19 -0000 https://status.ppro.dev/incident/359861#100f0a19f3c587fa799960bd7a05dcce76726804a98f69643184cfed28b8c68e BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 16 Dec 2024 05:45:39 -0000 https://status.ppro.dev/incident/359861#08491aa7069348aea128a02887388af9360ab23880b6d7128d4486d8db041487 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 16 Dec 2024 05:09:59 -0000 https://status.ppro.dev/incident/359861#be72389ec0c89f748706b592ad898a2afbc712ab0732d86e22b98843280d507f BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 16 Dec 2024 05:07:45 -0000 https://status.ppro.dev/incident/359861#87751c01fe7c1b2b02a7a6cd4193dde08553227966652cbe19b45bdc652636f3 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sun, 15 Dec 2024 14:10:38 -0000 https://status.ppro.dev/incident/359861#d853df5ff619ae00a91fc9df98d705c2a1c0f5fab0fab46144480338ac2ecbf8 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sun, 15 Dec 2024 14:07:15 -0000 https://status.ppro.dev/incident/359861#be751fa5489af95072e121f11bb733c5c0052e6f3205f6cea283211ff8d1ce42 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sun, 15 Dec 2024 12:13:26 -0000 https://status.ppro.dev/incident/359861#c6ded07acf954145e277eb320e0890f5a03bbcc35c1cff8a26ee52f898786557 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sun, 15 Dec 2024 12:10:04 -0000 https://status.ppro.dev/incident/359861#121811286b5ffd2b642ea943a441b00f9f85a466b55c6e99b68b813fbd007384 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sun, 15 Dec 2024 08:12:09 -0000 https://status.ppro.dev/incident/359861#124c4ade99a53e86f6c0146563799460a71fd47cff06e1ce00ee8c50e52299d4 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sun, 15 Dec 2024 08:10:35 -0000 https://status.ppro.dev/incident/359861#fb8129ec2dd86cf369604b3d676c21ecbbd06611169e40f8ca6abc371fdc5b70 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sun, 15 Dec 2024 06:10:04 -0000 https://status.ppro.dev/incident/359861#2172689a6b5d52c7d1ee6ec5e2a63fb880dc6ba3c23c66abe2e0fbf38c4d7cef BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sun, 15 Dec 2024 06:08:24 -0000 https://status.ppro.dev/incident/359861#d30654ae6c8e12adfad955ad98609ccc5ee63600090a6fe94da3df22d774a938 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 14 Dec 2024 12:36:59 -0000 https://status.ppro.dev/incident/359861#53ad5e94c109733dc98890c98e776fcd98212bbc64d0719afb94f853854590e8 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sat, 14 Dec 2024 10:15:13 -0000 https://status.ppro.dev/incident/359861#8fed3af0d7c9e4ece1d363e7f0a43fd09d0002a8c6fab0cf670c2dedc7d6f6c2 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 14 Dec 2024 07:19:39 -0000 https://status.ppro.dev/incident/359861#270175ee4a2d48175cb38687252ba03d7b481fa25f29d88765518d30f06a3744 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sat, 14 Dec 2024 07:18:07 -0000 https://status.ppro.dev/incident/359861#b49450f4292102a6b88c93762d2e99e69913f3b446f6b8b9bc654cf92389cd8c BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 13 Dec 2024 16:16:44 -0000 https://status.ppro.dev/incident/359861#e2bc25fe39a295257c4a3888ba53cf665fa57dea770f66ad1e8aac8cf6c9d727 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Fri, 13 Dec 2024 16:09:33 -0000 https://status.ppro.dev/incident/359861#4a9e767a46ae2902a84a0edf93699e8c0daea21068cb7058bfd515d5afb81dc5 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Fri, 13 Dec 2024 13:36:54 -0000 https://status.ppro.dev/incident/359861#c25dc6d7c85d81fab4272a53b7e878eb4219f008a9bea038ad25e0fdfe721c18 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Fri, 13 Dec 2024 13:35:10 -0000 https://status.ppro.dev/incident/359861#a5259eebecf5c4bf2d3840466a9bea7db1fe44f87419e0f0bd858c199a4161e3 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 13 Dec 2024 13:24:35 -0000 https://status.ppro.dev/incident/359861#a61cc91932b5150da7af3ca9b10f21b28a4c044b4a774a88284641b8676e0c3c BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Fri, 13 Dec 2024 13:22:57 -0000 https://status.ppro.dev/incident/359861#3dc4c1ca0631f528dda99cb596947f6fbd802f7c8f54d8b2c5e62a259462ae30 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 13 Dec 2024 11:45:10 -0000 https://status.ppro.dev/incident/359861#9e929c02f04687b9ee50d208e7ff02f1184452414a05c4861307b79963409caf BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 13 Dec 2024 11:41:36 -0000 https://status.ppro.dev/incident/359861#9e82aaddbb163f0aab1b0e5f890551fa8faa7bed5d5874acc2858684ddb875e2 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Fri, 13 Dec 2024 11:34:25 -0000 https://status.ppro.dev/incident/359861#3efb2ae29350020f4d445e2127d10481036fdf252d5331a49ca9278668e7a904 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Fri, 13 Dec 2024 11:32:54 -0000 https://status.ppro.dev/incident/359861#e2852cd32f7360ecd64977ff9143f4c9426ebf71aae41c0bdc6471805c19c16f BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 13 Dec 2024 10:24:43 -0000 https://status.ppro.dev/incident/359861#5950a582e530b6b205c31fc6c1f2fd508426a03a12dfd730653e7f3e88d1d7f9 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 13 Dec 2024 10:21:06 -0000 https://status.ppro.dev/incident/359861#181a4319ee2ba4fd4bdf17115e41459f6bdbbcd00365bdf183c35613386bddaa BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Fri, 13 Dec 2024 10:13:48 -0000 https://status.ppro.dev/incident/359861#d81e69360d5469d12c436c3bc6929548507994cdeb90bc023f81c45ba2509eae BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Fri, 13 Dec 2024 10:12:17 -0000 https://status.ppro.dev/incident/359861#969556884fe3758a99a3d2bf790e715b2fb47601ef341038bd823d804ca18213 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 13 Dec 2024 09:45:57 -0000 https://status.ppro.dev/incident/359861#5fce34377cf3e63f957eef1549613ca567efbff5de2e3136d064fa7d6bc8a55b BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Fri, 13 Dec 2024 09:44:28 -0000 https://status.ppro.dev/incident/359861#bf80fcd2dea4e3b7bb28c9e308041f472deff93fb74166a2ec043ad4632961de BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 13 Dec 2024 09:33:48 -0000 https://status.ppro.dev/incident/359861#e0f3d296924a0828bf66b2adca401761cbfcfcb30a49fb08085d91d268fa8cf3 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Fri, 13 Dec 2024 09:32:30 -0000 https://status.ppro.dev/incident/359861#d799a389fd2d041fe47229bbd81bcad2c7dcc3f96e11b53c6a227a9948cf7fa1 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 13 Dec 2024 09:26:07 -0000 https://status.ppro.dev/incident/359861#747449fb27499f97f2ad943520ab336b6c52d6974308bb3fb82f10ba75e1c796 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Fri, 13 Dec 2024 09:24:28 -0000 https://status.ppro.dev/incident/359861#9cd877f435ed7d13c9c0f22724274f181bf0a19d4eff89f4f040b9ea4b777fe3 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 13 Dec 2024 09:18:47 -0000 https://status.ppro.dev/incident/359861#4f6e0fb3167718edfb60d99c28606b4f2a5d743a276e16f77ebbba29020845fa BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Fri, 13 Dec 2024 09:17:12 -0000 https://status.ppro.dev/incident/359861#99946268c4d27cae7a42f84d01526cafb699ccaffc94301850730230f47a898c BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 13 Dec 2024 09:01:01 -0000 https://status.ppro.dev/incident/359861#13ef390a80225413c0d1a0f3f497b5746951dba08741b18e15d4f80d31b86187 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Fri, 13 Dec 2024 08:59:31 -0000 https://status.ppro.dev/incident/359861#e16abc59c6833ade36e6c11ac71b268b0b1a98860e9986b5247e5e11f1f563d2 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 13 Dec 2024 08:43:43 -0000 https://status.ppro.dev/incident/359861#aee77fc46ab812059f11c38a1cdbd380d3af9605dc623cc4981c1bbf6350aba4 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Fri, 13 Dec 2024 08:42:13 -0000 https://status.ppro.dev/incident/359861#533d7792e110111ac354ec8e929a1cb94c708dbe11e83d77418ab4202eb03fb2 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 13 Dec 2024 07:10:57 -0000 https://status.ppro.dev/incident/359861#93578814602a3a94f92d3d0b94cd36e896bd1dc9bd3fc194a148d79802a4c158 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Fri, 13 Dec 2024 07:09:22 -0000 https://status.ppro.dev/incident/359861#6389018b6c8d8b57f608b9877c504e8e3f00e93171af9972dfb67a1f712f08f3 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 13 Dec 2024 06:18:43 -0000 https://status.ppro.dev/incident/359861#07fbeeda9786e447434e6e975701f6fff6f128839f38bb69c71c580562b4818c BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Fri, 13 Dec 2024 06:17:14 -0000 https://status.ppro.dev/incident/359861#99a253475ca83b4dba229ef3de46d4110ce08b228b32b11b1f4505b4b20d13d9 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Thu, 12 Dec 2024 13:15:56 -0000 https://status.ppro.dev/incident/359861#9ac3057f38e94a15cac4b10419407d48025c63a395b84bf410ac04b8f2f23a13 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Thu, 12 Dec 2024 13:14:27 -0000 https://status.ppro.dev/incident/359861#2067bc27cdf628e70530a93f05a9369c5ca0e817ba367cc5fc13ae734263648e BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Thu, 12 Dec 2024 11:27:17 -0000 https://status.ppro.dev/incident/359861#004eab0e8a54a8b81a38340465a15c4a5d00fe705bdd44215c9250b58da325d7 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Thu, 12 Dec 2024 11:22:57 -0000 https://status.ppro.dev/incident/359861#603fce59c4df209828717fe7e473b4f3b12cc964adbb86efbb2ce7ec6b63b935 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Thu, 12 Dec 2024 10:59:26 -0000 https://status.ppro.dev/incident/359861#26a1d1a10f101dc627cfed344500b054f9d8b36d929e64014591c8e358357172 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Thu, 12 Dec 2024 10:55:55 -0000 https://status.ppro.dev/incident/359861#a264cfb2ad27e020e1e0ec7a88babfcc9a66f684e1a39d3a62817564dcfa41d8 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Thu, 12 Dec 2024 10:42:08 -0000 https://status.ppro.dev/incident/359861#785f77ee8f7f6126bc63d4307ece71428d793c6cb1ff4ff996ec5873ee18fee9 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Thu, 12 Dec 2024 06:48:58 -0000 https://status.ppro.dev/incident/359861#854b5dd771c3e5253eae556f1234568b33104318604397381a5d0858a5c4e4f3 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 11 Dec 2024 16:26:08 -0000 https://status.ppro.dev/incident/359861#343b5e3eea3910f5537c3644e557caa12069fb020c4ad655ee61557011c2c5db BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 11 Dec 2024 10:18:14 -0000 https://status.ppro.dev/incident/359861#f574d7cfc61a42743dfab848256039e179af866446baf8289d1a5ae795200c61 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 11 Dec 2024 07:27:16 -0000 https://status.ppro.dev/incident/359861#bc6db4241c76a029dbef1da1bee3939b327c4f4b02c2d9bac486d545879b3fd0 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 11 Dec 2024 07:25:43 -0000 https://status.ppro.dev/incident/359861#2abf2f93aa49624e076c609f4ec59358a0848c6bdba725eb46f0a2ed8577a6cb BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 11 Dec 2024 06:39:30 -0000 https://status.ppro.dev/incident/359861#1ab086189130d4bafdebf27238a1c7ce2daf6f9a26f893d74fb0f46fe9a8e951 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 11 Dec 2024 06:38:17 -0000 https://status.ppro.dev/incident/359861#f500a715588d146b59360eaf85f99422aa08aac914f65cd301f51b51422d92a8 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Tue, 10 Dec 2024 13:20:51 -0000 https://status.ppro.dev/incident/359861#a7783ddf23a7f1d59ee96c2bca17bbc080b642146af7aab717b9e03cede9b19b BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Tue, 10 Dec 2024 13:19:19 -0000 https://status.ppro.dev/incident/359861#99fdf20240c19d614a546afaf1a0113efdfb209b852c7f6fdc59b5c4a6495f0a BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Tue, 10 Dec 2024 07:12:44 -0000 https://status.ppro.dev/incident/359861#68fd07fed67ea383f1adc3fdd0f4271290c58864b1a9002cff9297b76d0ea803 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Tue, 10 Dec 2024 07:11:11 -0000 https://status.ppro.dev/incident/359861#f6e156744790374cdd1b37262b0008499d30afb999f778e408d99e81ec8e53ff BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Tue, 10 Dec 2024 06:15:33 -0000 https://status.ppro.dev/incident/359861#0595f380ae8b5d51ac5e1de49aa437665072e6864df00ef56b0364e3db167c48 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Tue, 10 Dec 2024 06:14:03 -0000 https://status.ppro.dev/incident/359861#166cd3ac175fcfc4e64109684742f6fa7b77c20bac2e7c667e89edf9654d7a9f BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 09 Dec 2024 13:12:02 -0000 https://status.ppro.dev/incident/359861#dd9a424650f2c5966adc3b60e1ffd42bf07d5f734b461f4070c33b1ff45cbafc BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 09 Dec 2024 13:10:25 -0000 https://status.ppro.dev/incident/359861#32649e01d6b69c45ea58ca2061c9762130f5db7d371f223bbb2748a16b62578f BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 09 Dec 2024 11:39:10 -0000 https://status.ppro.dev/incident/359861#2aeae101af68418efe31b4c537920666d50b7aa522d16821ced5eb888dace3ec BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 09 Dec 2024 11:37:48 -0000 https://status.ppro.dev/incident/359861#4e41d84bf44912796c705de762a0a5f72e60f2bc2f3ee0c20d54f2884858a3fb BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sun, 08 Dec 2024 14:09:41 -0000 https://status.ppro.dev/incident/359861#69d6a41e93a545c6b8c7cd5825eaa344b553b85b1a861efec8d1c49e23586ad9 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sun, 08 Dec 2024 14:06:28 -0000 https://status.ppro.dev/incident/359861#b852b3e4192b4347582d9f22e6c1bdb5edb7ca8e87b990ee63c1ecd090b542c3 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sun, 08 Dec 2024 12:13:49 -0000 https://status.ppro.dev/incident/359861#61e2e11c7f28f66463266e2d294210baa956416e9c20be0b8c65ca107f4a67d4 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sun, 08 Dec 2024 12:12:17 -0000 https://status.ppro.dev/incident/359861#f5e9c0c1d80cc88abf36b116e49923737b74d96d888aec75faf90efa201c1e45 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 07 Dec 2024 10:10:53 -0000 https://status.ppro.dev/incident/359861#995bef5ce1fa1ae74a296e9fef99c1b3473f598cb1d738fba0b51f5dbc17bdf3 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sat, 07 Dec 2024 10:09:28 -0000 https://status.ppro.dev/incident/359861#a5e703a89efa6d9e233421765615c5fce48a9ece4c3d53b8422199bfeeb6865e BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 07 Dec 2024 09:18:42 -0000 https://status.ppro.dev/incident/359861#483d10fb703781a3b0b83e58bf8f736d4fbb9e34843f1290f659828627446a53 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sat, 07 Dec 2024 09:17:12 -0000 https://status.ppro.dev/incident/359861#afcd1e9f7bd5d18c556bccf57ceb6b68917fa2a25175ba19f83b96c445ca5a96 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 06 Dec 2024 16:15:40 -0000 https://status.ppro.dev/incident/359861#7ff4f5002f721b8bbc6d1b43e15b281a0161a4f4777b5fc8cf7ece131e21f6bd BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Fri, 06 Dec 2024 16:13:54 -0000 https://status.ppro.dev/incident/359861#4c79807b3612de17fb91a918e8434a2cfc6fa0fbf8c7c62085c726d676f1344b BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 06 Dec 2024 15:21:48 -0000 https://status.ppro.dev/incident/359861#aafad1dff791d8c9201434cc4290f11f1d549192bf2b1b66e2936577626f79e0 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 06 Dec 2024 07:38:10 -0000 https://status.ppro.dev/incident/359861#28b6867174c42ce2c8a9a85f9052047944ccf29f0198d5d245941c82a24f90aa BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 06 Dec 2024 07:17:32 -0000 https://status.ppro.dev/incident/359861#d3f95459a6c2e36ebd74f956c03271af0442200173683c2068e5f5c9c060f462 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Fri, 06 Dec 2024 07:15:54 -0000 https://status.ppro.dev/incident/359861#7a43f56dc57fb3b7e091f99f458fc361c045efa4f59dd664137d55f55a5b7658 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 06 Dec 2024 07:03:10 -0000 https://status.ppro.dev/incident/359861#f7893678a1d6c4121d197304feb7710a6b544b9400d35fbc4be5e13c7f900e42 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 06 Dec 2024 06:59:47 -0000 https://status.ppro.dev/incident/359861#50132052a5b46c768d556a6766845175ed1e2dfad245ed198031f925bea2997e BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Fri, 06 Dec 2024 06:55:56 -0000 https://status.ppro.dev/incident/359861#8536f8f9dab10858f1ecb57acf0c954a7e1818d00f8caf9e7204f3cf32f7a45e BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 06 Dec 2024 06:53:09 -0000 https://status.ppro.dev/incident/359861#2132614339b4aae0712cff58710c904470d88d62777fe8f1cf9220066284c6ba BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 06 Dec 2024 06:47:19 -0000 https://status.ppro.dev/incident/359861#674a8f1eb14736d84d8b51a1fa853a1f7514e31a813985124fc3594a594b2009 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Fri, 06 Dec 2024 06:45:56 -0000 https://status.ppro.dev/incident/359861#d7f3ce833f04cfa5097828468205a488d7506340b113b04f1ce0a6fbef383c92 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 06 Dec 2024 06:44:36 -0000 https://status.ppro.dev/incident/359861#e663f8a09b91a5be9ecae9de071549b18ca66cf20609fc0ae4d820d8b399a223 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Fri, 06 Dec 2024 06:42:54 -0000 https://status.ppro.dev/incident/359861#4345f6b4ef93671fac076b96e2d01a43972fe65d006dc4f092d54f5d2ccdece8 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 06 Dec 2024 05:11:48 -0000 https://status.ppro.dev/incident/359861#4aa5a904d65bc62a35e1d78a5e7fa77d514c37aa92e8c2c660c990285d9bc40a BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Fri, 06 Dec 2024 05:10:15 -0000 https://status.ppro.dev/incident/359861#8d4a034f063f158e7def276fa0c9e8a224008a2737ddf75e7540b42bd98b1622 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Thu, 05 Dec 2024 21:17:19 -0000 https://status.ppro.dev/incident/359861#7e2986785b735abd337f1491a28e68333af26c1c062c15a2af11dae8aef8e5d0 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Thu, 05 Dec 2024 21:14:02 -0000 https://status.ppro.dev/incident/359861#06f9072225a3343ebd5263e7982006b6d0d7a52f4e4d8338b82af2de43a4feb3 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Thu, 05 Dec 2024 19:16:45 -0000 https://status.ppro.dev/incident/359861#6c47e4526a1e36298a87c13b5342544c950a0ab31f57157716447d7c82f29807 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Thu, 05 Dec 2024 19:14:58 -0000 https://status.ppro.dev/incident/359861#ad194f48309190503c73186a801c9f60e828cec28ce6d45865d5246baea3e3b7 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 04 Dec 2024 18:11:28 -0000 https://status.ppro.dev/incident/359861#3a9f566cb4a800a9822b9aaf259fcb987c780abe4d3425eea8b87f15cf84c5b9 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 04 Dec 2024 18:08:24 -0000 https://status.ppro.dev/incident/359861#5728df1262e6a5bbe9e7a012c4f916bf770141cd10d040613ad28f00d5a43611 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 04 Dec 2024 16:55:24 -0000 https://status.ppro.dev/incident/359861#34ce762db0428ec3ae0de81b0ed1980da16ed4c38c96d8c1eadc8c5aff90a8fc BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 04 Dec 2024 16:54:04 -0000 https://status.ppro.dev/incident/359861#2be715527e56e5cf2a95d9729790bf7a049121b138a6a47b30d72600f21cfae3 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 04 Dec 2024 07:49:14 -0000 https://status.ppro.dev/incident/359861#80f1b0114001f6c30acde34b2d364c327604b795ba3d19f14d3a613b65987592 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 04 Dec 2024 07:41:53 -0000 https://status.ppro.dev/incident/359861#5c7e7075f66b126029d41fc9fa5c9ef219a4e1229754c69995ca41ad564e047a BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Tue, 03 Dec 2024 18:27:59 -0000 https://status.ppro.dev/incident/359861#5c3342db4a3d63a4dd7e244a641334a301ce4a5f92960837e6593a34bf0dd6a8 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Tue, 03 Dec 2024 18:20:49 -0000 https://status.ppro.dev/incident/359861#d663cc2fc307bd94ed903b58bc4c16751fcadd56313d356e630dd7fd31404efd BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Tue, 03 Dec 2024 06:15:49 -0000 https://status.ppro.dev/incident/359861#58bc7be96282080a9697f7379ceb5783330db5cc7d1a7a2438929762ab7376bd BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Tue, 03 Dec 2024 06:14:19 -0000 https://status.ppro.dev/incident/359861#244b4b8e90958842e1d14fec72551b187d668a6e3a3da004fff23308e96e5ed6 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Tue, 03 Dec 2024 05:18:16 -0000 https://status.ppro.dev/incident/359861#88601bfa2edb8ad21cbdf7a886f73234917d9475b23eef0bd30ccf6747bb8020 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Tue, 03 Dec 2024 05:16:46 -0000 https://status.ppro.dev/incident/359861#12b86bd656f31ad69d27087f783f43579ada5954468f1a4edd64713e1b266f7e BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Tue, 03 Dec 2024 04:35:38 -0000 https://status.ppro.dev/incident/359861#354e3c0746034c9620bb6e95b3d79c2b74f7e1a94ea577b98904dad5773338d8 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Tue, 03 Dec 2024 04:28:17 -0000 https://status.ppro.dev/incident/359861#c1765e00f3db7221cb5e530186ffb7717821741619da3a8306a01906dea8becb BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 02 Dec 2024 10:31:54 -0000 https://status.ppro.dev/incident/359861#93700e3862a003ee90654d525a17d9d9a616160dd8327cd75027243c6298de33 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 02 Dec 2024 10:24:42 -0000 https://status.ppro.dev/incident/359861#3dddde8a049bc21c05dc2fb21bf8e9526db69aa2c28e03c2b04acbf179dcf867 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 02 Dec 2024 02:46:51 -0000 https://status.ppro.dev/incident/359861#80737987475960a98955679c6f0345166b8cd361f98749e360f9fbfe91e3a82c BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 02 Dec 2024 02:29:32 -0000 https://status.ppro.dev/incident/359861#2e145c53e3ecb8a07f337b099535c8cec08f57d5c6df2d9014940cd1382199aa BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sun, 01 Dec 2024 14:16:52 -0000 https://status.ppro.dev/incident/359861#d1cdf3f5a6c4ff3495904ce07d3580159fc6878ade807ae659765d14e034c300 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sun, 01 Dec 2024 14:15:13 -0000 https://status.ppro.dev/incident/359861#29a4d2c168469989786b94a5deebacd2fc7ba41fc5779296df9e0f246342fe13 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sun, 01 Dec 2024 12:19:33 -0000 https://status.ppro.dev/incident/359861#6d482a354bb5cfa7fe09b986ce2a10471c311940dbd8e1e0107a5b3cbaa8ec66 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sun, 01 Dec 2024 12:18:07 -0000 https://status.ppro.dev/incident/359861#062dedf23cbd45e7cf8c184d572c1f98072222075b8b6cab36434feb2e0251f3 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sun, 01 Dec 2024 10:00:18 -0000 https://status.ppro.dev/incident/359861#6ff8f88c1a109970899488ed0bc13a8a015896e5e2aadf86b5f7596696fc1e2d BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sun, 01 Dec 2024 09:56:42 -0000 https://status.ppro.dev/incident/359861#fa64923dac780f90028a2c48c12a374114c184fd9ade84ebf44ae3a4473ecc4e BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sat, 30 Nov 2024 16:19:11 -0000 https://status.ppro.dev/incident/359861#13329fb0add3f9fc618d5e1392f576bf035c3920ab6ed253dee48671346649bd BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sat, 30 Nov 2024 16:17:41 -0000 https://status.ppro.dev/incident/359861#4efc8d372e64e08cb479654ac58e095a4380e7dc390d7130d6a94faaf778e02e BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 30 Nov 2024 10:11:27 -0000 https://status.ppro.dev/incident/359861#9a7f62e6fa0b77e2e8f231ad1232a44e230625a783129bbcefd956b99a7a04d6 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sat, 30 Nov 2024 10:09:57 -0000 https://status.ppro.dev/incident/359861#030de27c0a18dc663963ef206657d6d56518436a8bdea91ade89a3741703f96c BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 29 Nov 2024 13:48:19 -0000 https://status.ppro.dev/incident/359861#37d2091ffde3bdfa9c687509c451c59898f57965e8d50fed93f358a308b670b7 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Fri, 29 Nov 2024 13:46:54 -0000 https://status.ppro.dev/incident/359861#54cbadebe073212d36d7d1f89c527b2c4d82b75f8f9be4010b651dc838535d75 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 29 Nov 2024 13:45:35 -0000 https://status.ppro.dev/incident/359861#9ce1706a066552bcf2d0fdb4b015f685bc9927d2093a0622a8b0daea4ec3200e BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Fri, 29 Nov 2024 13:44:07 -0000 https://status.ppro.dev/incident/359861#e4035293440d2ce3a6b45afb600f3976f50b6967528493c62b2508fbf0dcedda BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 29 Nov 2024 13:36:48 -0000 https://status.ppro.dev/incident/359861#843df1ee41ebb8df50a82400f96776fac914c0e8868e66b9ac63949dd36e54ac BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 29 Nov 2024 13:34:07 -0000 https://status.ppro.dev/incident/359861#8829d43ea9de195c63a844d5655a09ad1ce306c473cad2b0e8faf79f84439204 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 29 Nov 2024 13:28:22 -0000 https://status.ppro.dev/incident/359861#efa00c4a5d9ef439176c16a18f0c8f3f8bdd9f8b930e2977f7d1fe13c6742e48 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Fri, 29 Nov 2024 13:26:57 -0000 https://status.ppro.dev/incident/359861#51af82a8d73d0c68ef5703b5ae364ff90e1b3646bec9a969442330e62eea5d07 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 29 Nov 2024 07:19:05 -0000 https://status.ppro.dev/incident/359861#0a8ef960c35fd326a8a8da49481a9978f4c2f8d110521e8fa5e4185b827e147f BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Fri, 29 Nov 2024 07:17:21 -0000 https://status.ppro.dev/incident/359861#b6cab0f3cf388467c53803519f93335805d8baf421c6bb059c660f71d270489e BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 29 Nov 2024 06:51:42 -0000 https://status.ppro.dev/incident/359861#48c7522d5fc17f43ac93f2ac53ee69ce1c6faa6fa6b9ea2210ab79d684aac7e0 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Fri, 29 Nov 2024 06:50:10 -0000 https://status.ppro.dev/incident/359861#542c37afe4cc5516fd60192e9bfd8a57048f5ffeb63cfa14c77ae5183514c22d BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 29 Nov 2024 06:49:02 -0000 https://status.ppro.dev/incident/359861#aa7ac667731cbc157f14df07dede9d7c91c4b0147b21736d6fae30b52f91ad63 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Fri, 29 Nov 2024 06:47:22 -0000 https://status.ppro.dev/incident/359861#4aaca0d5d34c10d26b084b3e2059fab71fc3050b124f19b6f4a5a5108f3f0e72 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 29 Nov 2024 04:26:37 -0000 https://status.ppro.dev/incident/359861#bc9430d25d60f7956d9bcc48854892c9b532e262daed4ba0ec112ebf78ef5a55 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Fri, 29 Nov 2024 04:25:14 -0000 https://status.ppro.dev/incident/359861#93f3edf7e535aaf2fb6d557bbcef1e6b137690906fdb6033372b5e3684373e7b BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Thu, 28 Nov 2024 22:26:50 -0000 https://status.ppro.dev/incident/359861#8df84ad8228f503466506e67106c7ad6c324cc59df02d8f1570b4e808b8995d7 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Thu, 28 Nov 2024 22:23:15 -0000 https://status.ppro.dev/incident/359861#795890f3633d6f77e1fb26180fdb7630c30a213c252921629fdc4bbd3c75193f BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Thu, 28 Nov 2024 19:36:06 -0000 https://status.ppro.dev/incident/359861#e47ca969fb1dc169a219ab3e4c912caff8ef24a9fff314f7cb0330fdf0fb1a10 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Thu, 28 Nov 2024 19:34:30 -0000 https://status.ppro.dev/incident/359861#fd82e4507606b2c043199266d452f6d64a5068d60a28c1523e324437ab53a9d9 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Thu, 28 Nov 2024 12:27:15 -0000 https://status.ppro.dev/incident/359861#081dff80998ca5f002d193e8c1b5b20b4cb1c4ce0f5e3821b015b9b897bf1369 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Thu, 28 Nov 2024 12:25:29 -0000 https://status.ppro.dev/incident/359861#e2a10655c8ef3ae4dfd7f4f59b485fc38da799aa24d5fa1b8aa7f0d8312fa1c6 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Thu, 28 Nov 2024 12:09:54 -0000 https://status.ppro.dev/incident/359861#e8ce786fd5f8d52d067cb5612a93df79ee579ef8321309214dfbaa681627f565 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Thu, 28 Nov 2024 12:08:10 -0000 https://status.ppro.dev/incident/359861#e2b508fb6a6b0741c60d7e34ae28da691656f0830aa8a7906a5ada90c5701b59 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Thu, 28 Nov 2024 12:07:07 -0000 https://status.ppro.dev/incident/359861#19d1a91d88a5fceada73fd2a6aad53a95b180c4e50e284878d6afe22a4372d15 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Thu, 28 Nov 2024 12:05:28 -0000 https://status.ppro.dev/incident/359861#e080f55bc2176227cbd3a0dd156aca907a2e1eaa96adf616097c3e4f9833dad6 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Thu, 28 Nov 2024 11:58:10 -0000 https://status.ppro.dev/incident/359861#7245e7b7d6ef4b421773852ff9675b39187513fec53325cb214d08d2f40cc6f7 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Thu, 28 Nov 2024 11:35:06 -0000 https://status.ppro.dev/incident/359861#b32922abbb1500dd80f8f5d0d07df20dc9f36558cba26c355ff2cbab00cd76ea BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Thu, 28 Nov 2024 10:48:24 -0000 https://status.ppro.dev/incident/359861#6e606e88697d9fa13d3de595a6223c860cb15a7432e0c4b61a9d249ad476254a BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Thu, 28 Nov 2024 10:46:55 -0000 https://status.ppro.dev/incident/359861#65128ea4b252739346b22a0470d35d4b8fd65831d04a70de75e658f19f28bfff BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 23 Nov 2024 10:12:04 -0000 https://status.ppro.dev/incident/359861#c0cd10134ccb3a2c32f3fb0388b7faa36b4d9f7d28196392590c3a83387f159a BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sat, 23 Nov 2024 10:10:38 -0000 https://status.ppro.dev/incident/359861#6294fa5548c30e844a68e15ebfa2dec3714cbeb96513f2fe57f36d1bbe8b345b BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 23 Nov 2024 07:28:18 -0000 https://status.ppro.dev/incident/359861#e46ddcb42aef456b1d6d095dbe8c5f0bd623f7cd24fe3a14fc54ea2330528316 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 23 Nov 2024 07:24:47 -0000 https://status.ppro.dev/incident/359861#9afc473d6973d28d26b0a0834afa37079f0c6e701ec7882be1330a918eabae71 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Fri, 22 Nov 2024 16:11:33 -0000 https://status.ppro.dev/incident/359861#32f0f2ad24baba3d93f8ae1f0d1e1521c926c0a48f7f7a40d1873b1bed8aa6d4 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Fri, 22 Nov 2024 16:10:09 -0000 https://status.ppro.dev/incident/359861#82ca5753b7c1ab94ce5bc951e72e7cbd0efc950bc53f06d71a339fff8399027c BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 22 Nov 2024 15:19:16 -0000 https://status.ppro.dev/incident/359861#910d85667377cf308c0fcd33f6a6dbfbc4e633387d254a233a9fa18cbf585b2d BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Fri, 22 Nov 2024 15:17:53 -0000 https://status.ppro.dev/incident/359861#df149eac5c5df1e9f52110f4b9e65bff8fc8be4bf332136c252f35a296f2e476 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 22 Nov 2024 07:00:52 -0000 https://status.ppro.dev/incident/359861#d6c744c09f3df60ecc1c38d32a4107dbffa7b35c652a722a64ebefca9e92ba57 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Fri, 22 Nov 2024 06:59:05 -0000 https://status.ppro.dev/incident/359861#7f944e38d34ccc8741a21bb483f9a086007eaa9ee895b1639ddf1144565d321a BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 22 Nov 2024 04:28:12 -0000 https://status.ppro.dev/incident/359861#9116b34494a251e3a5125dad01f9143644ab1dc88fdb78cf3d12c850d3725c45 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Fri, 22 Nov 2024 04:26:30 -0000 https://status.ppro.dev/incident/359861#61d341ba0378e9980c2f11df2b306e1633d44d693d1ea2bcc7b21d4d4daf400a BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 20 Nov 2024 20:11:05 -0000 https://status.ppro.dev/incident/359861#100a56477a058cdc1c6e4e2deb411c4ffadf6b6a0050ece3582bdf4a727589f1 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 20 Nov 2024 20:09:26 -0000 https://status.ppro.dev/incident/359861#21f4515dd5a4bb65df4c0d2ee188e752a72f2fbe30619b302726e706dc7a31e0 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 20 Nov 2024 16:28:29 -0000 https://status.ppro.dev/incident/359861#d36b6b0fbb3cbb60ae71ef5ac885f715d194352e89a338a9b800f02788fcd924 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 20 Nov 2024 16:26:59 -0000 https://status.ppro.dev/incident/359861#eb9699a0cbd5d0ee744cdb2f8e0eed3769795510467df84de120d9984db63315 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Tue, 19 Nov 2024 06:40:43 -0000 https://status.ppro.dev/incident/359861#7e9a323d67dde12e5dc5adb0dcf7bf1995369a1f68254cab0e76b637c42844b3 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Tue, 19 Nov 2024 06:38:58 -0000 https://status.ppro.dev/incident/359861#5051a37742561b17ec3e3b4dccdfc725b0484908667152f8ce5d722c8fc64e21 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Tue, 19 Nov 2024 04:28:19 -0000 https://status.ppro.dev/incident/359861#fc2b4e01090a9dba0304ee33ec0774c276dc6c82ae8cd2349de479a8332db311 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Tue, 19 Nov 2024 04:26:47 -0000 https://status.ppro.dev/incident/359861#c8c78cfe0ebb85cc58dcaea58207e25f8566a4399de284857abdba51128bca5d BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 16 Nov 2024 17:48:20 -0000 https://status.ppro.dev/incident/359861#c4b2edc24db2f82a0390af51a5ffec928da6f552050957a9bc14d6759fa67c3e BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sat, 16 Nov 2024 17:41:02 -0000 https://status.ppro.dev/incident/359861#14e7056878593855d4c1f9d53e257e205603d874f09a08a619ef9132998edabc BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Thu, 14 Nov 2024 05:17:29 -0000 https://status.ppro.dev/incident/359861#56edf43bc0ddd460bd0fe16e6cba236081d3d8db9b7bb0d3048fab354507e438 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Thu, 14 Nov 2024 05:16:00 -0000 https://status.ppro.dev/incident/359861#e02e16c734f6d4d3ea7c92a71179598d69f189bb16baf2b46f4702903a0016f3 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 13 Nov 2024 19:53:42 -0000 https://status.ppro.dev/incident/359861#2e308fc69bda24be984cef2882fb9d157b909affeac48f014a38fe44c93392be BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 13 Nov 2024 19:50:12 -0000 https://status.ppro.dev/incident/359861#69926b3d0e5e8055f081b0207abf808117ae82bdbf8ca546a345efac54c7e517 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 13 Nov 2024 00:58:53 -0000 https://status.ppro.dev/incident/359861#4852195027448cf838fb9696f1a002bffa5984d68027096673d3a78a1b5c2832 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 13 Nov 2024 00:51:42 -0000 https://status.ppro.dev/incident/359861#371bdf8dca3012bda59a13504ede3aafe06cc9f9e7823cebf548a240de52c974 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 13 Nov 2024 00:08:58 -0000 https://status.ppro.dev/incident/359861#069060ecc391d494cbe496381bf18070a6fa936988967b0a895bdd1690b571bf BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 13 Nov 2024 00:01:37 -0000 https://status.ppro.dev/incident/359861#ddb3d6a72a55ba90758894a8a60ffaebfc067cc784167b8245fa1483e7341270 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Tue, 12 Nov 2024 12:51:58 -0000 https://status.ppro.dev/incident/359861#8f04f24ceb33d6c13b706212528f2b61686d76522c8dc11c3f597a458092568f BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Tue, 12 Nov 2024 12:44:45 -0000 https://status.ppro.dev/incident/359861#6e36032f9ef482216a7b8b10fdd3c9995ca7abc086614ddec014067a559f8ecf BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Thu, 24 Oct 2024 15:01:00 -0000 https://status.ppro.dev/incident/359861#455129f144086d27aa58c1adcac7515324d6c5402a0a8b7aba4968e810d3d271 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Thu, 24 Oct 2024 14:59:26 -0000 https://status.ppro.dev/incident/359861#f60cdc0cdac1469ac5493bfc2584bb42711c3bb6d3908fc5b47570f6efc4a341 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Thu, 24 Oct 2024 14:53:48 -0000 https://status.ppro.dev/incident/359861#c35eca73219601081823089858b0cbdb490ad64d9825e5dada134d02e707b953 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Thu, 24 Oct 2024 14:52:10 -0000 https://status.ppro.dev/incident/359861#c3e16b0ab4cf91812a35eddacf354b4e086ae8873a51547cdd7af2fe3fa7921d BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 23 Oct 2024 23:30:24 -0000 https://status.ppro.dev/incident/359861#a77dad1fdf37841aed7fb208665a75c40e65ab676f6532a6e4f035604f29de41 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 23 Oct 2024 23:23:10 -0000 https://status.ppro.dev/incident/359861#1b25c54c2fae295de947d3f28c6917384fdc3cfd0c62da17f71c26152438ffab BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 23 Oct 2024 10:02:44 -0000 https://status.ppro.dev/incident/359861#e03258678f8f391466cfccecd87f65e4afed79720b97e5b38c85b2052a974a80 ppro: hz wireguard & myst recovered. https://status.ppro.dev/incident/359861 Mon, 21 Oct 2024 22:33:04 -0000 https://status.ppro.dev/incident/359861#2061324c9d467227f661a46ea6bb7fc22392868c01939fd204dcfaf7dc3c8020 ppro: ovm myst server went down. https://status.ppro.dev/incident/359861 Mon, 21 Oct 2024 22:32:20 -0000 https://status.ppro.dev/incident/359861#97d17ca947a1602a824e92a6a3c6f344367cef4abde32db99a056e008a425313 ppro: ovm myst server recovered. https://status.ppro.dev/incident/359861 Mon, 21 Oct 2024 04:05:54 -0000 https://status.ppro.dev/incident/359861#4fa912cf8bdfae2aeafa6fbd463b85e4a56db7346aff1a628a9cb47fdf5ec77b BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 21 Oct 2024 03:58:38 -0000 https://status.ppro.dev/incident/359861#c1dd8c9ee389dc16aeef768647ff1da4c1ec92286bb81c4847616b8cef576bd8 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Tue, 15 Oct 2024 08:01:31 -0000 https://status.ppro.dev/incident/359861#c7cdd44f3135034bf273cd586adb40734a36bf9d18228c7e3771d453ca44830d ppro: hz wireguard & myst went down. https://status.ppro.dev/incident/359861 Thu, 08 Aug 2024 23:45:30 -0000 https://status.ppro.dev/incident/359861#fa37cd9b46bc5e7bf578f2a1e8a63a0fb994e12c8e05b18e0fb613c5365ff5f6 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Thu, 08 Aug 2024 23:37:29 -0000 https://status.ppro.dev/incident/359861#d377ada43ec06c5c77815ec2ea3562fd700d5b2c58d4609c07d60b9a91903717 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Thu, 01 Aug 2024 18:05:22 -0000 https://status.ppro.dev/incident/359861#e7714114418f87b29c26c76a02c76b628e4797096fac37854c9c60fbffd1df6c ppro: hz wireguard & myst recovered. https://status.ppro.dev/incident/359861 Thu, 01 Aug 2024 17:59:52 -0000 https://status.ppro.dev/incident/359861#a4a8d8690fcf74a1f704a3a7e2207598a6b53d0ac395136c05f83073420f8531 ppro: hz wireguard & myst went down. https://status.ppro.dev/incident/359861 Sun, 28 Jul 2024 20:40:04 -0000 https://status.ppro.dev/incident/359861#dcb214244db17d318f027edf6c0c811c18c0249aeba4561339a2a75ad7dcba31 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sun, 28 Jul 2024 19:08:10 -0000 https://status.ppro.dev/incident/359861#86090b3afaa000fbf57752305112d46e85cd656d213f8b659cdbebe9c2880dc1 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sun, 28 Jul 2024 17:35:59 -0000 https://status.ppro.dev/incident/359861#40678f5b05571023b7b20a4e5f6f014bda42ec26483bcc71116bb5c5887183e0 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 26 Jul 2024 07:23:52 -0000 https://status.ppro.dev/incident/359861#336d0bd80794f6f96ac5fbcc8841c872af37efae880d41ffbfa2ae226afe13f3 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Thu, 25 Jul 2024 19:14:11 -0000 https://status.ppro.dev/incident/359861#9e8273807575c97c96e3e95fc3de84766569d33f84555b40054f7ac93566ad90 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Thu, 25 Jul 2024 19:10:51 -0000 https://status.ppro.dev/incident/359861#8194b38ac8dc17423e899d03f434600620cb9d2878d9e6a65b00748decfb4014 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Thu, 25 Jul 2024 18:43:29 -0000 https://status.ppro.dev/incident/359861#8ba34eb52699b55947d3fdee32dc0a668d0810eeb4f8cc084857d79857b9bb46 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Thu, 25 Jul 2024 18:41:57 -0000 https://status.ppro.dev/incident/359861#0b8e4de5f1cfaf0e0ed37bc3f48cd9216f4901235c310d2fbe60527faa59b532 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Thu, 25 Jul 2024 07:04:19 -0000 https://status.ppro.dev/incident/359861#7098a876de30fe30c9688396f1d0f714cadd922a0235ee4791f6f678f826a5e3 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Thu, 25 Jul 2024 03:22:55 -0000 https://status.ppro.dev/incident/359861#ca1ca3ff23cd8b7db6d10aa55de629dd2f7b878bfc7019d3ada60ec154bbe72a BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Thu, 25 Jul 2024 01:07:00 -0000 https://status.ppro.dev/incident/359861#bdeee7ed82737f8b0ac797757e6f4a9bdf7961cf7c31559d767365c1ada7bf75 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Thu, 25 Jul 2024 01:05:38 -0000 https://status.ppro.dev/incident/359861#aebadba65d1618ed7592447f35e25553361b120f667da71d43115858d9377f83 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 24 Jul 2024 18:14:19 -0000 https://status.ppro.dev/incident/359861#c8291dfaa079dc5087511b7c2e25e08bfe2f3f972c1bc7b762d56fdbc6eb3677 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 24 Jul 2024 18:12:58 -0000 https://status.ppro.dev/incident/359861#0e7c35ca6b90558e57818d7d02e5aa742b11bbc168ed349404f8dbc6bbe3cf37 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 24 Jul 2024 17:35:35 -0000 https://status.ppro.dev/incident/359861#e68b86c12322521da7db120b7e8ffc57d91b6ff7f6dabe7310aa4659629aa865 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 24 Jul 2024 17:31:57 -0000 https://status.ppro.dev/incident/359861#6c2ced4dfa2829a63d272cda44d9a692d1895fa4571ab51fcf7cce70d4e63561 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 24 Jul 2024 11:43:32 -0000 https://status.ppro.dev/incident/359861#5eae05f92e76948a63373753a86fcffd5fd1d8a09e7f31d6d8bda6dcec5a562c BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 24 Jul 2024 11:41:54 -0000 https://status.ppro.dev/incident/359861#62b0ce5d046e8bf01652cf34e613322b340a7e3f74ab991017d37a519b6b16a4 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 24 Jul 2024 11:29:44 -0000 https://status.ppro.dev/incident/359861#f8a575a8dcb920cfe7a8a4ddfc53c98ff785081e35a25b829ea74bbf3578759b BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 24 Jul 2024 11:26:22 -0000 https://status.ppro.dev/incident/359861#bf9836375e1b160be138900f586774e441861c04b33c59dde8f463bcd23da477 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 24 Jul 2024 03:33:17 -0000 https://status.ppro.dev/incident/359861#264c4ebd3c95c8428819280334c54f9e908e6702d2873cb335d9496778cf7ae8 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 24 Jul 2024 00:06:51 -0000 https://status.ppro.dev/incident/359861#da93b3464413f17641e33d71d26bce4146193de25b1c3b0a585f555b6e59a17e BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Tue, 23 Jul 2024 21:41:02 -0000 https://status.ppro.dev/incident/359861#042f7e6c9ff2f99fbcef4c4fd1c4ef8bf64788c37335df580a2851dcd12967e1 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Tue, 23 Jul 2024 21:39:28 -0000 https://status.ppro.dev/incident/359861#1506e728e25d3124b2de636c08ad0fdd0d156acc5c5b4091396ddb7bc4ab23c9 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Tue, 23 Jul 2024 18:07:40 -0000 https://status.ppro.dev/incident/359861#0e23461a5ee20295c80c14d88ec39a9903a2e58995b299bde8431d4c0c72e01e BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Tue, 23 Jul 2024 18:06:11 -0000 https://status.ppro.dev/incident/359861#c84595d4d4dcc9100a9112b6ae92776efa0089b200b3fce8f7966764b6c8edc5 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Tue, 23 Jul 2024 16:17:43 -0000 https://status.ppro.dev/incident/359861#db137eb39c60df498d541432afff37903364b5794c4eeb0264b371bcd1a3138d BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Tue, 23 Jul 2024 16:14:06 -0000 https://status.ppro.dev/incident/359861#a33ce117669fe87cd67debe58dc6a477c2624f4e7569f6546e8fe77f3c01e3eb BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Tue, 23 Jul 2024 05:43:33 -0000 https://status.ppro.dev/incident/359861#575cab169388e621ef4539971685b2135c625a2f55a74a87b33d1fac49869750 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Tue, 23 Jul 2024 05:41:54 -0000 https://status.ppro.dev/incident/359861#e7e7f1513506cccae91db9d65421bee50819cc96ac5cf739aebe26e323dec471 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Tue, 23 Jul 2024 03:40:53 -0000 https://status.ppro.dev/incident/359861#d070ea8e0b659da83c3f966ee4203a95337b00a37469092cecf5617d0a35339a BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Tue, 23 Jul 2024 03:39:27 -0000 https://status.ppro.dev/incident/359861#0c14e42983b21ae8841b9209c3fe311b26591bff203c6cf61d8515cd5d26834f BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 22 Jul 2024 21:11:48 -0000 https://status.ppro.dev/incident/359861#5dedbc8ba13e2609155f1f1db4dae4bcbc3ae664567ccabd056f693eb400fb5c BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 22 Jul 2024 21:08:18 -0000 https://status.ppro.dev/incident/359861#6186f2d8ee8c8868993037ad2cd8a3ff587c7da6ebfca527e0d0ce157c8be8ba BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 22 Jul 2024 18:40:30 -0000 https://status.ppro.dev/incident/359861#381daa28a5adc42b38644ebe2f46d700c48a5fb0925631d27b09895b259b3558 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 22 Jul 2024 18:39:00 -0000 https://status.ppro.dev/incident/359861#bc2180d718fc12cf264679cc28adf0badbeae16339ef822c78053e86615a9362 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 22 Jul 2024 05:40:47 -0000 https://status.ppro.dev/incident/359861#76336bcfecd8f5c0c330b8548fb38947ea105bbb908132a051f2082f6ea375ff BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 22 Jul 2024 04:09:14 -0000 https://status.ppro.dev/incident/359861#5142700ae6ce5d79f554ba953964d1a666bfc8aca073d8a44fc094c27399f184 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 22 Jul 2024 04:01:59 -0000 https://status.ppro.dev/incident/359861#5c3ab5d988f79304d4fae597647b6d24dfaa2032fca9a169e1016c414b99ac1d BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 22 Jul 2024 03:14:10 -0000 https://status.ppro.dev/incident/359861#07e1cb70644bbbbc1abe109b505b17fdaa717369edd360b837662d84aab1e7da BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 22 Jul 2024 02:41:58 -0000 https://status.ppro.dev/incident/359861#cc15a32e669a88abd6192492f7b55e1c66f5a64724ffa61a8481149b4da182a9 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 22 Jul 2024 02:38:30 -0000 https://status.ppro.dev/incident/359861#be25233dbfd19910f94e3b9f4f323de1c7c338914ca6ab58f64b976b519723ff BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sun, 21 Jul 2024 19:10:23 -0000 https://status.ppro.dev/incident/359861#94d40a4afabf3769a497c8ee65b162cf6244c4435307f016730c281e587eded1 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sun, 21 Jul 2024 19:08:49 -0000 https://status.ppro.dev/incident/359861#cea2c4d223f0a2f8729113359e10fa088c67220026a8a19d572af3c743d65d71 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sun, 21 Jul 2024 17:51:00 -0000 https://status.ppro.dev/incident/359861#3db4661906d8cbf06fe7f81d15accd5211a0cfbe44b0c6f077ebb54eb005e4f6 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sun, 21 Jul 2024 17:47:31 -0000 https://status.ppro.dev/incident/359861#ed5f8865a31c758bb645ec9005191858e9b3d5a2956d9a716470236c59d53b50 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sun, 21 Jul 2024 13:13:19 -0000 https://status.ppro.dev/incident/359861#73f4087773dd44066cb608752a316c31980b784cee846654a26e62000b249016 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sun, 21 Jul 2024 13:09:46 -0000 https://status.ppro.dev/incident/359861#7ce0a0888844b227f66140c82aea1dca09090c2bc8b3f2df25fae82299d01626 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sun, 21 Jul 2024 12:35:58 -0000 https://status.ppro.dev/incident/359861#548c1375ceb9e5881a82eff75b8603a0e8506591360673c8be21f681b5e9e62a BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sun, 21 Jul 2024 06:43:20 -0000 https://status.ppro.dev/incident/359861#03dac4e379da0ca0d57ecda545b8ab14357a6879885068f6911bcbccaa3049ed BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sun, 21 Jul 2024 05:37:36 -0000 https://status.ppro.dev/incident/359861#60bd1e01c6de2f6e20fa37b34c46ff220de536472a9d45f76970d24713bc798b BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sun, 21 Jul 2024 05:35:56 -0000 https://status.ppro.dev/incident/359861#43bf2532567f8043ccc20fe79078f01e2be1c020676a67f4d9046d8c82e0267d BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sun, 21 Jul 2024 01:13:13 -0000 https://status.ppro.dev/incident/359861#05f47a264acd46e8f0fdc6aa84e8c43740bea306e52e3d71691d343b7dd6a9d6 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sun, 21 Jul 2024 01:09:45 -0000 https://status.ppro.dev/incident/359861#b85df8f933262a16e2bcf12c96195ad0b60ac8afaf884f30e34379749695f08b BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sat, 20 Jul 2024 23:42:32 -0000 https://status.ppro.dev/incident/359861#0b57c451dac39318cb9ca8c3fccf46ce92abbe04324f5e3d938e95359d06710b BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sat, 20 Jul 2024 23:41:07 -0000 https://status.ppro.dev/incident/359861#56700f61723be4cdeab67ac832d7524b368b1d5221cb91c8a9e18710f3b78518 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 20 Jul 2024 18:09:42 -0000 https://status.ppro.dev/incident/359861#f0fe741e4a16a379c237f13d8663979ba08d1da520fe82d12cc6b0e228ee653e BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sat, 20 Jul 2024 18:08:03 -0000 https://status.ppro.dev/incident/359861#a673bd825da33f6e913fabc37f351de2ab1cf4ab9c1288b8710ae6a0203f8aa1 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 20 Jul 2024 15:50:52 -0000 https://status.ppro.dev/incident/359861#2f28528d2031650a5505ff7a2e7395f04276ef18bab0f1083ac5d93452a82a49 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 20 Jul 2024 15:47:20 -0000 https://status.ppro.dev/incident/359861#9127055face8f5b7a8f5749f5ef9fb5eee106f602f6050aa27a3a2834cedfa88 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Fri, 19 Jul 2024 23:04:03 -0000 https://status.ppro.dev/incident/359861#de46753c1d69c62ba4b5420f7a7ea28816bf92a7164e534c85fca71e58e0903b BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Fri, 19 Jul 2024 23:02:29 -0000 https://status.ppro.dev/incident/359861#1c5a075d0dc1b921e8ca58cd428a86573b8d73d1ff1fb72add9432b12b9da477 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 19 Jul 2024 21:41:29 -0000 https://status.ppro.dev/incident/359861#6d9507ecbc554a878f3ecd27eb771dc6ccaaab8a768383ffcb024ee30dd6091b BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Fri, 19 Jul 2024 21:40:06 -0000 https://status.ppro.dev/incident/359861#3730b8869311f154ec5fafdfe38db51afa7e9d189d54ce678a60dbc82c88dd1a BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 19 Jul 2024 15:18:29 -0000 https://status.ppro.dev/incident/359861#1ba60683d41c766e5b75f99a93479c343becb6e9c9d321f3e850597c2067b3e9 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Fri, 19 Jul 2024 15:16:59 -0000 https://status.ppro.dev/incident/359861#e9338609a47e1b86eead027c92a1684cac983a0a94c638ae241bb697deaff9e9 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 19 Jul 2024 13:55:13 -0000 https://status.ppro.dev/incident/359861#d9e894748de9d945130d2da46ab4bb87734e98f548bc9406016fbf43a8078a0b BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Fri, 19 Jul 2024 13:53:46 -0000 https://status.ppro.dev/incident/359861#9fc95d14d63c158e3057c5e3a190ba2a6812775c3a21f1a8ae4be5f3b95234bf BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 19 Jul 2024 05:39:43 -0000 https://status.ppro.dev/incident/359861#44045d6fbb2686c4defb82726d1a45231ab5aaeea817638ad3cfb7c7deea75e7 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 19 Jul 2024 05:36:25 -0000 https://status.ppro.dev/incident/359861#787ba90170b78beaeadf5c9b3461b3e152883860d20ebc611eaad97765d390ba BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Fri, 19 Jul 2024 03:43:56 -0000 https://status.ppro.dev/incident/359861#39ea02eba154f0915f87215619b3949e0156eef357ead32cddf991653ce0060d BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Fri, 19 Jul 2024 03:42:30 -0000 https://status.ppro.dev/incident/359861#8d91f5000e261beef3d32d47c4e828d2d92a6b1f9df7013a9e66f9f931eec66e BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Thu, 18 Jul 2024 21:24:25 -0000 https://status.ppro.dev/incident/359861#e9f2163c028d30213e0f30fafb97d533d990936722be49d2fba16a6910bc0417 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Thu, 18 Jul 2024 21:20:54 -0000 https://status.ppro.dev/incident/359861#a91fe53e6c3d29994e0df5182d0e91949f490eba40553ac4121aafb922939c49 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Thu, 18 Jul 2024 18:53:15 -0000 https://status.ppro.dev/incident/359861#7c97e5f72a4401cd0a0bae9a99c017f5855a639fe8049264a3cca1b26aa829c2 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Thu, 18 Jul 2024 18:51:36 -0000 https://status.ppro.dev/incident/359861#4969bc6bd5b6144dc2c5770a7523ac3b7381e3a20f6aee68ceed19cf505515cc BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Thu, 18 Jul 2024 09:56:40 -0000 https://status.ppro.dev/incident/359861#a266a22996fdcf2037d341631afeb58b20b0f87809f005be35b575c7929cf112 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Thu, 18 Jul 2024 09:53:19 -0000 https://status.ppro.dev/incident/359861#a22b65d1565c59bc5ea4ee8a0034f2b49802314e2ab8a4715bc53a09f9ac273a BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Thu, 18 Jul 2024 09:46:02 -0000 https://status.ppro.dev/incident/359861#561c5965bcbfbebcd77acd976b65e27c66a52c1e4c405a682ed401b54bbc1e0a BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Thu, 18 Jul 2024 09:44:25 -0000 https://status.ppro.dev/incident/359861#8f43a05e710fb0a3e7bf033b99843732f9ef3c25648f3570638d8c84ca918c39 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Thu, 18 Jul 2024 06:16:01 -0000 https://status.ppro.dev/incident/359861#306d37c079a03b66e957502d9c95b5777f15af2da77289049074b39620784c5a BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Thu, 18 Jul 2024 06:12:46 -0000 https://status.ppro.dev/incident/359861#3e256d43ad375eb45600f2d06ce64fd23fd3f19acce9d44ad16b3ab4f64d3770 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Thu, 18 Jul 2024 05:25:03 -0000 https://status.ppro.dev/incident/359861#3ec66124290b28afaec14147562c3a92cf3f692e4385d64001f4dd77639fa060 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Thu, 18 Jul 2024 05:23:33 -0000 https://status.ppro.dev/incident/359861#9578f56c5e7c5bc2d7da2301bfc68a9a444cd5c820b7143a2031b1a4a4e18ea0 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Thu, 18 Jul 2024 03:17:41 -0000 https://status.ppro.dev/incident/359861#211ffacaf282469b9d5fee9f94a89004320519a7aee002dadcf6a2af86acb31b BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Thu, 18 Jul 2024 03:15:51 -0000 https://status.ppro.dev/incident/359861#8568142a76b3617516308e69ef95db327b0da99f1fb427e711e3945011aad5d7 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Thu, 18 Jul 2024 02:35:10 -0000 https://status.ppro.dev/incident/359861#55912103516110667068f1bda0b19e6d7f9516bb8318b89fb0ef2d761842fab4 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Thu, 18 Jul 2024 02:33:36 -0000 https://status.ppro.dev/incident/359861#3b33b19e804fbf37da09a933ec31adb988246a8f253b996799225cb0528d04bd BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 17 Jul 2024 22:32:30 -0000 https://status.ppro.dev/incident/359861#16a16cc63ce410c74d9d8ad4e96c5f946fb5b68df8456359f9074d4ff939621b BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 17 Jul 2024 22:30:52 -0000 https://status.ppro.dev/incident/359861#cc92c81871df762d6fc276cfe1e760da0c241274a6127f0d05f0c176e44101a5 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 17 Jul 2024 22:00:05 -0000 https://status.ppro.dev/incident/359861#f955f2ae6e024da996bd3974f59c4ec40f5008c39f9a195fec059af86846f691 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 17 Jul 2024 21:58:37 -0000 https://status.ppro.dev/incident/359861#c4ea7d47503e64e3dd7e3ced5bf256e27cee473ca5e9e77f90ffec17981c791b BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 17 Jul 2024 19:42:23 -0000 https://status.ppro.dev/incident/359861#8f7118eec6b3a3e660435c6595429f0a891c2e10327683f607053be57c420239 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 17 Jul 2024 19:40:52 -0000 https://status.ppro.dev/incident/359861#1be963bb95201d5ddb21ba533b92375b2a89756ffd81fcb82382d199d495ac1d BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 17 Jul 2024 16:48:43 -0000 https://status.ppro.dev/incident/359861#3d8d9e55209cdf94288cd3e3b049de3a5583311070f86e90726fd7db4ae3a079 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 17 Jul 2024 11:58:46 -0000 https://status.ppro.dev/incident/359861#635224b34d645d0ba754674333c6a54c0844184692905d5ea526c488e5e6a940 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 17 Jul 2024 11:42:59 -0000 https://status.ppro.dev/incident/359861#8c90b7ff125c7d2fae09cb92d779514c4a218bb06c35bac01b26994de4d80194 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 17 Jul 2024 11:41:33 -0000 https://status.ppro.dev/incident/359861#e247ea1dee05634aa68c27db35da6746af3a476548d7f92254ac846dde1e6f62 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 17 Jul 2024 09:35:00 -0000 https://status.ppro.dev/incident/359861#83e5b4d08c46975a63d6977c8d3cdd107c7e2e4bb2f3efbd6d6a665d21d2a356 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 17 Jul 2024 09:33:11 -0000 https://status.ppro.dev/incident/359861#7bbdf235427531812a3b2cb3fad2f72ea1973adbdcf1d320248355c9c57446ef BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 17 Jul 2024 07:17:15 -0000 https://status.ppro.dev/incident/359861#4c386d43b0d1bfa036391b8cd8bbed266334e8ef699fdbf42223e01ba0591204 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 17 Jul 2024 07:15:30 -0000 https://status.ppro.dev/incident/359861#57eb17511b5e31d0ea78b46083adac2c8ceba8914487d10569cf03a1dff57719 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 17 Jul 2024 00:14:13 -0000 https://status.ppro.dev/incident/359861#701f2cc8b21a346e955267cb205f46e566f6b2d7fc28257055729387030da85e BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 17 Jul 2024 00:12:52 -0000 https://status.ppro.dev/incident/359861#d7ac25186865b799c0b50f101dc51b860f6a1072c65a6c734147ba958b1c9293 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Tue, 16 Jul 2024 21:55:33 -0000 https://status.ppro.dev/incident/359861#3d6d3a477ad8e135dcd3288de2ee32646a9e88dffc0d99c8073626429129aab1 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Tue, 16 Jul 2024 21:52:03 -0000 https://status.ppro.dev/incident/359861#dabe123546d26e26824d049d3507cd63169903ca085ed57bbee7dca55aaad904 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Tue, 16 Jul 2024 05:42:05 -0000 https://status.ppro.dev/incident/359861#9de5ab1ed0b1b3afd9a90ebc1b4009a167f11a56344c5f5166eecad15935ca90 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Tue, 16 Jul 2024 05:40:22 -0000 https://status.ppro.dev/incident/359861#cd133b7c4435ffe1763e659720b469b60dcd6ba18b2d5dc28a9a2dc34ba866d1 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Tue, 16 Jul 2024 03:58:10 -0000 https://status.ppro.dev/incident/359861#65a874b481e503aa601dac6d594c16216bdd3b538b4d1c38cce7afeca94bcba0 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Tue, 16 Jul 2024 03:54:35 -0000 https://status.ppro.dev/incident/359861#14c074189d5ff47444611ee81cdedc47048d47bf83084b6b3a46316f6d730ca1 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Tue, 16 Jul 2024 00:11:40 -0000 https://status.ppro.dev/incident/359861#3c38687c36e9c46d891054e955b8e860987b2dd6c4de1163d4ccca0d36a048a6 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Tue, 16 Jul 2024 00:10:05 -0000 https://status.ppro.dev/incident/359861#99626399a09e7eba9da540aac1645118bee32fd44bb26752911ba78a8c46f865 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 15 Jul 2024 18:46:54 -0000 https://status.ppro.dev/incident/359861#2a9d51b76dcc807ca55329537ab4e520f291017c23fdab05ea6cc15fbb79c653 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 15 Jul 2024 18:43:23 -0000 https://status.ppro.dev/incident/359861#898f3222bb036a510d59a815421755779a054f92c5315927d736f15ed192a02d BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 15 Jul 2024 12:55:01 -0000 https://status.ppro.dev/incident/359861#276aba10ce9154d5b57c54633611f551f339586bdd8e4aba04eeeebac902aba5 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 15 Jul 2024 12:53:20 -0000 https://status.ppro.dev/incident/359861#d22414bdf10ab2667f75b2fce3971465458916bd66aeb98b598da41129405f7c BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 15 Jul 2024 12:47:51 -0000 https://status.ppro.dev/incident/359861#3d06318bf814a66daaa223cdc63de3585bf7cac5e1cf85737b1bd7aecc9fb4ef BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 15 Jul 2024 12:46:08 -0000 https://status.ppro.dev/incident/359861#821cad0f0485a792e938ca81f4a5fdb460ccccea4168c17d42b630e1dbb8b1e2 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 15 Jul 2024 05:40:41 -0000 https://status.ppro.dev/incident/359861#8ec52cfd36527e6d741a57a6c78616c67215cd0b7db86638e4912879a37805cb BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 15 Jul 2024 05:37:20 -0000 https://status.ppro.dev/incident/359861#752ac1f7271724518db85b28a8d49429b18d4918dc3d6c51db07056bc9f29953 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 15 Jul 2024 00:23:21 -0000 https://status.ppro.dev/incident/359861#89234ecdf5f3ea82a21a049a8c04885f110f9328aa2a11e0b36c74b2a2f23960 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sun, 14 Jul 2024 19:35:27 -0000 https://status.ppro.dev/incident/359861#82d536bef33ea7aa8eaad86e6ae7102aad5c4e016a44399d835280a3d1a48439 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sun, 14 Jul 2024 17:14:37 -0000 https://status.ppro.dev/incident/359861#2f2d3241f2e3d9185f42041b8f18983b74077d4921741617ab2df0c90a378378 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sun, 14 Jul 2024 17:13:01 -0000 https://status.ppro.dev/incident/359861#ebd4f0ea2835161dd41db3cd659bf77cc2090018bdb7e07d88746b1c7948647d BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sun, 14 Jul 2024 13:11:29 -0000 https://status.ppro.dev/incident/359861#d8082200e899e7ac3164021de04316dcd6e48817f44f1357f2f416a8af4f5c28 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sun, 14 Jul 2024 13:09:58 -0000 https://status.ppro.dev/incident/359861#43806f5484b4c0bd6d1e43f0bebf3e7d07d32122d4ed6ff168df1c7555170f62 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sun, 14 Jul 2024 11:13:52 -0000 https://status.ppro.dev/incident/359861#0ef79abb2f51136eb83d9d5d0ee58aba3533ab541b18a77dfacf15e4b4de81ab BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sun, 14 Jul 2024 11:12:24 -0000 https://status.ppro.dev/incident/359861#0cbcf39a2d7d36aa8c704b893d641989b58f4dca38002e2637df9e4b565b83cf BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sun, 14 Jul 2024 07:11:17 -0000 https://status.ppro.dev/incident/359861#786fb178b54bc6dc19843c5da61594f73160c869d447cf4a701fbbe21bdf0f80 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sun, 14 Jul 2024 07:09:34 -0000 https://status.ppro.dev/incident/359861#96f5bea29f2fbb16b46c0f3781c37943e2e5e12dec974410c61c61bd66ff525d BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sun, 14 Jul 2024 05:23:54 -0000 https://status.ppro.dev/incident/359861#a757eb7160f8fbe6ebc73df3a7bbe8984f95526b447532369688d7fa92b10713 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sun, 14 Jul 2024 05:22:26 -0000 https://status.ppro.dev/incident/359861#68b766439f7e636d4ba8203e6b7858e418964c218657edb31a8ed6b46f4aed25 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sun, 14 Jul 2024 03:16:02 -0000 https://status.ppro.dev/incident/359861#9bab99a320ee693c82514df61e3e40d7534a4cbfa22737021084fd3db4d4464e BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sun, 14 Jul 2024 03:14:32 -0000 https://status.ppro.dev/incident/359861#46a6a7b0127cfa15f07ead48fe81630da36f283857a92462a2d5c7a686176f68 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 13 Jul 2024 23:28:46 -0000 https://status.ppro.dev/incident/359861#398f316219a183b216837f8a6ecb6288650effff62b415a9d017e92a6af6c2c1 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sat, 13 Jul 2024 23:27:16 -0000 https://status.ppro.dev/incident/359861#f4b1b88b1e96075ce2a048ccb8aa3cf4ee71eca7710bc72dca77a5971378ad28 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 13 Jul 2024 18:26:00 -0000 https://status.ppro.dev/incident/359861#d50d85ff3a363123a35d9baa651890aa55fa6af9ec62144ced01aa593272e010 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sat, 13 Jul 2024 18:24:12 -0000 https://status.ppro.dev/incident/359861#f90861cf27ce4682b94d01e655d577c8daaf96e2b5ce2d1b70732bdff7999eab BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 13 Jul 2024 15:23:36 -0000 https://status.ppro.dev/incident/359861#df32923f97dc8be967087812246d984e833b681bc508f168f6b0911e098b341f BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sat, 13 Jul 2024 15:22:09 -0000 https://status.ppro.dev/incident/359861#76dbdaf2b439721719afe3b43a575871ed9be12720440769b8fd4d190f8acd87 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 13 Jul 2024 03:10:47 -0000 https://status.ppro.dev/incident/359861#02680e57c784012f4c6e765de10a8d7e1b093e28667454efb98f4f05a514811a BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sat, 13 Jul 2024 03:09:12 -0000 https://status.ppro.dev/incident/359861#d5add0fb7ea4aa1480478916b91fec93a7d0a2844c5ef0f0e1d7ee98432779a1 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 12 Jul 2024 23:11:42 -0000 https://status.ppro.dev/incident/359861#36858a1d5da40e514648bb8b2576c7ee513e410a061d6d7217cfba600dcf1b12 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 12 Jul 2024 23:08:10 -0000 https://status.ppro.dev/incident/359861#b8a233b4269df4ae29533560ec445a286915c3b2695ef42516f179863bfcbd6a BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Fri, 12 Jul 2024 18:09:47 -0000 https://status.ppro.dev/incident/359861#74e0c6733ad00476a9973e0da66ff259a97cd5ac64eb91544d94706ec81450ce BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Fri, 12 Jul 2024 18:08:00 -0000 https://status.ppro.dev/incident/359861#fe3e1c2fb59f0e1659c75987f7343352d409356ce2e344a5f8689be1a60d64e3 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 12 Jul 2024 15:07:14 -0000 https://status.ppro.dev/incident/359861#a098b4dc52af64a4d16c955c491725742167135bbbbe4d341250e037b7ec8a4d BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Fri, 12 Jul 2024 15:05:50 -0000 https://status.ppro.dev/incident/359861#f3d7235735245810890610b48edccc1c603687170237d4316c3f1ad2a6028503 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 12 Jul 2024 14:39:51 -0000 https://status.ppro.dev/incident/359861#8ed1e23830a52c6e6580dee7c84ad4fecd28ddd03fbcf976e833e956c89d750b BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Fri, 12 Jul 2024 14:32:27 -0000 https://status.ppro.dev/incident/359861#4b20cf796354f02f2516ece1adbac1a6f2fe7a6577bc20ffd97ab9c5abf07709 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Fri, 12 Jul 2024 11:27:46 -0000 https://status.ppro.dev/incident/359861#b3388a745c83ccd7253977dbdff4a8c998b5f0318d691a87c7adf7573fff2241 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Fri, 12 Jul 2024 05:40:57 -0000 https://status.ppro.dev/incident/359861#fe67ed4ce50448dac6fb07475d5a9cac5467f504f995356cf1a24d560101fa27 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 12 Jul 2024 03:28:42 -0000 https://status.ppro.dev/incident/359861#7d0606074d7889a08d07418b19e869ccc4dfbf7232a5f0ebd43b8c47490d3947 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 12 Jul 2024 00:10:54 -0000 https://status.ppro.dev/incident/359861#87a20ea0368be7a49cde1f0a9ce03908128c4fb919f092383ac5acf08518a19a BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Thu, 11 Jul 2024 18:19:32 -0000 https://status.ppro.dev/incident/359861#ef915c7f4463833ecd7d079cdf1a6bf72d7459ac55e536e37686088a6a3411b3 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Thu, 11 Jul 2024 18:18:02 -0000 https://status.ppro.dev/incident/359861#392443cd1cf3c56b3efaef4c21d47cc12870f858af5a38ba2fe7acfeb92aa862 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Thu, 11 Jul 2024 15:14:48 -0000 https://status.ppro.dev/incident/359861#ae1c8a9381656018f6702af36b1b371b65cd2eb1e0d870dd2d567a6bd1d0f489 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Thu, 11 Jul 2024 15:11:26 -0000 https://status.ppro.dev/incident/359861#e1a7752218b132319b6e6a83102550df81dbc08ade15b60f40e29dda20256d82 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Thu, 11 Jul 2024 13:28:13 -0000 https://status.ppro.dev/incident/359861#a992103d9a07b474029de8430cefc5044090b8154ba9c8c8aa70f18ee43aa84e BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Thu, 11 Jul 2024 13:26:43 -0000 https://status.ppro.dev/incident/359861#c93e655276e25ef3456a41679d361c3409bf729fa6eb5a618f9a5ca7e89fea80 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Thu, 11 Jul 2024 05:09:44 -0000 https://status.ppro.dev/incident/359861#3c5e0dba0b0799cfa77b245e7d32a7ff8cbf79fe7b0ecc798ca09da01075b83a BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Thu, 11 Jul 2024 03:18:09 -0000 https://status.ppro.dev/incident/359861#5d3cd8cd5f40255c863d0f50a11056e840998e23fd95db874260ca99307e8811 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Thu, 11 Jul 2024 00:22:28 -0000 https://status.ppro.dev/incident/359861#ee0f09e403ba031a9096615b122b904388761842a3cc2991023e62f789e40501 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Thu, 11 Jul 2024 00:20:58 -0000 https://status.ppro.dev/incident/359861#e11bac89b10b6a07d7c2d9d077f22144df8e083f33a84145970f9c62e570c619 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 10 Jul 2024 21:09:47 -0000 https://status.ppro.dev/incident/359861#0dbde270e8ef205b0b96e1a90c52cede75dcccc9e1f369244f718de56f707f7b BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 10 Jul 2024 21:08:10 -0000 https://status.ppro.dev/incident/359861#155f3151f24c57ff30faefe57a4c63eb5560387c3d31c241bf39e074a155b435 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 10 Jul 2024 18:27:34 -0000 https://status.ppro.dev/incident/359861#94b95fa7a1bf347c61bbf08ff5726d83e28452f4102139f7a6bfc0b33375f431 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 10 Jul 2024 18:26:01 -0000 https://status.ppro.dev/incident/359861#be836b39dbb775460f80caeae5ca153132f453e5b30ab97b18d30272b2672155 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 10 Jul 2024 15:29:23 -0000 https://status.ppro.dev/incident/359861#180dbd4ff2d88535f3fbbac41712ce320bc85e24a021cab0e41b659064f469ab BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 10 Jul 2024 15:22:08 -0000 https://status.ppro.dev/incident/359861#fe88f1d34b5fc0021c4988cb9bec13a2c9524b302511791726b8c778a4546d3d BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 10 Jul 2024 11:08:09 -0000 https://status.ppro.dev/incident/359861#4a9e4e388ce3a94a1f41e9a8a24f5e86eb97f41f7aacecc75590829dfe859f10 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 10 Jul 2024 11:06:45 -0000 https://status.ppro.dev/incident/359861#7f067c66b69a764e6c433d5d71d34560eee04cdab63afd658f094dd3bed36eec BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 10 Jul 2024 10:18:33 -0000 https://status.ppro.dev/incident/359861#afe2dd59435c8055fc0370fafbaa2169daf4baf36839dbe21f6e7106344b2b83 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 10 Jul 2024 10:13:58 -0000 https://status.ppro.dev/incident/359861#63161425c00450a097639b96e58f1b76cdc3cb3fcbb3cda38eecf1ce1646e7aa BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 10 Jul 2024 08:58:14 -0000 https://status.ppro.dev/incident/359861#c2a597577b741705864523594eaf02fca3178b6ec778703f5c854d278913503c BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 10 Jul 2024 08:55:47 -0000 https://status.ppro.dev/incident/359861#89c716bd93ba366582519cadd551347d7142b080e3a78198a8de5c2baeb3db76 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 10 Jul 2024 08:10:06 -0000 https://status.ppro.dev/incident/359861#0916b89494b1b9ae96f0527fd921035b76db91018af5f5db4316fbec52944ebf BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 10 Jul 2024 08:08:38 -0000 https://status.ppro.dev/incident/359861#d10f69e77a97ab18e487ed1fffc5ba9a8d01a287b385d4a0fe21ce5b80c5c1f4 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 10 Jul 2024 06:41:40 -0000 https://status.ppro.dev/incident/359861#f7b6dd9617ed75138f3c72ba308ed5ae81862fd2501ca39f3d56d4bdb6686a7a BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 10 Jul 2024 06:35:12 -0000 https://status.ppro.dev/incident/359861#1b743cfa6faebeb4c96420034a9d258f812f94e6c0b18de5fa1f855c3db2e183 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 10 Jul 2024 06:28:20 -0000 https://status.ppro.dev/incident/359861#a65fcb5c73af9d0fab0e7bb6ac1104038fe85563048f16878b10b860bc50ad2a BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 10 Jul 2024 06:24:23 -0000 https://status.ppro.dev/incident/359861#d093529d2eeaf6f279ff0a32ff0faa9026ee6b272fce19a1766af6f5074212a2 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 10 Jul 2024 00:06:27 -0000 https://status.ppro.dev/incident/359861#ac5e90824377690135e827ddcf920d6e7ee783e977739e46f41fa70494b1d42d BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 10 Jul 2024 00:04:56 -0000 https://status.ppro.dev/incident/359861#3da7d469c136cb3f5cba785ae0c1cd518e6321042dc1cb191fa2b3f75db136b9 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Tue, 09 Jul 2024 21:19:06 -0000 https://status.ppro.dev/incident/359861#927813061d30e79f123be5b19484a880c5a2050561546cdf082a246ac0ba87dd BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Tue, 09 Jul 2024 21:17:45 -0000 https://status.ppro.dev/incident/359861#dc029bf086fbf2a3c8fdcc130bd7f5aa666081bf14067b5db1cdb12485bde48b BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Tue, 09 Jul 2024 18:09:39 -0000 https://status.ppro.dev/incident/359861#404a2e9c38affeb1c928191f0454827290625c8bbb7dc0c9b9813044ff213705 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Tue, 09 Jul 2024 18:06:12 -0000 https://status.ppro.dev/incident/359861#b0f5e6a183ef4fd6e47cc82fdfa7b66ff97e69c5ae75c5e6df09c567c60a5e0b BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Tue, 09 Jul 2024 17:08:48 -0000 https://status.ppro.dev/incident/359861#87c4a7df54ff63019ee5e183994a62cc59ae726599dd163c59632db24d744c7b BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Tue, 09 Jul 2024 17:07:36 -0000 https://status.ppro.dev/incident/359861#5f998f4ab66d5a223d9407874c2fd4cab30f74a8e0c6d24ad95c987d5628180d BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Tue, 09 Jul 2024 15:45:11 -0000 https://status.ppro.dev/incident/359861#11454a56f6fb3024077ad1a2565a00c0a35032c61475890fc4b1977cd72a0a30 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Tue, 09 Jul 2024 15:13:50 -0000 https://status.ppro.dev/incident/359861#0d6b4faaf340c7757c95cd94d5e845400acf55dbeb3d1c8d119aba4bf7be88af BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Tue, 09 Jul 2024 14:22:14 -0000 https://status.ppro.dev/incident/359861#a3f5c0559f0f764e19e6a7dac5a41bba55f43d8df6c95cf36f098f18d0c0ac39 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Tue, 09 Jul 2024 14:20:36 -0000 https://status.ppro.dev/incident/359861#d26cef24e52ca3c44b134f1b804ac144276d044222972effcbee2667aab7fc6b BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Tue, 09 Jul 2024 12:36:10 -0000 https://status.ppro.dev/incident/359861#d720f8e2ce0273aaa3130f0bc0689463fbf050fc09858c160ce31ed6d979d9dc BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Tue, 09 Jul 2024 12:28:52 -0000 https://status.ppro.dev/incident/359861#4816a97d74fba8a0661af7a04fab6ef4ba92f283440d9e6961415f3307c02d6a BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 08 Jul 2024 22:00:40 -0000 https://status.ppro.dev/incident/359861#72e1b60cdcf1296ecd941b822b920d9fc90fc18aefd7ef5a54c5983a7ae6f9e6 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 08 Jul 2024 21:33:59 -0000 https://status.ppro.dev/incident/359861#e23fa20a5b86aba08d9b635dd8e40dea8bdac1850a6d4d8bac9658bd95de07d8 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 08 Jul 2024 18:43:05 -0000 https://status.ppro.dev/incident/359861#bffb3721f0547fbf36177b6c1cb4003803e0c75d95b2dc4060be2a9ee21f4e56 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 08 Jul 2024 18:41:32 -0000 https://status.ppro.dev/incident/359861#dab1fc2599b70296cb6399e1b83143b01ebcbb295427735192147de2521a5905 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 08 Jul 2024 15:59:56 -0000 https://status.ppro.dev/incident/359861#5c8a9ea2e9157b30f1849546efdf6b4e60d86ec3db7d76f31487e21d1b9eda5b BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 08 Jul 2024 15:23:36 -0000 https://status.ppro.dev/incident/359861#69fe5a145fc578f9c570b3fe9669d6b9172fbc8088744a4ecf25ecaaeac1eb88 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 08 Jul 2024 14:31:17 -0000 https://status.ppro.dev/incident/359861#110f794ee5771ce3a1056edd8da5df762108e0cef4b49b812b991d4b06bc6f46 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 08 Jul 2024 14:27:41 -0000 https://status.ppro.dev/incident/359861#ed90d04eba13e15aaa971a02a96e9747d1fbbcdbed995f3bac990c0f5427ad4f BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 08 Jul 2024 12:03:49 -0000 https://status.ppro.dev/incident/359861#e3d573fa638822ed6aa44359df3e59e3c0617b56173ee684f6f9dcfa9361aa17 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 08 Jul 2024 11:51:27 -0000 https://status.ppro.dev/incident/359861#d6715444d4ed2c715ac949ab066495dd54c69169f3b8179bd2e1a79cf1f37608 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 08 Jul 2024 03:05:47 -0000 https://status.ppro.dev/incident/359861#e7787277b12860d0ef8002886fb52e8f5aee7e6440ea1292ae02188c5d140950 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 08 Jul 2024 03:02:17 -0000 https://status.ppro.dev/incident/359861#624fcdf9266aa1d972c12a38c97cbcb246d8fd7c92f383fabad54527dd65b8d1 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 08 Jul 2024 00:35:07 -0000 https://status.ppro.dev/incident/359861#32f903d5e3ec8067a5824001420e459a9065f99f6f8b40c4528405a726a5e949 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 08 Jul 2024 00:33:30 -0000 https://status.ppro.dev/incident/359861#1ccc1bbd9c9bc9e5cfbcd5827a6da2caa08e99d1354a5a903a9a9d377ed94203 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sun, 07 Jul 2024 19:12:21 -0000 https://status.ppro.dev/incident/359861#eeecc6b5ce29ec1dbc5e0e528933949f514a0d61bda412c01371fdc50373e336 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sun, 07 Jul 2024 19:10:46 -0000 https://status.ppro.dev/incident/359861#a63ce53f5994088137036e6075614746aed37baf038dc9a382e1c287396b658e BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sun, 07 Jul 2024 17:15:00 -0000 https://status.ppro.dev/incident/359861#6062cae59bd897b51a04837b611bbe91adf8ae9ee3f006b7691d801a40850b1d BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sun, 07 Jul 2024 17:13:28 -0000 https://status.ppro.dev/incident/359861#a3343c6a7a6f0a984e811ed658777cc7a140680e0d7718c38b646666e4c4dade BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sun, 07 Jul 2024 02:12:06 -0000 https://status.ppro.dev/incident/359861#a3ae22d408d1d739749e51ac8c8080742e1a7252169949eb49f29bdc956ff320 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sun, 07 Jul 2024 01:10:32 -0000 https://status.ppro.dev/incident/359861#2130b29dcb2714455d9cf4e832fd17c063accb1f6f5b53d2078f48ab5239d052 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 06 Jul 2024 23:29:50 -0000 https://status.ppro.dev/incident/359861#0c935455cac1e07d05c51c27117bfef937380408aa78af8754585ee8dc35227b BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sat, 06 Jul 2024 23:28:19 -0000 https://status.ppro.dev/incident/359861#8c4000d9c63e3d22a37628f869f277224a152843cf2d1abb994d0d4a6778c687 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 06 Jul 2024 18:17:04 -0000 https://status.ppro.dev/incident/359861#90558b18b6884e399c53f04de5371cb28dbe545b172f06e84b4eda3012366d2d BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sat, 06 Jul 2024 18:15:38 -0000 https://status.ppro.dev/incident/359861#e4a4245cf1e4177c5d9ad0fb905ddf66bc2cf6d46f9bee9ae6ece19fc6e29f9f BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 06 Jul 2024 17:13:18 -0000 https://status.ppro.dev/incident/359861#5e8ec1fe062c743fc0fb85edbf3feac81fe57aa65e30b5e4864354b32948be95 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 06 Jul 2024 17:09:47 -0000 https://status.ppro.dev/incident/359861#bc69fc9ab1a6ac62c88f99529f9b4d4c1e8fa64b13a163ca6a6469a0035b4cc6 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sat, 06 Jul 2024 06:36:35 -0000 https://status.ppro.dev/incident/359861#13cc433f700450c07234ee368ade52f72d74cc14c7973f9156306a4e09aa0739 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sat, 06 Jul 2024 06:35:01 -0000 https://status.ppro.dev/incident/359861#42bd53da0d6cb7e65a5af126b559c557ee75c1e4ad9b2cdec5b12e8c504a5427 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 06 Jul 2024 06:19:22 -0000 https://status.ppro.dev/incident/359861#44460a30a55c551694fb28d0e9d466c019a588e0cbce28171d4e0e2564e74cab BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sat, 06 Jul 2024 06:17:53 -0000 https://status.ppro.dev/incident/359861#911197b20ff6b138abe8f4fd54fc584e0efca75037bcbf31b7fe8bdb8b6a2e74 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 06 Jul 2024 00:10:37 -0000 https://status.ppro.dev/incident/359861#3afca67b992e51d6d6164c777b90de2dd608b4b067ff97bfeb10dfd3f26bb3cf BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sat, 06 Jul 2024 00:08:55 -0000 https://status.ppro.dev/incident/359861#7f0c52420afba0bb7314df8c131fa3864398924b09236e4bfbbdef54df575fad BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 05 Jul 2024 21:21:45 -0000 https://status.ppro.dev/incident/359861#bf64a5fbfeab38f3e8ebf80b1e7b182e7a4d37882e479297043466544c1b616a BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 05 Jul 2024 21:18:15 -0000 https://status.ppro.dev/incident/359861#fcd97be8f0513f2f74af67296f6ad4ac43117619a147c894a36c760731bb543c BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Fri, 05 Jul 2024 18:23:34 -0000 https://status.ppro.dev/incident/359861#dc1acd435316998956013652ceaeb46dfc6902392d41f86bca24bf122bc84738 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 05 Jul 2024 18:20:16 -0000 https://status.ppro.dev/incident/359861#0ed678c3675faac32f7f90eeea1a2bb27f1a6c6abf33a9a1cf60284b6592b3cb BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Fri, 05 Jul 2024 14:27:46 -0000 https://status.ppro.dev/incident/359861#3396111c6693436806d75b400b02bc1d6e4147afd31b55fef46633450d3f4794 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Fri, 05 Jul 2024 14:26:15 -0000 https://status.ppro.dev/incident/359861#3296fdf808caefb9e132bf78c9e0fb1df748d2c1a54f3f9882edb4f0e5f4f159 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 05 Jul 2024 05:44:45 -0000 https://status.ppro.dev/incident/359861#b817872a4f4e61f3c28dde394faa96e1a92d2b41f1b2f173f9144431a67ae21e BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Fri, 05 Jul 2024 05:43:14 -0000 https://status.ppro.dev/incident/359861#687a3cf74b4203ecd56110c551820db3c117a870d415e31b7d04ee46ed03b742 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 05 Jul 2024 03:20:59 -0000 https://status.ppro.dev/incident/359861#3631b6276ed4c420c07a121b3c4ca6e54bda644b5980a1ee9109387e1b1dce9c BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 05 Jul 2024 03:17:33 -0000 https://status.ppro.dev/incident/359861#dc103fa5a956f0d87df991ad42c2408f1ce7182ce1e7fe211e796d6059921d53 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Thu, 04 Jul 2024 21:24:42 -0000 https://status.ppro.dev/incident/359861#430e7be65c125212e5fcc480602c353fbeedbbffc90dd3235c00692623428e64 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Thu, 04 Jul 2024 21:23:11 -0000 https://status.ppro.dev/incident/359861#e9f7c27c34b70eb4e5d635aa7012c25385dfcf34704d33e434070561334e7aed BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Thu, 04 Jul 2024 18:17:30 -0000 https://status.ppro.dev/incident/359861#ca46159cf75eebe774a12d87b4c6c80dfcc6f50d6baeb89e555e8c3ca4302d4f BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Thu, 04 Jul 2024 18:15:54 -0000 https://status.ppro.dev/incident/359861#28d19bc5169dc8e23076a2469328df51c559a0be79d7b0093519c38a06bd7355 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Thu, 04 Jul 2024 12:05:05 -0000 https://status.ppro.dev/incident/359861#a0fb121004dadb2c9839ff5928e29ba700db128d649cc9cf09c2006de2bbc84c BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Thu, 04 Jul 2024 11:57:46 -0000 https://status.ppro.dev/incident/359861#c7d6060df2096b142da8871de9e8d313d1df9a44fc5a603fde8ba72842a388fe BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Thu, 04 Jul 2024 09:26:31 -0000 https://status.ppro.dev/incident/359861#06a5b5e44421beaba2bc5dad02d1d248ca8d807cda2f4b2011cd87333dfc0c52 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Thu, 04 Jul 2024 09:19:22 -0000 https://status.ppro.dev/incident/359861#0e1f6d5584ad7607631ceace01482618c0ac758ec1f00be09979038bb48a02d3 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Thu, 04 Jul 2024 04:19:40 -0000 https://status.ppro.dev/incident/359861#58ae43e69b47013b4e104473b95a4f80c58dd922a4d359972bdc74686fed7824 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Thu, 04 Jul 2024 04:16:19 -0000 https://status.ppro.dev/incident/359861#3ecb7087e6fd5313dbd7d4c2f46f521db98cef95010fe25fb8524b2f6d04d989 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Thu, 04 Jul 2024 00:27:17 -0000 https://status.ppro.dev/incident/359861#46ab460996e37de8c4c598a8d38c03d95dfc28a28399163289771a91df93875b BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Thu, 04 Jul 2024 00:23:53 -0000 https://status.ppro.dev/incident/359861#22ccaa7e9b7758955f222fd54f898943a7d80127ad2a9dc88482b68170f4fc64 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 03 Jul 2024 18:15:45 -0000 https://status.ppro.dev/incident/359861#9b2f9f7994c8fecd1e953eaa07cde887f893b28e3cc1aa990523b9ebfc88bd31 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 03 Jul 2024 18:14:16 -0000 https://status.ppro.dev/incident/359861#7b5003e55fcdaf33226c560b01cf2a25ce184e8b36a3d6de1cc3f08205a2a14a BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 03 Jul 2024 15:33:19 -0000 https://status.ppro.dev/incident/359861#2ecc6ee816c30e7c5b73fddaa7f20cea4fac50d52660cd886496d141b1b0869a BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 03 Jul 2024 15:31:49 -0000 https://status.ppro.dev/incident/359861#087324a4af7d4ad7028ffd534ad444651b07a341def2682bb6a32b24d3621261 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 03 Jul 2024 00:37:56 -0000 https://status.ppro.dev/incident/359861#30ae503b3e4882d746352c15d797fae4827bae5629bd9bd93a871dcb0eeef068 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 03 Jul 2024 00:36:29 -0000 https://status.ppro.dev/incident/359861#c8a7726cca1d3197e7a89b1f2f65c744bdfac5601b2519f558832aa16c2534cd BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Tue, 02 Jul 2024 22:10:41 -0000 https://status.ppro.dev/incident/359861#be5fe466247518e7904e44604c21cf4d8ad931775be3f4e21a627f7beb7f5229 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Tue, 02 Jul 2024 22:09:02 -0000 https://status.ppro.dev/incident/359861#6c76ead8f1e57239120c1ccb46744c8322b979300b360920974c06ff117a7081 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Tue, 02 Jul 2024 21:16:19 -0000 https://status.ppro.dev/incident/359861#1691111cbbff9410b215d8e20d1251a7b38f957cefe0a70766569fa4f1e788d6 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Tue, 02 Jul 2024 05:53:13 -0000 https://status.ppro.dev/incident/359861#fc49005b9af0ecbca2daedaee3d29b6352734fe8843652a812dca9f9d56d5a92 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Tue, 02 Jul 2024 03:30:09 -0000 https://status.ppro.dev/incident/359861#785b4c583cb5794a38324a49d5e6faf54bd7cc91e7bfbca87db90fc51651bfb6 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 01 Jul 2024 21:22:25 -0000 https://status.ppro.dev/incident/359861#0d50ae3dcd4c407ec62174244696028492a50956e4c642a65ad924d7255ad92c BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 01 Jul 2024 18:43:34 -0000 https://status.ppro.dev/incident/359861#e4facc94c8f4da25b91a0beafff689e37d78890e65d281bb445664cfcfcb34fb BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 01 Jul 2024 18:40:02 -0000 https://status.ppro.dev/incident/359861#8c1865779d0a488efc5e7b99742d77c839883fdc369dc02275112bac6297744e BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 01 Jul 2024 04:12:20 -0000 https://status.ppro.dev/incident/359861#ae408283fd25b9aa2d37584b3f7058580226166b1b1aaee49e492f9a4e1201e9 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 01 Jul 2024 04:10:40 -0000 https://status.ppro.dev/incident/359861#0451ae230c7dfe39b0f0c283a4a3f1bc88d68a4d23fb1f3afc12c6eb78c4d26a BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 01 Jul 2024 00:14:51 -0000 https://status.ppro.dev/incident/359861#84fa4b4f4a401ecb02a05cfa91d668ab7a865b6c2cd19f9b371f51a610309655 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 01 Jul 2024 00:13:32 -0000 https://status.ppro.dev/incident/359861#f4cb589c2e653ddbe01e44c7834c016691560aeef63ce3daee7d4ae4fed2f2a3 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sun, 30 Jun 2024 19:45:33 -0000 https://status.ppro.dev/incident/359861#a840754009472772c936f478f89c8251be8a6ca7e7f20e853ec7257f588b83d4 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sun, 30 Jun 2024 19:42:09 -0000 https://status.ppro.dev/incident/359861#f51541a04fd37d3afd9a4607bd1ecf09173cee51aef4e7c55f5b665c6173364e BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sun, 30 Jun 2024 17:19:43 -0000 https://status.ppro.dev/incident/359861#2dca468e02555f5cd3e92c0ca0c4f55eea62157a20aa2bb6781658acb1150572 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sun, 30 Jun 2024 17:18:13 -0000 https://status.ppro.dev/incident/359861#9ff41abc471887808307d3207214c7340cd7ab77a09e48fd3dd7f761193f2e44 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sun, 30 Jun 2024 13:16:45 -0000 https://status.ppro.dev/incident/359861#121bc6bed82f03f6823714edfa2cb3248a6507f237b74bb0442ce9145659ed64 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sun, 30 Jun 2024 13:15:11 -0000 https://status.ppro.dev/incident/359861#bde891ee5e261358f738a07139c193172ae9cbf92b68027fcdca9f4f999b4180 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sun, 30 Jun 2024 11:22:48 -0000 https://status.ppro.dev/incident/359861#4cd4c6267324ed48051dd10071b9e6c827c2ff98e6dc478b96e264cddefa404b BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sun, 30 Jun 2024 11:19:18 -0000 https://status.ppro.dev/incident/359861#c87309895c3ac636a3826cc1dc3c90235ff211eb02ab8e7c11ad93c7409efc55 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sun, 30 Jun 2024 07:15:05 -0000 https://status.ppro.dev/incident/359861#a326ca5da8ff239ba67f31b65f8b494411b9a7b7727fe9289e9f8c885b0ec0cc BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sun, 30 Jun 2024 07:11:58 -0000 https://status.ppro.dev/incident/359861#58beb9c8e7d508177a98f605ec0098710629252d2084dfe1ac3f03d054aa617b BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sun, 30 Jun 2024 05:39:13 -0000 https://status.ppro.dev/incident/359861#9fbdb498ff7e8e6dfd49c5780a7bc506e71729d7729416b20034c8e610780119 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sun, 30 Jun 2024 05:37:46 -0000 https://status.ppro.dev/incident/359861#654bf6fa994392caf57de4f9fbb78619ce8d3c982458bdd143497b8c49f5180c BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sun, 30 Jun 2024 01:11:08 -0000 https://status.ppro.dev/incident/359861#e77fb5a4b74f3a3dc7b3f1494ec69efd082fc1f9c0af0548081934d1c40ed260 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sun, 30 Jun 2024 01:09:49 -0000 https://status.ppro.dev/incident/359861#96f23057787aa6e78b740993d1566043ffa5d56a7837710b012af73616f893de BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 29 Jun 2024 23:13:55 -0000 https://status.ppro.dev/incident/359861#680581cb7bc1e98d70df6ab51754282f7c45a9385c30abadbb5bc891e7253096 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sat, 29 Jun 2024 23:12:21 -0000 https://status.ppro.dev/incident/359861#cc565eaaf22cc25f97fb594d2c23498090ccaaef6f77da99508738150c275144 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 29 Jun 2024 18:14:24 -0000 https://status.ppro.dev/incident/359861#d9f09c0bba598e39e5c0fce66538b72fe45e66defee3a3a9bad047a3e535740f BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 29 Jun 2024 18:10:55 -0000 https://status.ppro.dev/incident/359861#3d67efb9b6a466f2cbe60574af74bdb9574a279bc61d4ae5c22fae6683fd2b79 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sat, 29 Jun 2024 15:13:39 -0000 https://status.ppro.dev/incident/359861#7e5801d16c8403894f6e23877b16dd48165f26a1fc33f0e743028b3da7e9a49a BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sat, 29 Jun 2024 15:12:05 -0000 https://status.ppro.dev/incident/359861#b9401c39b60f65cd7178a2171ab86b9e3b766261105d233e8bb9a40a3a7c2c12 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 29 Jun 2024 13:24:23 -0000 https://status.ppro.dev/incident/359861#272f1a7851ed684d35b6540f860ca478867755ef16cacc921362dcf21dfce8b0 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 29 Jun 2024 13:12:05 -0000 https://status.ppro.dev/incident/359861#94b7039d582c27274342d796eabce1f07120b77c36f7e241e97c35b0493a6abd BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 29 Jun 2024 13:04:22 -0000 https://status.ppro.dev/incident/359861#0a74e5f6f44e5db1dccd91ac249fab1f08b0ef5a4ccf9e9a86321adabb24a957 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 29 Jun 2024 12:22:06 -0000 https://status.ppro.dev/incident/359861#b7ebd9da187e630406ee182ae447ce46d4839391aeec0c5b90ae815f84746137 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 29 Jun 2024 11:59:23 -0000 https://status.ppro.dev/incident/359861#5aa9a8242152f089f75a861ed47b3ac540a22ff79fbf311d91a25d3b03d70cd6 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 29 Jun 2024 10:52:10 -0000 https://status.ppro.dev/incident/359861#26581059c6ef7117331ff192dc6c8f9a29c11be3da4c01f95aa9978820bbf13e BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 29 Jun 2024 10:14:18 -0000 https://status.ppro.dev/incident/359861#6d76898e4ee5f92ab576a5d01d399d901643a53dc6b679384d5e8e3328453cb3 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 29 Jun 2024 09:32:02 -0000 https://status.ppro.dev/incident/359861#27ea407067fc805cb98b48eb32baeca43246042bf50b32f6f653b911ed8ce289 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 29 Jun 2024 09:15:54 -0000 https://status.ppro.dev/incident/359861#cdc4af499bab35aa3dea67a135386eca86ec6a9d25e94cdc04b0de18bcd0cc8e BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sat, 29 Jun 2024 09:14:15 -0000 https://status.ppro.dev/incident/359861#abe48b33ed6c139cc4eaa111ea7e740034b055b7e4b4db91ef17a7bf5bb083f9 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 29 Jun 2024 06:23:28 -0000 https://status.ppro.dev/incident/359861#3b9f29598d7ca4b5e553ea418baadc26610aa419dab1741d063be0193ef7e3d4 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sat, 29 Jun 2024 06:22:09 -0000 https://status.ppro.dev/incident/359861#1e05d2bd2b44a786c1f8c23a38b4bad8d2e3671cf3849e8a93a59e630f5b1058 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 28 Jun 2024 15:14:50 -0000 https://status.ppro.dev/incident/359861#06a9834f160f300b6028baad9430549af900afe08dd4fc144559842fefc305ba BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Fri, 28 Jun 2024 15:13:21 -0000 https://status.ppro.dev/incident/359861#c411c7c44a1e1dca11d338e6b57acea81652078c6acdf123436c9f0c992732d6 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 28 Jun 2024 13:42:42 -0000 https://status.ppro.dev/incident/359861#8a8631417fdb5f1612e7fb7321889113a7244b26f86bc97fb75747d687d3937b BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Fri, 28 Jun 2024 13:41:02 -0000 https://status.ppro.dev/incident/359861#571511675923c11c3662432b26c11003b5171086448ac374d8026022d3a06a13 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 28 Jun 2024 12:34:59 -0000 https://status.ppro.dev/incident/359861#0a4b7296c35f2d25cd39c7e7589a4646fb6fe24ffb0c0df31264d8849cb7fcbb BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Fri, 28 Jun 2024 12:33:22 -0000 https://status.ppro.dev/incident/359861#5ea407aebd130613386069b563ded871dd125b3595abaa617dda340d67ecb92a BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 28 Jun 2024 12:27:37 -0000 https://status.ppro.dev/incident/359861#abd739cd3b424b54e476ee44638ebc74fc1abba604086d7a7c1d02720831ad15 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Fri, 28 Jun 2024 12:25:59 -0000 https://status.ppro.dev/incident/359861#96b1710a4c727c4942df7b0f2ba658f27b4b1676d65329bb5fe25d332ef64b61 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 28 Jun 2024 05:44:12 -0000 https://status.ppro.dev/incident/359861#d31ec542b289a9cb08ca0b327fc4d323be3c20cf3f8d9b8faacaa515ee3d0db9 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Fri, 28 Jun 2024 05:42:40 -0000 https://status.ppro.dev/incident/359861#73861d75f688d41ddb39a46ec7e7c89e4eae7c0ef360287d007432fcdeb79b0a BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 28 Jun 2024 03:46:57 -0000 https://status.ppro.dev/incident/359861#0296f04b02c4c31da461f6d95267bf065f0234602d965656bd81397f337fc856 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Fri, 28 Jun 2024 03:45:23 -0000 https://status.ppro.dev/incident/359861#22f58a0c27c7b79308e2c543729b7ba3152442491fff70059d35e9154e5027c6 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Thu, 27 Jun 2024 03:43:46 -0000 https://status.ppro.dev/incident/359861#9509ba3179bfc7f5fba3770c0701816867033b26557ce2f78d0a818ff8594f9e BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Thu, 27 Jun 2024 03:42:05 -0000 https://status.ppro.dev/incident/359861#56bddb10a64201d19f5f30759b3a6e7611670da8e2878a004c6248f7d4218753 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Thu, 27 Jun 2024 00:25:53 -0000 https://status.ppro.dev/incident/359861#17a39b5a2a5927077482590c2eb6903afd02ca76946a5b47779f481066e94055 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Thu, 27 Jun 2024 00:24:22 -0000 https://status.ppro.dev/incident/359861#35d36e3d09001bac9401c847ccf67be208381f9f4a30a7045b43a9dac8657198 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 26 Jun 2024 05:35:38 -0000 https://status.ppro.dev/incident/359861#36da5869b12ffc936dcbafa6f38f9b6c00dea8752f0575964101ac2c9753ee84 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 26 Jun 2024 05:28:18 -0000 https://status.ppro.dev/incident/359861#8bb7f8dbb3d5edda1ddc6b55fdbcbf0c71896a5352ed10cbe7e5374e4f9ae5f7 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 26 Jun 2024 00:22:12 -0000 https://status.ppro.dev/incident/359861#2a868826290359c495e66b5658633e0eba313723f32f478251db9b7c58b7f88e BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 26 Jun 2024 00:20:36 -0000 https://status.ppro.dev/incident/359861#a06d2d2d9ef8b80150870327157e24ccd2c0d390ace04b4ce35e639b8f0a6322 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Tue, 25 Jun 2024 21:19:58 -0000 https://status.ppro.dev/incident/359861#dbf387b28b9fd20645323c22f486195b453aa84fb85094202c72e1fff7e15ee8 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Tue, 25 Jun 2024 21:18:16 -0000 https://status.ppro.dev/incident/359861#71f86d499a4e6a36045a60888b37c48da04a806089fdac8e4004935cf9eb5371 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Tue, 25 Jun 2024 17:04:43 -0000 https://status.ppro.dev/incident/359861#767b642af5b3e9f5a48fbb3d62a12df6eaf388b42c634205bcf04a248a7e3196 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Tue, 25 Jun 2024 16:57:17 -0000 https://status.ppro.dev/incident/359861#dd16f36f0f2e3db794dd94a21e61e6d9f545c82556c56387a5140c04b1585077 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Tue, 25 Jun 2024 16:06:02 -0000 https://status.ppro.dev/incident/359861#74525fff2cc5d1be422d413fb7c1d6530a6ac3a9eb7e4165026049bd9cdb70c3 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Tue, 25 Jun 2024 16:04:31 -0000 https://status.ppro.dev/incident/359861#6d882865795e059f2d81221aef07ce380ba24ea56daa341620d52e30030db90e BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Tue, 25 Jun 2024 14:26:28 -0000 https://status.ppro.dev/incident/359861#af2978d4d7c247963f2c24236406777579f5088df79b7cbf1795947a8f873c23 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Tue, 25 Jun 2024 14:24:49 -0000 https://status.ppro.dev/incident/359861#845af38c1b32784212c754a8590a621e719dacf0f2973e2a31d0ff0850d4a7d9 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Tue, 25 Jun 2024 08:46:32 -0000 https://status.ppro.dev/incident/359861#f619af185e847404a8a9c09c2a619f78a1af98b781093bf31ba95c15fc219521 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Tue, 25 Jun 2024 08:38:38 -0000 https://status.ppro.dev/incident/359861#6a4c1f4aa174e24dea9d288cc13d1dd76152df31bed0789ee2254cff5db4351c BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Tue, 25 Jun 2024 05:37:12 -0000 https://status.ppro.dev/incident/359861#c5e39245d4cbb9817ff9189102dbaee40714e9ad497a225603540635c2844de4 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Tue, 25 Jun 2024 05:35:39 -0000 https://status.ppro.dev/incident/359861#03b77eec4ca0143b985b3f2c64872c97a67dc2a5158a6453544e31ce4abfc9c8 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Tue, 25 Jun 2024 03:19:24 -0000 https://status.ppro.dev/incident/359861#399bd4c077a7c950bb6fabb05da66cadc48b2267c85192b43a7c9b01b0f23d9b BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Tue, 25 Jun 2024 03:17:56 -0000 https://status.ppro.dev/incident/359861#d5ff9cee150ea94313e428af011f677a71746a06d6d0497df2963493d19a828b BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 24 Jun 2024 21:41:43 -0000 https://status.ppro.dev/incident/359861#ffae5ff689e5a5383856250dd44cd75f64cc10b2fbf0ced852e17ceb15277793 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 24 Jun 2024 21:40:15 -0000 https://status.ppro.dev/incident/359861#6b1d90d112435ae0c6fff05479cd2f84112a18acbab58712ed0eadc3bd5e12d7 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 24 Jun 2024 18:19:21 -0000 https://status.ppro.dev/incident/359861#959cffdcc806ad90429580358a2e6e11035ac57cc2d92714db7cf91e3bf3c989 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 24 Jun 2024 18:17:51 -0000 https://status.ppro.dev/incident/359861#9fb2bb747fbabfca8c2e582ba584dce0def8aae8da078634b6341ce947ec10c4 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 24 Jun 2024 15:15:58 -0000 https://status.ppro.dev/incident/359861#a94ff990b4f71768853cfb02e25315f0c873fc9ce833eac0fde3c2b5e16f3d1f BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 24 Jun 2024 15:14:32 -0000 https://status.ppro.dev/incident/359861#c5cdbcfb4cceef2bda68c67789686f1f3b3da46be2f2e3a16bd3cb045044072c BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 24 Jun 2024 14:22:19 -0000 https://status.ppro.dev/incident/359861#bd12871bcd4718fb996cf92bf16bef8aa10ae6a4d43d05293cd2ec32458d1872 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 24 Jun 2024 14:18:58 -0000 https://status.ppro.dev/incident/359861#5ddcc179d66e06d042e2669dafff1133decb92994c8482a9f88e0577cf3f5c99 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sun, 23 Jun 2024 03:24:40 -0000 https://status.ppro.dev/incident/359861#8ac8610008bf814e88e451ed9cb5cee80138264d7d3991e0c2e12dac4158bc1b BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sun, 23 Jun 2024 03:23:05 -0000 https://status.ppro.dev/incident/359861#07b6542759d8a735705ea2086a451ab911cb6fb13d420c8e19c332cb5cf0765c BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sun, 23 Jun 2024 03:02:23 -0000 https://status.ppro.dev/incident/359861#6b52ec186e8d88fa2b5186e67c153d78f256e6948420c85d7506cd5d1505cfb2 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sun, 23 Jun 2024 03:00:53 -0000 https://status.ppro.dev/incident/359861#341e91c546f06ee4d4f293cec64d583c54b4ec6400d35dfbc8581db16630902c BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Thu, 20 Jun 2024 07:33:15 -0000 https://status.ppro.dev/incident/359861#925939a0e838ba40e8f6be8e022bd5cb68d999a909cdb24e1921e49b0b919c8d BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Thu, 20 Jun 2024 02:04:52 -0000 https://status.ppro.dev/incident/359861#204ddd5f45c11bbbfe3d12d4a8525cbaf11eae1df77f661fcccf8ec4e6b8a677 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 19 Jun 2024 21:18:31 -0000 https://status.ppro.dev/incident/359861#2522f7f692416ee30f4b01d597ff8608a806b0794cd3caf39274e1f9f1595a5e BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 19 Jun 2024 21:17:19 -0000 https://status.ppro.dev/incident/359861#94ebf599d068433892e1d7e49911c12119a4107733675c0cfe66b41c28f7dcaf BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 19 Jun 2024 19:31:19 -0000 https://status.ppro.dev/incident/359861#f626ac691b1ba96a939246a129bcc66c298295b364d9e6c0fbe0c0978d919d6e BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 19 Jun 2024 19:29:54 -0000 https://status.ppro.dev/incident/359861#095590fb091bd4506541a9a6ca8bc9661354703b360ab7d9f0080e33d0b05ff2 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 19 Jun 2024 18:48:58 -0000 https://status.ppro.dev/incident/359861#d3e693c1b1df77415d3974c5b3d7e7c17b55902cc1754ca5872ffd922f71d213 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 19 Jun 2024 18:36:28 -0000 https://status.ppro.dev/incident/359861#65353accca3fce833e8bcb93db5c0eff63680a76d46bd3a3cc6a077c133c3b7b BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 19 Jun 2024 18:23:40 -0000 https://status.ppro.dev/incident/359861#4366f64cb7d0d62827abe8cf9e61f431658d00613f3c7d1e47e7eb61245625c0 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 19 Jun 2024 18:22:30 -0000 https://status.ppro.dev/incident/359861#5e0919f8415a665bd051658c70f6b2f807daff740a32db9c2e3752d39cd3cc1b BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 19 Jun 2024 18:05:56 -0000 https://status.ppro.dev/incident/359861#cb3a55b9b807618dac79076ee5c42b6882c22f52961aaa8eb1ba093dafa99af9 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 19 Jun 2024 17:54:20 -0000 https://status.ppro.dev/incident/359861#6aa4bfe826889a149de3769d0207e021791394d712dd72c2ea1946b1fecc8535 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 19 Jun 2024 15:23:44 -0000 https://status.ppro.dev/incident/359861#058226a4e533f1ccb242e3e7a5b11c0f3c682d8f63968d09fd0c636aece7834b BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 19 Jun 2024 14:56:23 -0000 https://status.ppro.dev/incident/359861#de6c7e3eb3007f896f10b40084927baba531b434dc39ebde15ecfbcf18901c6c BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 19 Jun 2024 14:13:35 -0000 https://status.ppro.dev/incident/359861#cf393db6726983bd4596cc8bd70a0f9c4433e62bc0ff8bf934dacf8213f4d886 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 19 Jun 2024 13:56:17 -0000 https://status.ppro.dev/incident/359861#a47223fd46f522bbc954cd609840de5f19013987a1e6ec441c3a9acd1f7b25e8 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 19 Jun 2024 13:07:28 -0000 https://status.ppro.dev/incident/359861#f54b8b954494e49153a398692dd48e44f91ff0225a0af44d62edbea1b5466e43 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 19 Jun 2024 12:54:47 -0000 https://status.ppro.dev/incident/359861#fe1afd127234664c46cc66ea358723997c37f5bf8f6bacf4987bace2a963a330 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 19 Jun 2024 12:22:23 -0000 https://status.ppro.dev/incident/359861#de41097cec1966d26b99f16490d855533b04901bbebd48dcd2c6fedf23995389 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 19 Jun 2024 11:59:52 -0000 https://status.ppro.dev/incident/359861#63b3d5b1e5922205f4cd94873fc3cf4d4953390c56d8baaf2cba677959470453 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 19 Jun 2024 05:08:05 -0000 https://status.ppro.dev/incident/359861#30e63a8bd024b208db2b622d7d52be90686b3e91d7ea9faed824e51b580226c1 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 19 Jun 2024 05:06:31 -0000 https://status.ppro.dev/incident/359861#6e75d64b93d71748b79ee8e3b28264c66af412d71778c715b110c08fcdb9e639 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 19 Jun 2024 03:18:43 -0000 https://status.ppro.dev/incident/359861#b9c8e9c1e90ead27a0b411dd87fde6097f11fb5ad03c5369dd367cfb91c66f29 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 19 Jun 2024 03:15:49 -0000 https://status.ppro.dev/incident/359861#336a3107c4924037fad6bc835d3f1146ff7667950acddd0557ee76f6c841d1ec BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 19 Jun 2024 02:06:39 -0000 https://status.ppro.dev/incident/359861#9de426014678c6da0f67cdb7a52638b8daeed4060eb09d3e097f11568b174f07 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 19 Jun 2024 01:58:23 -0000 https://status.ppro.dev/incident/359861#7b7433a7d3753b17a23239321f45fd52774f3b95e26e62b5dfdfbe914dc65f81 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 19 Jun 2024 01:50:19 -0000 https://status.ppro.dev/incident/359861#16332359ea7c913c917496a4923298724158f167702b8d4903057e8c89001d6b BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 19 Jun 2024 01:44:20 -0000 https://status.ppro.dev/incident/359861#f17f18a0afa5a7c4d48f24187745523e883055f8a6f278677b0ed36ba8dd998a BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 19 Jun 2024 00:51:37 -0000 https://status.ppro.dev/incident/359861#4c5468ddb1752ad9a1f6305109d8f1a9663646fccc751e84227438d8b2254b2e BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 19 Jun 2024 00:39:20 -0000 https://status.ppro.dev/incident/359861#996b4a9a98c4e4c2f6a945c55b5e38002eb22cb279935bd0ee1cb10e5c88f502 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Tue, 18 Jun 2024 23:16:48 -0000 https://status.ppro.dev/incident/359861#eb8ecb166dd0cd16d11fc1a9472185ea10549bfd857daeca681b90fe7292f486 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Tue, 18 Jun 2024 22:34:20 -0000 https://status.ppro.dev/incident/359861#8bedc77ddb008ab58b8562c0d0c0371ec952e5ec7ad3692757c12fa273f6c3b4 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Tue, 18 Jun 2024 15:57:41 -0000 https://status.ppro.dev/incident/359861#0622b7e03fce036385d962bbe77b24b796fe7d9f828fa60b3dabf0d40065d9e2 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Tue, 18 Jun 2024 14:59:25 -0000 https://status.ppro.dev/incident/359861#2c44600ea20440a43f59408107c50363f3a043f60378e8f36115967a0223dffe BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Tue, 18 Jun 2024 14:14:22 -0000 https://status.ppro.dev/incident/359861#6fea1cfb09f026c811e097dd19417be365c19af88129c2331c13ddc3cd05da5f BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Tue, 18 Jun 2024 14:06:42 -0000 https://status.ppro.dev/incident/359861#7c802b9b94dcd0096ba1658e8d99490f8f3d697988c433b9fa1ee644c7ee8163 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Tue, 18 Jun 2024 13:24:46 -0000 https://status.ppro.dev/incident/359861#a7e440ed7c1d34663447c9ded67afe0037d3bde513a4a8895ce4081070b327cc BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Tue, 18 Jun 2024 13:16:34 -0000 https://status.ppro.dev/incident/359861#bf74548b490cfc11e0641854ae01899b4f394cf800d1a8738da754d5fa7e40ab BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Tue, 18 Jun 2024 06:43:39 -0000 https://status.ppro.dev/incident/359861#525eeec60706a149ca73de215e794df2d3908a4eaa6bb45e3948143468b1f747 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Tue, 18 Jun 2024 06:42:16 -0000 https://status.ppro.dev/incident/359861#14bbaf1338f25deedbc2a0fef6ff90ee86d2cc4f940f57ac8262add5e9bad878 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Tue, 18 Jun 2024 06:36:36 -0000 https://status.ppro.dev/incident/359861#cb6d4dd5cd8dc4d737ac9289eb73ded44d961f51aedc94a7770553dd113cb122 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Tue, 18 Jun 2024 06:35:07 -0000 https://status.ppro.dev/incident/359861#a17cc57ef96e4214d5179a59214e61f9651f9b0945a4c14c14fc1d58df135a21 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Tue, 18 Jun 2024 05:57:07 -0000 https://status.ppro.dev/incident/359861#44619a427484ee0c3522c70c55347acdb50da679c038a1510789c94836d899f3 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Tue, 18 Jun 2024 05:53:35 -0000 https://status.ppro.dev/incident/359861#e89554e27fa1d9e0afe6f88ba9fda75e5a4b055aa7d9a7992183715971d2a87b BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Tue, 18 Jun 2024 05:21:30 -0000 https://status.ppro.dev/incident/359861#f79d1320792a352f1a88234813f1dcd3324bf79e9cebbf88b98f6c45a091d292 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Tue, 18 Jun 2024 05:19:55 -0000 https://status.ppro.dev/incident/359861#ca5de96463ee39b0c45f363cfcd94f8a23900417cb7359ae1630d8a20afd63f4 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 17 Jun 2024 23:08:32 -0000 https://status.ppro.dev/incident/359861#9d457c1e43e5a73e86a538814971fa1a7e661ad650ebac3023a0f7295e4990f4 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 17 Jun 2024 23:07:05 -0000 https://status.ppro.dev/incident/359861#273b40f9d0da8407fb203a3ae05b663dd13ecb06e1b921f39ce7b40da84a3e2c BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 17 Jun 2024 21:16:25 -0000 https://status.ppro.dev/incident/359861#5032269f4ed77e141f01a1e91c7d9a90897903d759917082a34c51920ee004b0 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 17 Jun 2024 21:14:49 -0000 https://status.ppro.dev/incident/359861#69bb0b119f232f513c749b9a028787e3bd465b7f68a32880631ad245d230ce55 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 17 Jun 2024 17:33:38 -0000 https://status.ppro.dev/incident/359861#873905cd61dab2fbc62b377e34927a49f60b180fd1380d1446f228fb640a5456 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 17 Jun 2024 17:32:02 -0000 https://status.ppro.dev/incident/359861#b8655e31e4fb66f2971e37c87a2b252300f54019e37c16264aa2ec2ee218df2f BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 17 Jun 2024 17:25:46 -0000 https://status.ppro.dev/incident/359861#1e29f700354fd591bea058a8221326f2f19e52631a07220fea6e3bf487804e48 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 17 Jun 2024 17:14:25 -0000 https://status.ppro.dev/incident/359861#bf1e0251eb3a450cc82a0c389cb5243d3be63d9ac54f208ec26786e2cf1cc625 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 17 Jun 2024 17:13:41 -0000 https://status.ppro.dev/incident/359861#dbb56ef660a19bc16be9944554cf8f2651e0c8001c8d2d48c713af41f2495351 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 17 Jun 2024 16:56:22 -0000 https://status.ppro.dev/incident/359861#7336e4ba26557249f3be0f1846d6f0ced467b49e9d4b76c945d5bedfd4e77b00 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sat, 15 Jun 2024 17:15:15 -0000 https://status.ppro.dev/incident/359861#0726fc51b33ab81f7e226a143e1f181cc8e5aee145cdc0ea33d37abb70631d17 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 15 Jun 2024 17:07:58 -0000 https://status.ppro.dev/incident/359861#431c7fa431eafb0870db58e80b0c185f7b3c1cf4675a3a2be88fa4decc8c7a8c BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 15 Jun 2024 09:09:52 -0000 https://status.ppro.dev/incident/359861#3c031992b60263b1b488a3200c6637b80dffe37d0af416a9c1668a5c6f24d6e9 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 15 Jun 2024 09:02:44 -0000 https://status.ppro.dev/incident/359861#4f67039c488ecf4dd955a7c12c18df21996bbf6a3d9eb3392457e6f21a8245d4 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 14 Jun 2024 17:26:25 -0000 https://status.ppro.dev/incident/359861#468fd5a171d0f156851a0d1d2fa8469743ca03ae3e392fcecb4bd8f89aa0fc50 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Fri, 14 Jun 2024 17:24:53 -0000 https://status.ppro.dev/incident/359861#4b29e337e31640edfe7dc8c12c999b0bd664c3ea44b3dff4870dcec6b3ed89e8 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 14 Jun 2024 15:33:26 -0000 https://status.ppro.dev/incident/359861#abbbafab4a58b55425c9b3f70a92aedc809e8b9d53a707c88698797760b7f100 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Fri, 14 Jun 2024 15:32:02 -0000 https://status.ppro.dev/incident/359861#0037dd5bd89e4858bea320b795701150534ab893fb07aeccfa4c892e15f221f8 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 14 Jun 2024 15:29:16 -0000 https://status.ppro.dev/incident/359861#4c439a35104997a020d82eaeeba4c79376d8be8352b9da834ba1847ccd8e5420 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 14 Jun 2024 15:21:56 -0000 https://status.ppro.dev/incident/359861#af0e973c862e142c5bb862835986017e179bb5aae021fe98d2db072a59908233 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 14 Jun 2024 02:27:40 -0000 https://status.ppro.dev/incident/359861#03d3d77437f0b1ec9136ebe5fc3e7eec621ab87f0ad23668b0932bf5ef8e6ebc BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 14 Jun 2024 02:10:09 -0000 https://status.ppro.dev/incident/359861#ab50528d9d21549de5664e79d49062078598cca4826e75432bc39a627736dd62 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Thu, 13 Jun 2024 06:47:44 -0000 https://status.ppro.dev/incident/359861#9c14d7fd0479e80e0e87c513a4516d39e3c9f1c08518d62dc8b2f8254ec8427e BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Thu, 13 Jun 2024 06:13:53 -0000 https://status.ppro.dev/incident/359861#079f7518e0bcc94e6660571b606901af7cba7d223363821e40a5a57a4edd2faf BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Thu, 13 Jun 2024 06:09:29 -0000 https://status.ppro.dev/incident/359861#fa07dba74c72ee9dc7d6a8c3257fa4297fbe08b4045ab7e7c368a941f54e8d35 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Thu, 13 Jun 2024 06:00:59 -0000 https://status.ppro.dev/incident/359861#8439864a17dcf4d5e2f0b02079fafb3c135f8daa553cf1c2555d918f39275288 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Thu, 13 Jun 2024 02:43:48 -0000 https://status.ppro.dev/incident/359861#6d961e0b1f9df61029ae29d37cfad682ab4e847e12dd20227310167f64768166 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Thu, 13 Jun 2024 02:16:01 -0000 https://status.ppro.dev/incident/359861#4624275d5cf45678ff57aab74b3a194b6f4d0676937888f3a32b7cafce1e0f5b BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Thu, 13 Jun 2024 01:58:40 -0000 https://status.ppro.dev/incident/359861#0e68824da8e98182983adee835ea509f0c581a5f9ff973357bf4c0d819ed53c3 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Thu, 13 Jun 2024 01:36:00 -0000 https://status.ppro.dev/incident/359861#ab5289773a96cc6d6c892cd04a6d952a06b115002de42ae8e19190c9990a33b5 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Thu, 13 Jun 2024 00:38:38 -0000 https://status.ppro.dev/incident/359861#e347db957ee33175999ff69b662564e8282c2698a4df9e403c936e8edbf99b74 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Thu, 13 Jun 2024 00:37:03 -0000 https://status.ppro.dev/incident/359861#2e02e3ecce1af693f5ffb48257667aec7c23964b01f706e8db24630ffd88a264 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Thu, 13 Jun 2024 00:14:27 -0000 https://status.ppro.dev/incident/359861#da14f62b31c7b73cfc20f45976cb35a03b6756ac801bed5f14b51c25073bc802 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 12 Jun 2024 23:51:23 -0000 https://status.ppro.dev/incident/359861#e9c1b2db56e6c790229b4ba6a1656341d98f09df4f532e6591d14ea724d6a685 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 12 Jun 2024 18:47:18 -0000 https://status.ppro.dev/incident/359861#f86397bffc83c3aaa22060b806afdb22127c169eec23b7d27b7d083cc5842694 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 12 Jun 2024 18:43:38 -0000 https://status.ppro.dev/incident/359861#eefffc53bc04087eb5f28845db1f15100e872ad31b28c5f6d851ac75b628feba BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 12 Jun 2024 18:31:28 -0000 https://status.ppro.dev/incident/359861#d820bd3bd5bcc57d117d3e0d300f7b23b818c7d4b54c1d71336e4b19be613d02 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 12 Jun 2024 18:28:47 -0000 https://status.ppro.dev/incident/359861#77fbb3a56e54c381b3aa4acf4aad39442f7295fa319aac23951e0a05903cfefe BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 12 Jun 2024 18:24:58 -0000 https://status.ppro.dev/incident/359861#e245202907798ac53915c224ff1de72628647b3aae581eacb82b60d5b485e65b BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 12 Jun 2024 18:16:00 -0000 https://status.ppro.dev/incident/359861#269baaa7674bc656900dacf1ae1ab12dfd1290fe8ebbfefd4caa6467883a991b BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 12 Jun 2024 16:17:21 -0000 https://status.ppro.dev/incident/359861#08c35be9689daad8371a20e0e0feea7e6131cdc638caae6d5b2e87003cd4dc90 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 12 Jun 2024 16:13:48 -0000 https://status.ppro.dev/incident/359861#0e47903bfbe4a361d8598de56278e9086d0146db7219f74795ce60b43d10049e BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 12 Jun 2024 16:09:26 -0000 https://status.ppro.dev/incident/359861#b4a97f1ac103c968f78d5f0ee098cc7aa5ed69c93f7978c3eb2d311efcf33f46 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 12 Jun 2024 16:06:27 -0000 https://status.ppro.dev/incident/359861#8dd0afa2b6909c45cc47d7b8854bbd9996f2322f6485f92c73e833f7eb24a2ad BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Tue, 11 Jun 2024 17:23:29 -0000 https://status.ppro.dev/incident/359861#0c7089e9147a7e26b0a8a6635fb311f2a956bba22f08cff8b35895a45e43a79e BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Tue, 11 Jun 2024 17:16:15 -0000 https://status.ppro.dev/incident/359861#fac048a4b2c037b5a6904319639bd9ff47794ca8788a5e9d68e6194660e8f35e BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Tue, 11 Jun 2024 08:44:15 -0000 https://status.ppro.dev/incident/359861#dd2862fadb1dd63d821b5c35ee26e52ba63d49e3408f6dafb3e3e810d516a193 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/359861 Tue, 11 Jun 2024 07:49:50 -0000 https://status.ppro.dev/incident/359861#6f044d8f39ff217ac5dbda4b20e9d1353d4bd4235dda76366fb4906e342e8676 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Tue, 11 Jun 2024 07:42:09 -0000 https://status.ppro.dev/incident/359861#dc61dee8be1eb1ae5e2e80194ec5353d3d964e543fed9efbf958f2e5c7ddc770 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Tue, 11 Jun 2024 02:59:26 -0000 https://status.ppro.dev/incident/359861#4cfeee976707c7a1774b4c7e27810db370db7195ca84243351f8313ca45ccdc6 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Tue, 11 Jun 2024 02:41:35 -0000 https://status.ppro.dev/incident/359861#ae80340d2a7f2146c5ad121f01c4fb08936964183f6886b4af9a8f810ddb9ff5 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 19:52:31 -0000 https://status.ppro.dev/incident/359861#eb7169c759b91960caadf04e4e14822729fb936c2acf78a8886ffe0ce946244f BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 19:49:00 -0000 https://status.ppro.dev/incident/359861#2c885faa68709ab2a1b87eb8417a20dc5e890b13eaf63f9b6394d2d59013d746 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 19:25:16 -0000 https://status.ppro.dev/incident/359861#fae72051a78c9dea2525671c76b7e8a6f3f739426c1d4d74b41096cda7c7f46d BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 19:22:30 -0000 https://status.ppro.dev/incident/359861#59b2ce433edddeba5bf6e4eb613c72526747ef0f31186b75a957ff2b331c0421 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 19:00:52 -0000 https://status.ppro.dev/incident/359861#6c69d4e7efa4533fad008454b9ce68d715f5489de23b036d0cbea28a32881fdb BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 18:58:02 -0000 https://status.ppro.dev/incident/359861#7cedfcf11c436d05ea5c5fe031e5ad395540c735a2ddadc742557c361271012a BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 18:36:39 -0000 https://status.ppro.dev/incident/359861#956e14c3cf62042d58926be1d69ef181de8e34df3f28c5d256d9935e7c5793eb BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 18:20:10 -0000 https://status.ppro.dev/incident/359861#e5f36771854cd38e46f47e7efbaef1913888894dfcbcf687dba2b3a8bd6fce37 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 18:17:32 -0000 https://status.ppro.dev/incident/359861#a6312a42ae25bd649613db59f4b2d98f8af54a7fd16e200edba3b81fe29b140c BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 18:04:41 -0000 https://status.ppro.dev/incident/359861#a1c3261e5428dbbfc98609286a219d48211e7007876c8c5aa2e8b9187a982a92 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 18:04:03 -0000 https://status.ppro.dev/incident/359861#ceef0c674090df62f32a73633f536da65c9676ff1b5f2cf57b9db08f886ad713 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 17:42:35 -0000 https://status.ppro.dev/incident/359861#d8dd977a51e669ede474825322c4e147f0d729e09e005421b3a79c2048c94e0f BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 17:36:40 -0000 https://status.ppro.dev/incident/359861#954bbacf97f522e57b9a3fb80fc15422ac9f11ad73c6805aaa3e926babd1eb55 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 17:20:05 -0000 https://status.ppro.dev/incident/359861#a9ff0b8dab73ea7b66fc1ce911b5f676e4c62e2382d8a22142b5a0772ee73a59 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 17:12:25 -0000 https://status.ppro.dev/incident/359861#9d656f3786c3d87ff0d1e2b46b1d823acfde924ac53b0d51f5dfcd7d456d5969 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 17:04:41 -0000 https://status.ppro.dev/incident/359861#adc9ef3704812801f39acdd987adfda73c8f884b67ad44f3781eb677420e9ca8 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 16:59:05 -0000 https://status.ppro.dev/incident/359861#b9a2efae9c88f58da4f18c7a731b79708f1e4fd63df8d54587e378ef4c837f22 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 16:12:30 -0000 https://status.ppro.dev/incident/359861#12509fc602e67fd665c75eb1f72fbb0f84f4c84f339346c4660f4a87d33a3a37 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 16:01:07 -0000 https://status.ppro.dev/incident/359861#e1fa8a55ec271197bc8e8a34ad618636e3c3bb4d29741da2049afff71cca6f7a BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 15:28:53 -0000 https://status.ppro.dev/incident/359861#beb16473f8231a3b1cb1cbff58b01c3c475e614162ba7c4949cdcaf62da811b4 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 15:21:38 -0000 https://status.ppro.dev/incident/359861#5519218a52c4f23e0c331200b821dde4429124dccea5bd46323783a53b47ba3a BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 15:14:01 -0000 https://status.ppro.dev/incident/359861#024d87d5a0ed105daf8ce543958f1e9ded215b7189d2e602a6654a0654fed099 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 15:00:16 -0000 https://status.ppro.dev/incident/359861#51fa0ae53b47aa043d9912982be67b3e62f82c17c05e634ebe7592e6e3dc0ea6 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 14:42:32 -0000 https://status.ppro.dev/incident/359861#8579c43054c4701ef4c0084d13b6491de3ab90d7d298e4d1908e3d3432f00be1 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 14:31:41 -0000 https://status.ppro.dev/incident/359861#96c73070b04a225d556c29aa8bbdc512165a227ee15f47f60235b90086158969 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 14:18:48 -0000 https://status.ppro.dev/incident/359861#ffafd8d4d4ef2982a360002dc0d151d5cb806605cffefde18c9e3b78dd8ec778 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 14:06:09 -0000 https://status.ppro.dev/incident/359861#c641b13f736d1ee9865bfa69e5468ddcf408d77b9d7e644c0fcd79ef23bf8cb8 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 13:34:02 -0000 https://status.ppro.dev/incident/359861#283e5ab81f955bf0d4a29d630269cb36b51501a2767e992028812de0e523d714 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 13:13:26 -0000 https://status.ppro.dev/incident/359861#8fc6ced4528201717866e354a5bc8565d719af5a1b11d451bdce857937ef80d2 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 13:06:06 -0000 https://status.ppro.dev/incident/359861#29f1422df26a56e67d1584fd5183cc97d91316017d9e98e1298414185dfc5032 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 13:03:48 -0000 https://status.ppro.dev/incident/359861#ce0bcba20cd5a695ebb132d0e767e504f3283280ba0bf28613ce8d8d774f9cdb BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 12:52:06 -0000 https://status.ppro.dev/incident/359861#89c0c6642a08f8f3dd523eb8a62f322374a8b152550e331830369257e00f1f0b BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 12:29:00 -0000 https://status.ppro.dev/incident/359861#49d9f5403caf70fd16ad26e595225da2703ef71e2f8d61433f1a2857ae5702b2 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 11:56:55 -0000 https://status.ppro.dev/incident/359861#8b8b00f0110539f3a2101ba91097f667c3d4f67e9c8d52706335f7e916c705e9 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 11:46:10 -0000 https://status.ppro.dev/incident/359861#6bf2ddb38381763a4cf6058468bd378fb80579e0cec85a8818830bf13a1f4edc BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 11:43:33 -0000 https://status.ppro.dev/incident/359861#9892dd7621a81ff534621fa8429246c7d215fac8c22a2da11e3b67d4d9854fdf BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 11:25:29 -0000 https://status.ppro.dev/incident/359861#42374aa4dca8ced1e3535973d6456c79ee1dad2352a80dd3941b0b749b6f0c67 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 11:18:26 -0000 https://status.ppro.dev/incident/359861#ad55a83b54cfa8b2bc49e83a70e92ba3d2a41685fe3aef53f1b4192d5d82f3b5 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 11:14:50 -0000 https://status.ppro.dev/incident/359861#7a49b861c7e339231b0053af236f7a69e9b20203d8c0b545a37b28978a67dcbf BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 10:52:03 -0000 https://status.ppro.dev/incident/359861#2a3f12853585c863a92fd4e736507f85180d60e25c896bf31f29236c657d4f09 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 10:45:35 -0000 https://status.ppro.dev/incident/359861#4350d3232b36332bc141a76febb33bbb982f70b8e8d5990fc6db7920457249fd BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 10:44:26 -0000 https://status.ppro.dev/incident/359861#3db802cb01debd7575ddb6fd0585eb1beacfd2248492f4d40ce0081c21000fa3 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 08:12:07 -0000 https://status.ppro.dev/incident/359861#2c023bd06971e144308f7e8e19f215c6b6b3a8bcea6675584b9fbfef52481e77 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 07:09:13 -0000 https://status.ppro.dev/incident/359861#519bae61ee225c738086797ce3f46b49aa76049c89af1b86d955227f14b630c5 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 07:08:47 -0000 https://status.ppro.dev/incident/359861#fb71b8f455a99a3a0be99f821c954289f4f2a600e9409669b624779ef320e6d0 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 06:55:56 -0000 https://status.ppro.dev/incident/359861#a041fab2d32ee3751d295e83464d2daca9553c8fc22acbbf5b038a5e97660f8a BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 05:47:45 -0000 https://status.ppro.dev/incident/359861#0d60651bf353fa7d9b6e750e4a19f799c929cb58dd9058530834d1ae8574e5b8 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 05:15:14 -0000 https://status.ppro.dev/incident/359861#9ce94cf478313b5ddf002a7f47911a578bd069bca87db8b6990d19e44ef3bc62 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 03:32:26 -0000 https://status.ppro.dev/incident/359861#915d35ee3413974698ce639b46f0808d825651d5c16259f94869443cd21b8d26 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 03:30:50 -0000 https://status.ppro.dev/incident/359861#e88dcf908b3edb3e732a9194f19821f0a79a50057ed9364ead211f0fc127cc7d BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 03:20:14 -0000 https://status.ppro.dev/incident/359861#59faf0f98e947b787a222a705269dd2d97e99932d3a716e3ecce76ff1ea54c60 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 03:18:39 -0000 https://status.ppro.dev/incident/359861#edffb008d445bdef67197483efe12d63c3052ed137ae0c7c5a417950cab124b4 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 03:17:27 -0000 https://status.ppro.dev/incident/359861#d97bc6f885fe0e15b6af4c09134981bf3b11234ab5c7c840f58cc3007d5e0165 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 03:16:03 -0000 https://status.ppro.dev/incident/359861#97ad62874b2deab01adefddba859bbc234b4068c83f1c2bb748586695da19475 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 02:49:39 -0000 https://status.ppro.dev/incident/359861#454fcfc2f4651b5d6919ff39a18a9f51cd49782f9441e608ab0e10d0c9a73c35 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 02:38:20 -0000 https://status.ppro.dev/incident/359861#2c270b8a26939c494b1c7f9848272267234ea16fe85bde65a8a2b46e946b32d0 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 02:37:24 -0000 https://status.ppro.dev/incident/359861#18dcbe2a73fec4c80e4fdab7bfab110b228fb05cfc6f0b469e37ed5c79104f2c BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 02:25:14 -0000 https://status.ppro.dev/incident/359861#f99127436e0c0bb17365e8618b7c42b53c324569629e32d29e5c1f87c46aaf08 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 02:16:11 -0000 https://status.ppro.dev/incident/359861#37d0d1c6a87e7435ed156bd5473a734650bc2eec7141bc29bcf050b2f68d5aa6 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 02:12:37 -0000 https://status.ppro.dev/incident/359861#632d2c70f49011954ed1fc62a5e63d8830db8d422ee63f1c021035bfff569976 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 02:03:40 -0000 https://status.ppro.dev/incident/359861#d0e3b8f474c9a860016af86b338bc007e1ef07ee2c63c916a4f9b55fb52ead63 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 02:01:04 -0000 https://status.ppro.dev/incident/359861#83977519c5b15c57c7bdcaad5e76f80e962ef818c6f9597566359c4e8c7eeb05 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 01:55:09 -0000 https://status.ppro.dev/incident/359861#c16a1e06c3d3c1bd87c34e434f985221a93e81474bf07e5bd0156bc6460844fc BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 01:38:24 -0000 https://status.ppro.dev/incident/359861#fcdb7cc419e5d1ab1e30424d14114d23901c03340d1acb93f4981732f6228880 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 01:05:58 -0000 https://status.ppro.dev/incident/359861#597aa166abc54fb91148057e123412dbee0ce859c09e00cee73b80701f73d2b2 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 01:02:43 -0000 https://status.ppro.dev/incident/359861#e1823669fa3e9e7de291ea093e1bc5accb477aa2f5adbd4b9e846fdcb9f84cac BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 00:43:45 -0000 https://status.ppro.dev/incident/359861#b6fe4eacb02df2f158422a06d8d3c6df186f307c7f4c43393579061ae2921718 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 00:30:46 -0000 https://status.ppro.dev/incident/359861#280b7465dce8e4f351214b5e075a088e89f6fa40829f3dff20590326aa3a4f45 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 00:25:16 -0000 https://status.ppro.dev/incident/359861#b3c221bab5edd8772fe47e5ed4be430785120c186fdd83ab6187880c90f073dc BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 00:12:22 -0000 https://status.ppro.dev/incident/359861#d8c6b7ee9d1a0915bac3d7f889391985c7020c12be893a87293e29ee947d3886 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 00:03:38 -0000 https://status.ppro.dev/incident/359861#1a24b2ea2b987e21fd2a8dc4fe85a19f9d6daba72fda6044c8c87eb4644e310b BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 10 Jun 2024 00:01:04 -0000 https://status.ppro.dev/incident/359861#0e84c678f5e0e6fcd4110f018231fdb476d6c37ab5e67ec61a79661cac8c2c9b BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 23:44:43 -0000 https://status.ppro.dev/incident/359861#ffb834fbd6019322fb4d35fe926da6a7613bae323b406abc72c0956e0f1e8dd7 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 23:38:37 -0000 https://status.ppro.dev/incident/359861#7cc2c896933e35f97c1b83cf212f80f1367d23e3ee0d21d2b7e77e5541fee96f BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 23:32:18 -0000 https://status.ppro.dev/incident/359861#b2eefbfcbbf35cd7ff3d0d0d74c220fecea32e8fc33c1c60a42d6435158881da BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 23:21:06 -0000 https://status.ppro.dev/incident/359861#c34649a54662a370dd3e86e1fb172ca86fcbe9653854e1d39c795b09a986c993 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 23:15:08 -0000 https://status.ppro.dev/incident/359861#3d0a34d14b577f79d0953e72699c2e2821744c0e2379dc56bd3b1402d1d3b8c1 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 23:12:27 -0000 https://status.ppro.dev/incident/359861#d1d8d39872061b4bf554ae3788aba2ee8ee9e282f070923ac7a358f8a2a70b56 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 22:55:09 -0000 https://status.ppro.dev/incident/359861#a01963d6ba86f2f0d5cddc70c2fda695a4ccff3b17701d5c110259744b0431b5 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 22:52:29 -0000 https://status.ppro.dev/incident/359861#8ef35bc5341397cfbf7dd38f27c5527cd5fc187b4436ad29b9d5b174c2f961b7 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 22:34:47 -0000 https://status.ppro.dev/incident/359861#068d2b102fe575e916b90a51510bb92967f634acd496243f20d8737c201c85e7 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 21:43:36 -0000 https://status.ppro.dev/incident/359861#fb8724bea5fb5fca9cd85cabf4a6e2b71d4d40ab84fffe7a2f4ab55cd98f1ae0 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 21:35:55 -0000 https://status.ppro.dev/incident/359861#a103d256fc60a10f01747e6a06dff878452c72d9b3113d5a44d3c610896b106c BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 21:32:30 -0000 https://status.ppro.dev/incident/359861#2884ef37415be1638d84feb55e205af0c347a07843d833a7672d3303266d32f6 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 21:24:39 -0000 https://status.ppro.dev/incident/359861#95adb6027c70bd9186806729acc3b0e3da4f86ff5345524c49c39ccb2a9b4aaf BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 21:13:17 -0000 https://status.ppro.dev/incident/359861#e7b611fd2ff62e96a74381efb56606a1f71739a4cce6915a97d27324ef7975fa BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 21:12:24 -0000 https://status.ppro.dev/incident/359861#3fa161a08aae86c891b1ed067ef521ca28d2e1a7df541e3a78456e2648fad70e BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 20:25:13 -0000 https://status.ppro.dev/incident/359861#54e1a9875428057b14e3affcf4b5822613c456ed40f37db5d96dbfecf613704b BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 19:37:26 -0000 https://status.ppro.dev/incident/359861#b204155079b09195df51b5a7a574c411ba16ef95181e99a494dc2956bc2d57c2 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 19:30:13 -0000 https://status.ppro.dev/incident/359861#b1dcce8ed7937c3a2360a05d76c33d92175db5bf17ff4f527b47f8df6ac42160 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 19:16:20 -0000 https://status.ppro.dev/incident/359861#b2ec49147988ac00bb54f888a8cb795319381e499bfdac52bcee5534ff75933b BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 19:03:38 -0000 https://status.ppro.dev/incident/359861#00f3fc9e31489aabe1ef13bce0fb562e32067f18172086dfc607db5057e84a42 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 19:02:25 -0000 https://status.ppro.dev/incident/359861#58b3ee698f1f5695e3ff012ea7c116d21b73952d99ff610c100d0646279b20db BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 18:56:08 -0000 https://status.ppro.dev/incident/359861#dbcb00a56f12787522b103497156f5e07b0fcd123fe0b395b118d99110a842bf BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 18:24:38 -0000 https://status.ppro.dev/incident/359861#beae5a1b96ea496eb90facf6e441fba208f1dfc93b062a34673a50042561ff44 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 17:57:35 -0000 https://status.ppro.dev/incident/359861#42841e877e3964f4b53d5a1fc067f09af546b9b3b1c9d73a7db04fe6ad83f325 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 17:53:12 -0000 https://status.ppro.dev/incident/359861#01f3113ba348e8be15c23dc3857c705e4e643d36dfbbcf9270bed26bedfa25fe BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 17:26:04 -0000 https://status.ppro.dev/incident/359861#6aa192d87fd96a9ea1b275e46186dd050aa0438f6a1ad494e8a9170d242d3a16 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 17:24:44 -0000 https://status.ppro.dev/incident/359861#af5ce1a8340c280e5393520cc6a36634f076a5cad79a66d11eb23f0154f160e8 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 17:02:48 -0000 https://status.ppro.dev/incident/359861#86fccc455c7169fef1fe0acc00a1d0d4c35974e8317ad9c443d74fdf4ff5f21c BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 16:40:00 -0000 https://status.ppro.dev/incident/359861#2ff3be990706d77354f4dd2d9e65393b5fdb10c0ceda8e0c1645b60f7fc48266 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 15:03:37 -0000 https://status.ppro.dev/incident/359861#3f8b2042476bd8eec87d1a12c46d510280e04f9ea49a15cc73a06e2808dc70c5 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 14:46:13 -0000 https://status.ppro.dev/incident/359861#0c72f8da7c37d33ce71cc944bafee9ab360f759d5569452914fd51050b50359d BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 14:42:47 -0000 https://status.ppro.dev/incident/359861#1c0c8af556b68fbe872dfeefa837c75837f37bd983fc822e43513bef77f652bc BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 14:34:45 -0000 https://status.ppro.dev/incident/359861#ef516be54ae873f1b64750654a0cb313780436a5afd461f5a63d68fa73aadc81 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 14:18:37 -0000 https://status.ppro.dev/incident/359861#c7528bd9960499f8b41b356d19eb7e35015ed165c2656763230062cbba6172eb BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 14:11:03 -0000 https://status.ppro.dev/incident/359861#3225b765faf8e0d477f9383945355e1753a4db1e1cd7faca07c836cdd24f747b BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 14:07:29 -0000 https://status.ppro.dev/incident/359861#ab2566ed07184f052ecba3935813e43ff30d60aaac180d8dd696321c10599453 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 13:33:39 -0000 https://status.ppro.dev/incident/359861#4a32a14c446173e889217461b586cebfcc0044dd1819e6797cfb1e859462dd74 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 13:29:39 -0000 https://status.ppro.dev/incident/359861#5a159d9c5e71b68205fc67ad71b1895fc457dc0fc6567108a4db25c65fef1c38 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 11:11:23 -0000 https://status.ppro.dev/incident/359861#779cc235aed8674eadacbd023730aaa5ada9be5f066c5faea32a173351d07e66 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 11:03:11 -0000 https://status.ppro.dev/incident/359861#3480a558fac517789c4076452c0789339ebc4a1ad8d0dd76b6c5c612b8ab8b0f BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 10:35:55 -0000 https://status.ppro.dev/incident/359861#5f9ae7d9be6ac3eca09259cb0a20c8f17a21ac0dcc4c63e8604008d6c4127fab BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 10:27:33 -0000 https://status.ppro.dev/incident/359861#dcf3d7b7b84c7ecfa8e7564031a9a240c6ae2ef782e0dbd468c181464148745e BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 10:20:10 -0000 https://status.ppro.dev/incident/359861#41ac6c7216413117e61fa2c9b79cc8f2096f06e4424383614de2ccc719d42b21 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 10:08:38 -0000 https://status.ppro.dev/incident/359861#5eb96796f77b2ca442282106bbf3193af1b718a1e165d184fee42974f758be94 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 09:25:48 -0000 https://status.ppro.dev/incident/359861#c6a7521b81e73e254d0d9ab82152d4bea3ee19fab246a0e699102da3044c6b0b BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 09:07:26 -0000 https://status.ppro.dev/incident/359861#42c29489a3c2d64956c60a5c900aacd3a7cb3f1e920d2a8606b560578669565e BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 08:59:39 -0000 https://status.ppro.dev/incident/359861#a859033711d5e22a606b978ba5b97029efcf15b8767c71e75fcd988b5f64b452 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 08:48:41 -0000 https://status.ppro.dev/incident/359861#4c7ccee020e077665d71e37393d2a0ec7cbf07d182eee9e04ffbdeb2e8e63a97 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 06:10:46 -0000 https://status.ppro.dev/incident/359861#2101d82ba04e1a8b7987c8af2b5da625d4db4919edb547f367c1686c80f3272f BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 05:53:03 -0000 https://status.ppro.dev/incident/359861#7967bc0b08432bf4a7f86105e41b4ed008e08fc486aae190c76f9eda440eb7f0 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 04:26:07 -0000 https://status.ppro.dev/incident/359861#a0bff9e7d976bf3fc25bcfdd1c053b2384922a9c8490e59d8bfc014662d62c80 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 04:03:38 -0000 https://status.ppro.dev/incident/359861#039c7a7a78b6f088745b4a8c569cfb5d296ffbd57c307eab221e06b2ec4ca32d BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 04:00:51 -0000 https://status.ppro.dev/incident/359861#af35d452d5a2d8223d9a59fae0606ede521f281c1518fbc9d6f1bb905944cbc9 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 03:37:24 -0000 https://status.ppro.dev/incident/359861#17893c5ef0121953ece83545509eb078d18ec68301b2a1030427ff3c5105e24f BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 03:19:33 -0000 https://status.ppro.dev/incident/359861#f1e356ffc7158ebbb129bb1783e30f563a26c2d0426640744b3813bcd950647f BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 02:27:09 -0000 https://status.ppro.dev/incident/359861#d875f2be04da93d94743c8e1d7042a17188c7bce29a24c29df882da51d311930 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 02:23:03 -0000 https://status.ppro.dev/incident/359861#71f8c9c0312b97c341599a7e3d0679334ab6021d3c3731eac7931e766680fd49 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 02:10:46 -0000 https://status.ppro.dev/incident/359861#26a555e655370dc18bbd3323bd31a23f34d21b9f0c5cf9c97c1b12eb58c3320e BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 01:30:07 -0000 https://status.ppro.dev/incident/359861#4270a14afc257a30f5d5c90884cadc8c1ec09108c016d9b499374714bb7fdfba BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 00:57:20 -0000 https://status.ppro.dev/incident/359861#35a287f9c3bfce21ce2c14800723434e3868370b3bdaa1886766c8f52abe7a73 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sun, 09 Jun 2024 00:33:10 -0000 https://status.ppro.dev/incident/359861#40cbb223869c8114451824d08c765e0cac87e6a1c63b28fdf8af05046a6dc243 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 23:51:00 -0000 https://status.ppro.dev/incident/359861#7c06f92c54307b5e94bfda2b526f51c51909fc3bab5789c30af8461eb34bedcf BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 23:45:00 -0000 https://status.ppro.dev/incident/359861#0a72affb0fbbb4048e8c5536cfa4156bbf250f466f656fce3cd69d566d042c44 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 23:37:11 -0000 https://status.ppro.dev/incident/359861#d12e2973a206b501b1db383384731e44e28214ac3af501ede90d50dd2e820ffb BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 23:25:00 -0000 https://status.ppro.dev/incident/359861#9bb6edb20e45ce894749e07d8035ca1a6bba534933a18a803baa5775fdc63f9c BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 23:03:33 -0000 https://status.ppro.dev/incident/359861#fdca29d962125ada7db35d6b878c84b9528d5a273df30370f50606c4999c5bf4 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 23:02:26 -0000 https://status.ppro.dev/incident/359861#ee783b8d08c8ba3cf451de7335ae6483a0f420268b89a168a4908725bebbd83f BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 23:00:48 -0000 https://status.ppro.dev/incident/359861#c0568a69644fc9e8bfc309839bfd99e7fe7ce3de45ebc3b36887d85ae3434356 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 21:55:00 -0000 https://status.ppro.dev/incident/359861#a2ba585e28c79c3cb14fadddc3d4ff6da35ad1ab456fa824f384cdc8b1d1e147 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 21:17:13 -0000 https://status.ppro.dev/incident/359861#5b9ae4aaef7f8161bc30fc5121b72c23a864ef929f8457d24d407d8787c5716a BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 21:00:03 -0000 https://status.ppro.dev/incident/359861#45089018fb256aa81a96ace1d0e742f82a069c403a60a4d2f9bb35ab75103c8e BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 20:57:36 -0000 https://status.ppro.dev/incident/359861#76b07bae3ad42cfae37567de2fe8098276b306224801e78323b82b866d0cb555 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 20:44:39 -0000 https://status.ppro.dev/incident/359861#be34db631ff0c27c71347cf37f64287bae4e070a6b392e9aab48aedb872dedd7 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 20:18:22 -0000 https://status.ppro.dev/incident/359861#841acb18c65b0bd2ce3f4649463aef8c89d817ddbd6838524975bdeeab09d5dd BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 20:17:20 -0000 https://status.ppro.dev/incident/359861#3b29cf0e5afd36ee1ce14a906e86430cf4561750dfe636808236b94afd68f6eb BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 19:56:03 -0000 https://status.ppro.dev/incident/359861#4db0ccc36071186d04e2ae641971f2b10d6d924b1397753852274ea236a4e5c6 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 19:38:28 -0000 https://status.ppro.dev/incident/359861#28ce3c4237f26a67dd842304114a05c80b799dc6e03c0134e6d0b9e3c50794e2 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 19:24:35 -0000 https://status.ppro.dev/incident/359861#de3d22b9a2bc32c2dfee8aca244cc1590bfb4c9927892e0f7f98cff90299632d BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 19:15:38 -0000 https://status.ppro.dev/incident/359861#c6b11975e13c184765d577a4225d9a81d5caa20f0867951ebed6068e78304d1a BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 18:02:27 -0000 https://status.ppro.dev/incident/359861#56583108fb4c6fd717f8edf6eb66d9702e7e66ec56b761ad0085b0be0f43ea50 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 17:53:14 -0000 https://status.ppro.dev/incident/359861#bc3659f8a3830c146db0ea580f5afbaadbeb8a2d333f3a14722a0dcb7ce4a2f9 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 17:35:55 -0000 https://status.ppro.dev/incident/359861#9b9dfe21fd4d2ee4be5f4b9b2697376ba02e258e6f7edc60e42b4f97bd43bfc0 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 17:29:37 -0000 https://status.ppro.dev/incident/359861#28408a66278f0330bf5c7eaff56ebd0a246d08421d67bba694659df836b02b0c BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 17:22:09 -0000 https://status.ppro.dev/incident/359861#59073b42f4f9594d433123a844e7793ada248e5aab6913a24f0f60cd72e7e747 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 17:08:58 -0000 https://status.ppro.dev/incident/359861#8febc8445f64c0bcabb76e9cf7cb1c53d53512fa9abe5f9d4f7e79445f7331d5 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 16:57:18 -0000 https://status.ppro.dev/incident/359861#d46098fd41ab1f8a7022a80b2d91ec5daa996cfea973fdd4f061cdcbc71bb3e7 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 16:41:45 -0000 https://status.ppro.dev/incident/359861#56ff1eda7d30c3b75653a16b29553dde83e00d79ef5b12a9a3a03012f8da151c BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 16:33:41 -0000 https://status.ppro.dev/incident/359861#1b79c09d693c082e3acd0bd956c1017f155910a647e78f20d62517df8e773d9b BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 16:10:10 -0000 https://status.ppro.dev/incident/359861#2343b2faa2072b267f9bee9c08f08921fed1367e6e1a669501cc156604dc4055 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 16:02:40 -0000 https://status.ppro.dev/incident/359861#abea7a83df578d77879a499cc3247fdaaf270d5654972f79950480562260fae4 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 15:34:58 -0000 https://status.ppro.dev/incident/359861#d4d1a75374e3a6fa6b03ce701801397b548e6b7daeb81f5706a0266c59117a91 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 15:31:20 -0000 https://status.ppro.dev/incident/359861#cec55928f61bef43ed8729f1580c7eb262eb39db868eac6f297ae2ab5225335b BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 14:58:43 -0000 https://status.ppro.dev/incident/359861#105bb2b7172d912ba46b37bfc1b4bbdf177abf2e334e1d2ee24ca3fcffd22776 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 14:47:10 -0000 https://status.ppro.dev/incident/359861#dbe1f452a46505f1999b6704ded82fe666c35fd1a5b662b8f225e5c8aae75061 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 14:35:02 -0000 https://status.ppro.dev/incident/359861#fa083e6975c43f8f117658fb445e88fa0e3727342ef4e1bf68fe9bd809886d28 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 14:17:39 -0000 https://status.ppro.dev/incident/359861#4152e24ccd4a77a43d47ff58fe4e889895e72923e13ee4cd0d04fd2d9e523300 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 14:14:48 -0000 https://status.ppro.dev/incident/359861#58e83dcb43d13281179e8c9de04882e6469c9227261e3f58d8ad383d644197af BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 13:47:30 -0000 https://status.ppro.dev/incident/359861#48b4a1c7df4ff73cec9d5e2bf941c8346caa5fcb413c26d8c2403a37fb0fc165 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 13:36:21 -0000 https://status.ppro.dev/incident/359861#2cc8e7b24cb49c890a44982b99d7a34d453a617b211fa849675d58fa28b8c0fd BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 13:29:50 -0000 https://status.ppro.dev/incident/359861#28aac73b0412c80af5be3f6258b087833dd8fcf001b491675b236e2d4df8abd7 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 12:53:41 -0000 https://status.ppro.dev/incident/359861#76029de77154058359d138ae3c56d6b11853076290ed789cb2be78cb035d730f BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 12:52:01 -0000 https://status.ppro.dev/incident/359861#cb521040bc2b8fb41cd10cc4d36dc893cb6727696eae24994bfa2ec8ff9632ce BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 12:31:14 -0000 https://status.ppro.dev/incident/359861#ddf689706e7a34e2d515ed8307fca750fea7fcee11a9dfc8a43a4f87c18d412b BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 12:29:51 -0000 https://status.ppro.dev/incident/359861#b8b8e8b9ae8e7c77cf1a79ed64894bb6497b038344a5222961ee1c52ed03d584 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 12:14:07 -0000 https://status.ppro.dev/incident/359861#0fe47b0d6d7cc961815661d48c91723b7333d0e02478cc49be8e91b3748962fc BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 12:11:52 -0000 https://status.ppro.dev/incident/359861#c6c56330b18caf3c9a819da2d2ea821b1077cbaa5dc90a460a059b484837105d BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 11:42:22 -0000 https://status.ppro.dev/incident/359861#79925db2bbdd09d4eb6384344ca1db491895416d9b478bd1b9306ead1b5ae899 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 11:28:52 -0000 https://status.ppro.dev/incident/359861#521a78df548bb6067dee44288a030d9d12f4e3f3336153d5e3555d1997972fc3 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 10:39:42 -0000 https://status.ppro.dev/incident/359861#7ecfdc836ac26874d4d954e0dab7dda65dbd17147b9621461f4a665e9f2f54f2 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 10:21:26 -0000 https://status.ppro.dev/incident/359861#53520bedd7132a5d9cf508d7b8df0e79aff8030f36f0c5dbde67ee62eebf62ce BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 10:17:00 -0000 https://status.ppro.dev/incident/359861#ba7157f7791791603dbdfa24dd1dac37b317187aeacf13e097db1ad286093f28 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 09:13:49 -0000 https://status.ppro.dev/incident/359861#aab76d306aa303972f2110d98a4879da4f6dc8f742cbfbfe86e6cb889ffa32e0 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 09:06:24 -0000 https://status.ppro.dev/incident/359861#427b60e4e8b5801a72d8c0230233fcf915821fad4e048dcc3f1346bd83d42fb4 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 08:48:30 -0000 https://status.ppro.dev/incident/359861#e9f39594f131a84fb58ece8aaa18d82facce524371917a4904f803dd294163d5 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 06:14:36 -0000 https://status.ppro.dev/incident/359861#ebb3546e11d5f8ce5c3d691a213607a8bede127d632c4087f5760d4efed56a2c BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 06:11:01 -0000 https://status.ppro.dev/incident/359861#e800d908c8aab9d51816caebb0df165cea03d513a940cded8e17c4260d24c8d0 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 05:31:59 -0000 https://status.ppro.dev/incident/359861#5d6f0002367a092a2ffe46649d01c58faf635d89f7feb7c50af6aa68f53be69a BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 05:23:31 -0000 https://status.ppro.dev/incident/359861#40930f570831344a9ab95948e6840a35e6d6e003f397760f0a60d4a210b791c2 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 05:10:08 -0000 https://status.ppro.dev/incident/359861#192cf2ba9757c46d3a2a2d657d97594ca8721b429a33470dff88ec18132c68e1 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 04:57:20 -0000 https://status.ppro.dev/incident/359861#7a1882510164c0fcf2b188f8ef2bc12619886c5dc3f55965dd6620ed978cd935 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 04:44:50 -0000 https://status.ppro.dev/incident/359861#2ae8f806b55173053a7b687373038b4a12ee81861a91cf3d6989884c58842fbd BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 04:26:50 -0000 https://status.ppro.dev/incident/359861#54b4de3fd35eb43d7173b678693138f3f6e297e3e487f35e066a564a99ae6812 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 04:04:35 -0000 https://status.ppro.dev/incident/359861#d90cc8e0afe10f9ac37affdaed2b963e7eb6df750aa20a38b4492b3d14fe52a8 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 04:01:13 -0000 https://status.ppro.dev/incident/359861#e40e6ab4b1f2501d6d657010c38871aeefa6ac3b2ff8cb8b4d96a06af72d6f3e BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 03:47:05 -0000 https://status.ppro.dev/incident/359861#a08d3bad27c9708b0568ba6dcc70501f2a365976a8a666b112ba42becf6901cb BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 03:28:57 -0000 https://status.ppro.dev/incident/359861#a148e5065a2fe04a5d393d566b495c2f935b1f68dc87c48aa1f28b24d10f9606 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 03:16:18 -0000 https://status.ppro.dev/incident/359861#ef151594d992d4f5d4080165e940b26f02a2cf6f822fe7ef7d5045a80cd86904 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 02:54:37 -0000 https://status.ppro.dev/incident/359861#54e6406a0b4fd2d63ee18403ce7653809583924698c5cea98b86ef6fbc1fce39 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 02:48:57 -0000 https://status.ppro.dev/incident/359861#c67fac6cd46527a2b2ccf06a7bb8843ba02cf91a6654a0a5ba0aa360848fcc7f BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 02:46:18 -0000 https://status.ppro.dev/incident/359861#c4bc837c6c5c3026213f71c9d188040d95e7a1e7008fd947841f6d6692b39fbd BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 02:29:04 -0000 https://status.ppro.dev/incident/359861#95946c0e9c0e44601ae3bbe37ed7542cd756bb10f92eb4c0245e07759d1d9115 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 02:26:21 -0000 https://status.ppro.dev/incident/359861#a80a6aaf9dbf6ec8fdb21d560f497ffec040604e5f450df42cd955a2ac7d84dc BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 02:12:26 -0000 https://status.ppro.dev/incident/359861#53f05861716f41afa261c8c188661273547c53cee620437b17cda823dabd1e38 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 02:09:29 -0000 https://status.ppro.dev/incident/359861#a91c1badbda8de942a9e528cc6370882fc0e04ebf002a4ff86189ec732a10f42 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 01:42:19 -0000 https://status.ppro.dev/incident/359861#05726dce4b3648c541a687cfc67dbb51bb7559d1afbed3feb312f06ffec2402a BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 01:39:42 -0000 https://status.ppro.dev/incident/359861#c082660784c4d281ba1160681f48e8d1a443a9221347a261bc8e40c0fb02f026 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 01:38:31 -0000 https://status.ppro.dev/incident/359861#dce8ca17bdbf7a9a7b91aa656869531e4ad4190bd8f592c9b0931c07b0ad7d70 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sat, 08 Jun 2024 01:31:32 -0000 https://status.ppro.dev/incident/359861#513860fb661fdbe066829eecd755598e0d3d480e59fdd2f7d81b0e966c0d8702 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Fri, 07 Jun 2024 23:43:50 -0000 https://status.ppro.dev/incident/359861#0456586285f9ec50dac3bc72f1cff0634febb2b406b01c0fe28501608c51ce01 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Fri, 07 Jun 2024 23:42:29 -0000 https://status.ppro.dev/incident/359861#f703f893eed643dd79d041175900acf5da052a30d69d53c4faab40f8ee205308 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 07 Jun 2024 23:24:44 -0000 https://status.ppro.dev/incident/359861#ac11043d1eb825b9276e23f25d8222caf085e0ad01860482266901401d971db1 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 07 Jun 2024 23:12:00 -0000 https://status.ppro.dev/incident/359861#3627f99e20dbcad8fce6f1380e6c7a8ad73f4cfb6bb03b988a361f8c015bcc12 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 07 Jun 2024 22:14:50 -0000 https://status.ppro.dev/incident/359861#da629d97c3db7f1fad2abb06e0e543f2bc2001022911abe0000138b8e68e7807 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 07 Jun 2024 21:41:58 -0000 https://status.ppro.dev/incident/359861#f936bed0517739c248367366f6d993fd1cd23ccb5a9c435fd5f516db5e93f50b BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 07 Jun 2024 20:21:06 -0000 https://status.ppro.dev/incident/359861#d97d82b25faa26b0879c2fe391489e70857f265bb2aeba553fe4394ad96cbce7 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Fri, 07 Jun 2024 20:13:24 -0000 https://status.ppro.dev/incident/359861#199fa0d7be350277dbbabf36a3d4b42a23addc6f168bbe8751d617ed81fb9ba8 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Fri, 07 Jun 2024 15:04:47 -0000 https://status.ppro.dev/incident/359861#47eeac70cf152d34b336dbc51d542df315a493d89ec69abea53a2dc9e2a086bf BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 07 Jun 2024 14:52:09 -0000 https://status.ppro.dev/incident/359861#4f11b2019cba9418cef3b064e79136608d1bbe4250a6c3b7f457ec8eb9570640 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 07 Jun 2024 14:51:15 -0000 https://status.ppro.dev/incident/359861#fc1c343ff6383a5964dd51fe562e431312809b3380a0a10ce26a8a51bc67ed2c BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Fri, 07 Jun 2024 14:43:40 -0000 https://status.ppro.dev/incident/359861#4de3445b1d8b09218c161cb41aaeb18d1cb8719b852c279b6c1a05094fc70d5f BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Fri, 07 Jun 2024 09:14:02 -0000 https://status.ppro.dev/incident/359861#43c5a81b5f9a11048ea2aceb0f60b911fa5931a7defbf14f8fa6fe1d22d23876 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Fri, 07 Jun 2024 09:07:25 -0000 https://status.ppro.dev/incident/359861#1d2eeb215237c08d3ca4fb29e3ff92c5c7a5aa138272c97658a11141a6887b4b BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 07 Jun 2024 09:01:37 -0000 https://status.ppro.dev/incident/359861#1cc1e1fe56b82a7b32a7062f907b0fb8fd9f9b25728df7717def6682e07bf2e9 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Fri, 07 Jun 2024 09:00:09 -0000 https://status.ppro.dev/incident/359861#4cfd81a21f6858d07e4cf9cc52b5a0f620641a36744c0ae6707b6594ad491766 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 07 Jun 2024 05:47:01 -0000 https://status.ppro.dev/incident/359861#6e1d3450e6e3d8b02bdb5e707652af624a9c890e631ee205910ceec2af76ab92 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 07 Jun 2024 05:43:39 -0000 https://status.ppro.dev/incident/359861#91d3b96ca6c4e3a38226dac499bbd75d2834ecad55664412de7edbd66014ae5e BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Thu, 06 Jun 2024 23:21:14 -0000 https://status.ppro.dev/incident/359861#54d986dd9bf73c97c8668d6f0118c9df0864d6930124a98bd71a4c67c63f7029 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Thu, 06 Jun 2024 23:19:49 -0000 https://status.ppro.dev/incident/359861#8c37630ff64b1c66021515a3a50382d27b8d7582d6f57232eacdb5c43eaa0eb1 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Thu, 06 Jun 2024 21:48:30 -0000 https://status.ppro.dev/incident/359861#2da1d181795194c09072da64dca6a774fea0713d093d83bb887d5a5b01067a39 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Thu, 06 Jun 2024 21:46:59 -0000 https://status.ppro.dev/incident/359861#15707f82655a0986dde9c3d4fe48473c3342c5fad4686378f313c69a6c31f931 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Thu, 06 Jun 2024 17:51:13 -0000 https://status.ppro.dev/incident/359861#3803d82ae02dc93450b1e342045fc9fcdcf4d3aa39b2f001d9d79c989c3079ce BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Thu, 06 Jun 2024 17:49:49 -0000 https://status.ppro.dev/incident/359861#a2bbe4bb2e189cea1af427fc9f0f4fdceeae4d6ea70c5b67e457dc404fbd51e7 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Thu, 06 Jun 2024 17:32:30 -0000 https://status.ppro.dev/incident/359861#d2142ecebd95e1731da893a7a94d0e4883cf1505981121fb44d0d0d3e4d45db3 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Thu, 06 Jun 2024 17:19:18 -0000 https://status.ppro.dev/incident/359861#ca249e81d7a7cc5c292581deec9e047cf36ce4b6d5173458da324e05938cb692 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Thu, 06 Jun 2024 07:56:07 -0000 https://status.ppro.dev/incident/359861#fd2c12ea08074e27a19e03948c508fe70c4dbbfa3cdf1f644932975908b231ca BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Thu, 06 Jun 2024 07:42:38 -0000 https://status.ppro.dev/incident/359861#6f944399129385455e2cb54b7b01c197ad4e26de75b9cf3156afe97fab37cf72 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Thu, 06 Jun 2024 07:33:37 -0000 https://status.ppro.dev/incident/359861#3e2daed8e1970ba208b57a7ba0754a347a0d85f9e4cb65aee35a19afe2f29078 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Thu, 06 Jun 2024 07:30:28 -0000 https://status.ppro.dev/incident/359861#2790ad335f71a2b4d8124580ab6d1aafa4fc97f6eee9484f34f59454239aa7d7 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Thu, 06 Jun 2024 06:57:41 -0000 https://status.ppro.dev/incident/359861#72669ba3163dd1264a867902a88c1d892fd89d5aebfaa31946daa8169b4485fe BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Thu, 06 Jun 2024 06:56:16 -0000 https://status.ppro.dev/incident/359861#a052a87fa9ed8c6ced481e7a4dead74b202f34755fa88f51660f3f8dfd5e9576 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Thu, 06 Jun 2024 06:50:26 -0000 https://status.ppro.dev/incident/359861#7e6efd9d8fd40431301ce440580b0daaef862ca5e7508cd43a5b475f0ba3deee BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Thu, 06 Jun 2024 06:49:01 -0000 https://status.ppro.dev/incident/359861#665f5a69e0c32b345f432427e36cfbdf4ff1146d04b574eb9c1fb21fe1f9fd82 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Thu, 06 Jun 2024 05:47:52 -0000 https://status.ppro.dev/incident/359861#3cb0cba3c8738f9fff268767c8ad7afe3aa92f677b30239204b7ef619cea0965 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Thu, 06 Jun 2024 05:46:18 -0000 https://status.ppro.dev/incident/359861#d868b6a8810146001d4089d6ad06d11626d2d5fccb61ceab5a797b3fdb2c7a41 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Thu, 06 Jun 2024 01:15:18 -0000 https://status.ppro.dev/incident/359861#998dee08c105d09ccd467ff1334ee903f634705ad84b1bf5f3e7b7b0c1130e42 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Thu, 06 Jun 2024 01:13:49 -0000 https://status.ppro.dev/incident/359861#65174ca3be013382f324d18b804e2e69720c4c05be9d55b6bf605f7b21412cfb BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 05 Jun 2024 23:27:35 -0000 https://status.ppro.dev/incident/359861#4f1653c182ca4488f49426f8ee1bf26cc5164a981096c45abc1adaba54bd0399 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 05 Jun 2024 23:26:13 -0000 https://status.ppro.dev/incident/359861#22a50ac5628c414d1e069f6d953cf6f9ec3a95dfa2a731e2576142cdf14610a6 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 05 Jun 2024 20:48:13 -0000 https://status.ppro.dev/incident/359861#4dffad52793f0188d589b0965d710d54f103fc5d8ac1b04ffe3df7a3ddb6d243 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/359861 Wed, 05 Jun 2024 20:40:56 -0000 https://status.ppro.dev/incident/359861#03953ffe30fac5f5206a379ffc2c7bc58672335cdbaf4328ffcc508ed38de2e3 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/359861 Wed, 05 Jun 2024 19:15:19 -0000 https://status.ppro.dev/incident/359861#776e1ede1298a1df8230729e4988f535e85bf30353638c23b060a5c0c875ec9f BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 05 Jun 2024 19:13:51 -0000 https://status.ppro.dev/incident/359861#3db90b56aadd4e55704bbf0942d50825f07f715383416bf3c6fa1b7280829d64 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 05 Jun 2024 15:55:51 -0000 https://status.ppro.dev/incident/359861#9175c8009fb93cb56fb1acaacee7fdd68ad562e08cc547e9775021b91c7f8afe BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 05 Jun 2024 15:52:22 -0000 https://status.ppro.dev/incident/359861#c8597c4a6cbc9475bbe87f0bd550c80ff088a75df0dd4d0d881d8eccbd23d6dc BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 05 Jun 2024 14:26:01 -0000 https://status.ppro.dev/incident/359861#99e504f0114e55e2f3166704a0d90374ae73142cd557db4fbd65e95b0a5134e6 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 05 Jun 2024 14:24:33 -0000 https://status.ppro.dev/incident/359861#dc70e4aa080f7e05c81b16e025585229655b2fc1d2bfc28f00632b100121481d BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 05 Jun 2024 12:16:23 -0000 https://status.ppro.dev/incident/359861#665e229680ed68449ba66f4bc2791d7c19776864ff158617754790ac50fe48ef BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 05 Jun 2024 12:09:02 -0000 https://status.ppro.dev/incident/359861#6fcd2bf06f21a74ddb90713bfefaf0173f1292474c296c743180974527e8cb90 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 05 Jun 2024 11:55:04 -0000 https://status.ppro.dev/incident/359861#c1af0fb0a5328f44421bf220ea383f581df5f371bd6c346b17dbba4d882c6e6f BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 05 Jun 2024 11:47:35 -0000 https://status.ppro.dev/incident/359861#9c80cd681b613022052f08503d26d8f49ab7a9872dd8ee06293ea9113133e050 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 05 Jun 2024 09:14:30 -0000 https://status.ppro.dev/incident/359861#ba9ce8ca8e2685abe1cfadf59c4f62c1ba5c055f8fc618c0589f6c3faa8a7efe BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 05 Jun 2024 09:07:19 -0000 https://status.ppro.dev/incident/359861#e4a2fd548fec507870a2a9c7df272724b8d2b9824b7c0697fd1e8d73f25ace74 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 05 Jun 2024 04:06:01 -0000 https://status.ppro.dev/incident/359861#aa728c3c4aa2db6295bae526bee11dd673e0cb471fc14bf941d0c6e6eedc8336 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 05 Jun 2024 03:53:25 -0000 https://status.ppro.dev/incident/359861#3b52e646d6e83087b812f9cf4469c2e94759fb3428f5be44474f57f1b4e7ab3f BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 05 Jun 2024 02:10:55 -0000 https://status.ppro.dev/incident/359861#7b8bcf738b12cc2938635607ae6d2f3fb3741d9ab5de030536a34e1ac9c41dec BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 05 Jun 2024 01:58:26 -0000 https://status.ppro.dev/incident/359861#7f2899dcdcd0d598e96bc40ece6f688f806df77e1d15114972c048467ff78d1a BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 05 Jun 2024 00:22:42 -0000 https://status.ppro.dev/incident/359861#807f9144a9699c4b2fe7d36cc85529abb2650cb72aa0c820dfa085a439597934 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Tue, 04 Jun 2024 23:55:37 -0000 https://status.ppro.dev/incident/359861#bfd9af89ee8f7e925a1c884773cc51ba7eef7f1119c1975d154df88cf05e696f BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Tue, 04 Jun 2024 19:54:04 -0000 https://status.ppro.dev/incident/359861#f88a721064dd757ef5e338ac9054edc98a98fbcd1b7d2e8a5aef03ff4996a521 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Tue, 04 Jun 2024 19:45:55 -0000 https://status.ppro.dev/incident/359861#5a947b17f338b4b494c69999a3d04d1c4b77ffb9551396e470023e0d3d3da2ab BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Tue, 04 Jun 2024 17:32:51 -0000 https://status.ppro.dev/incident/359861#2644076ee69358369d594125b4a491f29dacf318d8dd34d1bce9d74a21c7a36f BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Tue, 04 Jun 2024 17:26:03 -0000 https://status.ppro.dev/incident/359861#6b4f25e184584c7d25ef077678816df0afe0ad60a9e7e79a6b02c21dd4d15fbb BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Tue, 04 Jun 2024 17:09:09 -0000 https://status.ppro.dev/incident/359861#f8c91ee90c10e089e3af6aa5a3a92f10ff204ac916ae77e4937eec2d126b088f BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Tue, 04 Jun 2024 17:00:34 -0000 https://status.ppro.dev/incident/359861#eb13b265b10233522a78b15df57cb91b39c8960526837ce8e9c32e32d22b1a53 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Tue, 04 Jun 2024 13:30:01 -0000 https://status.ppro.dev/incident/359861#fc86a3a0b577cabae2020ebfd96e4694b26fe41503ae023f4c5617c35ab2cb9c BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Tue, 04 Jun 2024 13:28:51 -0000 https://status.ppro.dev/incident/359861#29812f24a633ac4c29e93dc5f413be33b90a7d1155d8d543c9b51ae1121e7099 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Tue, 04 Jun 2024 12:20:55 -0000 https://status.ppro.dev/incident/359861#0c209ccdba81e01b5cfc7d719629e7170a79077af8deec2d42c59b810cb06519 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Tue, 04 Jun 2024 12:19:23 -0000 https://status.ppro.dev/incident/359861#8bd8071685058f01e800dfa3cdc783533029aefcaeaef357157a533c722a1371 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Tue, 04 Jun 2024 12:17:59 -0000 https://status.ppro.dev/incident/359861#0e503736fb6009b243c45b9372e3ce6f2dd1bb082b43b0856e9b4d4093855ae3 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Tue, 04 Jun 2024 12:10:43 -0000 https://status.ppro.dev/incident/359861#9a4944c71ea2fab7f8a1264966c0554b7fda33e320f1e14e291d9be644d51fcc BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Tue, 04 Jun 2024 08:06:45 -0000 https://status.ppro.dev/incident/359861#47d5a6238be04d51cc8e5cbd05489f7770e7dd33061c86b10cbe1e28a40887be BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Tue, 04 Jun 2024 08:05:10 -0000 https://status.ppro.dev/incident/359861#3e54ff11a2ccd3608aa66b32b3e69dee79500a175b627975e0a0bab6a68b930b BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Mon, 03 Jun 2024 21:32:26 -0000 https://status.ppro.dev/incident/359861#3662d20a9ff9a3699e006a0147aa8a2fff0f1c7894acecebd1ccb13b77d8aa9b BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 03 Jun 2024 21:30:53 -0000 https://status.ppro.dev/incident/359861#1727fc95aed0bcc57f1959961b63aa0d5b30bc39dffa84b9d36ff63f9a656ed5 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Mon, 03 Jun 2024 06:09:29 -0000 https://status.ppro.dev/incident/359861#94f777596036368a3186087887c1cfe746737bc7615ee171c6a7d9d9209ce681 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 03 Jun 2024 06:07:57 -0000 https://status.ppro.dev/incident/359861#d6ca9ce09efd4fae83a702e8a8774db63689ae319acbd90ae8752198ec5ceac1 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 01 Jun 2024 23:20:36 -0000 https://status.ppro.dev/incident/359861#36658268be4f9403a0c6238ad5911762f5e2205dada65a9210ef37d78d9fb636 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 01 Jun 2024 23:17:02 -0000 https://status.ppro.dev/incident/359861#1f3511e6213d2e7c47ec43241a56ca402a053b011931211bab36b54e250fb527 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sat, 01 Jun 2024 18:32:44 -0000 https://status.ppro.dev/incident/359861#3b6b457665ca07b81b9455c678a20a94872b7c5c00a5553842bc9879dde42b54 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sat, 01 Jun 2024 18:29:12 -0000 https://status.ppro.dev/incident/359861#9c2978914a2f47a74cbe45041a4fd3eb3f48ae005152cb66bdcd325936b3a46d BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Sat, 01 Jun 2024 15:40:44 -0000 https://status.ppro.dev/incident/359861#6f7abbe6f871edf785ca5cbe3f5af1aeeacb86f8f531a125150aa8cfed6332af BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sat, 01 Jun 2024 15:37:03 -0000 https://status.ppro.dev/incident/359861#d096966eec071437e3d6292b893a944797b1fb85d0d064b1989f258db785bca0 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Sat, 01 Jun 2024 04:17:40 -0000 https://status.ppro.dev/incident/359861#46641a0f94ef91776208b20c4cceffc141b44f769036b708d9d3184ef9709cdc smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/359861 Sat, 01 Jun 2024 02:35:41 -0000 https://status.ppro.dev/incident/359861#f6c60eedefad82703f02989f11fee52be29bb40d512f2cf6b2edde04b24471aa smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/359861 Sat, 01 Jun 2024 02:02:24 -0000 https://status.ppro.dev/incident/359861#e3a5bac8b81a8c946223280b32d5bcff0ee4035558295515d7baf011751c8988 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/359861 Sat, 01 Jun 2024 01:39:28 -0000 https://status.ppro.dev/incident/359861#a6475371087373d24cfc105038a1e25bdf95b911adc156c4d85d833dcb3b13e7 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/359861 Sat, 01 Jun 2024 00:58:52 -0000 https://status.ppro.dev/incident/359861#7c638651d1ebbd8e8f198f9a8d73edaac99016536dfd67c7fbdffd4d6054547d smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/359861 Fri, 31 May 2024 23:40:41 -0000 https://status.ppro.dev/incident/359861#364b5c66198f56f5f14bbbffa6be5ef0e458eb11214ca835280236e47d34dca5 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/359861 Fri, 31 May 2024 22:09:45 -0000 https://status.ppro.dev/incident/359861#057a33523cb5f5caf1370c4b8a119a39a105aba88afd6c1a6e4de8f718b1a7c7 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/359861 Fri, 31 May 2024 21:27:04 -0000 https://status.ppro.dev/incident/359861#c741d69726dd00466489c1b1f5dc1bf9d873587ff1c5cad05dac4e09eb3f7548 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/359861 Fri, 31 May 2024 21:19:44 -0000 https://status.ppro.dev/incident/359861#584478b6e50944a95dcbab15672ad9f2a2c4b1b0f479d1c73a940aba95fb6191 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/359861 Fri, 31 May 2024 20:52:07 -0000 https://status.ppro.dev/incident/359861#9f7feb6dea39eec401067541f029558e49180911d75a78af331b58c3251d806a smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/359861 Fri, 31 May 2024 20:14:55 -0000 https://status.ppro.dev/incident/359861#69ae526bf3dcd5011c1ddf2c9e702051728fc2d136e2b528504dd8625692e9c4 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/359861 Fri, 31 May 2024 18:46:00 -0000 https://status.ppro.dev/incident/359861#3f4bc6433f8703a5bdcbc81348b6111ace5901985556bfe30d64cb68c10a717f smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/359861 Fri, 31 May 2024 18:18:07 -0000 https://status.ppro.dev/incident/359861#80ccc281d6d8b5228afe69a41974145144fdf8b3667215fb70a302cfc07d5bbe smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/359861 Fri, 31 May 2024 18:07:20 -0000 https://status.ppro.dev/incident/359861#701bbf10964a89433aff03de5c331d1bf7a02e07d704b1c35695698450db4b3d smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/359861 Fri, 31 May 2024 10:06:53 -0000 https://status.ppro.dev/incident/359861#e33ca79fb6c587f8fb58ad0f38ece617b24fd1a71142a54c5f76364c3945be78 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Fri, 31 May 2024 09:59:38 -0000 https://status.ppro.dev/incident/359861#e1560a0ebd8d1f196e980e4b4f742424deb67001a30a5fe7816fc5d9b36a5f70 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 29 May 2024 12:32:29 -0000 https://status.ppro.dev/incident/359861#8818a138dc8cac3afcade699e7cab9b0b7b7239a8e39fa11e1a8d184bade79dd smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/359861 Sun, 26 May 2024 17:08:05 -0000 https://status.ppro.dev/incident/359861#1cc696f5874a615f16bf4ef8d45a3a64c6dd714cb2a4ddc37d8f7f1215488756 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sun, 26 May 2024 17:04:26 -0000 https://status.ppro.dev/incident/359861#46c090fd82e88e0edde07e81440489e6ebdb4ad5af54a700c10e62c2eb4a0ff6 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Fri, 24 May 2024 18:50:36 -0000 https://status.ppro.dev/incident/359861#a4a45a7af14c3dfb24f7a87e861c39b5849cf15a5173017f9acd4f36a1c3d45c BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 24 May 2024 04:45:20 -0000 https://status.ppro.dev/incident/359861#ea357f326e92e472d600bcd210b085b99199fe8124eff3c9967597e7894b4751 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 24 May 2024 03:18:09 -0000 https://status.ppro.dev/incident/359861#ddb3ef92adc88699c981e5822fc27c42cab8a774a19102eca82779f65d239fe7 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 24 May 2024 03:00:30 -0000 https://status.ppro.dev/incident/359861#3a594ea935c6fc0b75b02ebf7ad22153b1583e6a9358c0880942cedefa07ed8f BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 24 May 2024 02:38:08 -0000 https://status.ppro.dev/incident/359861#9468edf3cd0a8a0c1e92717d9ff4896726dddf889eb5ac940f01734d5040fb0e BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Thu, 23 May 2024 19:15:21 -0000 https://status.ppro.dev/incident/359861#3f4520085ff05c010fb0a1736f9094be3d17efe54fe5e00c877129ffe2025095 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Thu, 23 May 2024 17:14:08 -0000 https://status.ppro.dev/incident/359861#6196e128911721ea72960eddc49a2cb702f3aec11622e37a5856e37f9540bc39 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Thu, 23 May 2024 17:12:29 -0000 https://status.ppro.dev/incident/359861#ae28c1a437516c3770ee0391538e789f9bc5ec311b24144e3b39b141b5782c79 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Thu, 23 May 2024 05:05:41 -0000 https://status.ppro.dev/incident/359861#ba4120782c240cdda568a717922d474f9928d7869076f7b37cb5098988741e06 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/359861 Thu, 23 May 2024 05:01:32 -0000 https://status.ppro.dev/incident/359861#a65e446d885362f9b00e91fbe5d09d891f69eae02df72f48fdfc63f34ae4d5de BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Thu, 23 May 2024 04:49:13 -0000 https://status.ppro.dev/incident/359861#f8e6ce8a278f13cfa0678605d5cd5011c225d3fdf38b1d52f3624f14b81980a0 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Thu, 23 May 2024 04:36:25 -0000 https://status.ppro.dev/incident/359861#44d3078f9c01272d77de76e0ffdeb8bd06f088a9ca17c4f576a9fed636f05f05 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Thu, 23 May 2024 04:32:54 -0000 https://status.ppro.dev/incident/359861#6b9f9fb762a3187ad32f85d7ba4b4671abb693754a68d1906f46691a6b1e80db BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Thu, 23 May 2024 01:20:41 -0000 https://status.ppro.dev/incident/359861#23c758aa6b288ae05446284ca5071c14ed8fcb8dbaed5abe5f6a293366336661 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Thu, 23 May 2024 01:19:13 -0000 https://status.ppro.dev/incident/359861#76652c8270773bda2c8014f0203ce2bf21f5b74130ef56ed71a6da0db30b5c02 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 22 May 2024 21:46:31 -0000 https://status.ppro.dev/incident/359861#ce26ffdd2096488df5ccd57e3ae4b3c67534148372e411256ee3498f16bce0cf BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 22 May 2024 21:43:08 -0000 https://status.ppro.dev/incident/359861#b32f15acd57c19a964aa894b34066ce9c7cd57e0d879b5f983ba8c779e547daa BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 22 May 2024 19:30:42 -0000 https://status.ppro.dev/incident/359861#00a18a3cb87790f688f23742335ead1403961a08c7aadd7bd4bcd12c1c2ddbd3 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 22 May 2024 19:29:13 -0000 https://status.ppro.dev/incident/359861#8c037a543fae434906ed66a1ac1f2dfb5175a8f6bc30f1563f41e48cd32fbcf9 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 22 May 2024 03:09:24 -0000 https://status.ppro.dev/incident/359861#6ea15b6eb2c9f00908cead3431ce540b1140315f1f1d8d96e1195f99d5ed8c24 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 22 May 2024 01:27:13 -0000 https://status.ppro.dev/incident/359861#5402bbe3cb5d142d7f7cfcc9c7806e8032ae6625dc4fe4ccf40f87ca6c53c724 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 22 May 2024 01:01:34 -0000 https://status.ppro.dev/incident/359861#f034574699e82462e61a0e3ec89c511ce6c7323ab823412ccab15a7968202ca2 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/359861 Tue, 21 May 2024 23:05:57 -0000 https://status.ppro.dev/incident/359861#7fd30b3a1d70e4ff2bb3f9524c2139b36eb9774ae2aaabb6b0f8388d9d77f4f8 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Tue, 21 May 2024 23:04:20 -0000 https://status.ppro.dev/incident/359861#c33fd86c53d5be25db6a1b5b0ed21bad3bef3e80b7ab41ecce4b5104f656d4f2 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Tue, 21 May 2024 22:29:15 -0000 https://status.ppro.dev/incident/359861#4d544ee56bf757a9f29fadcd6bc77dd5b6784533e90328220ae999e10df8ef72 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/359861 Tue, 21 May 2024 21:23:36 -0000 https://status.ppro.dev/incident/359861#07dd20c97460ac54fccb8f824babdad7bfabdf80f1a7da2dd9b00f964e085a81 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Tue, 21 May 2024 21:22:08 -0000 https://status.ppro.dev/incident/359861#5cd17cad24ef8e34cc0f9843e6375c42405adc56d0f9075e73e051380ba07c76 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Tue, 21 May 2024 15:25:48 -0000 https://status.ppro.dev/incident/359861#f0728b322fcec9f649c81bf9f6be03f323863bd1e29a6bca834d76c30815c3e7 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Tue, 21 May 2024 15:24:24 -0000 https://status.ppro.dev/incident/359861#c1290bb6eb96d25b5d0e42450175172bdb21b949e222fe370e7b298b64107761 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Tue, 21 May 2024 14:58:34 -0000 https://status.ppro.dev/incident/359861#0d66f59ac4aefb08bc3e6c995e4255f8e6d914e8d67c60739b8ffae61c295098 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Tue, 21 May 2024 14:57:07 -0000 https://status.ppro.dev/incident/359861#84e3009d4f3620c05bad04fc20c1adcd970df1ef37ce43b5d0a8922703d9ea27 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Tue, 21 May 2024 03:58:22 -0000 https://status.ppro.dev/incident/359861#e9547d539a387c619e170c87be99898b1d7a1d49bfa1357698acd119e338613a BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Tue, 21 May 2024 03:49:48 -0000 https://status.ppro.dev/incident/359861#0ce23c8b50ec3b3f389f183dc65b342ba230ff04e63394bb61cc89cb0e9bcf9b BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Mon, 20 May 2024 21:27:01 -0000 https://status.ppro.dev/incident/359861#8db90b75160af54d734d89c2e42f7be9d08f99bd59087115270f9121d819749c BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Mon, 20 May 2024 21:25:29 -0000 https://status.ppro.dev/incident/359861#fe6c332efdf0a7193f48901dad87f7ae06e42117eac0f2f9ecb0fb60709d32fd BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sun, 19 May 2024 17:53:46 -0000 https://status.ppro.dev/incident/359861#74a25475ea1de15bd7215976d53676689cf610832adf2b6da630357d8981ca23 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sun, 19 May 2024 17:46:35 -0000 https://status.ppro.dev/incident/359861#ae19814847480a812aa8dc61a2c533b24be873e65c2bfda174979accf4837ffb BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Sun, 19 May 2024 16:18:50 -0000 https://status.ppro.dev/incident/359861#220344441fece4ef2453059c8058b05b9e2367648663c2b9d0feca612d0cd0c7 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Sun, 19 May 2024 16:11:35 -0000 https://status.ppro.dev/incident/359861#c900bca73effd5552c1500c611c9d8194eff584e0594f5608976d8d7f762b6d7 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 17 May 2024 04:37:59 -0000 https://status.ppro.dev/incident/359861#25602860e013808f3ebdc4d8ca9776829206158a14b00becc946bc02d2d6a759 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Fri, 17 May 2024 04:36:40 -0000 https://status.ppro.dev/incident/359861#db19ca00796bbba0ad94c62cb614af730e9ea4d322789732859712cd852df7ff BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Thu, 16 May 2024 23:34:19 -0000 https://status.ppro.dev/incident/359861#54a262b559bde9309dc7f1e2bf8a87917990d40899d27a90f58b43b269b59010 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Thu, 16 May 2024 23:30:48 -0000 https://status.ppro.dev/incident/359861#8e389731f37531adf3f36f69b7cfe0488c08f6b3391920e48d9272476eef956c BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Thu, 16 May 2024 05:55:18 -0000 https://status.ppro.dev/incident/359861#661bf93ed5361ce0e6052ad992b2b81a52e384af33b8fc659cccefcf4c1a2857 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Thu, 16 May 2024 05:53:46 -0000 https://status.ppro.dev/incident/359861#dc2adb3bc83de8c3b02bf52c6b5e9cb6c8f0ff024a1ae664f11c2d2686caa01c BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Thu, 16 May 2024 02:11:35 -0000 https://status.ppro.dev/incident/359861#504f4dc5a266483f75808e96b5bb47fd927ca784c900f2c3d9e3e5ebe18ef3c8 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Thu, 16 May 2024 02:08:14 -0000 https://status.ppro.dev/incident/359861#dfdeb276d829bc720e1336451f3f446042a0320efce1cf9260fbc985add6422c BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Thu, 16 May 2024 00:50:21 -0000 https://status.ppro.dev/incident/359861#5d2a9dbfbf5a3607eea08908ef1c48d1fc02833fb0eecc0de99f5b12dae3b947 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Thu, 16 May 2024 00:23:14 -0000 https://status.ppro.dev/incident/359861#e3b90b9913332355114aef2d64242393cb894d1b9f5b1c9fdae60badbb3f0afc BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 15 May 2024 23:30:18 -0000 https://status.ppro.dev/incident/359861#8b6937ce2e9e0aa4b29c0534cf6833686dd86fd2ade7f0af0ad37fd2b83a1ff9 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 15 May 2024 22:08:49 -0000 https://status.ppro.dev/incident/359861#6a66cd151f9fa66817f16c5c3b68088e7bc7c4e77323d76adce9491a841e62ed BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 15 May 2024 19:56:36 -0000 https://status.ppro.dev/incident/359861#6b71874ac08fb1188cd35da814212264e0bfdc0317cf7fcaa5db0e96c5ffba03 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 15 May 2024 19:33:15 -0000 https://status.ppro.dev/incident/359861#46d3db8fc3c5d03a4b40be773941dc399f5fb6521217445a5ecdb65e54a0f70d BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 15 May 2024 06:58:01 -0000 https://status.ppro.dev/incident/359861#45d94f672203a6a6ccd06746eec099324b52820ad5e822acac2994c3c959190a BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 15 May 2024 06:50:32 -0000 https://status.ppro.dev/incident/359861#8fcb0588b00555436a73bd99e2b440bfc8802f8983c22f924a4c6edf55aa96fa BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 15 May 2024 06:04:00 -0000 https://status.ppro.dev/incident/359861#d2ab04845c5641a228443f62757e76880bae45f84f808385c2f4bc1bf86c7734 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 15 May 2024 06:02:27 -0000 https://status.ppro.dev/incident/359861#cb0b4f2f4ec150e9294ab1a55557bdb46a7675319e2061e2309234b0c2df62e4 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 15 May 2024 05:21:38 -0000 https://status.ppro.dev/incident/359861#12a17b997ae49460c7b3090a0307ebf08708e6815a09ad8a813dd8dd924a1a0e BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 15 May 2024 05:20:08 -0000 https://status.ppro.dev/incident/359861#8fcd9bfacc63622485b2acfc3b39c9eb3dbf3f3d1a55138809bf3b615da7ab03 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 15 May 2024 02:09:27 -0000 https://status.ppro.dev/incident/359861#b6dbf7922cec43ef802809d817b39c089b3c7beca6d31ace82f5b03a268058e2 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/359861 Wed, 15 May 2024 02:02:17 -0000 https://status.ppro.dev/incident/359861#3f44c763fa6ce7447ccfef0336dc77166497b893a2c3d603e183e425b4617ddd smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/359861 Wed, 15 May 2024 01:59:37 -0000 https://status.ppro.dev/incident/359861#ef8079408dcc7618da4b22b8a0d9ced948ed53a77aebb2329a57ce1e1723d332 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/359861 Tue, 14 May 2024 23:47:16 -0000 https://status.ppro.dev/incident/359861#d0d8513c28d07a1be458edaf1ad3c53df128c80a61a64f263d0dd0c9c8e5b672 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/359861 Wed, 08 May 2024 10:18:40 -0000 https://status.ppro.dev/incident/359861#3485abe2a08cf1fa1c52b3b02788b5456d96cebf5ec4344c72a1b5e5e8fe07cd BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 08 May 2024 10:11:26 -0000 https://status.ppro.dev/incident/359861#6d0259bb5e7e25d33fd1035dfff9bfe2053b47918f93c54ce9df2d33f8f9c564 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Fri, 03 May 2024 05:22:54 -0000 https://status.ppro.dev/incident/359861#6ce69810485bef9433e0056948a2982e0e51abe24ff7488259385b2d00712723 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Fri, 03 May 2024 05:21:28 -0000 https://status.ppro.dev/incident/359861#9c7cb432b9bf6f3ed1b86e7ba7b007daa9da46431243051cea3f221a0f9bfda5 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Fri, 03 May 2024 01:20:48 -0000 https://status.ppro.dev/incident/359861#610c76e0959c7eb333b0e44a3e43cee5f9c907297bf46580564bbe07d3a37254 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Fri, 03 May 2024 01:19:09 -0000 https://status.ppro.dev/incident/359861#add079060867b18b9e98ea8bb39083d21cf30c886b5cde3b56a94c97a10f78c4 BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Thu, 02 May 2024 19:07:38 -0000 https://status.ppro.dev/incident/359861#65925ef7ed858d659ddc0383dc4a269331cd074919da1cc92b98e78bcfe15ddd smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/359861 Thu, 02 May 2024 18:55:29 -0000 https://status.ppro.dev/incident/359861#af69243ed32ed7fcb0b1d5a9752723c865436adb9c6dfc65c2d223aa106a68af smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/359861 Wed, 01 May 2024 23:58:35 -0000 https://status.ppro.dev/incident/359861#95eafd3de14b9c5a5525af133968fc052defe8432545aa5b8f385215c35f8bf2 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 01 May 2024 23:51:31 -0000 https://status.ppro.dev/incident/359861#4f85743e688678e972affebcf11ff5f9cf217062c4f1340b9eac61a60b5d205b BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 01 May 2024 12:12:23 -0000 https://status.ppro.dev/incident/359861#d5b93cf5117955812e63123af1327b519b437acd6e36ceb513d3a64992ee7069 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/359861 Wed, 01 May 2024 05:59:28 -0000 https://status.ppro.dev/incident/359861#6ce067e95e88d6bb63cf81d0765b8c117763ad3c4b22995c979be58d4a550294 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 01 May 2024 05:56:02 -0000 https://status.ppro.dev/incident/359861#20f25134a89fa48af05d52cf613b79b84608edb5d8d65d4279bc5a456d6b2bf0 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359861 Wed, 01 May 2024 02:33:35 -0000 https://status.ppro.dev/incident/359861#9f47b9dc5b052f143bfcc915a6863137b8e031a0ef47875e8b6759c0018fb0c9 BrovaPh2 ups status went down. https://status.ppro.dev/incident/359861 Wed, 01 May 2024 02:32:02 -0000 https://status.ppro.dev/incident/359861#2ba709d42dc28eb6832bb2ac9a5c9c5377bfea5d6e61d8126fb4840cbd11dccf BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Tue, 30 Apr 2024 07:14:47 -0000 https://status.ppro.dev/incident/359861#cc7f4c3eeefdda5767ca92022181104d42bb10c5d4c794637282dee8da1af1a6 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Tue, 30 Apr 2024 07:07:40 -0000 https://status.ppro.dev/incident/359861#f48da1edfa0866ffcce1ef5a3710703190b36374f7bd0ddce6ba38acbf3f993a BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 24 Apr 2024 22:55:24 -0000 https://status.ppro.dev/incident/359861#51335a2c0ed39f9d486d900b20ad887ebe7964d3422af7b18ff6e8a359334346 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/359861 Wed, 24 Apr 2024 22:28:17 -0000 https://status.ppro.dev/incident/359861#9ec81cc755e8c7e68a00728e3debc0ecc0e7d096bdfb05860b1e5e5b10c24eea smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/359861 Wed, 24 Apr 2024 22:11:04 -0000 https://status.ppro.dev/incident/359861#30d0f30d61d047d14e2855a4ab38d2097cdc47821b75924d764c94589d1c8188 ppro: ovm myst server went down. https://status.ppro.dev/incident/359861 Wed, 24 Apr 2024 22:10:20 -0000 https://status.ppro.dev/incident/359861#b2906b58aecc86bf5b86d7898db431b926c832def1adbb51ac2469b72ca83102 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/359861 Wed, 24 Apr 2024 21:05:25 -0000 https://status.ppro.dev/incident/359861#b7d72ebc284556d50929f103208f3920c40d72a549675e4a4b1dc7e242b1c26a BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 24 Apr 2024 20:58:12 -0000 https://status.ppro.dev/incident/359861#f82e4892954f4ba74bc2edb138e297177339d7abbd3a16e028794f853c74b2be BrovaPh ups status went down. https://status.ppro.dev/incident/359861 Wed, 24 Apr 2024 00:44:13 -0000 https://status.ppro.dev/incident/359861#e35f39a22820f32f76858e4663592a916f7516698a269ab13fb997e0f19aa403 BrovaPh ups status recovered. https://status.ppro.dev/incident/359861 Wed, 24 Apr 2024 00:37:03 -0000 https://status.ppro.dev/incident/359861#9c461aeb78fffcff7dcdb40e41e3a66c786aa1fb6715f181d68a16455342aa8f BrovaPh ups status went down. https://status.ppro.dev/incident/359630 Tue, 23 Apr 2024 12:28:54 -0000 https://status.ppro.dev/incident/359630#b908290aaa4714761b0ef0bdebc19993e25dd0471495a0ca65ff201e1999bd1e BrovaPh2 ups status recovered. https://status.ppro.dev/incident/359630 Tue, 23 Apr 2024 12:21:40 -0000 https://status.ppro.dev/incident/359630#a473bb6eb0493391968e3698a9cc9a58b485aa007bcdc5f61a8e1c8f3380d0bb BrovaPh2 ups status went down. https://status.ppro.dev/incident/358449 Sun, 21 Apr 2024 21:28:45 -0000 https://status.ppro.dev/incident/358449#d28610ce060a48938d22eb74ed8e67f1be462a3f75c83b183e090c86da555097 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/358449 Sun, 21 Apr 2024 21:21:31 -0000 https://status.ppro.dev/incident/358449#8080edf9bcd9e44188079aed2776b387e5edace775635c75d757cd2b457b87b9 BrovaPh2 ups status went down. https://status.ppro.dev/incident/358449 Sun, 21 Apr 2024 05:44:18 -0000 https://status.ppro.dev/incident/358449#a5f7a9ea4ff6348615c971fbc25dd5798c09c842f538e9068d245e3b04bcfe8f smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/358449 Sun, 21 Apr 2024 05:42:09 -0000 https://status.ppro.dev/incident/358449#7f3e5a693825d42d5892b151ae1dd660aa2013c881de3b6beffea0dd2f1f2132 ppro: ovm myst server recovered. https://status.ppro.dev/incident/358449 Sun, 21 Apr 2024 05:05:17 -0000 https://status.ppro.dev/incident/358449#efae78388efeef34254e1f1baf8d187523c1e08a0019758f788146408599a850 BrovaPh ups status recovered. https://status.ppro.dev/incident/358449 Sun, 21 Apr 2024 04:39:23 -0000 https://status.ppro.dev/incident/358449#0c089242b192ec4caaa3d865746f8591d3632ceba88f8051bcf44960aeae7317 BrovaPh ups status went down. https://status.ppro.dev/incident/358449 Sun, 21 Apr 2024 04:27:01 -0000 https://status.ppro.dev/incident/358449#641a176373b9920b0cfacafefcb5edb3dbf726f1ee9bc0a64058cd6a07bc5bad BrovaPh ups status recovered. https://status.ppro.dev/incident/358449 Sun, 21 Apr 2024 04:16:53 -0000 https://status.ppro.dev/incident/358449#d22becdce30a4c6b73b8459e9b56d7eac575217d0b44ce63c48e7e7585d50abf BrovaPh ups status went down. https://status.ppro.dev/incident/358449 Sun, 21 Apr 2024 04:07:00 -0000 https://status.ppro.dev/incident/358449#4cc7b947363ec73b4dae153304a43de60c782e9cfefed2437fbe82f88d92cf6d BrovaPh ups status recovered. https://status.ppro.dev/incident/358449 Sun, 21 Apr 2024 03:32:11 -0000 https://status.ppro.dev/incident/358449#5091ec6cbe1fbcba20c5555f88308c9a129a5cdcb3ea1dedb8c094ff5dd72d2e ppro: ovm myst server went down. https://status.ppro.dev/incident/358449 Sun, 21 Apr 2024 03:19:05 -0000 https://status.ppro.dev/incident/358449#9b44525ea767280dc6e5daa1066d8b1c522af2f4c012347b279e21cb2d8a051d BrovaPh ups status went down. https://status.ppro.dev/incident/358449 Sun, 21 Apr 2024 02:56:51 -0000 https://status.ppro.dev/incident/358449#2309002df2f3099e9c4785f13c643803c38c44ce0029cfeac7c09a81c0f14c3e smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/351214 Thu, 18 Apr 2024 07:40:45 -0000 https://status.ppro.dev/incident/351214#da1b709260c07f2665bca02e2d38eccb8fb46c4195a50260f08b454cae8f91c5 ppro: ovm myst server recovered. https://status.ppro.dev/incident/351214 Mon, 15 Apr 2024 10:05:05 -0000 https://status.ppro.dev/incident/351214#36f4868ec63abc45e6576cfcc0ae5b1e3c05346c7485d44255a24e65be81c74b BrovaPh ups status recovered. https://status.ppro.dev/incident/351214 Mon, 15 Apr 2024 09:57:50 -0000 https://status.ppro.dev/incident/351214#fed21f9e3a1003a3ef0e5bab98b0f58b32ac1ece4a7941322cd5662ae9ae6c7b BrovaPh ups status went down. https://status.ppro.dev/incident/351214 Fri, 12 Apr 2024 00:59:12 -0000 https://status.ppro.dev/incident/351214#496028332dbfb621a9655ecf2e679a8f8272efa0181e9b4ff9a177d9f7a6ee66 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/351214 Fri, 12 Apr 2024 00:47:05 -0000 https://status.ppro.dev/incident/351214#af02cc58362aa4dac9d245482593d01000bd155401657c289d55471a5196f13a smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/351214 Thu, 11 Apr 2024 04:32:05 -0000 https://status.ppro.dev/incident/351214#e2c1832042f8c1741142cf5d331bcaa71a363c288ecf9a9d7ffd7dcb84d47135 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/351214 Thu, 11 Apr 2024 04:25:00 -0000 https://status.ppro.dev/incident/351214#163c2558c6f67fbd5a1f42d346e8533dfa3f3bedf9da56e7c2a28f7c3acd3c8f BrovaPh2 ups status went down. https://status.ppro.dev/incident/351214 Wed, 10 Apr 2024 06:27:01 -0000 https://status.ppro.dev/incident/351214#d997202cdcffda9e75a30690b9423c50a2d78b0dcdd2751dcfad1f72fece51e1 BrovaPh ups status recovered. https://status.ppro.dev/incident/351214 Wed, 10 Apr 2024 06:19:30 -0000 https://status.ppro.dev/incident/351214#6dce94df947649163d3646f114e62709b05edf15e2a625f8f49c46e82991f5cd BrovaPh ups status went down. https://status.ppro.dev/incident/351214 Tue, 09 Apr 2024 09:20:41 -0000 https://status.ppro.dev/incident/351214#2a4cee9b6ac29d09fc2b60c7281d1d42eba4cfdd359380e35b236fc82518ebf4 BrovaPh ups status recovered. https://status.ppro.dev/incident/351214 Tue, 09 Apr 2024 09:13:00 -0000 https://status.ppro.dev/incident/351214#d2d95fffe989e18b7c7e8df4b9d38ae20b8ea93f2a0d32ce61ab0b065fe80d94 BrovaPh ups status went down. https://status.ppro.dev/incident/351214 Sat, 06 Apr 2024 11:10:30 -0000 https://status.ppro.dev/incident/351214#0e459a3993a5a68f39721cb657e113e315be2e21c468df5e62f3379b6cfa42e0 BrovaPh ups status recovered. https://status.ppro.dev/incident/351214 Sat, 06 Apr 2024 11:03:20 -0000 https://status.ppro.dev/incident/351214#94371f081738e34dd8caa5c912051c2356950d971cfab6439e167bd207802134 BrovaPh ups status went down. https://status.ppro.dev/incident/351214 Fri, 05 Apr 2024 14:31:53 -0000 https://status.ppro.dev/incident/351214#dd2ca5b4d26addf375adf484931c362a699df6f5bdff59173ad9e7d08f17f12a BrovaPh2 ups status recovered. https://status.ppro.dev/incident/351214 Fri, 05 Apr 2024 14:24:43 -0000 https://status.ppro.dev/incident/351214#42d7a69a8165363783264ce6cfcc4af7b5d74b55c13e010c88a861b856d374d3 BrovaPh2 ups status went down. https://status.ppro.dev/incident/351214 Fri, 05 Apr 2024 07:40:04 -0000 https://status.ppro.dev/incident/351214#175e684cfddf4908e474ab2d02117be310a000186a3010969c0b1078bbd5ef09 ppro: ovm myst server went down. https://status.ppro.dev/incident/350248 Wed, 03 Apr 2024 13:33:20 -0000 https://status.ppro.dev/incident/350248#1b2101245416919f612c5d1e6841af1835f9e725bd5362477f389d9829f4b60c BrovaPh ups status recovered. https://status.ppro.dev/incident/350248 Wed, 03 Apr 2024 13:26:09 -0000 https://status.ppro.dev/incident/350248#3b60b51b5a268f11f1f10320a0a928720fef645e78a50260722185cb4e664861 BrovaPh ups status went down. https://status.ppro.dev/incident/348483 Sun, 31 Mar 2024 02:39:43 -0000 https://status.ppro.dev/incident/348483#534653ba70cdb00f491c0c277c61f437b2c09e260d6a389e30f79ee7d54a3d88 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/348483 Sun, 31 Mar 2024 02:38:09 -0000 https://status.ppro.dev/incident/348483#4c801cde273a2823ca09f706471a189e83de3d56d626c953487c8991c6c33946 BrovaPh ups status recovered. https://status.ppro.dev/incident/348483 Sun, 31 Mar 2024 02:32:39 -0000 https://status.ppro.dev/incident/348483#7b396387fc3f35800b674e21f0eb38ad9c6044911c7e5ba8a36d5d988260f762 BrovaPh2 ups status went down. https://status.ppro.dev/incident/348483 Sun, 31 Mar 2024 02:31:10 -0000 https://status.ppro.dev/incident/348483#725b94e5a6d7c88d9390b6bca1e7bfea5f96df2db7105523705a8573da7b7524 BrovaPh ups status went down. https://status.ppro.dev/incident/348135 Sat, 30 Mar 2024 05:17:51 -0000 https://status.ppro.dev/incident/348135#b188539c3bbe99752abead909a312533683272821aabc9a3d151771e9c5c382d BrovaPh ups status recovered. https://status.ppro.dev/incident/348135 Sat, 30 Mar 2024 05:10:40 -0000 https://status.ppro.dev/incident/348135#1a83aa016a65f530fada0536c6956c5322d87496b9be7cf86c1bd575bcd8be43 BrovaPh ups status went down. https://status.ppro.dev/incident/346560 Wed, 27 Mar 2024 06:44:36 -0000 https://status.ppro.dev/incident/346560#bdd6b0e53b0f337c7d10167d45e02fcaa2dd2d10569c96b6f6fc3fd1f86f88f1 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/346560 Wed, 27 Mar 2024 06:42:55 -0000 https://status.ppro.dev/incident/346560#178f4194cda59e912699fef193a12a014fa938a3cc5e98464cdcc0f7b4428fbf BrovaPh ups status recovered. https://status.ppro.dev/incident/346560 Tue, 26 Mar 2024 23:30:39 -0000 https://status.ppro.dev/incident/346560#762a9ca481ecf4aa6cc88dbf24dd06b30c7e2b9c78b96d03126558a534c8d4e2 BrovaPh ups status went down. https://status.ppro.dev/incident/346560 Tue, 26 Mar 2024 23:27:27 -0000 https://status.ppro.dev/incident/346560#f1de6b5417211d336416328023604c5390b86222a995e2744bf9ef56e4e44ca1 BrovaPh2 ups status went down. https://status.ppro.dev/incident/345304 Sun, 24 Mar 2024 10:30:02 -0000 https://status.ppro.dev/incident/345304#7b763505249904a3d52f2f0d2ac3aece2b651aa53829d86d9a69a53b992f54e6 BrovaPh ups status recovered. https://status.ppro.dev/incident/345304 Sun, 24 Mar 2024 10:22:49 -0000 https://status.ppro.dev/incident/345304#c8a3b57864d2303fa2adb7636f79863fb2c831d3bd1e7859b85106418729ec73 BrovaPh ups status went down. https://status.ppro.dev/incident/344266 Thu, 21 Mar 2024 21:42:55 -0000 https://status.ppro.dev/incident/344266#bbb0049fcf902d243e6a7b974055e0f02eb789fbe9f88a2527f3362a4fcf0a65 BrovaPh ups status recovered. https://status.ppro.dev/incident/344266 Thu, 21 Mar 2024 21:39:23 -0000 https://status.ppro.dev/incident/344266#1772fd40705a3a53481b98d6f3b539c35e20565da18de3e966929ea5bb164b2b BrovaPh2 ups status recovered. https://status.ppro.dev/incident/344266 Thu, 21 Mar 2024 21:20:38 -0000 https://status.ppro.dev/incident/344266#8e7869149d99276c0d2dbc6f0261d38fb19b8a082cd704c1a30e02091a29f14e BrovaPh ups status went down. https://status.ppro.dev/incident/344266 Thu, 21 Mar 2024 21:17:13 -0000 https://status.ppro.dev/incident/344266#b769e9320042bc2b50d857de394aeadd432d5f0baebf8348e7d60eef71fdf98f BrovaPh2 ups status went down. https://status.ppro.dev/incident/338242 Fri, 15 Mar 2024 23:13:21 -0000 https://status.ppro.dev/incident/338242#eeff6653f5db81ca9c115d06d54ee9766c7c3e23e7e96f30b575b9aecece4a70 ppro: ovm myst server recovered. https://status.ppro.dev/incident/338242 Thu, 14 Mar 2024 17:38:28 -0000 https://status.ppro.dev/incident/338242#31277a8d73250438e2ff0d75b4a412deaddeba59fda3d31cd6475290d86ab705 BrovaPh ups status and BrovaPh2 ups status recovered. https://status.ppro.dev/incident/338242 Thu, 14 Mar 2024 17:38:28 -0000 https://status.ppro.dev/incident/338242#31277a8d73250438e2ff0d75b4a412deaddeba59fda3d31cd6475290d86ab705 BrovaPh ups status and BrovaPh2 ups status recovered. https://status.ppro.dev/incident/338242 Thu, 14 Mar 2024 15:53:36 -0000 https://status.ppro.dev/incident/338242#d80a26bd944cf99cb9e6f56debfc7921bf41417627af357130a0a147fcedf68e BrovaPh2 ups status went down. https://status.ppro.dev/incident/338242 Thu, 14 Mar 2024 15:52:02 -0000 https://status.ppro.dev/incident/338242#e08160fd817651165a4e00ef10ef25d41448753a268986e9ad256cffc67f0673 BrovaPh ups status went down. https://status.ppro.dev/incident/338242 Mon, 11 Mar 2024 08:04:21 -0000 https://status.ppro.dev/incident/338242#5136b888ecc74244a219d6d8f6f1a6a566587634ce19a5ea28f5095931607c73 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/338242 Mon, 11 Mar 2024 07:57:15 -0000 https://status.ppro.dev/incident/338242#c25aac2e7c3417264736c09f4b7f1e7ea13cbbb572528d614d6142d651db28da BrovaPh2 ups status went down. https://status.ppro.dev/incident/338242 Fri, 08 Mar 2024 20:45:40 -0000 https://status.ppro.dev/incident/338242#b99aa05e576ac644ab3021363474942c68d956e4312dbe11c2bc8ca5cc96c586 ppro: ovm myst server went down. https://status.ppro.dev/incident/337061 Thu, 07 Mar 2024 19:43:39 -0000 https://status.ppro.dev/incident/337061#a924668bd1964178849733e45e2c82562ad979ad0064fb96536296e60fffaa16 ppro: ovm myst server recovered. https://status.ppro.dev/incident/337061 Wed, 06 Mar 2024 11:54:25 -0000 https://status.ppro.dev/incident/337061#3e5670e9772520aa2398bde9279c636e855feec26cb7468b823b7bab91027754 ppro: ovm myst server went down. https://status.ppro.dev/incident/333854 Fri, 01 Mar 2024 13:42:25 -0000 https://status.ppro.dev/incident/333854#c75b531b98703cc023b3901c285266aecab64c9ba5ebef08701f26f05e685c65 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/333854 Fri, 01 Mar 2024 13:05:14 -0000 https://status.ppro.dev/incident/333854#97b037787a50e38b4db70c1c43f8f329ba7e1f81c0f3d435b42a509b8a664a76 BrovaPh2 ups status went down. https://status.ppro.dev/incident/333854 Fri, 01 Mar 2024 03:27:26 -0000 https://status.ppro.dev/incident/333854#1874d4865da761ee2321212bc78dea3fd697b73a96e019518edd23e8eb7f5f54 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/333854 Thu, 29 Feb 2024 18:19:36 -0000 https://status.ppro.dev/incident/333854#0a1e13f524f24c853f86af1fc6da3f33072d6985e09c3038d89be238db59f5a8 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/329609 Tue, 20 Feb 2024 18:29:26 -0000 https://status.ppro.dev/incident/329609#07d79a674325318746aa91b7deba978f54e66c3063ee12d40d2d67b04b7c131d BrovaPh2 ups status recovered. https://status.ppro.dev/incident/329609 Tue, 20 Feb 2024 18:27:33 -0000 https://status.ppro.dev/incident/329609#a9bbf9ed8883eb1040c4a879038d4d0c655e09683ea650c199369c0f598ec349 BrovaPh ups status recovered. https://status.ppro.dev/incident/329609 Tue, 20 Feb 2024 18:21:50 -0000 https://status.ppro.dev/incident/329609#120750c7917c41a6a6383c9c5930e409110099d7ac1908bd249363619fdec223 BrovaPh2 ups status went down. https://status.ppro.dev/incident/329609 Tue, 20 Feb 2024 18:20:06 -0000 https://status.ppro.dev/incident/329609#945da42615a1f2514a5863868ac917b7831dd1150a8510bcdbb81504b0ed0164 BrovaPh ups status went down. https://status.ppro.dev/incident/328942 Mon, 19 Feb 2024 12:02:03 -0000 https://status.ppro.dev/incident/328942#45abc2bee565c5538ae673127d930a34134e184d212e4d1526683ace2d1d0705 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/328942 Mon, 19 Feb 2024 11:54:54 -0000 https://status.ppro.dev/incident/328942#c70fbfd002e4b4cd75d5c446c17eb284b9e416fa8df675f1bfadf66d9afd94da BrovaPh2 ups status went down. https://status.ppro.dev/incident/328595 Sun, 18 Feb 2024 16:18:20 -0000 https://status.ppro.dev/incident/328595#80a24deb09e6249d3aff1943bff84d81f08e6fb9bf539664bd33387ec7ed0d95 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/328595 Sun, 18 Feb 2024 16:16:52 -0000 https://status.ppro.dev/incident/328595#94edb063b62d919f5920b9ed6edf5247017295f2015a04289320fb62abfe3728 BrovaPh ups status recovered. https://status.ppro.dev/incident/328595 Sun, 18 Feb 2024 16:11:07 -0000 https://status.ppro.dev/incident/328595#0e31b87d5de8d2c75935cc7cc19390994cc18670abdc8024cf743e1c1b3c9f2c BrovaPh2 ups status went down. https://status.ppro.dev/incident/328595 Sun, 18 Feb 2024 16:09:46 -0000 https://status.ppro.dev/incident/328595#74b5ff6d30f0f7dac8836959ce112f3c11b708132ff01b17852a78e7213651fd BrovaPh ups status went down. https://status.ppro.dev/incident/328190 Sat, 17 Feb 2024 15:27:14 -0000 https://status.ppro.dev/incident/328190#778a78b3f124422b222ad35ba60644b8855a33a23e0a5512422ac97ef700b27c BrovaPh ups status recovered. https://status.ppro.dev/incident/328190 Sat, 17 Feb 2024 15:23:59 -0000 https://status.ppro.dev/incident/328190#d853f03ec08c38b7e07f4ae69ec9a97d40f6ee43279f1afc26aea24b54cf6f09 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/328190 Sat, 17 Feb 2024 15:20:04 -0000 https://status.ppro.dev/incident/328190#a0ad74631abc23adda4914aa6a98933a774a94b95aa405958d45507bc7bcaf1f BrovaPh ups status went down. https://status.ppro.dev/incident/328190 Sat, 17 Feb 2024 15:16:36 -0000 https://status.ppro.dev/incident/328190#71ab9172cf115492d12ba9c8e47595de4079eaf8e39a9f48d7a05b147ec927e9 BrovaPh2 ups status went down. https://status.ppro.dev/incident/323690 Fri, 16 Feb 2024 22:58:58 -0000 https://status.ppro.dev/incident/323690#2d2745298fed1e6f80c9a2ad8936d18fa9a69e78382b2dd7664fb03c21393c33 ppro: ovm myst server recovered. https://status.ppro.dev/incident/323690 Fri, 16 Feb 2024 09:36:20 -0000 https://status.ppro.dev/incident/323690#4d167613421d477d63928cb3c1591a8af821620816e289d0d7d6993ede76ac0c BrovaPh ups status recovered. https://status.ppro.dev/incident/323690 Fri, 16 Feb 2024 09:33:00 -0000 https://status.ppro.dev/incident/323690#e35bd444e9d4fe0c2e2129c2e5508e7bbdcc6950302a2b4608125c19a3bd8e9f BrovaPh2 ups status recovered. https://status.ppro.dev/incident/323690 Fri, 16 Feb 2024 09:29:29 -0000 https://status.ppro.dev/incident/323690#0e8cb2f1e3f770d5dc5881e427a341e7ef902a32a4ad310882951b923a8e91b7 BrovaPh ups status went down. https://status.ppro.dev/incident/323690 Fri, 16 Feb 2024 09:25:46 -0000 https://status.ppro.dev/incident/323690#9947f7df3ba41719c306c5de64fc90f9eee1ae59ef0b4ca8504cfbce11264387 BrovaPh2 ups status went down. https://status.ppro.dev/incident/323690 Mon, 12 Feb 2024 23:48:43 -0000 https://status.ppro.dev/incident/323690#8a9e367e4ae734a73377fe470e82d721e02049d0bf93e7a0d8002a88d368462c BrovaPh ups status recovered. https://status.ppro.dev/incident/323690 Mon, 12 Feb 2024 23:41:42 -0000 https://status.ppro.dev/incident/323690#ac5946274abb85e51e0ce093cbe27d9597e023e1146fe0fca0f34a599d5b5e0b BrovaPh ups status went down. https://status.ppro.dev/incident/323690 Mon, 12 Feb 2024 17:25:30 -0000 https://status.ppro.dev/incident/323690#95b20d2443681e1181800c38102d30cb11c9e66c367c2d61061ae10693ee14ac smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/323690 Mon, 12 Feb 2024 17:17:39 -0000 https://status.ppro.dev/incident/323690#8c37d9cbb9d1972209276e02d3e416275313f749c515ac67e816e9dd75e7bec2 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/323690 Sun, 11 Feb 2024 20:46:58 -0000 https://status.ppro.dev/incident/323690#70f9c9cea056357817a7c3ea2763dbde1d9eb80057feb21b42d5a444e843b180 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/323690 Sun, 11 Feb 2024 20:35:02 -0000 https://status.ppro.dev/incident/323690#172d17e5309e6653beb55d3055ea77b553074f67c1c31923b1f0f01acc4dc7c2 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/323690 Sun, 11 Feb 2024 04:37:45 -0000 https://status.ppro.dev/incident/323690#85ecc1cb8fae58c83f6ba7241c511239423c4eb8b8f88e490c7895acd41323d2 BrovaPh ups status recovered. https://status.ppro.dev/incident/323690 Sun, 11 Feb 2024 04:30:00 -0000 https://status.ppro.dev/incident/323690#0730cd67d25543e99aea0828c3cfed00e35c4b7bd2c81c2c27ebe488adc34a87 BrovaPh ups status went down. https://status.ppro.dev/incident/323690 Fri, 09 Feb 2024 23:09:58 -0000 https://status.ppro.dev/incident/323690#268787978d41091b57912607c0e8d49e649476103514e3cc7d9ce0d3d91deeed BrovaPh ups status recovered. https://status.ppro.dev/incident/323690 Fri, 09 Feb 2024 23:06:32 -0000 https://status.ppro.dev/incident/323690#de69a3358404a17ad8f6498d8c2ee9e559ffd294a92e2387ea0b9f4b1bc7eb7a BrovaPh2 ups status recovered. https://status.ppro.dev/incident/323690 Fri, 09 Feb 2024 22:57:36 -0000 https://status.ppro.dev/incident/323690#be6cddc9e258f8e6fb3f63ab6336140d5f864e14d7ba6e9358b47314be4d0fc3 BrovaPh ups status went down. https://status.ppro.dev/incident/323690 Fri, 09 Feb 2024 22:54:23 -0000 https://status.ppro.dev/incident/323690#470274bac82b3438aac015e23bac31fdd2d950f577b7b5d0dd223ca5ccb7c9a3 BrovaPh2 ups status went down. https://status.ppro.dev/incident/323690 Fri, 09 Feb 2024 14:15:08 -0000 https://status.ppro.dev/incident/323690#772d7fa1a1e258340b5ffdd7150f5f5eea02622a7084c120cddf8b4e825c61ea BrovaPh2 ups status recovered. https://status.ppro.dev/incident/323690 Fri, 09 Feb 2024 14:08:13 -0000 https://status.ppro.dev/incident/323690#25c086f15704d74141508fe7a970b7d1bf6d63d7887153fcf24348959c61447f BrovaPh2 ups status went down. https://status.ppro.dev/incident/323690 Thu, 08 Feb 2024 18:23:32 -0000 https://status.ppro.dev/incident/323690#5bdabf9320cf94702d42c01f8edb20a950a92b0ea7b5c1a4ce92a52c6d40cd1d ppro: ovm myst server went down. https://status.ppro.dev/incident/323690 Thu, 08 Feb 2024 05:11:01 -0000 https://status.ppro.dev/incident/323690#7d601dc9c806f7162b365bec17916910b92e6c73a32fadf63c215de4c759d640 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/323690 Wed, 07 Feb 2024 22:37:41 -0000 https://status.ppro.dev/incident/323690#191e4a4f7a8202bf2903577afc9f6a0ec874b3fbf6c2287a66e6b860729bfb15 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/323690 Wed, 07 Feb 2024 20:14:33 -0000 https://status.ppro.dev/incident/323690#f2c2f1cdaeae00d3840862b94d88df0b16d79b3bb5db32b9595ae99196b7f795 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/323690 Wed, 07 Feb 2024 19:21:57 -0000 https://status.ppro.dev/incident/323690#7b5191a17bce37f0888c5cc7c14dfb73b9e85a85e1c35137087907677c004f3a smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/322922 Tue, 06 Feb 2024 14:48:58 -0000 https://status.ppro.dev/incident/322922#f709d6fbb369695fcd0ce04cb288f9a397bf08ce094d353167fdf72889dd247b BrovaPh ups status recovered. https://status.ppro.dev/incident/322922 Tue, 06 Feb 2024 14:42:12 -0000 https://status.ppro.dev/incident/322922#8071581087de489b2fe03df1e8e656a43a78dab4ff666bb7145be00b41de114c BrovaPh ups status went down. https://status.ppro.dev/incident/322922 Tue, 06 Feb 2024 08:40:41 -0000 https://status.ppro.dev/incident/322922#8097bedfd4efbeaf54cdee1135e86c3be76d10d2caef30cb48b7804def6ec6af BrovaPh ups status recovered. https://status.ppro.dev/incident/322922 Tue, 06 Feb 2024 08:33:19 -0000 https://status.ppro.dev/incident/322922#b65a8d801fcf594cc705820dc293b4c42534139cd3242e8b84451ded42ab01c3 BrovaPh ups status went down. https://status.ppro.dev/incident/322020 Sun, 04 Feb 2024 11:12:30 -0000 https://status.ppro.dev/incident/322020#f3e2cee8abaa559d769ab8c433e917efb6973e2e9fe567e4a389f9cfcc4fa86e BrovaPh2 ups status recovered. https://status.ppro.dev/incident/322020 Sun, 04 Feb 2024 11:05:23 -0000 https://status.ppro.dev/incident/322020#698af1102012d0bdf990042c77bffed9f3751d56dd541d987d2c43d5e3d99b39 BrovaPh2 ups status went down. https://status.ppro.dev/incident/320816 Thu, 01 Feb 2024 16:15:01 -0000 https://status.ppro.dev/incident/320816#4c5354d1776889edd1b6842f35f5c0716bf3eb9873858369924a223b52ce22d3 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/320816 Thu, 01 Feb 2024 16:09:20 -0000 https://status.ppro.dev/incident/320816#a7b10f311da264538f957c2a6cb73cacb641815f51c44cab9418b58bd17bb715 BrovaPh2 ups status went down. https://status.ppro.dev/incident/320816 Thu, 01 Feb 2024 11:20:05 -0000 https://status.ppro.dev/incident/320816#53c6dc7ada5a91841433bb83aefbcdfe292df77ec8cf4321ff4090042eab2d0e ppro: ovm myst server recovered. https://status.ppro.dev/incident/320816 Thu, 01 Feb 2024 11:10:10 -0000 https://status.ppro.dev/incident/320816#71062609fcee75c51123f1431174f05a77b9d937bd01cf7153b34e9cf8d7f5f7 ppro: ovm myst server went down. https://status.ppro.dev/incident/320390 Wed, 31 Jan 2024 14:24:39 -0000 https://status.ppro.dev/incident/320390#d3769058b19c2bee6d7520a8e8eb2c79e59f7f151d6ac27a1be11c24824c66d5 ppro: ovm myst server recovered. https://status.ppro.dev/incident/320390 Wed, 31 Jan 2024 14:15:27 -0000 https://status.ppro.dev/incident/320390#127192f8bea5c4a083ad01b7bc92eb9dae1c82b6a55cb8c30bff49b9f8e9d49b ppro: ovm myst server went down. https://status.ppro.dev/incident/318008 Fri, 26 Jan 2024 08:38:27 -0000 https://status.ppro.dev/incident/318008#d0913f0810f9c9d7e82f116bbaa4298e1a42a3e1b34e676caa9cdc0df5f5095a BrovaPh ups status recovered. https://status.ppro.dev/incident/318008 Fri, 26 Jan 2024 08:31:13 -0000 https://status.ppro.dev/incident/318008#f7a2a988efcd6b4503c6344f1dc81d922dd31f04add4cd209680598efedbd8f7 BrovaPh ups status went down. https://status.ppro.dev/incident/316545 Tue, 23 Jan 2024 08:07:35 -0000 https://status.ppro.dev/incident/316545#b94b00c53a0007337b0453599e336ff44f84bbf8a41116fb2a7f75eabd4f018d BrovaPh ups status recovered. https://status.ppro.dev/incident/316545 Tue, 23 Jan 2024 08:00:19 -0000 https://status.ppro.dev/incident/316545#452f5f0a724da7bd626d487bb0b085d2f512656cb398b1f17fa18370fa4e8ea2 BrovaPh ups status went down. https://status.ppro.dev/incident/314399 Thu, 18 Jan 2024 09:31:57 -0000 https://status.ppro.dev/incident/314399#08a2d87d21f83c5c2a4eadd5aca17a773f7fb591549ec9a1e63cb18f2651d41e BrovaPh2 ups status recovered. https://status.ppro.dev/incident/314399 Thu, 18 Jan 2024 09:24:52 -0000 https://status.ppro.dev/incident/314399#720a92d80bed42dcd892eac35fc249a3b0d3b6976b474b136e05ae4d86018717 BrovaPh2 ups status went down. https://status.ppro.dev/incident/313822 Wed, 17 Jan 2024 08:44:47 -0000 https://status.ppro.dev/incident/313822#db9b8e8999a899ef1102ccd01b586529d1461259ba37ba5139eaa0e27949e5f3 ppro: ovm myst server recovered. https://status.ppro.dev/incident/313822 Wed, 17 Jan 2024 08:34:53 -0000 https://status.ppro.dev/incident/313822#9f77e8f642f97d63a4b17430d0835fbb7e5f4f109b1b8c7a32c552ee75c54c5e ppro: ovm myst server went down. https://status.ppro.dev/incident/313418 Tue, 16 Jan 2024 11:17:21 -0000 https://status.ppro.dev/incident/313418#c5115b7edf6b809036a003ed0eb4c87be98365ecf88470f6adf2b785f22f6274 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/313418 Tue, 16 Jan 2024 11:10:12 -0000 https://status.ppro.dev/incident/313418#2ca9be418005413092f7a9fb0fee1b3ac76b4eddc6fc7a142f4304d4fa9892cc BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Mon, 15 Jan 2024 22:09:09 -0000 https://status.ppro.dev/incident/183067#029f2b9511a42ee7d1d1bea8344ebadcf887bacc8e19503676abe34c970bf206 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Mon, 15 Jan 2024 22:01:49 -0000 https://status.ppro.dev/incident/183067#61d1dc3aa8c956f71d16e4720f38f3d7f38d2089a72e1a267870aee1bf657750 BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Mon, 15 Jan 2024 12:48:32 -0000 https://status.ppro.dev/incident/183067#78e089a354a46c06a8c901d8db080bb956f8992cff0762b4670d7471339afb3e BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Fri, 04 Aug 2023 04:17:52 -0000 https://status.ppro.dev/incident/183067#00b289df025cfb656cb705d4a522b87c8f4159099ceb953c48dcc8a5f7684377 ppro: ovm myst server recovered. https://status.ppro.dev/incident/183067 Fri, 04 Aug 2023 04:09:21 -0000 https://status.ppro.dev/incident/183067#b6b5f7b8b1c4e79632502890fdd86c0529e9d611d5a8ed89add36bdd0a3c47f3 ppro: ovm myst server went down. https://status.ppro.dev/incident/183067 Tue, 01 Aug 2023 20:33:14 -0000 https://status.ppro.dev/incident/183067#6b61189f699a37fb35df941e417eaccfb6515f2241a9992e30d427032c6a03c3 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Tue, 01 Aug 2023 20:25:58 -0000 https://status.ppro.dev/incident/183067#c45a53ceeb3d7c8f622a1f3db8e5987f0571417b4398ac653f4af47ef3b36748 BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Sat, 29 Jul 2023 20:15:12 -0000 https://status.ppro.dev/incident/183067#ec6f32c4814ff421c80aecd40935585767774264bd992d7233244d3e8b961eae BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Sat, 29 Jul 2023 16:33:02 -0000 https://status.ppro.dev/incident/183067#ea16b7bde8d97d4e377fbc388d5791ef313ac2f449aa8c64e57c1ecd9e695e8e BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Thu, 27 Jul 2023 05:42:57 -0000 https://status.ppro.dev/incident/183067#849f3328fef69ef709f59273235c18249f758858a25192a7be01e41360130f1d BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Thu, 27 Jul 2023 05:00:44 -0000 https://status.ppro.dev/incident/183067#4d11fad380e35070b04f52f9633e6021a7c419e97c525fa52fec4c7f00b39d34 BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Wed, 26 Jul 2023 12:31:51 -0000 https://status.ppro.dev/incident/183067#a46398cf7762ff7e48e9e01baaa016d608dd703fe5c4fe2786ce5c0ac0c24a95 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Wed, 26 Jul 2023 12:19:39 -0000 https://status.ppro.dev/incident/183067#a62fdace8f08442aec7637f7a62c5e73f350faf4749a9645df1e47c5c9fe07e7 BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Tue, 11 Jul 2023 14:19:12 -0000 https://status.ppro.dev/incident/183067#44b9879e2273e01afe3737a844fa9dc53e143408fff041d7fb7401c3941d1629 fj: jpyther docker service recovered. https://status.ppro.dev/incident/183067 Tue, 11 Jul 2023 14:14:10 -0000 https://status.ppro.dev/incident/183067#345da74754ea012e1dc93f01e689bb3e7853bcda647dfcb45e12a1fcef6d44fb fj: jpyther docker service went down. https://status.ppro.dev/incident/183067 Mon, 10 Jul 2023 08:50:09 -0000 https://status.ppro.dev/incident/183067#d97fb6cc334033d6f13879b867ee1416bac8b95401c3ce721ef5b415f1c95004 fj: jpyther docker service recovered. https://status.ppro.dev/incident/183067 Mon, 10 Jul 2023 08:06:12 -0000 https://status.ppro.dev/incident/183067#b97215def6de4ccd7d78877b0e39ad6eae5b4a643074face6b4b2ee67a1e2576 fj: jpyther docker service went down. https://status.ppro.dev/incident/183067 Mon, 03 Jul 2023 19:42:04 -0000 https://status.ppro.dev/incident/183067#defd9ea441e27fde1e6b47b663f3daf9ff10653fa873351cbd5487ae3203cf0a ppro: ovm myst server recovered. https://status.ppro.dev/incident/183067 Mon, 03 Jul 2023 19:25:03 -0000 https://status.ppro.dev/incident/183067#2c5b4f09d514ebda972ca66a5ed31e4a70753e102df156e4a1240412f4ff5a40 ppro: ovm myst server went down. https://status.ppro.dev/incident/183067 Mon, 03 Jul 2023 19:21:15 -0000 https://status.ppro.dev/incident/183067#fc39a41405eca4cf7d2908f43545d9e4a9df5b76859256afbf73c8d32fda5a6b ppro: ovm myst server recovered. https://status.ppro.dev/incident/183067 Mon, 03 Jul 2023 19:13:05 -0000 https://status.ppro.dev/incident/183067#6e1c03597f57dc30da2d07c58913fea0be466479106d0f92ce8883445e98469c ppro: ovm myst server went down. https://status.ppro.dev/incident/183067 Mon, 03 Jul 2023 19:03:06 -0000 https://status.ppro.dev/incident/183067#320b5f1ca4ebdd976584b7803ba6192056dda29ed88568c1f3531403df15c690 ppro: ovm myst server recovered. https://status.ppro.dev/incident/183067 Mon, 03 Jul 2023 18:55:04 -0000 https://status.ppro.dev/incident/183067#98225c7173822188582e0139fb12c2bc15e447cea9b485275a7c68da2ec94fae ppro: ovm myst server went down. https://status.ppro.dev/incident/183067 Mon, 03 Jul 2023 18:51:05 -0000 https://status.ppro.dev/incident/183067#d6ff002f8f2645e33204371aebd4de2ad7d07f3a89ab1ec9732c8a1e39741030 ppro: ovm myst server recovered. https://status.ppro.dev/incident/183067 Mon, 03 Jul 2023 18:43:00 -0000 https://status.ppro.dev/incident/183067#cfcfa6b9c898c942cbde6597cc0ca7db43554687e23da422d0a805d918e3f98a ppro: ovm myst server went down. https://status.ppro.dev/incident/183067 Tue, 27 Jun 2023 17:14:58 -0000 https://status.ppro.dev/incident/183067#ec6278e6f959d8a162e8c06280697bad23be7fdd6196dd84b76a528d2e154540 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/183067 Tue, 27 Jun 2023 17:13:34 -0000 https://status.ppro.dev/incident/183067#4c7753bcfa694e57c98c691c2524e92790d5f1c835615ba401c6b9bd535a898f fj: jpyther docker service recovered. https://status.ppro.dev/incident/183067 Tue, 27 Jun 2023 17:08:21 -0000 https://status.ppro.dev/incident/183067#40443bc9393146723f0485627fbbfdfe69e6a4014e7843f7c60fd77e838170df fj: jpyther docker service went down. https://status.ppro.dev/incident/183067 Tue, 27 Jun 2023 17:07:57 -0000 https://status.ppro.dev/incident/183067#1534c0918fb6e24be8129a76fb1a29418a56f4153227a50056273e30ed50bf4b smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/183067 Tue, 27 Jun 2023 10:29:35 -0000 https://status.ppro.dev/incident/183067#937248add3cb3d037e72b9a3b62ac5dbff961551d71107082c32407563d0f7ce BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Tue, 27 Jun 2023 10:22:10 -0000 https://status.ppro.dev/incident/183067#e42793876470f7305495eb15b819f04fdcefab2a6ab27f9e00c2c985ec471ea7 BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Mon, 26 Jun 2023 15:33:55 -0000 https://status.ppro.dev/incident/183067#b63dd4b69953b08f92cf48c5bd630d7007150d95eb845dd2d44888021a613654 ppro: ovm myst server recovered. https://status.ppro.dev/incident/183067 Mon, 26 Jun 2023 14:58:59 -0000 https://status.ppro.dev/incident/183067#36bdb8347cc38fc804cd20200ad03c9825b5bf0404500b672436f0800951539b ppro: ovm myst server went down. https://status.ppro.dev/incident/183067 Mon, 26 Jun 2023 14:06:34 -0000 https://status.ppro.dev/incident/183067#7a7523ec6f92415c61eaf21391cccea6982a7fdc5d6ea9d3f131a6155a952560 ppro: ovm myst server recovered. https://status.ppro.dev/incident/183067 Mon, 26 Jun 2023 13:55:36 -0000 https://status.ppro.dev/incident/183067#f117a87711cf83a8cac1e0da14113ff01d8ed0c8fe18e43c6b25192ee04b1665 ppro: ovm myst server went down. https://status.ppro.dev/incident/183067 Wed, 21 Jun 2023 17:16:25 -0000 https://status.ppro.dev/incident/183067#6ee84701e9b6b189828b3c0abace4d0bb88697e23863b082f17fffc65f336253 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Wed, 21 Jun 2023 17:09:21 -0000 https://status.ppro.dev/incident/183067#ebe130dc7b881ca7a0bb6ba57bb6c09217cc0c4c33ee78e8ee4f049b57434de3 BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Wed, 21 Jun 2023 12:50:08 -0000 https://status.ppro.dev/incident/183067#4551fcd91fe786464f63bb30fd64306f630ecebfe18b018cf4158344f26e32f9 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Wed, 21 Jun 2023 12:43:10 -0000 https://status.ppro.dev/incident/183067#667ce14e6a1bfa27fde779d1799f4983125e70533e764bdcb02dba8caad7fc4c BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Wed, 21 Jun 2023 06:44:35 -0000 https://status.ppro.dev/incident/183067#1f43c2a243068ffe32f278cf6fcf74eeb1717872ad5ecc1ec5d341fd44f1aa54 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Wed, 21 Jun 2023 06:31:28 -0000 https://status.ppro.dev/incident/183067#46b18de8aee9b39db1435b8f9923fe37980f9da70c1a79031710031f04d08c24 BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Wed, 21 Jun 2023 06:14:13 -0000 https://status.ppro.dev/incident/183067#3839367e5907172d2a92204b7899a9c21723bdbb436fb503e2618352b9a0605f BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Wed, 21 Jun 2023 06:01:00 -0000 https://status.ppro.dev/incident/183067#6288883a194d139dc3eccd310ad143e3ff23284c0f36a4c0be02e20d1885c2e8 BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Tue, 20 Jun 2023 03:37:05 -0000 https://status.ppro.dev/incident/183067#7260b4b510b9c6dc4e6eb7cd4e2e1cf1dde99bf99c363c8d37a12afa62cf99f6 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Tue, 20 Jun 2023 03:29:48 -0000 https://status.ppro.dev/incident/183067#b502842d476a9cd61da862b5e6a4d8cb7a983b325d635593dffa93f0b186e95f BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Tue, 20 Jun 2023 01:15:45 -0000 https://status.ppro.dev/incident/183067#4af994b6fba85abeec2ec99cdae01da50657e9483773d7c3f5f2be70ed2a5315 fj: jpyther docker service recovered. https://status.ppro.dev/incident/183067 Tue, 20 Jun 2023 01:02:34 -0000 https://status.ppro.dev/incident/183067#2bb6ae7db105ffe7da34dc483658b395e0eab953f1eadf72ac98c8ad2ef9f166 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/183067 Tue, 20 Jun 2023 00:35:20 -0000 https://status.ppro.dev/incident/183067#0410c156862d14babfa179133657be9ea34733658c8f2ecd1399764e628298bb smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/183067 Tue, 20 Jun 2023 00:31:54 -0000 https://status.ppro.dev/incident/183067#0e29359866eb35198d7557a64ff50bf55d4516ee476179ff3907f811aa6d9c0e fj: jpyther docker service went down. https://status.ppro.dev/incident/183067 Mon, 19 Jun 2023 01:33:29 -0000 https://status.ppro.dev/incident/183067#0e2c33e2418658a631926ba6657edac4fc6dd0524b5a15bd16bba042ba505f44 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Mon, 19 Jun 2023 01:26:26 -0000 https://status.ppro.dev/incident/183067#88ddb3ab52c392e4f9eec4abdffa0a5d92f6c7397f0669392e8aa91652f6c8cc BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Sat, 17 Jun 2023 14:26:13 -0000 https://status.ppro.dev/incident/183067#0f53221268d17f6862827f4eaa81a58c55ed014fe0ceabeeec45cdee510b5a89 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Sat, 17 Jun 2023 14:19:18 -0000 https://status.ppro.dev/incident/183067#baa9e0070cb94ea4a23c9db42ae1eccc3573a969b0edf3ec867636f6d1f7c9f0 BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Wed, 14 Jun 2023 13:09:50 -0000 https://status.ppro.dev/incident/183067#5422cc39a9db7ab85bf666b2d71c29ad2104f58e17acb2bbebc4e8ad07902c8c BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Wed, 14 Jun 2023 12:47:51 -0000 https://status.ppro.dev/incident/183067#c507e9f21f420c9ba588cc647e90b5be330faa5b694126e5bb414801ff36c5d7 BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Tue, 13 Jun 2023 22:49:44 -0000 https://status.ppro.dev/incident/183067#a49df344f644fcd0d84913d082d47c40cb1209e010b0ac32fc26a4999b66b58a smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/183067 Tue, 13 Jun 2023 22:48:15 -0000 https://status.ppro.dev/incident/183067#b4350e400af20b0a3b63e40b6ffa8fed2e57cee5dfc6b4a2df74cea7ffdf7c9e fj: jpyther docker service recovered. https://status.ppro.dev/incident/183067 Tue, 13 Jun 2023 22:42:37 -0000 https://status.ppro.dev/incident/183067#3eb9023f186eb3a8d42d6cca77e7050ef9d11370f8bded62785360c2853aeea0 smvs.chubynske.org.ua and fj: jpyther docker service went down. https://status.ppro.dev/incident/183067 Tue, 13 Jun 2023 22:42:37 -0000 https://status.ppro.dev/incident/183067#3eb9023f186eb3a8d42d6cca77e7050ef9d11370f8bded62785360c2853aeea0 smvs.chubynske.org.ua and fj: jpyther docker service went down. https://status.ppro.dev/incident/183067 Mon, 12 Jun 2023 07:14:48 -0000 https://status.ppro.dev/incident/183067#584c179518562845a245eba4193492bc320bb1ec07fe3c30a4edc84afb426229 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Mon, 12 Jun 2023 07:07:37 -0000 https://status.ppro.dev/incident/183067#1c71d3303e3aa4112ca273d53ab597b9de20b5e494b79d04f399c3f32dfe9a8d BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Mon, 12 Jun 2023 05:10:44 -0000 https://status.ppro.dev/incident/183067#2ac3d1cf299abcbb239e36e157fea0c34ccf8b9d04bb9bf75f1b5a8d5c27d56d ppro: ovm myst server recovered. https://status.ppro.dev/incident/183067 Mon, 12 Jun 2023 05:05:49 -0000 https://status.ppro.dev/incident/183067#1e8b46b445a357b974adb752062b6a8dc3efa533f667c9286b2e8ba19800860b ppro: ovm myst server went down. https://status.ppro.dev/incident/183067 Sun, 11 Jun 2023 02:11:29 -0000 https://status.ppro.dev/incident/183067#4e01be5c0a7fee24a9c35b0f6e1891ebe8ed5d2b0420de7c5eb4ee179334918b smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/183067 Sun, 11 Jun 2023 01:29:09 -0000 https://status.ppro.dev/incident/183067#2e3d6d696363315a18bf70264cc129847724fefb5909760311b8d7b7c2451470 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/183067 Sun, 11 Jun 2023 01:16:05 -0000 https://status.ppro.dev/incident/183067#18292135cb9dc7a173fd073785749975aef8dbe2cf13bccb196074a4cbbe32f0 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/183067 Sat, 10 Jun 2023 23:54:05 -0000 https://status.ppro.dev/incident/183067#9834ec7c029cc0486289694d899963f83b351151d9ac24016c1e2a7ef54e6dd9 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/183067 Fri, 09 Jun 2023 04:48:11 -0000 https://status.ppro.dev/incident/183067#e6b8149c6de3880b5fa19ba0f42777ce9b55b3d120f57eec2d211573025ed051 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/183067 Fri, 09 Jun 2023 04:46:21 -0000 https://status.ppro.dev/incident/183067#b7a52c49e12b80ccf86aa30fd7f1ecaea71239e68b869774b524636e2e31285c ppro: ovm myst server recovered. https://status.ppro.dev/incident/183067 Fri, 09 Jun 2023 04:41:05 -0000 https://status.ppro.dev/incident/183067#13f4af8e8d6e2e61654fbdb9a420ec09e767c400e31b64118f1d68e04c79971b smvs.chubynske.org.ua and ppro: ovm myst server went down. https://status.ppro.dev/incident/183067 Fri, 09 Jun 2023 04:41:05 -0000 https://status.ppro.dev/incident/183067#13f4af8e8d6e2e61654fbdb9a420ec09e767c400e31b64118f1d68e04c79971b smvs.chubynske.org.ua and ppro: ovm myst server went down. https://status.ppro.dev/incident/183067 Tue, 06 Jun 2023 07:22:22 -0000 https://status.ppro.dev/incident/183067#af66b2590ea23dedd3b763e795093bbf983a38699a8566707a2bdff89529111c BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Tue, 06 Jun 2023 07:14:58 -0000 https://status.ppro.dev/incident/183067#5c00b8592d1d89f0558cacc86a309585d5c761a3acdad8fc6ee0993b8cde8be9 BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Tue, 06 Jun 2023 05:42:23 -0000 https://status.ppro.dev/incident/183067#05bc6e5d00f35c09227e493575d0fefda0f93133cfd1b7987fe4ae6ba43660a2 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Tue, 06 Jun 2023 05:29:57 -0000 https://status.ppro.dev/incident/183067#5edbe9eb5b9a80cb64d7c8f5b6ac79b39c158be69c642502294cd425e54a291b BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Fri, 02 Jun 2023 08:11:57 -0000 https://status.ppro.dev/incident/183067#ed65e2d2753acafa0c0016118f99900d5112d91222595dc5c54f4ab5a09c47ce BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Fri, 02 Jun 2023 07:39:29 -0000 https://status.ppro.dev/incident/183067#cc49a4859ef5f9893e5e798eb7699dc80b254e512721ff5aff18262e1849f3d0 BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Thu, 01 Jun 2023 03:24:16 -0000 https://status.ppro.dev/incident/183067#67325227cf12ffd8ed6f25bb429ca18e3f2e438892ef7edb39347a866180eb3a BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Thu, 01 Jun 2023 02:22:29 -0000 https://status.ppro.dev/incident/183067#6bd99c7694620d1622a009ba032d075e8647f518cabe18b77d75214eb9f72344 BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Wed, 31 May 2023 04:12:17 -0000 https://status.ppro.dev/incident/183067#4bf6490de6aac4bef0f3f991418ba4a3bd974e8172b1186d4ee14d13443fecee ppro: ovm myst server recovered. https://status.ppro.dev/incident/183067 Wed, 31 May 2023 04:07:07 -0000 https://status.ppro.dev/incident/183067#c2c5a84a47726edefb0b1ea5972733fa8f554f9d73001cf974163253217d1084 ppro: ovm myst server went down. https://status.ppro.dev/incident/183067 Sat, 27 May 2023 19:57:38 -0000 https://status.ppro.dev/incident/183067#7040b3425703032a0da6bf9d53c73519979fc68811956e761db5277174889571 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/183067 Sat, 27 May 2023 19:55:40 -0000 https://status.ppro.dev/incident/183067#fb60308fa518672e195fe2de1ecb2e4d9057d4ccf93c1cc0ea106772ce8fa5fe ppro: ovm myst server recovered. https://status.ppro.dev/incident/183067 Sat, 27 May 2023 19:54:51 -0000 https://status.ppro.dev/incident/183067#d20fe574c008fe60a21ff91c9d8451159060e1a452454a0ec31e45a2346ba0d5 fj: jpyther docker service recovered. https://status.ppro.dev/incident/183067 Sat, 27 May 2023 19:50:40 -0000 https://status.ppro.dev/incident/183067#1edda3cb5b5777362a9602b17da0f7960f7929cae319afbb69f77e2e149056b4 smvs.chubynske.org.ua and ppro: ovm myst server went down. https://status.ppro.dev/incident/183067 Sat, 27 May 2023 19:50:40 -0000 https://status.ppro.dev/incident/183067#1edda3cb5b5777362a9602b17da0f7960f7929cae319afbb69f77e2e149056b4 smvs.chubynske.org.ua and ppro: ovm myst server went down. https://status.ppro.dev/incident/183067 Sat, 27 May 2023 19:49:59 -0000 https://status.ppro.dev/incident/183067#07717f3b78add76f537f955eec53923f422a7aafa9dc7012042f76f2f43d7123 fj: jpyther docker service went down. https://status.ppro.dev/incident/183067 Sat, 27 May 2023 19:29:04 -0000 https://status.ppro.dev/incident/183067#85df67ab7752f2e80ae18380811f8863f88093c2f060e179f1cee553af6e48d2 ppro: ovm myst server recovered. https://status.ppro.dev/incident/183067 Sat, 27 May 2023 19:28:01 -0000 https://status.ppro.dev/incident/183067#5eb7aa0f95fecda53eef628f3ef5277420f9b2db8cec606b96dea122e3027902 fj: jpyther docker service recovered. https://status.ppro.dev/incident/183067 Sat, 27 May 2023 19:23:47 -0000 https://status.ppro.dev/incident/183067#bd99e115419a4bada3624bca02d8f30368b40d85764ee3d8f9c8a88f75665c46 ppro: ovm myst server went down. https://status.ppro.dev/incident/183067 Sat, 27 May 2023 19:22:49 -0000 https://status.ppro.dev/incident/183067#a59d736f019a4a3e70b5fa214a853179114fce7565c8eadf18d1e687b2d2a962 fj: jpyther docker service went down. https://status.ppro.dev/incident/183067 Sat, 27 May 2023 14:21:41 -0000 https://status.ppro.dev/incident/183067#14ccd89796dc208b28f2cf3e1b75cd8647ef6c62056a5f76d6a1a9f08ced8a21 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Sat, 27 May 2023 07:04:30 -0000 https://status.ppro.dev/incident/183067#54b7c7490c2ec0b689b003ae2a597672d314046a03ac2e282f8ed0c74a4ff8c3 BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Sun, 21 May 2023 22:56:32 -0000 https://status.ppro.dev/incident/183067#652b107eafda118df7788f0d858cad123079fbe1b6e93a4208f1fc448bba8ce9 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/183067 Sun, 21 May 2023 22:55:52 -0000 https://status.ppro.dev/incident/183067#7a6ceb5328beb82df4d62a6e352ebf27e592352e8ccf2d91462543ba52b3719d ppro: ovm myst server recovered. https://status.ppro.dev/incident/183067 Sun, 21 May 2023 22:54:51 -0000 https://status.ppro.dev/incident/183067#15a7afbe1228413e1294cc48685849cc98c13dbb9029668480a40144be9113c9 fj: jpyther docker service recovered. https://status.ppro.dev/incident/183067 Sun, 21 May 2023 22:50:42 -0000 https://status.ppro.dev/incident/183067#32abdbf482767605a07e66812ad7ca5df1a11b6d4967ed636178e258d5dc9bd9 ppro: ovm myst server went down. https://status.ppro.dev/incident/183067 Sun, 21 May 2023 22:49:39 -0000 https://status.ppro.dev/incident/183067#42f3c55c29d91312e09466f853da2a4832df0c0d70ab0b5fd9dad43df510a151 smvs.chubynske.org.ua and fj: jpyther docker service went down. https://status.ppro.dev/incident/183067 Sun, 21 May 2023 22:49:39 -0000 https://status.ppro.dev/incident/183067#42f3c55c29d91312e09466f853da2a4832df0c0d70ab0b5fd9dad43df510a151 smvs.chubynske.org.ua and fj: jpyther docker service went down. https://status.ppro.dev/incident/183067 Sat, 20 May 2023 11:24:27 -0000 https://status.ppro.dev/incident/183067#75fa1c30dd49d63222e9298d7965a08aba51dc4696f89684863f8e75707a3507 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Sat, 20 May 2023 11:17:10 -0000 https://status.ppro.dev/incident/183067#f935a9dd2795c2479d77df7b8eded041a4d64d0067d974df750269f078cb61a8 BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Sat, 20 May 2023 11:14:31 -0000 https://status.ppro.dev/incident/183067#1522c7193833eb0793fc193e5f375f1ed0ea1a168aef22d6086c3c186c82bfbe BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Sat, 20 May 2023 10:57:07 -0000 https://status.ppro.dev/incident/183067#6c04c1115cf8e34f351b46bf4767df2057439e3c128e00ba19ca746645d23a99 BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Thu, 11 May 2023 20:14:05 -0000 https://status.ppro.dev/incident/183067#c806af99c487a10ef451a5ce84e9839f24db19fcbfe3799b107af90805314fd6 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/183067 Thu, 11 May 2023 20:11:31 -0000 https://status.ppro.dev/incident/183067#7a9548abfaaba07d812d62d5d8f2333e3b04bb98230aa7821341a53e0153a8ae fj: jpyther docker service recovered. https://status.ppro.dev/incident/183067 Thu, 11 May 2023 20:06:02 -0000 https://status.ppro.dev/incident/183067#3664c07f11eb7cf59f887c37bfc5978e132365b23ad6e7267f35ca1b981e37e3 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/183067 Thu, 11 May 2023 19:27:03 -0000 https://status.ppro.dev/incident/183067#3c71976f59f4b763a7582ceeedb83129b98ed7aa1dffb321199afa24c122fc41 fj: jpyther docker service went down. https://status.ppro.dev/incident/183067 Sat, 06 May 2023 10:00:26 -0000 https://status.ppro.dev/incident/183067#a1c258d2e32b164463052350c255cdb405622177d44c5fe60094bb2266719737 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Sat, 06 May 2023 07:08:16 -0000 https://status.ppro.dev/incident/183067#39c9012e82fa226549c57e3a3f1807ee9ca598ffa258850f1c924887fd204ec2 BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Wed, 26 Apr 2023 16:16:16 -0000 https://status.ppro.dev/incident/183067#a7aafa762ac377d6ce651ee7d4a4043ff1f08c263c5265b936d5d218ea36a54b smvs.chubynske.org.ua, BrovaPh2 ups status, and ppro: ovm myst server recovered. https://status.ppro.dev/incident/183067 Wed, 26 Apr 2023 16:16:16 -0000 https://status.ppro.dev/incident/183067#a7aafa762ac377d6ce651ee7d4a4043ff1f08c263c5265b936d5d218ea36a54b smvs.chubynske.org.ua, BrovaPh2 ups status, and ppro: ovm myst server recovered. https://status.ppro.dev/incident/183067 Wed, 26 Apr 2023 16:16:16 -0000 https://status.ppro.dev/incident/183067#a7aafa762ac377d6ce651ee7d4a4043ff1f08c263c5265b936d5d218ea36a54b smvs.chubynske.org.ua, BrovaPh2 ups status, and ppro: ovm myst server recovered. https://status.ppro.dev/incident/183067 Wed, 26 Apr 2023 16:15:10 -0000 https://status.ppro.dev/incident/183067#5e7e7914c48c81119ec89bf54ab446cf3809c3bb2319f413a097ccfa6a7213ed fj: jpyther docker service recovered. https://status.ppro.dev/incident/183067 Wed, 26 Apr 2023 16:10:58 -0000 https://status.ppro.dev/incident/183067#673414d588c9729fa939f5ef342317e01f6203843db6ff595cc638a815121dc1 ppro: ovm myst server went down. https://status.ppro.dev/incident/183067 Wed, 26 Apr 2023 16:09:50 -0000 https://status.ppro.dev/incident/183067#f98849e1c9b2ac64b12acf3be50feaddf0111e18c40585b92e0bca6689b19e7b smvs.chubynske.org.ua and fj: jpyther docker service went down. https://status.ppro.dev/incident/183067 Wed, 26 Apr 2023 16:09:50 -0000 https://status.ppro.dev/incident/183067#f98849e1c9b2ac64b12acf3be50feaddf0111e18c40585b92e0bca6689b19e7b smvs.chubynske.org.ua and fj: jpyther docker service went down. https://status.ppro.dev/incident/183067 Wed, 26 Apr 2023 16:08:47 -0000 https://status.ppro.dev/incident/183067#984a9f981d86f5dc5a946d6ec8d07a7e55d3c7a56522d3adbe9ee670cbfe2769 BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Wed, 26 Apr 2023 16:01:56 -0000 https://status.ppro.dev/incident/183067#4bfde3868fe193479a1beb1d578905865b0a664376c34b681e74b85acaeaf30e smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/183067 Wed, 26 Apr 2023 15:54:28 -0000 https://status.ppro.dev/incident/183067#d238522f760eade4f9cff90397bb257e512244bc498bd26fb566ae5c5881634b smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/183067 Tue, 25 Apr 2023 03:19:08 -0000 https://status.ppro.dev/incident/183067#4c792b607846e3d1f1baf1f7df202ba3b58d05e1c640ed6617b6c53177a53b50 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Tue, 25 Apr 2023 03:07:19 -0000 https://status.ppro.dev/incident/183067#1a7f9e2a162f17f8f0b93c663061eed38a10685c599aa69641c7179e7e93952a BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Sat, 22 Apr 2023 23:09:32 -0000 https://status.ppro.dev/incident/183067#363c91fbe82092b9ee6b1671a7a83d284373e6b5c670a86d19d7e4452f02cfa6 ppro: ovm myst server recovered. https://status.ppro.dev/incident/183067 Sat, 22 Apr 2023 23:08:38 -0000 https://status.ppro.dev/incident/183067#dc3ed99848c16056728507549832ba1c6705a928819fb073195715c1df1c482f fj: jpyther docker service recovered. https://status.ppro.dev/incident/183067 Sat, 22 Apr 2023 23:04:07 -0000 https://status.ppro.dev/incident/183067#8ba935591498a3ee752a076a45fd2bb85171701e6185f5fede82a5a91b5c1816 ppro: ovm myst server went down. https://status.ppro.dev/incident/183067 Sat, 22 Apr 2023 23:03:38 -0000 https://status.ppro.dev/incident/183067#3ae88cfe25b2e68ea94f0ad302546f40806231d4faa8bbff754aad455bb0b800 fj: jpyther docker service went down. https://status.ppro.dev/incident/183067 Tue, 18 Apr 2023 10:15:59 -0000 https://status.ppro.dev/incident/183067#92fe93633d538ed340d53306fb45e695393b2a2569fc20e6eb8d417a4e173c0b fj: jpyther docker service recovered. https://status.ppro.dev/incident/183067 Sun, 16 Apr 2023 06:41:37 -0000 https://status.ppro.dev/incident/183067#3a365fdf457f1d9dcb296162aad5c4c1771e11c83949ddd83f3dfe042960c5b3 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/183067 Sun, 16 Apr 2023 06:34:20 -0000 https://status.ppro.dev/incident/183067#b612c12a1ee3b8d605519a1df6c7f200d4b0c644af6f8c15f84d6f2b288705e6 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/183067 Thu, 30 Mar 2023 08:30:20 -0000 https://status.ppro.dev/incident/183067#c5deac67e0aa2f4289cf218450b139636430f7c8ecf04f864e7a39956947a28e ppro: ovm myst server recovered. https://status.ppro.dev/incident/183067 Thu, 30 Mar 2023 08:24:45 -0000 https://status.ppro.dev/incident/183067#85db382ca22e7da29ffc5f3470a5f56494481efc00096db45a25eff7ca54ffa0 ppro: ovm myst server went down. https://status.ppro.dev/incident/183067 Wed, 29 Mar 2023 14:34:04 -0000 https://status.ppro.dev/incident/183067#81f8959ecc1653a64ab659b32ee3c55e222a23f520541fe4c556192d51767520 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Wed, 29 Mar 2023 14:01:45 -0000 https://status.ppro.dev/incident/183067#6741d573099714710d5f221f236b803982680feec025a2832840b2f96c6d5cf1 BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Tue, 28 Mar 2023 20:22:34 -0000 https://status.ppro.dev/incident/183067#59f227f0c5abecf617be6ce786b9096b8f69e2122f801a9ebce0b3c057bbc1f8 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Tue, 28 Mar 2023 20:15:15 -0000 https://status.ppro.dev/incident/183067#287368b1b3c5c857b9d307d493e97c783b69d6f00b25b03cb4099df121f96f46 BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Tue, 28 Mar 2023 13:36:58 -0000 https://status.ppro.dev/incident/183067#9908ebb51b0029c17021c75e2491613745dc08fa0d2a8aa3ab598bf1c0e4e69c BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Tue, 28 Mar 2023 13:33:10 -0000 https://status.ppro.dev/incident/183067#a7a8829982ff954340fd9573ad21e305cc8e5e16018a03a8e86db00677aea117 BrovaPh ups status went down. https://status.ppro.dev/incident/183067 Tue, 28 Mar 2023 10:50:40 -0000 https://status.ppro.dev/incident/183067#53aaf7015b4e3fba90f9e8ed4b8abe1289248ec4d9b621e5ffb3a66d1dd6a36f BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Tue, 28 Mar 2023 10:50:21 -0000 https://status.ppro.dev/incident/183067#5133c4dcc21c83b63ee030d092f91882705b5458509fe2475034d284a3b9ae24 BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Tue, 28 Mar 2023 08:37:48 -0000 https://status.ppro.dev/incident/183067#4456d16f8be2a3728674551a50d7b7045a617f1758f0a2d18f7bb398abe63ab8 BrovaPh ups status went down. https://status.ppro.dev/incident/183067 Tue, 28 Mar 2023 08:31:31 -0000 https://status.ppro.dev/incident/183067#6f484ac49ac0027b169e3e3d53e99447f7c63b7b5480b0a3c03fefdbc7260fbe BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Tue, 28 Mar 2023 07:59:17 -0000 https://status.ppro.dev/incident/183067#04c631b3b72f87624d662b0037429ed9c771e9f8d8d6c34b67c59feb3fcf7f41 BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Tue, 28 Mar 2023 04:47:16 -0000 https://status.ppro.dev/incident/183067#5407c6a040445e8a7f7979f06ca2cd694404d04b54b966ac5bf541087bd662cb smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/183067 Tue, 28 Mar 2023 04:40:24 -0000 https://status.ppro.dev/incident/183067#f6defee0ce15898311b337d10774291990ccb29403ae4acbc7a7b54c5781130e smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/183067 Mon, 27 Mar 2023 10:04:48 -0000 https://status.ppro.dev/incident/183067#b182e5b94c897ad79528bea28e240f7b41002487034adb3b6c3938b104e9f3cb BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Mon, 27 Mar 2023 09:47:05 -0000 https://status.ppro.dev/incident/183067#966f5c4b497c54ff0bbf98ae9e32bb4a31a88cf5e5d7690f96edc9394e3bb453 BrovaPh ups status went down. https://status.ppro.dev/incident/183067 Mon, 27 Mar 2023 07:00:46 -0000 https://status.ppro.dev/incident/183067#17bf241d6ee1ed9a1b79d56eb731ad0c88c3b52fb088da99318762ca40b2ac25 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Mon, 27 Mar 2023 06:23:24 -0000 https://status.ppro.dev/incident/183067#926cf89e26eb244a791a10f63fe60c5dc5241f66641989c8c6659cdbcbc661c9 BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Sun, 26 Mar 2023 14:28:46 -0000 https://status.ppro.dev/incident/183067#e04e5052859e4b84ece1d6a04b5eb782de30e2f9f443f0a5027752d1b68dc1eb BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Sun, 26 Mar 2023 14:11:01 -0000 https://status.ppro.dev/incident/183067#01fdee2d117889f92371e6f36edc5efddc857a28c0a0b66b127f43f09bf7ea92 BrovaPh ups status went down. https://status.ppro.dev/incident/183067 Sun, 26 Mar 2023 02:41:01 -0000 https://status.ppro.dev/incident/183067#627527fafabb4d677caac903475556266b20a3c73a33f855358d7f9bc93655ad ppro: ovm myst server recovered. https://status.ppro.dev/incident/183067 Sun, 26 Mar 2023 02:40:31 -0000 https://status.ppro.dev/incident/183067#f2ec7000c3e3cb219b7fc87555eaa8f2fa904c2a26fe6f8782f06cd1a0fb7e2e smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/183067 Sun, 26 Mar 2023 02:35:07 -0000 https://status.ppro.dev/incident/183067#fc720da2fc3b9073bccc4b14db4c59b4450e7a52265d7ed5515ea217a760a5e6 ppro: ovm myst server went down. https://status.ppro.dev/incident/183067 Sun, 26 Mar 2023 02:33:26 -0000 https://status.ppro.dev/incident/183067#e60f172b849d1141fd50edc4686149415cdb4a9863e067b048984c579cd6d122 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/183067 Sun, 26 Mar 2023 01:43:45 -0000 https://status.ppro.dev/incident/183067#a60a363724064e0b056854062e0b9b11da62cd19d30f4f8214e38a191b1c0159 BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Sun, 26 Mar 2023 01:26:08 -0000 https://status.ppro.dev/incident/183067#1f19a2a0050c05128a9601c9ae79aeb8f0ddcfb246352144a8486ecd112784e0 BrovaPh ups status went down. https://status.ppro.dev/incident/183067 Sat, 25 Mar 2023 21:43:53 -0000 https://status.ppro.dev/incident/183067#2420c24152509e3785aa8a55b4104cb75c68521b2b7c4a91b53d2d00fe7bd65d BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Sat, 25 Mar 2023 21:36:27 -0000 https://status.ppro.dev/incident/183067#3d3e9a2ea817cee060f7ea462ee6d7446bbbf31972c5231b2316f32af139b93d BrovaPh ups status went down. https://status.ppro.dev/incident/183067 Sat, 25 Mar 2023 19:28:53 -0000 https://status.ppro.dev/incident/183067#9911b4399d0940f9be020e0bd53cc35041e24f8020dae8bf517ffff5c813a2e6 BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Sat, 25 Mar 2023 19:21:26 -0000 https://status.ppro.dev/incident/183067#2573c3631f286cfe9a2f026eab0706289e8ed9ce09e8948e323b7703ccf4c021 BrovaPh ups status went down. https://status.ppro.dev/incident/183067 Sat, 25 Mar 2023 18:08:34 -0000 https://status.ppro.dev/incident/183067#a49ece174ee99f3f33c10f0cbd57c77c3bda28c8fd4de5d85668b013f1eff78f BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Sat, 25 Mar 2023 18:01:25 -0000 https://status.ppro.dev/incident/183067#5bf026bb01f3de79d45333cccd409bb99ef3c0ed4b7da86ada0f15acd75ae8fa BrovaPh ups status went down. https://status.ppro.dev/incident/183067 Sat, 25 Mar 2023 16:43:39 -0000 https://status.ppro.dev/incident/183067#d34cdf5f0da267513694e261cebf8ab0dd61cd3b15627ac4144c9c254139d954 BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Sat, 25 Mar 2023 16:30:40 -0000 https://status.ppro.dev/incident/183067#3882e680855144d1f90a22be36bbb06cfb61c5a23066d6cc40dae6a995c18b45 BrovaPh ups status went down. https://status.ppro.dev/incident/183067 Sat, 25 Mar 2023 13:38:49 -0000 https://status.ppro.dev/incident/183067#d9273609545f37bad48131d65184cdbfe33101ebfed56dd73fff48534df965b0 BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Sat, 25 Mar 2023 13:31:19 -0000 https://status.ppro.dev/incident/183067#f417e038c8e4ba0a6f8fa324a1d7871e0b19fca702c4c4dbc065c3f8e8e527a3 BrovaPh ups status went down. https://status.ppro.dev/incident/183067 Sat, 25 Mar 2023 01:04:43 -0000 https://status.ppro.dev/incident/183067#42b56c7d74542639c117fc9264e177c5af34226d98ce6d0435913976b892eeb5 ppro: ovm myst server recovered. https://status.ppro.dev/incident/183067 Sat, 25 Mar 2023 00:58:36 -0000 https://status.ppro.dev/incident/183067#58104aad8b3d296ac5a106eaafc0830411c94255e6de3d8ede850eda2420be5b ppro: ovm myst server went down. https://status.ppro.dev/incident/183067 Fri, 24 Mar 2023 17:00:08 -0000 https://status.ppro.dev/incident/183067#b08296893d90c533d8eb4c5674d93461f047f20bf47767264fad4943ad3c9c9b BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Fri, 24 Mar 2023 16:52:20 -0000 https://status.ppro.dev/incident/183067#62e2dca96b1d569e2a0e1dc1b68407a9d52434b12ed7d43dd394a42d4e9a2c14 BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Fri, 24 Mar 2023 05:56:55 -0000 https://status.ppro.dev/incident/183067#f4e0dc85cfd708586403f4032fd8540dd8e47891825f1e6c6a58cf986890ba79 BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Fri, 24 Mar 2023 05:39:02 -0000 https://status.ppro.dev/incident/183067#99a804d717bc8b405bd9d0b4e6904432ac11b377efd618fa677ca3916a664cfc BrovaPh ups status went down. https://status.ppro.dev/incident/183067 Thu, 23 Mar 2023 20:13:30 -0000 https://status.ppro.dev/incident/183067#24441adb5af52acc0a6c60aec4b8fbdbfdc3a26bd001de4d436fd3a6e3c5dab1 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Thu, 23 Mar 2023 20:01:08 -0000 https://status.ppro.dev/incident/183067#53dc208cf5505b0ef834bb3b69af197d7c7e24b10c3a48d63b073d966bbb831d BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Thu, 23 Mar 2023 19:59:17 -0000 https://status.ppro.dev/incident/183067#e2e0c20af6765b366d2f4a5fdda42000818f5b9f40716cf52522cc1410f88825 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Thu, 23 Mar 2023 19:51:00 -0000 https://status.ppro.dev/incident/183067#408123cc2f02fb4cf6c2de42b9527241fb5aad45819d0b59dc4852976c60ea61 BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Thu, 23 Mar 2023 18:53:25 -0000 https://status.ppro.dev/incident/183067#5717a0c2697e26c6824741c112c53632f8ceefde21bd5be1e647d6278f333d8c ppro: ovm myst server recovered. https://status.ppro.dev/incident/183067 Thu, 23 Mar 2023 18:44:17 -0000 https://status.ppro.dev/incident/183067#0d5278fb0d68ca270b2adb493f032ac840b67dd5bc1a0ed4620edaf2a5c955ea ppro: ovm myst server went down. https://status.ppro.dev/incident/183067 Thu, 23 Mar 2023 14:28:10 -0000 https://status.ppro.dev/incident/183067#52cbac1a40c569b55389aa8f7bd9409bfc0a2856dc3436427fab032a7def87fe BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Thu, 23 Mar 2023 13:59:37 -0000 https://status.ppro.dev/incident/183067#b79a2ecbb87f1b017e4b89593107d2c86c316a0d33501ebab6f17261d454744f BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Thu, 23 Mar 2023 12:15:42 -0000 https://status.ppro.dev/incident/183067#8cdc20c4ada897309d566a23f027f05e26fa28515230d02fa1696f35bd93a106 BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Thu, 23 Mar 2023 12:08:09 -0000 https://status.ppro.dev/incident/183067#6af7e37cf2bb1398a07fc4aa3901a79eaf6616783c834780f697f1cc7caed698 BrovaPh ups status went down. https://status.ppro.dev/incident/183067 Thu, 23 Mar 2023 10:45:37 -0000 https://status.ppro.dev/incident/183067#36c489ad12f5c9468467f1cae69ebc1014a6af9989956466114196415741ffa4 BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Thu, 23 Mar 2023 10:42:18 -0000 https://status.ppro.dev/incident/183067#4f5fa4214d9063dbe12b4a42467c64a677f1b0860390d7220e6528060c228ec7 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Thu, 23 Mar 2023 10:28:08 -0000 https://status.ppro.dev/incident/183067#46cd48159c7de3ddcc24bde9805ce456a430b95dd6df268a8216a3d0e87e2016 BrovaPh ups status went down. https://status.ppro.dev/incident/183067 Thu, 23 Mar 2023 10:21:00 -0000 https://status.ppro.dev/incident/183067#8d1a89de34985d6ecce5b2fc047819636755761cdcda0471bbe08d298562d9e2 BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Thu, 23 Mar 2023 01:37:28 -0000 https://status.ppro.dev/incident/183067#b24869b4722adae72ff6a267154a5cbd20d1960c11f505d8cec9ff0d5b96dc73 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Thu, 23 Mar 2023 01:26:05 -0000 https://status.ppro.dev/incident/183067#c1a568d4317654f99ac4de5f2eceb2be3f199a03f41c992071493ba28d17c899 BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Thu, 23 Mar 2023 01:18:21 -0000 https://status.ppro.dev/incident/183067#2fe85d983ef84fdabdcbadea93d3001d2fe51cb1f4bf68098e3ff9f57c56e9ad BrovaPh ups status went down. https://status.ppro.dev/incident/183067 Thu, 23 Mar 2023 01:15:53 -0000 https://status.ppro.dev/incident/183067#569847534f515caf94e3953ac3850b1f4e81ff2c1f49dc3500d6edf72e8036fb BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Thu, 23 Mar 2023 01:15:03 -0000 https://status.ppro.dev/incident/183067#650aaf9ef7a1bc745e72507b21f3bc7f44c3bb77e4f506225bbd108377132774 BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Thu, 23 Mar 2023 01:08:24 -0000 https://status.ppro.dev/incident/183067#686efafd892bd93b30229a094cc06905795b33637fd2b5d281976787bcb296ff BrovaPh ups status went down. https://status.ppro.dev/incident/183067 Wed, 22 Mar 2023 21:37:48 -0000 https://status.ppro.dev/incident/183067#2c1f3e6d6229190200314f1fda1ffdde107da13153566bf7cfbede08e7ad95c4 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Wed, 22 Mar 2023 21:29:52 -0000 https://status.ppro.dev/incident/183067#2fb4eb3224ee3c2b88ddb2d145f69ef67fdb2e1abdc2638d7e7d52d0bbaa36a5 BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Tue, 21 Mar 2023 21:35:26 -0000 https://status.ppro.dev/incident/183067#58116222b6790486c0f1fc96320a3247c229c68c1c40f26d70e6f9ada1a77aa8 BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Tue, 21 Mar 2023 21:27:56 -0000 https://status.ppro.dev/incident/183067#14fb966b6fd6618b8a563d84b525b545af5eb3d17df46e97ac4c75404cf0b680 BrovaPh ups status went down. https://status.ppro.dev/incident/183067 Tue, 21 Mar 2023 11:28:52 -0000 https://status.ppro.dev/incident/183067#5c2f4b385d22ee1462cf242df6c1119becc5345d33daa0f2dd03868c7ac080a5 BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Tue, 21 Mar 2023 11:16:37 -0000 https://status.ppro.dev/incident/183067#e3dd56998528d3e46c5dee50019313e678beb8fbb26ce1f83e007b786edc76c2 BrovaPh ups status went down. https://status.ppro.dev/incident/183067 Tue, 21 Mar 2023 09:39:22 -0000 https://status.ppro.dev/incident/183067#e381eb71cbbf85ee7fd6b66111750ddb248581d878a981f2ef12495d8d6a0e0a BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Tue, 21 Mar 2023 09:31:35 -0000 https://status.ppro.dev/incident/183067#eb0619d47a22f9ceeb870bc90b719d73e4aa2514509bb46cda363898bf186af5 BrovaPh ups status went down. https://status.ppro.dev/incident/183067 Tue, 21 Mar 2023 08:55:34 -0000 https://status.ppro.dev/incident/183067#7def3b66d145a10328d1356a53e9e360aed787430120aae60e181215772bd0df BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Tue, 21 Mar 2023 08:47:38 -0000 https://status.ppro.dev/incident/183067#c8d44047a5f76a0e7342d11276dff93d02f5055290baf479467d60d0874f5c94 BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Tue, 21 Mar 2023 04:34:31 -0000 https://status.ppro.dev/incident/183067#820fc04bfaec3ba1d1cdf4dd132ddb957f09b7324c1977a22690f05f3dd353d6 BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Tue, 21 Mar 2023 04:31:31 -0000 https://status.ppro.dev/incident/183067#193dc682c2f53ef74db1d3855762f2a261051fcf4a20464cb5672053841e7a4c BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Tue, 21 Mar 2023 04:26:36 -0000 https://status.ppro.dev/incident/183067#4bca6aac1b44b04f4286f7f69b738edc0128c9440f6e0a7b48d7c6b0849315f1 BrovaPh ups status went down. https://status.ppro.dev/incident/183067 Tue, 21 Mar 2023 04:23:25 -0000 https://status.ppro.dev/incident/183067#d7ac7ea0940da35be7a56afea8d3d4a26b6c1302e21b1e835fc588a2d8de737b BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Mon, 20 Mar 2023 15:50:34 -0000 https://status.ppro.dev/incident/183067#2b96b54fb3d0340a082e840fb996cab723ee9baff3a0fe4b9afbf1a972619d2c BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Mon, 20 Mar 2023 15:42:58 -0000 https://status.ppro.dev/incident/183067#18052bff08299d85a42722e3cf43de07babad792339da0634f13a129c2f5bb23 BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Mon, 20 Mar 2023 13:39:49 -0000 https://status.ppro.dev/incident/183067#a41f0083a33f7638f0674c29e4586acc638751a7f810f2c708a3911befb43720 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Mon, 20 Mar 2023 13:32:17 -0000 https://status.ppro.dev/incident/183067#c2611a89ed81bdc6958bc25184a941186712084d0903ca5b4449514037c95fd6 BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Mon, 20 Mar 2023 09:53:21 -0000 https://status.ppro.dev/incident/183067#75fde2b5e011819273b5b9a0ec8d426e2c2a0c7775404abcfe5496b43460539f BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Mon, 20 Mar 2023 09:45:26 -0000 https://status.ppro.dev/incident/183067#bd3ac193838a98a0de1697d22b8b979ee151dfdb851830d3844356cbc0f34862 BrovaPh ups status went down. https://status.ppro.dev/incident/183067 Fri, 17 Mar 2023 11:27:03 -0000 https://status.ppro.dev/incident/183067#f5f413bd1d68515f90ba01f64035dee355192e0398faca25fce870e229b0bf13 BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Fri, 17 Mar 2023 11:04:09 -0000 https://status.ppro.dev/incident/183067#d257f84d97dbf685bcd80a08794014e3de92866b289a5f504565dc8b17fb4ea5 BrovaPh ups status went down. https://status.ppro.dev/incident/183067 Thu, 16 Mar 2023 22:56:06 -0000 https://status.ppro.dev/incident/183067#de00cb8591ef351fb5099a4f38e84604a6fa975adb1cd2347fdd1b9995ee9e68 BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Thu, 16 Mar 2023 22:48:57 -0000 https://status.ppro.dev/incident/183067#3053a3b3629f0d5efd78955f1500a92478efb24b6b8366bc7590f3a895ebfc27 BrovaPh ups status went down. https://status.ppro.dev/incident/183067 Thu, 16 Mar 2023 13:14:47 -0000 https://status.ppro.dev/incident/183067#57c195ea0577ae5f4f86d29158b007788e87099b83a5bceddbd37005034ddd68 BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Thu, 16 Mar 2023 13:06:47 -0000 https://status.ppro.dev/incident/183067#4e8ba343f724b1dc8cb0cef06b84551e8e3c41612424d71a3644648ae1ae2d5f BrovaPh ups status went down. https://status.ppro.dev/incident/183067 Thu, 16 Mar 2023 13:06:11 -0000 https://status.ppro.dev/incident/183067#c01032dc9d28377fc2c2a861f83e580018d4c9be244fa850d9eccdfcf3fa54a7 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Thu, 16 Mar 2023 12:59:58 -0000 https://status.ppro.dev/incident/183067#f83183081faaa5fc07488ad948b37a99d8e2d6441cfae456b643bf085f31909c BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Thu, 16 Mar 2023 10:23:27 -0000 https://status.ppro.dev/incident/183067#eeeea6c8704edebf4531938febf258215d349963ea1a08a2ba24abb57cc7580f BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Thu, 16 Mar 2023 10:11:33 -0000 https://status.ppro.dev/incident/183067#88d4f6e7840cf2132d4d2ca49bb788f1792a7304b5e2f19422aae841fa60a4d0 BrovaPh ups status went down. https://status.ppro.dev/incident/183067 Thu, 16 Mar 2023 09:55:27 -0000 https://status.ppro.dev/incident/183067#31b55a501b609da1de59c3c4986728405b493a4cd6455a2ef5051c25d44cbeee BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Thu, 16 Mar 2023 09:43:11 -0000 https://status.ppro.dev/incident/183067#e6ed35177b93aab73ec804b2e3ae4ec279909f24631afa394b1a0c83c0b9370e BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Tue, 14 Mar 2023 14:22:33 -0000 https://status.ppro.dev/incident/183067#a2da388fdfe1ee94d0a73cb4a77e72af74bf6b7446ab11c1af4121f4bc3124ba BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Tue, 14 Mar 2023 11:53:57 -0000 https://status.ppro.dev/incident/183067#f4eaee181cc9384416dc41c664df78846cd734804c20eb9780210070913987ed BrovaPh ups status went down. https://status.ppro.dev/incident/183067 Tue, 14 Mar 2023 11:33:34 -0000 https://status.ppro.dev/incident/183067#2295adbbd783d50b6ad612a7ed1ef34828117a86c2bc8e0e427a7d01b0550aca BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Tue, 14 Mar 2023 11:24:08 -0000 https://status.ppro.dev/incident/183067#155e0674cde57d49a68421652ac74e3158c585dfb18270164c9dd83c5684468f BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Tue, 14 Mar 2023 06:35:12 -0000 https://status.ppro.dev/incident/183067#1a2cdc072eb3e787361cdb6c27c18374b82075ac1c32c54916d431cc5945a87b BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Tue, 14 Mar 2023 06:22:37 -0000 https://status.ppro.dev/incident/183067#dfbedd8e4891b85ad197664c4ba786d65a7e53147f254b70161548b72a20563f BrovaPh ups status went down. https://status.ppro.dev/incident/183067 Tue, 14 Mar 2023 06:19:59 -0000 https://status.ppro.dev/incident/183067#d30c5ff3136a486d53e449b5877de057b3a66f6dd7d0b8917f688b9d219e982d BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Tue, 14 Mar 2023 06:07:43 -0000 https://status.ppro.dev/incident/183067#088956124ca44e41493b3c8f719159613d90742d1dc7274e4ea6f0289dc10386 BrovaPh ups status went down. https://status.ppro.dev/incident/183067 Mon, 13 Mar 2023 11:08:51 -0000 https://status.ppro.dev/incident/183067#d2a307e3a285be211fe4808d1340e8a24dfb66c67d82d2934b3cacf7071bb004 BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Mon, 13 Mar 2023 11:02:00 -0000 https://status.ppro.dev/incident/183067#bd66dfca2a4977f325fcb606fd6bd0845d5aa11bf7cd1425d37f733bfc0a0811 BrovaPh ups status went down. https://status.ppro.dev/incident/183067 Mon, 13 Mar 2023 09:39:30 -0000 https://status.ppro.dev/incident/183067#24546dd8a09307be74950fdd92f361d548e43c376c42dca0ae1f5bec4426b9b7 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Mon, 13 Mar 2023 09:28:34 -0000 https://status.ppro.dev/incident/183067#33def655b078c24e17a9ccf2572fa8e068eda78c51e11fc2a65b5f37411eb17b BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Mon, 13 Mar 2023 09:26:46 -0000 https://status.ppro.dev/incident/183067#dec57595dc6276c4fd8cba34afd2126316ed3236338153ab576ccc7a4721d947 BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Mon, 13 Mar 2023 09:15:46 -0000 https://status.ppro.dev/incident/183067#06aa84761f4bba133a95377f70cfb8bc307845e476880f2899d5667c440ea080 BrovaPh ups status went down. https://status.ppro.dev/incident/183067 Mon, 13 Mar 2023 04:27:52 -0000 https://status.ppro.dev/incident/183067#27dd2640e1806297f36da6082e1a80cda18565e936837b12de23aa125d8809d6 BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Mon, 13 Mar 2023 04:01:33 -0000 https://status.ppro.dev/incident/183067#49406eabd2f8e718e2544b628e908ae4072c3b102dbfd84f444d5384097ff8d4 BrovaPh ups status went down. https://status.ppro.dev/incident/183067 Sun, 12 Mar 2023 20:44:56 -0000 https://status.ppro.dev/incident/183067#4c451baa4010e82b00fb6f66614f7e2b64b08b368a069126867718ab589c9107 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Sun, 12 Mar 2023 20:36:45 -0000 https://status.ppro.dev/incident/183067#8727a93e9867884f629f60fed59e48c701b00c6557b6b0321fcd061c9ff3ecda BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Sun, 12 Mar 2023 18:27:59 -0000 https://status.ppro.dev/incident/183067#4c3efb64300298308007e275324c9369934f11dc603ad144b293448b5aab2e1e BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Sun, 12 Mar 2023 18:10:45 -0000 https://status.ppro.dev/incident/183067#1d7ba0b060f344ff85a56ea382cf7ee54c3b4a08539ab53e2b7538db1ff14357 BrovaPh ups status went down. https://status.ppro.dev/incident/183067 Sun, 12 Mar 2023 00:17:59 -0000 https://status.ppro.dev/incident/183067#1477c85365e2115aae09927b3dcddb33c6e259088e2a9b0e5fce140ed0cd67a1 BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Sun, 12 Mar 2023 00:10:13 -0000 https://status.ppro.dev/incident/183067#eb8d731324c9197d3a3d4e990a7f2dbca675bd688ce26def7caca04f8aa4f13c BrovaPh ups status went down. https://status.ppro.dev/incident/183067 Sat, 11 Mar 2023 05:02:31 -0000 https://status.ppro.dev/incident/183067#016f5ebf35f383b44554e77fe92d0beb9e0338cc387b9eb9a87de22f1d54fd63 BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Sat, 11 Mar 2023 04:45:21 -0000 https://status.ppro.dev/incident/183067#81850375750cf20781fa61b5bd5cda8e7bb308237d06451290c16151df2430d6 BrovaPh ups status went down. https://status.ppro.dev/incident/183067 Sat, 11 Mar 2023 02:47:40 -0000 https://status.ppro.dev/incident/183067#7c3aec9848f1f51789fd9c0b1a506500f72b1a9b8e592610250c078ae5a19d1d BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Sat, 11 Mar 2023 02:40:09 -0000 https://status.ppro.dev/incident/183067#7dfefd50fc4f216397d53982af906c609d9163387709907e1df86c9117efb012 BrovaPh ups status went down. https://status.ppro.dev/incident/183067 Fri, 10 Mar 2023 11:53:14 -0000 https://status.ppro.dev/incident/183067#dc549f5d4367089599b4bc388c1ef473839ee758349cd22ab596eff732ba9c2c BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Fri, 10 Mar 2023 11:45:36 -0000 https://status.ppro.dev/incident/183067#3a9be211c071360515c2874b78841d05d84085ea6dd327c2e4179fcbd991f629 BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Fri, 10 Mar 2023 07:16:20 -0000 https://status.ppro.dev/incident/183067#a974571f4696f87b8efa6350cf8011824346515857b0e6ec3bd81fccc4f60d76 BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Fri, 10 Mar 2023 07:09:06 -0000 https://status.ppro.dev/incident/183067#f06af298f63d5c78196e1f01287fc2cd43d1f3b889a099382f0403ac6344709f BrovaPh ups status went down. https://status.ppro.dev/incident/183067 Fri, 10 Mar 2023 05:46:36 -0000 https://status.ppro.dev/incident/183067#48abe6808e683629513f5206384d67369eefd2179e20558d97eaa4cae1905f9a BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Fri, 10 Mar 2023 05:24:25 -0000 https://status.ppro.dev/incident/183067#6cb1ac6d34f09512c798157428b07c8dda3aaee2d625fbf908cdcb3410dc1445 BrovaPh ups status went down. https://status.ppro.dev/incident/183067 Fri, 10 Mar 2023 04:31:32 -0000 https://status.ppro.dev/incident/183067#de8a99e9922703c281cbf34f800bbceb818acfa8dfc349f808e11f5642d1f5a0 BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Fri, 10 Mar 2023 04:24:15 -0000 https://status.ppro.dev/incident/183067#b34cef76ba8bc438c4395c38aae61c8a83f620d3859119a653a9898da491a1fe BrovaPh ups status went down. https://status.ppro.dev/incident/183067 Thu, 09 Mar 2023 20:12:43 -0000 https://status.ppro.dev/incident/183067#a27550599ff5c134a9dcb74f9dbe1b617cddc96384f03f5c58f1ccd9f84a0f01 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Thu, 09 Mar 2023 19:30:41 -0000 https://status.ppro.dev/incident/183067#176057d0edf6745cfd0385bd89783d17ee42544c9d20096105687460e8cc6025 BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Thu, 09 Mar 2023 15:57:25 -0000 https://status.ppro.dev/incident/183067#a1c853d3644c97da673794c4dc65f4b28e9c1329871b90f8b2b42e7db778cb01 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Thu, 09 Mar 2023 15:50:12 -0000 https://status.ppro.dev/incident/183067#c0942624a60f5cf5cab7b18fc7120669de3fd860dafde21975c3d9ffabeb5a38 BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Thu, 09 Mar 2023 11:36:50 -0000 https://status.ppro.dev/incident/183067#532c25ab77bc3984e45a59d9d6ccf0597049a9d3b431c897297c5a47e940e8ef fj: jpyther docker service went down. https://status.ppro.dev/incident/183067 Thu, 09 Mar 2023 11:21:09 -0000 https://status.ppro.dev/incident/183067#d0800141514d26ac3b953449fdd74d07aa3db64f0e3aeb58ff4ddb6aba6ce0eb fj: jpyther docker service recovered. https://status.ppro.dev/incident/183067 Thu, 09 Mar 2023 11:12:27 -0000 https://status.ppro.dev/incident/183067#0597bf1d5fcbf269d0c4960b138b9926148e6b9933d290c54774f96d3e932cf0 fj: jpyther docker service went down. https://status.ppro.dev/incident/183067 Thu, 09 Mar 2023 10:22:29 -0000 https://status.ppro.dev/incident/183067#40a313d78229d7e8446e11144e096d69c98b59aeb1073deb5fdce630688c2b60 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Thu, 09 Mar 2023 09:54:06 -0000 https://status.ppro.dev/incident/183067#e49a22ecff0ac2dc3ebe3cc4a4e1b26c63c3e0f00c88d807b6f4f0f31e1fe56c BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Thu, 09 Mar 2023 06:21:17 -0000 https://status.ppro.dev/incident/183067#4699000d78351ba4ef04b8b40d5aa8cee1569869e63ed077b0c065b3d1c7f4b1 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/183067 Thu, 09 Mar 2023 06:20:08 -0000 https://status.ppro.dev/incident/183067#6e389270e8e76bdd7f0f939152f301b2194a79ebf93d644e0749ef9527e2c419 BrovaPh ups status recovered. https://status.ppro.dev/incident/183067 Thu, 09 Mar 2023 00:19:04 -0000 https://status.ppro.dev/incident/183067#0c3ee127add45ef0618f79d6bd014abe5b44305bd3dd6b10d5f2dae75f0e4f3f BrovaPh2 ups status went down. https://status.ppro.dev/incident/183067 Thu, 09 Mar 2023 00:17:24 -0000 https://status.ppro.dev/incident/183067#1e7cdd3c262c186a84d7c8f01ac40efe4605c8d0657b219e963fa757d84ff378 BrovaPh ups status went down. https://status.ppro.dev/incident/182656 Wed, 08 Mar 2023 14:34:25 -0000 https://status.ppro.dev/incident/182656#bce4742a38c05d8eeddc43f60c279e5f0bdc751d6c6fc0a5c7189b573ac6eaa0 BrovaPh ups status recovered. https://status.ppro.dev/incident/182656 Wed, 08 Mar 2023 14:17:32 -0000 https://status.ppro.dev/incident/182656#c72129a45010d7cee563c487d3e67021d6eecba0379eeb73e6ce4ffa59784b76 BrovaPh ups status went down. https://status.ppro.dev/incident/182656 Wed, 08 Mar 2023 11:29:33 -0000 https://status.ppro.dev/incident/182656#257cb833db4e0f292645ad19ea06d541771d08e566031107a1f825028362408e fj: jpyther docker service recovered. https://status.ppro.dev/incident/182656 Wed, 08 Mar 2023 11:21:03 -0000 https://status.ppro.dev/incident/182656#0cadbbd3f7cb1b67797532a911a3298bbdf7b8241c7a69a0c2b6718685c2ddd7 fj: jpyther docker service went down. https://status.ppro.dev/incident/182656 Wed, 08 Mar 2023 10:46:11 -0000 https://status.ppro.dev/incident/182656#afaa3a50869b78d07bfe9a750415c75696d1c41fae4bdb4469b6d325cb785294 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/182656 Wed, 08 Mar 2023 10:38:50 -0000 https://status.ppro.dev/incident/182656#798160eb49cb0d23f69e8c0c45d6bb48de4f4723555e62cfa9eaa78519c035ac BrovaPh2 ups status went down. https://status.ppro.dev/incident/182656 Wed, 08 Mar 2023 08:39:14 -0000 https://status.ppro.dev/incident/182656#64cac98d3f0663c4192469ab746b4433be58d5ad1ecdbc65fd6486fbe566ea34 BrovaPh ups status recovered. https://status.ppro.dev/incident/182656 Wed, 08 Mar 2023 08:31:43 -0000 https://status.ppro.dev/incident/182656#4d18028a44d7b43408647d35db46f5296fa4ffec3b5beff0d77c4fbf15712640 BrovaPh ups status went down. https://status.ppro.dev/incident/182656 Wed, 08 Mar 2023 02:49:12 -0000 https://status.ppro.dev/incident/182656#d79d31e2bf1d1298e6bc1e5bf145884c1177f01dbcd12c0ca1a6be08095c84ff BrovaPh ups status recovered. https://status.ppro.dev/incident/182656 Wed, 08 Mar 2023 02:36:10 -0000 https://status.ppro.dev/incident/182656#bb15767032ba1e7f05eb317481474134145a1d7fff83df6483e41ec19cbfe613 BrovaPh ups status went down. https://status.ppro.dev/incident/182361 Tue, 07 Mar 2023 12:34:51 -0000 https://status.ppro.dev/incident/182361#3b8b759d756a1ee3b405be399406c2248a7aa5d001f9b2d71ec2d44e517439bb BrovaPh2 ups status recovered. https://status.ppro.dev/incident/182361 Tue, 07 Mar 2023 12:22:14 -0000 https://status.ppro.dev/incident/182361#85bd5f8e09360ff0a7a760578c93ef99042fd3966b4142f29d73366f9207c317 BrovaPh2 ups status went down. https://status.ppro.dev/incident/182361 Tue, 07 Mar 2023 11:39:37 -0000 https://status.ppro.dev/incident/182361#6799982d4e135deb820f115f7fc017316f2d61f131cbab430567403591e31869 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/182361 Tue, 07 Mar 2023 11:32:29 -0000 https://status.ppro.dev/incident/182361#3ec02fe50865f854d3f7c668025021a28cb851190a8def5b18f6709a2acbe17e BrovaPh2 ups status went down. https://status.ppro.dev/incident/181467 Sat, 04 Mar 2023 21:41:12 -0000 https://status.ppro.dev/incident/181467#b97a08e268dea4e5cb676b6e7484f2fd90a4ff9f934b660ae77b52209bdb21bb BrovaPh ups status recovered. https://status.ppro.dev/incident/181467 Sat, 04 Mar 2023 21:29:05 -0000 https://status.ppro.dev/incident/181467#901a113f37e4675075a6108e4f72894544da2ccd911cbced929b8a4504206cd4 BrovaPh ups status went down. https://status.ppro.dev/incident/180912 Fri, 03 Mar 2023 14:39:33 -0000 https://status.ppro.dev/incident/180912#e01fce5e79ac059fabf04a85f9d5402ed034380a26422a102b7c5aecbbf6a1a1 BrovaPh ups status recovered. https://status.ppro.dev/incident/180912 Fri, 03 Mar 2023 14:28:38 -0000 https://status.ppro.dev/incident/180912#1b991cf0fd4b30a13fc179efbfabfdf8d67bb63eaa786c6979ae6c2e6c769823 BrovaPh ups status went down. https://status.ppro.dev/incident/180912 Fri, 03 Mar 2023 00:28:06 -0000 https://status.ppro.dev/incident/180912#db8bd2d69bd7bb15c69d5c1d8cb90fa40ce86d46f799ec3bf51c2df84d1c8c73 BrovaPh ups status recovered. https://status.ppro.dev/incident/180912 Fri, 03 Mar 2023 00:20:15 -0000 https://status.ppro.dev/incident/180912#c064ef398295d5bed825ecc480da00ea6545420cd56ccd45f3fcf1b2ea88f1eb BrovaPh ups status went down. https://status.ppro.dev/incident/180657 Thu, 02 Mar 2023 14:48:27 -0000 https://status.ppro.dev/incident/180657#dccbf8173bd7fabe66615526b70ace27e5d99cd9fba8d6c93115a74c5dfbc88a BrovaPh2 ups status recovered. https://status.ppro.dev/incident/180657 Thu, 02 Mar 2023 14:35:41 -0000 https://status.ppro.dev/incident/180657#2bab088c0b795d114f471a21c4cecf075194afa8224d97c14fee38c990e0e856 BrovaPh2 ups status went down. https://status.ppro.dev/incident/180657 Thu, 02 Mar 2023 11:52:25 -0000 https://status.ppro.dev/incident/180657#f02690c2449e448d0ba1868213ce9785772b4dd4c69f2e07c3d7ab3f51c73b89 BrovaPh ups status recovered. https://status.ppro.dev/incident/180657 Thu, 02 Mar 2023 11:45:05 -0000 https://status.ppro.dev/incident/180657#bd4396c9cde0aebc7fa6c3dafd0359aa020a93ed52021da39d42147f2ccd7bab BrovaPh ups status went down. https://status.ppro.dev/incident/180657 Thu, 02 Mar 2023 08:37:19 -0000 https://status.ppro.dev/incident/180657#d3b916ba18acdc0cdb8ac65781cd7da51865fda0a063b69445261441c74aa3b9 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/180657 Thu, 02 Mar 2023 08:30:06 -0000 https://status.ppro.dev/incident/180657#53020180a8d00050dd6327ced6265f87321c773e50c3600d1198281c5c83c40e BrovaPh2 ups status went down. https://status.ppro.dev/incident/180127 Wed, 01 Mar 2023 07:43:46 -0000 https://status.ppro.dev/incident/180127#86e733e7e8197b358f6381368f5330159529d217caed3f2b7edf3d4cbde0ecda BrovaPh ups status recovered. https://status.ppro.dev/incident/180127 Wed, 01 Mar 2023 07:40:31 -0000 https://status.ppro.dev/incident/180127#3f26a403726e3e30ea17fab23c10e237fe55ffcf1e91dec45d23e88ce022178a BrovaPh2 ups status recovered. https://status.ppro.dev/incident/180127 Wed, 01 Mar 2023 06:51:46 -0000 https://status.ppro.dev/incident/180127#cff39dff736e004a25d96dca8d5a0ad031396f355fea1f69a95bc0b33c830a36 BrovaPh ups status went down. https://status.ppro.dev/incident/180127 Wed, 01 Mar 2023 06:48:17 -0000 https://status.ppro.dev/incident/180127#ac8996ae6ff6a27f11e4876ac6cf09298c0d914c0a68e73e39b8a31aefa97315 BrovaPh2 ups status went down. https://status.ppro.dev/incident/180127 Wed, 01 Mar 2023 01:00:42 -0000 https://status.ppro.dev/incident/180127#8255e7ba2fa8f599f4c21009433c0affb01282a6c3979fe72f46d0beca61fd3d BrovaPh2 ups status recovered. https://status.ppro.dev/incident/180127 Wed, 01 Mar 2023 00:52:45 -0000 https://status.ppro.dev/incident/180127#b5207ca7f1541ab91d4cacdfcb37a3170b64c03cdf94bd249001f026ab0014f9 BrovaPh2 ups status went down. https://status.ppro.dev/incident/179994 Tue, 28 Feb 2023 16:55:26 -0000 https://status.ppro.dev/incident/179994#822d86852297fece91f15eefb0b7cc2f0e8b80b7f6db5d14bea88bcc70ae181e BrovaPh2 ups status recovered. https://status.ppro.dev/incident/179994 Tue, 28 Feb 2023 16:42:40 -0000 https://status.ppro.dev/incident/179994#a3bcad245a820a68b3850a387eaa3720ca907624f919d339772c8ec3ef9e1b0c BrovaPh2 ups status went down. https://status.ppro.dev/incident/179431 Mon, 27 Feb 2023 14:54:43 -0000 https://status.ppro.dev/incident/179431#e2478efc7012bdc2abfcd6504dc1b62d9dd6bfab63926a27c1fd978e750be7dc fj: jpyther docker service recovered. https://status.ppro.dev/incident/179431 Mon, 27 Feb 2023 14:40:10 -0000 https://status.ppro.dev/incident/179431#2d007fc0c285c3e5deb9249e37891c1d4738df544341d587b084978395eb89cc fj: jpyther docker service went down. https://status.ppro.dev/incident/179431 Mon, 27 Feb 2023 11:13:51 -0000 https://status.ppro.dev/incident/179431#8a11022140dedb2f430c0c58f4f234bb5a6255d9d4cb73f1826c927838092867 BrovaPh ups status recovered. https://status.ppro.dev/incident/179431 Mon, 27 Feb 2023 11:01:50 -0000 https://status.ppro.dev/incident/179431#2c083626fad4f81899eff21950129dc58d4081b70ade69bc843fb6f01b30055e BrovaPh ups status went down. https://status.ppro.dev/incident/179431 Mon, 27 Feb 2023 09:45:21 -0000 https://status.ppro.dev/incident/179431#c8bd745012c9a4859b872de0b6483d23c45b543d6c0b11b39c69c63083a7ab82 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/179431 Mon, 27 Feb 2023 09:37:14 -0000 https://status.ppro.dev/incident/179431#856a3b2e42abdf08be1ca8c0fe4fc89eaa8a094033e4bdb76adff3c93d6680fc BrovaPh2 ups status went down. https://status.ppro.dev/incident/179431 Mon, 27 Feb 2023 09:05:59 -0000 https://status.ppro.dev/incident/179431#92c9786dc2e8b4e39ff70d5c864a7044c2276dc4b884e33aee97546fcbc1fbfa BrovaPh2 ups status recovered. https://status.ppro.dev/incident/179431 Mon, 27 Feb 2023 08:53:03 -0000 https://status.ppro.dev/incident/179431#c3b62bc22dfc80e544e1ba5e0d16243a2afd1e359b6525a30ff64357ef1ac851 BrovaPh2 ups status went down. https://status.ppro.dev/incident/179431 Mon, 27 Feb 2023 08:15:10 -0000 https://status.ppro.dev/incident/179431#77a6b56ceb5d3d605014384f8aa0e60fc7ea64f63c1f4300c65e46deb2369c89 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/179431 Mon, 27 Feb 2023 08:07:55 -0000 https://status.ppro.dev/incident/179431#27ed31372566c44b0f1964573e92e551824ee875ee11182bcee8097f9ff55233 BrovaPh2 ups status went down. https://status.ppro.dev/incident/179431 Mon, 27 Feb 2023 06:50:16 -0000 https://status.ppro.dev/incident/179431#ece6c2961ad23c3adb02d439699d07f18e470b67c57d7ce62a51d1d3cb25675b BrovaPh2 ups status recovered. https://status.ppro.dev/incident/179431 Mon, 27 Feb 2023 06:48:28 -0000 https://status.ppro.dev/incident/179431#517dc79a2c4ea0fd3caca0e00cb804bf69a21f8e37f46281a434607ed3735687 BrovaPh ups status recovered. https://status.ppro.dev/incident/179431 Mon, 27 Feb 2023 04:18:12 -0000 https://status.ppro.dev/incident/179431#fabf97227259b36525f2bc0344225abe79d80d4124d60a4111a53ba65f23c963 BrovaPh2 ups status went down. https://status.ppro.dev/incident/179431 Mon, 27 Feb 2023 04:16:28 -0000 https://status.ppro.dev/incident/179431#1ae6897c60b5bede80a5869b891dc3a543788abd49c612ddbca9a00529f98e12 BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Sat, 25 Feb 2023 08:27:59 -0000 https://status.ppro.dev/incident/167167#0c416a71246baacf11d81a9a4f7b5a3ce700b0ddefb7530d7fc11553718172a7 ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Fri, 24 Feb 2023 18:45:06 -0000 https://status.ppro.dev/incident/167167#3aa4380452264d6862c7269b33ebff31ea19cf03c949187381891c6de0851192 fj: jpyther docker service recovered. https://status.ppro.dev/incident/167167 Fri, 24 Feb 2023 15:16:09 -0000 https://status.ppro.dev/incident/167167#b359cc5b0749cc94cab3290633691224de5b01e31506f91f4f95b4494a5720c1 ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Fri, 24 Feb 2023 12:39:33 -0000 https://status.ppro.dev/incident/167167#274d137750ec862d36b3d5377dde4a4c7d399c70f53ac8745ec4a4f7898281c9 ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Fri, 24 Feb 2023 12:13:13 -0000 https://status.ppro.dev/incident/167167#015e357411964eaf1537b36814623351fb43c06555508ac275cdf30463767fce ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Wed, 22 Feb 2023 16:34:21 -0000 https://status.ppro.dev/incident/167167#cecf4392ae5039ddb0a44ae0bee3ba9b728525ae6645ce1bd687905268d535b8 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Wed, 22 Feb 2023 16:33:04 -0000 https://status.ppro.dev/incident/167167#bbf5ca32b1d036496232d57420bed6f1ec3d4d046e777021fb01c5eee8b99374 BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Wed, 22 Feb 2023 16:12:08 -0000 https://status.ppro.dev/incident/167167#b7afe20c51f7f5fd6cfd8acddef7e571b03c99e2d08e5d7167b775f53e8bf4dc BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Wed, 22 Feb 2023 16:10:58 -0000 https://status.ppro.dev/incident/167167#3e0ba9f635ba0acb2f9a63a11614696189c68a94a4810a474330ca2f7eaf11df BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Wed, 22 Feb 2023 15:30:01 -0000 https://status.ppro.dev/incident/167167#9392156b13ba67200b519ecd0da4f56b11de572017c4144f2a4c315a79ddbdea smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/167167 Wed, 22 Feb 2023 15:22:53 -0000 https://status.ppro.dev/incident/167167#c065ae52dad71dd0c4899bc2bc18f34d0d2f30009f9f3c78a4613cc2dea3219d smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/167167 Wed, 22 Feb 2023 10:38:29 -0000 https://status.ppro.dev/incident/167167#8d8cb6d9a12e0561e690bcd8001296f9c2ca263574c08e4d12e8d28518afed4a BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Wed, 22 Feb 2023 10:31:20 -0000 https://status.ppro.dev/incident/167167#aed4e77936918651746b6aa90a3f91e246db1708aff473936fba95473729fb5c BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Tue, 21 Feb 2023 07:49:57 -0000 https://status.ppro.dev/incident/167167#661ca770b5144aef043d1658c40bf53fa3b4ba6be54fb57ac1c4496ea803b88d BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Tue, 21 Feb 2023 07:46:29 -0000 https://status.ppro.dev/incident/167167#4af7c020768506d84ad1dcd371949660a538c4b76d4c93c45269f37dde30f523 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Tue, 21 Feb 2023 05:17:17 -0000 https://status.ppro.dev/incident/167167#12283e6812b738b01de9bf0641ad6d0e8e930820b0ae7fb129e17a2dd229c4f5 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/167167 Tue, 21 Feb 2023 05:05:09 -0000 https://status.ppro.dev/incident/167167#4f2deca15916b60b15b238a615b07abae0d1ad1e4e9a7b625ec20f6d361becf1 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/167167 Mon, 20 Feb 2023 20:08:04 -0000 https://status.ppro.dev/incident/167167#2e003a16ec40e56426936efac998652aa7cafbf39adb94fb6b8df14296366709 BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Mon, 20 Feb 2023 20:04:17 -0000 https://status.ppro.dev/incident/167167#f876d18b0f7b67c01e3c3ffa11ec3a065a9ca577556cd279a12d3cca9bf386c3 BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Sat, 18 Feb 2023 10:37:09 -0000 https://status.ppro.dev/incident/167167#d9a793a284d818950bec0fdc80280fc8b16f9f955710c3e07ed2f82d18e4c03f BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Sat, 18 Feb 2023 10:29:50 -0000 https://status.ppro.dev/incident/167167#dec022cc9e10ae80a571e85117811c242d45197535eeece957817fb936111c20 BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Sat, 18 Feb 2023 08:58:28 -0000 https://status.ppro.dev/incident/167167#7feac037b62d591ffb1214e356157f3dd197fc22fee5bbde47b1b65af6f0d4fd BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Sat, 18 Feb 2023 08:57:12 -0000 https://status.ppro.dev/incident/167167#27e687753ddeb2275de4e45e06e7bf765ad3023ab37cfdc8dba0496c8e950e7e BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Sat, 18 Feb 2023 04:15:10 -0000 https://status.ppro.dev/incident/167167#ce7faee17b36d306e9f9b94d8edb5647497b8192e40364829f517008c7a084d7 BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Sat, 18 Feb 2023 04:11:16 -0000 https://status.ppro.dev/incident/167167#916f52293251d12a9075c37455d083ce3bcee5fbaa71a6f5fc74792980b5e5ce BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Tue, 14 Feb 2023 03:50:47 -0000 https://status.ppro.dev/incident/167167#1f71558701f0bf3e120672681d75a75a5e526e273f5d88bdb1164b84be569044 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Tue, 14 Feb 2023 03:38:39 -0000 https://status.ppro.dev/incident/167167#d139ee1f841b2fd81d85227c1cc00f80edb1902680fde68d687c9c73ff96f607 BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Sat, 11 Feb 2023 01:19:34 -0000 https://status.ppro.dev/incident/167167#dbfcd60be1886fc25612c591e6d58d5f12e5edfd376b28dd35da2b4681bc9880 ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Fri, 10 Feb 2023 22:05:16 -0000 https://status.ppro.dev/incident/167167#cf68ff80339a08990af77c4f0d8a179d9ce45120679d27b874d4d0e12b6e8b46 ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Fri, 10 Feb 2023 16:25:39 -0000 https://status.ppro.dev/incident/167167#c6c9b312ee8b7364ccfaf27913e038dcf6fc8702d082a3b9babbcd0b05b377b4 ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Fri, 10 Feb 2023 16:19:40 -0000 https://status.ppro.dev/incident/167167#1110f8f50c22a4593204051fa37148e9f762341b1480932dda64691076c9ae2c ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Fri, 10 Feb 2023 16:13:39 -0000 https://status.ppro.dev/incident/167167#e589395b10a680c05d7d6c2deae1215fdfc25f7c1e98b7982ef8509057654ba8 ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Fri, 10 Feb 2023 16:08:15 -0000 https://status.ppro.dev/incident/167167#86fc3749e2c2cf88c371c141edf48eea1fa4e2eadfa809a26ed66d442577b8dd ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Fri, 10 Feb 2023 13:16:16 -0000 https://status.ppro.dev/incident/167167#77a9220635d8ea611616c539bb54fc8f3cec2de5c28cd909495a42c4afa85101 ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Fri, 10 Feb 2023 13:02:14 -0000 https://status.ppro.dev/incident/167167#d53d75a172433450b81c9a633ff06f513951f9f9aa3477c3d6884e5bef52d391 ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Fri, 10 Feb 2023 08:28:17 -0000 https://status.ppro.dev/incident/167167#dc734784d0f3c955e0f2eabfc60737e22baadfb13a79a9182ec8bc2a5835349d ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Fri, 10 Feb 2023 08:22:12 -0000 https://status.ppro.dev/incident/167167#998898f00a83998b097803bcef1ffd9c03f02f1d91425f9b7891576c8f9a6020 ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Fri, 10 Feb 2023 08:16:11 -0000 https://status.ppro.dev/incident/167167#22d97d02674f5a1057be3dc2f648a40b831219e5e439e2018d26ee98e87a22be ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Fri, 10 Feb 2023 04:14:13 -0000 https://status.ppro.dev/incident/167167#2c993c2d4d5119638388c4bc9ce99594eb247fb5cc6233e3ef07d139d99d425f ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Thu, 09 Feb 2023 22:42:48 -0000 https://status.ppro.dev/incident/167167#1ee68487eabd0b304c789dbe85078672d31de309fb0cf5c95d34ed3de04b9648 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Thu, 09 Feb 2023 22:35:28 -0000 https://status.ppro.dev/incident/167167#8e89fa3674b3ebff9df837bf8e82816a0d1345a633f34cf46e8967c4a51f28b8 BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Thu, 09 Feb 2023 22:13:16 -0000 https://status.ppro.dev/incident/167167#7d1172f858fba31969d4ffc237aa7e2b8bea0e06ce4008572ff74ed6ed0b41f1 ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Thu, 09 Feb 2023 19:14:07 -0000 https://status.ppro.dev/incident/167167#f130e5b9713b9ad7d435f7d8b1040971752f1f6c497e3c2965c2e4a7757574a8 ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Thu, 09 Feb 2023 07:11:59 -0000 https://status.ppro.dev/incident/167167#4c09517cb44761ca841e3b47044edcd06c28f1258a602537a1f9d72020c52dae ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Wed, 08 Feb 2023 16:12:56 -0000 https://status.ppro.dev/incident/167167#f85061a9b4ee00e94722092fad049bf609ad8197932ff2ffdcd718069ee2a1a1 ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Wed, 08 Feb 2023 10:26:54 -0000 https://status.ppro.dev/incident/167167#1c37588c91c410fc6786b3fc533f1927cc37092fc8f680fbc9638b61abbabd26 ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Wed, 08 Feb 2023 10:16:09 -0000 https://status.ppro.dev/incident/167167#ba37af75bc77b63cfff72e0fff01d8f0773689e74691664e429f5e3e1e11eb8f ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Wed, 08 Feb 2023 08:18:03 -0000 https://status.ppro.dev/incident/167167#9568e82a87b54fedabf62fcf8d5fa64dede7e72645c0bfddaa3db222a1235694 ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Wed, 08 Feb 2023 07:12:51 -0000 https://status.ppro.dev/incident/167167#0d9a7ecdc54a8f45c0b0913ba8122f62ab80a2ead1efb6b382d59d95943ef52e ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Wed, 08 Feb 2023 06:49:48 -0000 https://status.ppro.dev/incident/167167#6f9f8df8be4a5cfb4add3f8292c2b4a02374b8719490e2615d17cbbe0e955938 BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Wed, 08 Feb 2023 06:46:16 -0000 https://status.ppro.dev/incident/167167#2040e6a924e59bf5c445a67109db1c8e641078388623fed212b854e197913e9d BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Wed, 08 Feb 2023 06:38:53 -0000 https://status.ppro.dev/incident/167167#f5b46756d43f8bb45810f21a8e25f0761e000fdbfb40add63be1f38f68ab08c8 ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Wed, 08 Feb 2023 06:32:32 -0000 https://status.ppro.dev/incident/167167#8a56032fd5d2850984eba566e23bf94ff74e0fefaaf1aeae5ed8510fcbfaec71 BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Wed, 08 Feb 2023 06:29:23 -0000 https://status.ppro.dev/incident/167167#d64adb4d17f2f759375eaced9abaa7d14c1746df5521bec5999d466a72f8b296 BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Wed, 08 Feb 2023 05:48:50 -0000 https://status.ppro.dev/incident/167167#50573c0b79769d119e6b0da6e1117ecf0e069f330a9ec1fcd1040840233f80cb ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Wed, 08 Feb 2023 01:23:56 -0000 https://status.ppro.dev/incident/167167#2485227e3ba411394bf304cc9bb89f0c0e19f6daf7aa46ea51b90ed61d033997 ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Tue, 07 Feb 2023 22:18:49 -0000 https://status.ppro.dev/incident/167167#77c4b47bc6d56878f74b3f044681911f1385e9488eb87823151377af57fd3e07 ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Tue, 07 Feb 2023 18:09:35 -0000 https://status.ppro.dev/incident/167167#727954b5e1f50164e16bf7c484f57cd4dcf99bd1a0b5892bda82c6d99f5a79d9 BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Tue, 07 Feb 2023 18:06:10 -0000 https://status.ppro.dev/incident/167167#0a81fd67bc1fbe49b05d8520663453ee7323e46c43314d939096822fd63ccc2e BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Tue, 07 Feb 2023 18:02:28 -0000 https://status.ppro.dev/incident/167167#cf05c9f096fd1ced83705d92185b21a7956e44a2a1db091e582f52703ebad4f9 BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Tue, 07 Feb 2023 18:00:08 -0000 https://status.ppro.dev/incident/167167#0404724934e8316727aeff9bc15fceb5eed60b420a7a9b1023c241b37e5d83f8 BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Tue, 07 Feb 2023 16:45:43 -0000 https://status.ppro.dev/incident/167167#00b245e6870bd5b968a5f41067abdb57bca6e4d084e7e7bd849039680aa285be BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Tue, 07 Feb 2023 16:44:27 -0000 https://status.ppro.dev/incident/167167#b14db7bddde9281fbe7bacb9a638c31f44494c460fa134765fed335440f31a79 BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Tue, 07 Feb 2023 16:18:41 -0000 https://status.ppro.dev/incident/167167#f805c3b5312d8be9bcab7e960bcb0f92b284c1850ed9d15e46683e1a47510a06 BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Tue, 07 Feb 2023 16:17:04 -0000 https://status.ppro.dev/incident/167167#c5b4c9c5df0a6a79e5d8ab644f79652ff97dd868178db310b374509fe91d74d3 BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Tue, 07 Feb 2023 14:39:18 -0000 https://status.ppro.dev/incident/167167#5903150bf93d4e3903a3afa685780265fc3e76deeab377e08f7d98055891a69b ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Tue, 07 Feb 2023 14:28:27 -0000 https://status.ppro.dev/incident/167167#e48263b7d8e6f282399a9c629554ac00c67a7cfbbbd795769b7505f738369831 ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Tue, 07 Feb 2023 13:30:57 -0000 https://status.ppro.dev/incident/167167#14c14f37691a20d3f8eda15572fafe87dbb461185f3716340c0cf75ed53017e6 ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Tue, 07 Feb 2023 13:16:34 -0000 https://status.ppro.dev/incident/167167#62a08f5151d7f71c2f428bbba99a3f08f6635e1daa628c0d49393aa421c9212d ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Tue, 07 Feb 2023 04:13:17 -0000 https://status.ppro.dev/incident/167167#01d4631927262070c1d8ee8153f9e6a26b07c9d7861113374419c503349556db BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Tue, 07 Feb 2023 04:06:07 -0000 https://status.ppro.dev/incident/167167#15e4e6244a7191c5d6d6987a95756d2fbb2482834e6e7a5335fc3634c59aa6a6 BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Mon, 06 Feb 2023 22:15:03 -0000 https://status.ppro.dev/incident/167167#efc413ffe156fe79e21f82eff9b203ca10ac81884ba8ce58b831c2c12cbff2d2 ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Mon, 06 Feb 2023 19:10:04 -0000 https://status.ppro.dev/incident/167167#9684b19f771e6eaca175b3be74a3cfbb9f307173dc3ba704ca0d05061eaad5b7 ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Mon, 06 Feb 2023 13:50:57 -0000 https://status.ppro.dev/incident/167167#4ed175dbfb95734ad0f60fd3ef4c66c19569a2980943bbf2d87993df919ac3cb ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Mon, 06 Feb 2023 13:39:54 -0000 https://status.ppro.dev/incident/167167#874f920d8508bbd7299c37877901fe2fe8eb493a6ee6bdf6fb5786876876d2d5 ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Mon, 06 Feb 2023 10:36:09 -0000 https://status.ppro.dev/incident/167167#a289aa147828ac2f6b024662ac7e16bc71b902d3a70c26cfbc7e46f87a4fd342 ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Mon, 06 Feb 2023 10:22:04 -0000 https://status.ppro.dev/incident/167167#8fdeaed0363f1874a60d2f5cb01b04c6356144ed3deaecec02d32c7da6c05356 ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Mon, 06 Feb 2023 06:30:06 -0000 https://status.ppro.dev/incident/167167#bb37d1a03f996c493ee0230d2671547e96f9eb91e5e3711182cb9b5a111f845f ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Mon, 06 Feb 2023 06:13:05 -0000 https://status.ppro.dev/incident/167167#24b295f9e5e40e82779cbb7a8e73c0b3d6a5cf52456b0ec009b19b192db52b98 ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Sun, 05 Feb 2023 20:57:08 -0000 https://status.ppro.dev/incident/167167#2fb7dfeec9db49c1b90fe46341992c235c580956346b135d51338e9995402334 ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Sun, 05 Feb 2023 19:16:06 -0000 https://status.ppro.dev/incident/167167#7b3409301f19c376672d0304d29adb2d999ac6955954dcb1c7447e42d3c11bfa ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Sun, 05 Feb 2023 11:32:47 -0000 https://status.ppro.dev/incident/167167#0146d66000b4c476c774d2d04785d684071e7a49951e7388944e96e3225ceb64 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Sun, 05 Feb 2023 11:31:36 -0000 https://status.ppro.dev/incident/167167#5d7b2ecbdfcd3f721aeb97b0280f605347e2803cead594c949a089b74bdf4118 BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Sat, 04 Feb 2023 18:40:43 -0000 https://status.ppro.dev/incident/167167#75a4a162efc27df6eea68ea89eb298512a572e8ff071955c924c4db3555c9614 BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Sat, 04 Feb 2023 18:39:23 -0000 https://status.ppro.dev/incident/167167#c0b09862d61730384540570b0c983850b63139c9d096419b69b61398c97da6b1 BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Sat, 04 Feb 2023 18:17:46 -0000 https://status.ppro.dev/incident/167167#00ee7acb6c6ecf846b02c38c798d534a9b2c16089dd8699cc4412044310d25e4 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Sat, 04 Feb 2023 18:16:31 -0000 https://status.ppro.dev/incident/167167#fdc36a181a19e3c02f986ac2947249ad6d9cc06f4a4776ed98280defd3779c60 BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Sat, 04 Feb 2023 17:23:36 -0000 https://status.ppro.dev/incident/167167#bfbad635105d6f854ae2bf54a3fca5cbef161919654daeba56d150c2aaef4f67 ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Sat, 04 Feb 2023 16:33:07 -0000 https://status.ppro.dev/incident/167167#533775d2f99c84edc0a2dd0bbb2877fe42b86d50868a8cbb8536bdb2a6cdb08e ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Sat, 04 Feb 2023 10:20:41 -0000 https://status.ppro.dev/incident/167167#9982568d84f9389244c07222494e1f2febcfd748c12c19cd1fb9e34170c8030f BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Sat, 04 Feb 2023 10:19:24 -0000 https://status.ppro.dev/incident/167167#f860531f4c6fa44d748f381a90fa66038eab4fd06a5f06cd31f98e6177286c75 BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Sat, 04 Feb 2023 10:17:34 -0000 https://status.ppro.dev/incident/167167#cfcbd72a03dffdef8142c9f3a380a488de74f9e475a53d65734a81e4c2e69e06 ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Sat, 04 Feb 2023 09:56:37 -0000 https://status.ppro.dev/incident/167167#d0af61bdabef56262208f3417b9560fb1595e93d760cdbf08bba10492fb4ddc7 BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Sat, 04 Feb 2023 09:52:50 -0000 https://status.ppro.dev/incident/167167#9b9e891f1b77d7d5bd256891c5fa6977558663953b6994a84e3f04e57faf5439 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Sat, 04 Feb 2023 08:42:32 -0000 https://status.ppro.dev/incident/167167#1ba1af3415d97369b134a4eff67ddd11904a944d9de4df3e08d31e8c0c78ddbc ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Sat, 04 Feb 2023 01:23:40 -0000 https://status.ppro.dev/incident/167167#adef65e15b4bb3980b3d7ddcbe1354ca966339cdce0c96baf6a3e9a62048f8a2 ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Fri, 03 Feb 2023 22:03:25 -0000 https://status.ppro.dev/incident/167167#000c89a0f40266ec0737f0e93060c2f0011c0911ae73202d402f84999413287a ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Fri, 03 Feb 2023 18:55:36 -0000 https://status.ppro.dev/incident/167167#9d0bd91c23443abb64ab81790b2be69b2632320555976a0f9a319027ab9e5fe9 BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Fri, 03 Feb 2023 18:54:05 -0000 https://status.ppro.dev/incident/167167#7e9d57e1c3116994927fc50ce312a44dc284879d07df195ad20c484e1435c7ff BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Fri, 03 Feb 2023 16:04:42 -0000 https://status.ppro.dev/incident/167167#b92e5f5906b9f1e2207fb6d500928743dc669911d69fcb7566276bf1a967bf38 ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Fri, 03 Feb 2023 15:50:46 -0000 https://status.ppro.dev/incident/167167#32cce93b69efc34090043e30203311a517812f977371e092bcaae71183ef2145 ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Fri, 03 Feb 2023 13:39:46 -0000 https://status.ppro.dev/incident/167167#ddf6e5ecf7786b80d9b4646d4c474ef08c916dfb970ecac537ef71c6b6a165c2 ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Fri, 03 Feb 2023 13:34:42 -0000 https://status.ppro.dev/incident/167167#179342511f9a5c314bd44a1a9051e117d61378815ba4d5d8c02e030b445dbc5f ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Fri, 03 Feb 2023 13:27:44 -0000 https://status.ppro.dev/incident/167167#9fdaebd40df14078b4c4e6d3cbd917885a5d1ef0b0e878f1a7c965f427820d2a ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Fri, 03 Feb 2023 13:07:38 -0000 https://status.ppro.dev/incident/167167#37043a8e0f7742207ae11c5e73b2600791f724eb8c5a078b68866e0c47d105a6 ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Fri, 03 Feb 2023 02:53:38 -0000 https://status.ppro.dev/incident/167167#85733c617962e3961409f6142f098900ebae0a88744a7b0b0a5311a61958a4b3 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Fri, 03 Feb 2023 02:52:21 -0000 https://status.ppro.dev/incident/167167#084c2d5204ed0b7f545c44a8f8dfc54e8e754e6b592b000651d4c8bf777ae0b5 BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Fri, 03 Feb 2023 02:45:05 -0000 https://status.ppro.dev/incident/167167#358bb8a0c1c80d713086a9ab942c0f8419a36e27dc1e47341150afd9e77ab7d7 BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Fri, 03 Feb 2023 02:41:24 -0000 https://status.ppro.dev/incident/167167#32a0aaf672c67ef1edca4ee23dc63365a9526325b9039d8cc83461b7290974ef BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Thu, 02 Feb 2023 20:58:43 -0000 https://status.ppro.dev/incident/167167#3da888e02b5fe0803190148d05948bd21feb4ac73a5926ec30953989e9d715b4 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Thu, 02 Feb 2023 20:57:05 -0000 https://status.ppro.dev/incident/167167#08f23a8013dec27cdb7905a8cd4551347b90e6fd0626fdf18e37c37ee4899cfe BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Thu, 02 Feb 2023 20:21:25 -0000 https://status.ppro.dev/incident/167167#a8ded6ce3314b1cc17e635de65fa6ddc41c37c41c1d736b230c7e950fb3216c1 BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Thu, 02 Feb 2023 20:19:56 -0000 https://status.ppro.dev/incident/167167#a31c7e3ab4efc9311e5030acad26f044af0c040dd30eb103ae158033a20fe465 BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Thu, 02 Feb 2023 13:37:06 -0000 https://status.ppro.dev/incident/167167#e33963941457ec151fa9664bf27e2d689c8541f95951c22b4c3488621a9fbf59 ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Thu, 02 Feb 2023 13:25:56 -0000 https://status.ppro.dev/incident/167167#d21d7f085df2d98e45e460d9330a78bd5855728832ce3c70dcf84699a6fdd6e6 ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Thu, 02 Feb 2023 10:27:36 -0000 https://status.ppro.dev/incident/167167#05707d1f17e0b3965f67d54fdf3f86b027dc40be8d6cf8ed181a0c3b2a90d072 ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Thu, 02 Feb 2023 10:04:43 -0000 https://status.ppro.dev/incident/167167#a7bc1b3ba296d07c75a4b62aa486a703df8adda0974eda1a81b31cb32e5703c3 ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Thu, 02 Feb 2023 05:52:45 -0000 https://status.ppro.dev/incident/167167#bf2a3356a56dad50dad896e2b0a5c6ff10c7c2c3d539d51ce497592584da54d5 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Thu, 02 Feb 2023 05:51:08 -0000 https://status.ppro.dev/incident/167167#c461cb930ef0cc011c7ddc9120c68019867fc25e0ff71f412bee4567c8648147 BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Thu, 02 Feb 2023 04:54:37 -0000 https://status.ppro.dev/incident/167167#6069f49b2a6be7662869c1258b0ff786d00b31a366d649902f75345fbc329645 ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Thu, 02 Feb 2023 04:20:42 -0000 https://status.ppro.dev/incident/167167#ba34e63abde4e75cd04aaeeed53ceb6b13fb5489e442a3720febfab6467c9b9c BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Thu, 02 Feb 2023 04:19:05 -0000 https://status.ppro.dev/incident/167167#04cf62de4e7e823f38a1dfc47e22f62b0ae3157452f445c4b03b17d48a0b45d7 BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Thu, 02 Feb 2023 01:16:22 -0000 https://status.ppro.dev/incident/167167#f2f9531fc7b045a57e4c76856621d5fe2b7dbc7c481a18cd21048f1492d41db5 ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Wed, 01 Feb 2023 19:18:23 -0000 https://status.ppro.dev/incident/167167#a611f9ebe403e3e26d97e2698c73a27a36f9e73443cbab462d2caaa1c8ffa1cb ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Wed, 01 Feb 2023 18:21:03 -0000 https://status.ppro.dev/incident/167167#ff93d0b53f6feea7b00c3d7d1863002588d22dccf261307e45e27dbdc7f7203a BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Wed, 01 Feb 2023 18:17:49 -0000 https://status.ppro.dev/incident/167167#ce0b0e95c31f3979a15329c5db97ba21c769087e1e8b6e73a2f6b3a9478389a7 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Wed, 01 Feb 2023 18:14:00 -0000 https://status.ppro.dev/incident/167167#dde8ea6332fbc17bb92b787b6b16650b8bc6d68841ae9fec611bdbdee3d0d014 BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Wed, 01 Feb 2023 18:10:38 -0000 https://status.ppro.dev/incident/167167#37b02f37b8a93d0c7b9439d48222a45418136d3c066da44aa57185a4f105bd22 BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Wed, 01 Feb 2023 16:10:20 -0000 https://status.ppro.dev/incident/167167#be6a02185a576f182fd8793530b771d77921daa83d2c6427298b1db2a5ca7c07 ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Wed, 01 Feb 2023 06:51:29 -0000 https://status.ppro.dev/incident/167167#f4ac827105a03c906cf49433a37dd7ef746fe9368050ffef6401b7d4c8c6a082 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Wed, 01 Feb 2023 06:49:57 -0000 https://status.ppro.dev/incident/167167#db4dad590b14538cec6aebb3b2a323321532a60cbe886c8578cceae1631d2302 BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Wed, 01 Feb 2023 06:19:26 -0000 https://status.ppro.dev/incident/167167#7f8c8bad0737af05ac425abf8e6267c502c19b7efb8c3159fce919d5e620397e BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Wed, 01 Feb 2023 06:17:48 -0000 https://status.ppro.dev/incident/167167#f0f0bfcb5f756f787df26d53545748d22e2b7c80babd9c5496d32904ea3afd8c BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Wed, 01 Feb 2023 01:17:24 -0000 https://status.ppro.dev/incident/167167#16515a53c6a6b4edeb49004e34d67aee25702e2b86a2f636bc18b7620be5772b ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Tue, 31 Jan 2023 23:56:18 -0000 https://status.ppro.dev/incident/167167#50144d27899c46ea191284fa564d229a18fd7fd99362fa4b56d432a2891542dd BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Tue, 31 Jan 2023 23:49:47 -0000 https://status.ppro.dev/incident/167167#fb93dd18fcb9df55eb4cfd6cae9ab02cdb76a806c855bee933435179f36c2731 BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Tue, 31 Jan 2023 22:29:26 -0000 https://status.ppro.dev/incident/167167#c0293bf27795e69ed89a284a3399ca103144a12a815d70f460220ab1fdeebf6c BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Tue, 31 Jan 2023 22:28:00 -0000 https://status.ppro.dev/incident/167167#dc7542f84e40c63d9b035ee789458fcdb894c5d96ce626e8a2a64a940fc18835 BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Tue, 31 Jan 2023 22:12:17 -0000 https://status.ppro.dev/incident/167167#03439f1a3e3368986ca708bb9597935f0065f866954762b40e44cb4d4cd26205 ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Tue, 31 Jan 2023 16:36:33 -0000 https://status.ppro.dev/incident/167167#a600c2bab85ea38184265095a31db7170736c1b2f7b16ebc20e83faaaf831dfb BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Tue, 31 Jan 2023 16:34:51 -0000 https://status.ppro.dev/incident/167167#5d1cc6f43bf555196c6f16caed90954afc345d0291fde54dbed80fc6ea5b2ed2 BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Tue, 31 Jan 2023 16:23:15 -0000 https://status.ppro.dev/incident/167167#15a84fc90ec702368029eee61d3c300465843604b0477b9ee29c05d406268c0b ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Tue, 31 Jan 2023 16:12:15 -0000 https://status.ppro.dev/incident/167167#af2dee4c228f1d81b6db8edf9fade53f84639670ff2ab6c7252b438df47ae020 ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Tue, 31 Jan 2023 15:39:25 -0000 https://status.ppro.dev/incident/167167#61a7d717f1ebc494ec818b69fb16f6759f8b8ffe19cf9839172af0fa81872e4e BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Tue, 31 Jan 2023 15:37:47 -0000 https://status.ppro.dev/incident/167167#762c545c0b68095ff3745ace0916fa436f1dbb2a85e2f467a89967e6469475ab BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Tue, 31 Jan 2023 13:38:16 -0000 https://status.ppro.dev/incident/167167#7b31e7e3df9e3bd8953fb2e1203d8e9135bc750ae39cb7da3a7b65f611857405 ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Tue, 31 Jan 2023 13:20:46 -0000 https://status.ppro.dev/incident/167167#1216929c5482a69d4f94bb3ca33b970749fe25474ee2ad1c145fd6bfbb1eecd0 ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Tue, 31 Jan 2023 12:01:48 -0000 https://status.ppro.dev/incident/167167#184b37f16a064c3b5034e0c30f2a1bd7a7687752a5d8affe475e8661f77ccbfc BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Tue, 31 Jan 2023 11:53:44 -0000 https://status.ppro.dev/incident/167167#9a8a6defa61e918ebbd273e4ee796ff622a6d134ae2593cbfd32ad797c2bf3fa BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Tue, 31 Jan 2023 07:07:02 -0000 https://status.ppro.dev/incident/167167#000b1df03c8158d82c2b70b4c8baa7ccea09411821ba078f2226c9a63a0d3f1d ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Tue, 31 Jan 2023 02:09:56 -0000 https://status.ppro.dev/incident/167167#236966550953f69f4cfc40312af8091f03e54a8bbd30100da850b538cffd25b9 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Tue, 31 Jan 2023 02:03:30 -0000 https://status.ppro.dev/incident/167167#bffab0b4cf443b0a59117f3b5b4cd64a73c8476e49118e1e2384eda529cdd3a7 BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Tue, 31 Jan 2023 00:17:58 -0000 https://status.ppro.dev/incident/167167#6da24a640699f14baa3977f4d7fb30e113a04c83129ce4c8622a53716f4e677d BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Tue, 31 Jan 2023 00:16:15 -0000 https://status.ppro.dev/incident/167167#7f5a915d1be8231446dd4e35eb467db602185b79b8cc7273b925523a05a1cc9f BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Mon, 30 Jan 2023 22:19:58 -0000 https://status.ppro.dev/incident/167167#d2e6ae3982aa7d6a1ea6ec27e76c8b8481492fcb09c0c1fcbf224de92821f034 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Mon, 30 Jan 2023 22:18:27 -0000 https://status.ppro.dev/incident/167167#65658f4116f96dc9f30e2c2b4d031c52136876904664df80f6fa761fdf215afa BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Mon, 30 Jan 2023 19:07:47 -0000 https://status.ppro.dev/incident/167167#23d931301032d3f30fd413324a732d20440185bf1c0e7bacee3b376ae8013388 ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Mon, 30 Jan 2023 18:22:45 -0000 https://status.ppro.dev/incident/167167#44d18bc413170f27d29028fea2efe32cb4d5347685aa869d33e454a3146a6766 BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Mon, 30 Jan 2023 18:21:25 -0000 https://status.ppro.dev/incident/167167#f7c9f08f9366395bd6b837f0d503c34513dda055faa7458c79eb103996e7c020 BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Mon, 30 Jan 2023 13:24:28 -0000 https://status.ppro.dev/incident/167167#718c1afb1cf3e0dc1a2f9eed4d1245ae5bb2b7b87da139866440094476fa7836 ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Mon, 30 Jan 2023 13:17:37 -0000 https://status.ppro.dev/incident/167167#269346c44e5bc8486bbe1143ba4c5a6e4376290335294dfab436179539ac932e ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Mon, 30 Jan 2023 11:26:44 -0000 https://status.ppro.dev/incident/167167#9f55a8b7d702e7fd3a7152ed08e9f6987da8fcfa0e58b9d8067db4d922a3a9f1 ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Mon, 30 Jan 2023 11:21:43 -0000 https://status.ppro.dev/incident/167167#0125591bd4418639d79b7378d2497c69d8067621ef575d06463aa47c61af9831 ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Mon, 30 Jan 2023 10:29:39 -0000 https://status.ppro.dev/incident/167167#7821a1436af3b74fe1227816e95302167d7c70e1de5a3415b0188b921cfcf6e6 ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Mon, 30 Jan 2023 10:15:49 -0000 https://status.ppro.dev/incident/167167#f45ee3a526513b553cde3b639c9991b21bc5a49668097a1c68ca4dea49b6ec48 ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Mon, 30 Jan 2023 04:03:46 -0000 https://status.ppro.dev/incident/167167#e1c02ca1d15d6df42100facb3ace1a521b0ac6eb80e1ff54e406f7f3433e38a7 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Mon, 30 Jan 2023 04:03:04 -0000 https://status.ppro.dev/incident/167167#1731a6a63a97a1f16c2d68beff272eff96f5f86687f26d398763f1348fbde88a BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Mon, 30 Jan 2023 02:16:53 -0000 https://status.ppro.dev/incident/167167#4c902fc591496d9ebd3e7ab7c14706fe199d34f31c8a6d701aee9d0cb7102576 BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Mon, 30 Jan 2023 02:15:16 -0000 https://status.ppro.dev/incident/167167#a2c7681b7bdbce1cc9c669c7ccbe10b578f67a89ca55f56d1c5933baa3af9ca7 BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Sun, 29 Jan 2023 21:54:15 -0000 https://status.ppro.dev/incident/167167#4815d1d9e7a3bcc801110a29494080af3784e6f163fa5f6b4b4a59722a531f93 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Sun, 29 Jan 2023 21:52:25 -0000 https://status.ppro.dev/incident/167167#dc1caf831bd413926b564af59b1aece7a126a8a1816d6f9ccc36fefe054e72e2 BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Sun, 29 Jan 2023 18:15:34 -0000 https://status.ppro.dev/incident/167167#7f3beb391eff2aaf3197c2d5c24cc8e43d716d4d1ee5dd5c85ffa2f354278ae1 BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Sun, 29 Jan 2023 18:11:44 -0000 https://status.ppro.dev/incident/167167#25d26d709ed7a948beb3a637eb320619875ba18a5450e1c062b8a495b4223859 BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Sun, 29 Jan 2023 14:13:55 -0000 https://status.ppro.dev/incident/167167#8f195ce453933ca9a826dd6f3dd2237d77c51cdf5ab5cd5ef520872050533f83 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Sun, 29 Jan 2023 14:12:25 -0000 https://status.ppro.dev/incident/167167#34f026b75ecf9090ac1417508acff1ee9be176cc6674181593786cce79030766 BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Sun, 29 Jan 2023 13:11:35 -0000 https://status.ppro.dev/incident/167167#2c387fe0bd853a3af0a4698dc1ae6f9e3ff8b661e01242c24c5fd5dc801409e9 ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Sun, 29 Jan 2023 10:09:35 -0000 https://status.ppro.dev/incident/167167#911f99f64a04b423f2cf6487c2c1bc0490f3167f7a4dcab7ae1689d58ad43fbd ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Sun, 29 Jan 2023 04:17:41 -0000 https://status.ppro.dev/incident/167167#2bae6500926b0d275c8b7198f7ec806894dc6790eb56bf2872b68eac8c2c537e ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Sun, 29 Jan 2023 02:21:54 -0000 https://status.ppro.dev/incident/167167#030552832cce998801ce5eb18cdda20f9a1dc072a26b498b029577997e52d402 BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Sun, 29 Jan 2023 02:20:15 -0000 https://status.ppro.dev/incident/167167#ceddc4ee631d89327692707929cf125687fe8eada79718c7c9791fd62e9b2af2 BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Sun, 29 Jan 2023 01:09:47 -0000 https://status.ppro.dev/incident/167167#bb291101a2b0c9115e5629f5f64e0e6a4042f53770083e024281e5704c5e505d ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Sat, 28 Jan 2023 22:09:03 -0000 https://status.ppro.dev/incident/167167#63b9d940123741bd5efccd7d2dedacc8e779bc902e8de18fda30afdc43066347 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Sat, 28 Jan 2023 22:03:01 -0000 https://status.ppro.dev/incident/167167#7348cd4f894df7fe1398df6784b6ff2b20cd98ebd969159f4c5693c98e9ee5be BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Sat, 28 Jan 2023 20:14:46 -0000 https://status.ppro.dev/incident/167167#6846cbfb46c9c2997a907792003870dc49b3b8f0dca5a7c916739f20077f5019 ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Sat, 28 Jan 2023 18:25:24 -0000 https://status.ppro.dev/incident/167167#431c4ba9ff661e618ae453726e4b3ffcb64667bcc0b5cffce02736e5099585b1 BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Sat, 28 Jan 2023 18:21:46 -0000 https://status.ppro.dev/incident/167167#290cb659bb20c4e89dd38beb815cae1b9891341363bb5acdb7b98d4d71c8f458 BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Sat, 28 Jan 2023 16:12:33 -0000 https://status.ppro.dev/incident/167167#8fe8d889f5e327c7f03d4baf0d16ef8b4796c5630e0fd5f4db5d78eb35808fb6 ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Sat, 28 Jan 2023 14:00:04 -0000 https://status.ppro.dev/incident/167167#6c33c5f11f1bcd2497b56bccf976dfcd0ae4aa16d6a77592c8d2a957da48d4f2 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Sat, 28 Jan 2023 13:52:33 -0000 https://status.ppro.dev/incident/167167#5cc559c80393fe832d6847ec2f8087eac91cc5f07ad0c80394fc275abf5d6bb7 BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Sat, 28 Jan 2023 10:20:25 -0000 https://status.ppro.dev/incident/167167#b9fa9d69424a13e6d482fd7eb448cca1062903a1e8b99396c6d136b1c7734d8f BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Sat, 28 Jan 2023 10:16:45 -0000 https://status.ppro.dev/incident/167167#3ad335eb71694469c29b8163b5c06e085c1ee5ce8ac7c987c73cc1284c46f491 BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Sat, 28 Jan 2023 05:52:32 -0000 https://status.ppro.dev/incident/167167#1618caedeb9e6eb24c82b69f23584d2b5ef5a3cc85fed4bf0006455571232253 BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Sat, 28 Jan 2023 05:48:45 -0000 https://status.ppro.dev/incident/167167#c35e179e9bcb9254a1b11c5b2967e0a7cf9bb9a377359e9374d1c58cd036d8fb BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Sat, 28 Jan 2023 02:41:42 -0000 https://status.ppro.dev/incident/167167#3eec011dbd3639a0227a4c3e900d9554cf463984889ef87fc72cf5af2a4e3b90 BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Sat, 28 Jan 2023 02:40:24 -0000 https://status.ppro.dev/incident/167167#6b33fe337a3dec4f5b88420a6263751279830c13be8809466ae5c62be1a773e3 BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Sat, 28 Jan 2023 01:41:36 -0000 https://status.ppro.dev/incident/167167#38dba1c50d795cadd762e2cf60b76c8c79fdd87423613d1a1dee70154af7d0dd ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Fri, 27 Jan 2023 22:12:30 -0000 https://status.ppro.dev/incident/167167#f285cf8b7c967bd68b986a70edf5c13d059f6bbb0c3149be3b49f4e725da6e7a BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Fri, 27 Jan 2023 22:08:50 -0000 https://status.ppro.dev/incident/167167#123195b3276c399dee4a635d20c40f4b050c996ca4d292fb6e220774383899e8 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Fri, 27 Jan 2023 22:06:44 -0000 https://status.ppro.dev/incident/167167#b8caa18ab7af03e5f27cd518bcce82976e08ff9828341ff21beaa9e6300d64c7 ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Fri, 27 Jan 2023 18:35:25 -0000 https://status.ppro.dev/incident/167167#909f25c96a3eac160799b3eb01ebb1af9c738f2ac295d95f72979da4a86437ed BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Fri, 27 Jan 2023 18:31:53 -0000 https://status.ppro.dev/incident/167167#22fbb9316484264b65dcd1219bc37bbdeae84c903b06d5184c580db199a34ca4 BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Fri, 27 Jan 2023 16:23:48 -0000 https://status.ppro.dev/incident/167167#163af847e9e97a74f0a6d8fcd4e30a61afd3d6de264751b767b4274c347c9a18 ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Fri, 27 Jan 2023 15:42:34 -0000 https://status.ppro.dev/incident/167167#25a36beb06b90f910dcf04dcb4b7e8016b472542f469561b58b5500d7478ee8b ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Fri, 27 Jan 2023 13:47:36 -0000 https://status.ppro.dev/incident/167167#8aa55f103745cfa7266536ac9e17fed64ea86a7e8460dff21cc2cc664ab89eef ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Fri, 27 Jan 2023 13:12:33 -0000 https://status.ppro.dev/incident/167167#740adabec935fff814c0a7725bef7699f999c3abaa3c214ebce92bed5d101ebe ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Fri, 27 Jan 2023 08:19:27 -0000 https://status.ppro.dev/incident/167167#7a83a563569b992ac6ee1ead6fcf487bf2727de385068775c51ebfe30dadd5f1 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/167167 Fri, 27 Jan 2023 08:11:25 -0000 https://status.ppro.dev/incident/167167#3410a2c197745408dbdcf61b00c11a192883918d653b7635def6158c7a59f63a smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/167167 Fri, 27 Jan 2023 08:09:28 -0000 https://status.ppro.dev/incident/167167#2542287cca48593a7283c0486ae80947702abb0207d7c347c8355d132d6d659d smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/167167 Fri, 27 Jan 2023 06:57:23 -0000 https://status.ppro.dev/incident/167167#c574955f3eddb4b94878823a325caefc3615eec4d5e10a37cf789bd35d44a83e smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/167167 Fri, 27 Jan 2023 05:48:48 -0000 https://status.ppro.dev/incident/167167#e0739469e307a38cf505be353c0ad4f7c3a058d613f9ce3e7da34be974928821 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Fri, 27 Jan 2023 05:47:22 -0000 https://status.ppro.dev/incident/167167#baf6f33a649eeed71fb6d52010160f277797d08a73fcf506166bbd6e8534dc1a BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Fri, 27 Jan 2023 02:20:13 -0000 https://status.ppro.dev/incident/167167#48eae44f9cb1f40ecd02281743088f5b7afc37468ba1f0bd60c06fac822552e0 BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Fri, 27 Jan 2023 02:16:44 -0000 https://status.ppro.dev/incident/167167#d2e162424194b3358e1d4a3457aa50960b54524eac2cf05fce7048c57d0b2052 BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Thu, 26 Jan 2023 22:13:53 -0000 https://status.ppro.dev/incident/167167#0667d817f8b083e839f9c3f3c51e0e7f5edd745828b053280cee8b533de3c9ea BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Thu, 26 Jan 2023 22:12:37 -0000 https://status.ppro.dev/incident/167167#dddd2c602e6d39b61dc295a2a859340a2c8fb4b9a45bf7f50771b81a053e023b BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Thu, 26 Jan 2023 20:19:51 -0000 https://status.ppro.dev/incident/167167#641f393ff1877cd8c7fc76159d7d6848e22aad35595272551219a7cb77ed4d6d BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Thu, 26 Jan 2023 20:16:30 -0000 https://status.ppro.dev/incident/167167#377e9aa3a0b8d71263f33f00d6078d3c47dae93c5dfb96fd1b76e85f0e8640c9 BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Thu, 26 Jan 2023 13:43:49 -0000 https://status.ppro.dev/incident/167167#fb4cdb7a4713f3af801ea9b7d3f97ed3384d31d7c24ed4362386c91820c330dd ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Thu, 26 Jan 2023 13:32:40 -0000 https://status.ppro.dev/incident/167167#2b046295b2cc2c6408a16f27f49cfd32187ffaaa7025d2278610b770e6d01fa2 ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Thu, 26 Jan 2023 11:28:09 -0000 https://status.ppro.dev/incident/167167#93d1fa7ce089b6dc9d839561620dc7a683870eba1f870f2cc0b8e578b98f86ce ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Thu, 26 Jan 2023 11:10:45 -0000 https://status.ppro.dev/incident/167167#77900f8ee5ea74610ae053c45e29e1c24a90f1dda91bc866c6f3e13b66f0ac9c ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Thu, 26 Jan 2023 06:51:35 -0000 https://status.ppro.dev/incident/167167#a680eb0a4f4786e3f7c9dc1948e95c04a4222512c547e51d5dd8e674ea5c2bea BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Thu, 26 Jan 2023 06:50:07 -0000 https://status.ppro.dev/incident/167167#296723a3eb28f504ce027929371049eb225082af4718efe9ea2ea7073cbf6171 BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Thu, 26 Jan 2023 05:12:33 -0000 https://status.ppro.dev/incident/167167#c9cd865bd333c463e1f2efb97d3a026a8525e36ce8b6e4cc0c7e1881747bc586 BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Thu, 26 Jan 2023 04:49:06 -0000 https://status.ppro.dev/incident/167167#d5a1216fb913db92658e6e2710251a82c99430f3a45e3c2ba77f0d75e9c43e39 BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Thu, 26 Jan 2023 03:06:40 -0000 https://status.ppro.dev/incident/167167#c2a5c43fbbd42a548b30f78b51cc1aefe6213b4b6323753c190886a42c5f8aca ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Thu, 26 Jan 2023 01:10:31 -0000 https://status.ppro.dev/incident/167167#847274c0eb7d43d0b5d30924af01e6afef223e02b8e7c2826189a7481000054e ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Wed, 25 Jan 2023 23:07:11 -0000 https://status.ppro.dev/incident/167167#6201ce75d664a5a121ee6156623241be42154ead5e1ab196e801b38511b4b19e BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Wed, 25 Jan 2023 23:06:18 -0000 https://status.ppro.dev/incident/167167#0bc928788c9c8b5c83edba13fbbc6df3edc794efe0a22294710cf837167682d1 BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Wed, 25 Jan 2023 22:38:05 -0000 https://status.ppro.dev/incident/167167#157d1ef75f6f04ccbe1235c86fe0edc5cf692cf7baa285aad7338390773bb049 BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Wed, 25 Jan 2023 22:34:44 -0000 https://status.ppro.dev/incident/167167#cc5086c9ff2042a09f8ae9b6b37ba647be7cf026cbb497e1506e949e21b06dbc BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Wed, 25 Jan 2023 19:18:46 -0000 https://status.ppro.dev/incident/167167#3fed982c60ebf63ed5fce127fcbe458aa8c82c928072541949abad1eb8a3f4ad ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Wed, 25 Jan 2023 18:02:06 -0000 https://status.ppro.dev/incident/167167#2a21a0046d317c074bd61f01a86d05a5bcee5d739499a2a29978d9659d1550a0 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Wed, 25 Jan 2023 18:00:38 -0000 https://status.ppro.dev/incident/167167#a9acd314571c14605b065be9b25a7adb9c5d1dcda13467ab809a8412c0121265 BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Wed, 25 Jan 2023 16:40:35 -0000 https://status.ppro.dev/incident/167167#c0e70a5bf4c267392ff9772c1fecb818fe70d7a78e7b0e95b0556d1cb61bd29c ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Wed, 25 Jan 2023 16:17:34 -0000 https://status.ppro.dev/incident/167167#772a10b27fc74ba27bac611adfb99f3a70da2c724875852dde6fcc5887e59ac2 BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Wed, 25 Jan 2023 15:59:57 -0000 https://status.ppro.dev/incident/167167#0abb2097ecf531bd9a3959165048352b42cfc46e631adc3c101849d1cae084f7 BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Wed, 25 Jan 2023 10:51:04 -0000 https://status.ppro.dev/incident/167167#2ab125de657d35d3581df6a4d2dbdce19af7ac9421138b31b99edde69c4bf581 ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Wed, 25 Jan 2023 10:39:58 -0000 https://status.ppro.dev/incident/167167#404f87f2194dc82a05c4ae21e6bec5996ec6695c7d96920f069916a430c8dd0d ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Wed, 25 Jan 2023 09:57:16 -0000 https://status.ppro.dev/incident/167167#2a3d5e7624f92ddc90197b0420d27b4e84178b80d5875ec03bd0019d0f744f4c ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Wed, 25 Jan 2023 09:46:20 -0000 https://status.ppro.dev/incident/167167#fbe8347f490cf7abf744140fcb234f17a6fd6560f0842ee62967f4e851e95092 ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Wed, 25 Jan 2023 09:33:08 -0000 https://status.ppro.dev/incident/167167#38240a8421464303f65f51b9afaf5f02e3d96520ecb864335f9f2629d458b579 ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Wed, 25 Jan 2023 09:12:57 -0000 https://status.ppro.dev/incident/167167#b3377027fd44e1b53918f3627eb9d09647270add4086991b5755a8cf75e8d875 ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Wed, 25 Jan 2023 06:49:43 -0000 https://status.ppro.dev/incident/167167#2c0fe0dc601d38efdcfdc0640dcae708fa94f3024b7744b1f83ef4b54f6afdbd BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Wed, 25 Jan 2023 06:46:12 -0000 https://status.ppro.dev/incident/167167#cc7122c39cf5ecd2ffa82909e80573eb32979633b0abc36ca6cc33d975bb94db BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Wed, 25 Jan 2023 06:19:07 -0000 https://status.ppro.dev/incident/167167#1ed1b9508a3bd8aa6054dc0b90f8c0e4ee8da3f544757a5cd57c177bb50b2beb BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Wed, 25 Jan 2023 06:17:39 -0000 https://status.ppro.dev/incident/167167#e04e9542f09c51b5f2b3b2074a43f87e04c6daee6a5ad89090a8e417c1d6d282 BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Wed, 25 Jan 2023 01:12:07 -0000 https://status.ppro.dev/incident/167167#4c15683f908281a1af5ac66b9abf10cacba0a9f3b019bad7d8a409cd7e8f7818 ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Wed, 25 Jan 2023 00:26:08 -0000 https://status.ppro.dev/incident/167167#b4d9853a602a3b61494ab62c1278a57e696ecfacb6393ad5567996d5269ae021 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Wed, 25 Jan 2023 00:14:53 -0000 https://status.ppro.dev/incident/167167#f320954626c4b54f64df25728215e2eb1500c439ba652b03df731a37d139eedd BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Tue, 24 Jan 2023 22:53:32 -0000 https://status.ppro.dev/incident/167167#6670683f1a4c0eec9da3d4c7e863f5e81500af2c17c8107f2402452a7546f1c3 BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Tue, 24 Jan 2023 22:22:34 -0000 https://status.ppro.dev/incident/167167#29fbcfb699785604b5caee1210b6347f545fd00be5bd302e8f7d075df637393a BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Tue, 24 Jan 2023 22:22:03 -0000 https://status.ppro.dev/incident/167167#31df8a104d523f76c7c003c2d5e751590d57b4a70d61190a85146baaff6f44b4 ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Tue, 24 Jan 2023 20:21:07 -0000 https://status.ppro.dev/incident/167167#3843204ad167e49e86c1a52ffe29386483901d55a7c8502f0106a73f4d20622b BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Tue, 24 Jan 2023 20:19:52 -0000 https://status.ppro.dev/incident/167167#f561520937b814309db983d07ae0acfb901d2a4d9c397da21bbf27e139cd2556 BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Tue, 24 Jan 2023 19:02:04 -0000 https://status.ppro.dev/incident/167167#404da95fc96b36262c164b307b4cad1ad75288133da9c9fdac5a205f4d8db896 fj: jpyther docker service went down. https://status.ppro.dev/incident/167167 Tue, 24 Jan 2023 17:04:04 -0000 https://status.ppro.dev/incident/167167#66a6c9e4bd5ce03fdd4113fb7fbbb8e3caa82109d6cce4fe59abc56b0b7d4dcb BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Tue, 24 Jan 2023 17:02:34 -0000 https://status.ppro.dev/incident/167167#33e89d7690853faf4779f52af3cf34015e880535928b36fce29b42c20f46b035 BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Tue, 24 Jan 2023 16:53:56 -0000 https://status.ppro.dev/incident/167167#97ad021637ff98bff331d4c259b6fd47faca76777d531f38c0096d98a510ba70 ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Tue, 24 Jan 2023 16:43:03 -0000 https://status.ppro.dev/incident/167167#2a8176cc002df27911a5f96d6a15b8141fd34c00d6e7222f02f57271a2932d87 ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Tue, 24 Jan 2023 16:30:10 -0000 https://status.ppro.dev/incident/167167#20f5c7f157e5e42a053abed838eaf4b1a27c4da7a0b56dd7d0bff4601279523f ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Tue, 24 Jan 2023 16:24:52 -0000 https://status.ppro.dev/incident/167167#52f83db39ce382bcf0eaf6cbdc50c41c757153008e26bcfde9e9050cdfa63405 ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Tue, 24 Jan 2023 13:16:38 -0000 https://status.ppro.dev/incident/167167#681607fae49c2fbfd7c85bfd2cb812ec14ae1aef2875330fcc29e8bb67635d4a ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Tue, 24 Jan 2023 13:05:38 -0000 https://status.ppro.dev/incident/167167#d3847b4bee35f1eea21dccf4417be41a5e5b5ad6ce146e662ce6b3c18bd68697 ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Tue, 24 Jan 2023 09:03:22 -0000 https://status.ppro.dev/incident/167167#ceb651f4ba55b92c406b1a0e11ba5a7a848bec044a6dc2c7c2d8447295ce111a BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Tue, 24 Jan 2023 08:59:50 -0000 https://status.ppro.dev/incident/167167#1fb726cf3263f7e267861a09717fa2d57a31780a162bfa7711cbf8e9703e3242 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Tue, 24 Jan 2023 08:10:48 -0000 https://status.ppro.dev/incident/167167#d4d0076d6ac1a04716406c86963fe744e434712a094037bfa8ed6079a73e4bd5 BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Tue, 24 Jan 2023 08:07:31 -0000 https://status.ppro.dev/incident/167167#0aa53704354499a959f9063d03b7c980632392327a87127695b574136270615d BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Tue, 24 Jan 2023 07:25:24 -0000 https://status.ppro.dev/incident/167167#d3be5406116d1988b7e2e62b91ff8f44e1f399dac59177d38350574e876cbe60 ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Tue, 24 Jan 2023 06:44:24 -0000 https://status.ppro.dev/incident/167167#024b21177266e57d7bc8ff3be15751f168e534d82542abfb65bb3c488a378b92 ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Tue, 24 Jan 2023 04:09:17 -0000 https://status.ppro.dev/incident/167167#701417090f9a88d723eaa1c26c93884207b7c1469046da79d6d63f893ddcc6eb BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Tue, 24 Jan 2023 04:08:13 -0000 https://status.ppro.dev/incident/167167#25129ee7a008b3c6ddc010ae9b21f663d6c898b41e846f74b7882245eb978403 BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Tue, 24 Jan 2023 02:47:14 -0000 https://status.ppro.dev/incident/167167#7af6d91713c3c87f5debe322adb82e6f938509661ad421cfc4ee6f6a6cb181c8 BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Tue, 24 Jan 2023 02:45:43 -0000 https://status.ppro.dev/incident/167167#668302ad4419c35aed4f7e64a82a975b2347215bfb79404aa4962e35daa7135f BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Tue, 24 Jan 2023 01:54:27 -0000 https://status.ppro.dev/incident/167167#e0d1212eb9b40978a96ea61802a4e9453388beb8868126bfc2866a16c79ae433 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Tue, 24 Jan 2023 01:52:47 -0000 https://status.ppro.dev/incident/167167#90feb773ec8db7e30ba1c4e3a30b71c5581b4210587b48a03eed653cb50838d2 BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Mon, 23 Jan 2023 23:57:17 -0000 https://status.ppro.dev/incident/167167#b9bce26bb7c215ed35732bae211e4ca0e122058bacd96baac94f42870f2b9d1a BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Mon, 23 Jan 2023 23:55:47 -0000 https://status.ppro.dev/incident/167167#d1aa226926de5631bad80e8acdfeedc84a6320a2343142ce8c9727c014a52743 BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Mon, 23 Jan 2023 22:04:19 -0000 https://status.ppro.dev/incident/167167#7e5b334965b86970bff07c83193671e3ad201896cfd8e2c54f8d3437fafdd09b BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Mon, 23 Jan 2023 22:03:15 -0000 https://status.ppro.dev/incident/167167#f3596a3ee33d8160dc1c5bda5dc4cb0619ac16e0953b01ee4261785eb0338e74 BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Mon, 23 Jan 2023 18:10:43 -0000 https://status.ppro.dev/incident/167167#689d137b03e27d1858b013859032a7acc738080b858a69d95f56a6c37eb8287c BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Mon, 23 Jan 2023 18:06:12 -0000 https://status.ppro.dev/incident/167167#a5a43c518e37c1459c34b38ac3dd571387186b8519beddbbd7c3ea9c4168d5fd BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Mon, 23 Jan 2023 13:27:37 -0000 https://status.ppro.dev/incident/167167#33a9947c0e44e30e7af078946f67bf48296dc191e2ef17f4614c9124bcb9078b ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Mon, 23 Jan 2023 13:16:38 -0000 https://status.ppro.dev/incident/167167#a9ee0be3f706206f0ffceae7a252c5953078ee0beb6199112ac6e121f977071e ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Mon, 23 Jan 2023 12:48:51 -0000 https://status.ppro.dev/incident/167167#642ba5b40a3225c2a5134ff7478a09dd850277fc6aa02a6033e9b6b5b1be62d3 ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Mon, 23 Jan 2023 12:43:34 -0000 https://status.ppro.dev/incident/167167#65a65ad0d9b7d2ae441b8bab42710e79d5eb44f47f4a9f23a218dbda75f3a48a ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Mon, 23 Jan 2023 10:38:48 -0000 https://status.ppro.dev/incident/167167#66771bfd7f232c17d21e3e64056502146f27ab57ac594ae2173963a7dcc14066 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Mon, 23 Jan 2023 10:37:22 -0000 https://status.ppro.dev/incident/167167#f8754531f9518efe300881147aee52220a179dc01356d36cfd9e1c6c797cca8e BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Mon, 23 Jan 2023 10:30:29 -0000 https://status.ppro.dev/incident/167167#897f907f0c0eac79c84d36c8bf738027ff59e99e2f053ed020206a9d48b3854f ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Mon, 23 Jan 2023 10:16:36 -0000 https://status.ppro.dev/incident/167167#9cc497796523bc4c051d18d40e35b720d74f64213f1287c58573fe396959a67a ppro: ovm myst server went down. https://status.ppro.dev/incident/167167 Mon, 23 Jan 2023 09:51:34 -0000 https://status.ppro.dev/incident/167167#52b5b431b53a3b4a1398fd8eda1373ee8768bb682f657b992abe5b9c54f3bc1a BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Mon, 23 Jan 2023 09:50:15 -0000 https://status.ppro.dev/incident/167167#7792071bcdaf1c0ef05c3cd670ab4c2683767a538b2d8b904e6fa5284b5c59db BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Mon, 23 Jan 2023 04:45:22 -0000 https://status.ppro.dev/incident/167167#44c6e85f68bb71839f3ded48f98cf820f5c4b89373b9bdaf7020be8ca67eabfd ppro: ovm myst server recovered. https://status.ppro.dev/incident/167167 Mon, 23 Jan 2023 04:18:36 -0000 https://status.ppro.dev/incident/167167#244cd219316e668e50eb19de7ab0eb1036522c4b3db02f0c23362f903a75b4f1 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/167167 Mon, 23 Jan 2023 04:12:27 -0000 https://status.ppro.dev/incident/167167#635dd375711ddfe7986b36d1706eadbbc6599163e13bc4a320a81540e78edf75 BrovaPh ups status recovered. https://status.ppro.dev/incident/167167 Mon, 23 Jan 2023 02:11:29 -0000 https://status.ppro.dev/incident/167167#01dbc45e34e6e227f7181cffd64a384aa121f5953cfb2232232ae1b6388f0605 BrovaPh2 ups status went down. https://status.ppro.dev/incident/167167 Mon, 23 Jan 2023 02:09:59 -0000 https://status.ppro.dev/incident/167167#bf276472b9856d93fe55eac386bf506072eb0fce382404fe1a7c0b282f71808d BrovaPh ups status went down. https://status.ppro.dev/incident/167167 Mon, 23 Jan 2023 01:19:19 -0000 https://status.ppro.dev/incident/167167#9a9ed1b3e4f934a38f128e64cbf51c15c759a21e10effd0ebcd42471e6986d4e ppro: ovm myst server went down. https://status.ppro.dev/incident/166910 Sun, 22 Jan 2023 21:58:22 -0000 https://status.ppro.dev/incident/166910#cdf9f46d5c9a7b47a732583851095ea6ff154e95a0f11c63f1c902b0907c6184 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/166910 Sun, 22 Jan 2023 21:57:04 -0000 https://status.ppro.dev/incident/166910#219943a6852706f135a768816175ff2e9123d3eb1edb1cb6e01934af306f0ca8 BrovaPh ups status recovered. https://status.ppro.dev/incident/166910 Sun, 22 Jan 2023 18:16:17 -0000 https://status.ppro.dev/incident/166910#9c11f5dc034f67225e7e5eb8795b28bbc725a28cc2a49fe892eb834a5667901e BrovaPh2 ups status went down. https://status.ppro.dev/incident/166910 Sun, 22 Jan 2023 18:15:09 -0000 https://status.ppro.dev/incident/166910#24f104231500ba7332431e1cce37be9fcbdd8c72f933d3063af6d5c522e738a9 BrovaPh ups status went down. https://status.ppro.dev/incident/166910 Sun, 22 Jan 2023 13:15:25 -0000 https://status.ppro.dev/incident/166910#84bc8484de9fb025fc08273dc4c14627d36658bebd45cab3aa66cb13483d8347 ppro: ovm myst server recovered. https://status.ppro.dev/incident/166910 Sun, 22 Jan 2023 12:13:23 -0000 https://status.ppro.dev/incident/166910#93a356e61285f0eef5439aa86b69502213c683287f555752b6f726f30d064ea0 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/166910 Sun, 22 Jan 2023 12:07:12 -0000 https://status.ppro.dev/incident/166910#f8b4979461b5c2ec2c97cba77913b628d3ccadf846942851af28fe6e3a32ae52 BrovaPh ups status recovered. https://status.ppro.dev/incident/166910 Sun, 22 Jan 2023 10:19:20 -0000 https://status.ppro.dev/incident/166910#d4a167a010311da22e4e0e56589d667a0b14413d2ae126d08b0fddc0aca1f8e1 ppro: ovm myst server went down. https://status.ppro.dev/incident/166910 Sun, 22 Jan 2023 09:56:28 -0000 https://status.ppro.dev/incident/166910#42cc2be57413837711d724a2531f2f1a81944e81e6975312039b31ce2049ce61 BrovaPh2 ups status went down. https://status.ppro.dev/incident/166910 Sun, 22 Jan 2023 09:55:22 -0000 https://status.ppro.dev/incident/166910#1c5c5abf3f7bc6927b2ac796e9791b5e772233685efd69e2b105ffd9bbf9ea84 BrovaPh ups status went down. https://status.ppro.dev/incident/166910 Sun, 22 Jan 2023 04:41:14 -0000 https://status.ppro.dev/incident/166910#30f815b3e665114e09b90da0c2482c993fbe1e70c04241494884d2254cd4eddd ppro: ovm myst server recovered. https://status.ppro.dev/incident/166910 Sun, 22 Jan 2023 01:09:03 -0000 https://status.ppro.dev/incident/166910#972fef530e11e153ab87ab2415915842eaf83ff4feb0cc49b1fca87d7c641191 ppro: ovm myst server went down. https://status.ppro.dev/incident/166274 Sat, 21 Jan 2023 21:22:20 -0000 https://status.ppro.dev/incident/166274#68cd99c81b8b1bfaee2272b07637a91f3f202882b7238009d236507332f52346 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/166274 Sat, 21 Jan 2023 21:21:05 -0000 https://status.ppro.dev/incident/166274#7fe4f5024fc7640fbccae21524917a9a19acbc4258d52e5fbeffa71f9b00e0bb BrovaPh ups status recovered. https://status.ppro.dev/incident/166274 Sat, 21 Jan 2023 21:01:22 -0000 https://status.ppro.dev/incident/166274#b08ebfae7f84d0eea025ffde9a0ead981e3636e5e59769be07c10c0544f98886 fj: jpyther docker service recovered. https://status.ppro.dev/incident/166274 Sat, 21 Jan 2023 20:50:19 -0000 https://status.ppro.dev/incident/166274#a5ac4cbecc4b6cbc97c147170753bd9837d0680b8f4d942ba35c80038037cbcc fj: jpyther docker service went down. https://status.ppro.dev/incident/166274 Sat, 21 Jan 2023 18:14:12 -0000 https://status.ppro.dev/incident/166274#c8cf361fa90b40883380ce1597f8ec664709547c5a489135a0730f2f5947721f ppro: ovm myst server recovered. https://status.ppro.dev/incident/166274 Sat, 21 Jan 2023 16:11:29 -0000 https://status.ppro.dev/incident/166274#6b0a7fa2b760bf9114d40d5a1317a6e29889ad63ec12dd641ba21f286db5f8e0 ppro: ovm myst server went down. https://status.ppro.dev/incident/166274 Sat, 21 Jan 2023 06:25:14 -0000 https://status.ppro.dev/incident/166274#7d334a0e9a268be8436aa590a1a898e8793d839e45dca2f90e3a1286ec69522a BrovaPh2 ups status went down. https://status.ppro.dev/incident/166274 Sat, 21 Jan 2023 06:24:02 -0000 https://status.ppro.dev/incident/166274#f5ed454de30c665cf915c4f8965f702bcac82f6a91ee67b89903569708cfd674 BrovaPh ups status went down. https://status.ppro.dev/incident/166274 Sat, 21 Jan 2023 01:14:21 -0000 https://status.ppro.dev/incident/166274#ef1ec843578aac472a6f41cd5a6b47776bc4e331f513b494ea6f688f4c37105f ppro: ovm myst server recovered. https://status.ppro.dev/incident/166274 Fri, 20 Jan 2023 22:05:46 -0000 https://status.ppro.dev/incident/166274#ee4b71129087603535767abf962d44f18c00d1a9b911f9376aec80ae1fbe41a8 ppro: ovm myst server went down. https://status.ppro.dev/incident/166274 Fri, 20 Jan 2023 21:52:13 -0000 https://status.ppro.dev/incident/166274#22e61912ee6b691cf12375335ccfdab8d77e9a971138417a8f3ec73a7e41d27b BrovaPh2 ups status recovered. https://status.ppro.dev/incident/166274 Fri, 20 Jan 2023 21:45:31 -0000 https://status.ppro.dev/incident/166274#e05e449a70edb9309cc3ea40c88e559493ab765864cc35200644ecfc3c45853c BrovaPh ups status recovered. https://status.ppro.dev/incident/166274 Fri, 20 Jan 2023 18:04:52 -0000 https://status.ppro.dev/incident/166274#2bb4dd99645f545be96de6af42f2c2d1d806dacadcce99bc2f0f923d60455b5e BrovaPh2 ups status went down. https://status.ppro.dev/incident/166274 Fri, 20 Jan 2023 18:03:23 -0000 https://status.ppro.dev/incident/166274#8359630ab6307b8bb00e0997566c3747b955b34f2acf9dd9dbb1f525e7abe651 BrovaPh ups status went down. https://status.ppro.dev/incident/166274 Fri, 20 Jan 2023 16:22:56 -0000 https://status.ppro.dev/incident/166274#3b7e4f11e9f08b53ced95a5726c6a66451424889d42674986a0eeb4b914d76bb ppro: ovm myst server recovered. https://status.ppro.dev/incident/166274 Fri, 20 Jan 2023 16:11:53 -0000 https://status.ppro.dev/incident/166274#1a3fb9fe65df48d52f3086de0e5473bfd9ca07af8663cc8c7591e5a7190f1b69 ppro: ovm myst server went down. https://status.ppro.dev/incident/166274 Fri, 20 Jan 2023 13:28:57 -0000 https://status.ppro.dev/incident/166274#516c8fe50bc0264e9ad43b1f3217fdb97545ead3c40686028d8133b02d4a6c45 ppro: ovm myst server recovered. https://status.ppro.dev/incident/166274 Fri, 20 Jan 2023 13:08:58 -0000 https://status.ppro.dev/incident/166274#10fb3273ca0c8c84499009d7bfb75456658241bc3f1a6598412511c51d7778be ppro: ovm myst server went down. https://status.ppro.dev/incident/166274 Fri, 20 Jan 2023 12:22:35 -0000 https://status.ppro.dev/incident/166274#011e83a7c473429f2c824a8955081971c0346885924f31474fdb1e29b9ab4cb0 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/166274 Fri, 20 Jan 2023 12:14:40 -0000 https://status.ppro.dev/incident/166274#d260b2d31e302da6049626857decf65bfacadd37247a2741e63c3a30da8e9616 BrovaPh2 ups status went down. https://status.ppro.dev/incident/166274 Fri, 20 Jan 2023 10:19:39 -0000 https://status.ppro.dev/incident/166274#89557fec593f65568a35d19be01900ffcdb061cbbf75d4ad8f0208b6fdb7f404 BrovaPh ups status recovered. https://status.ppro.dev/incident/166274 Fri, 20 Jan 2023 10:16:34 -0000 https://status.ppro.dev/incident/166274#be31a4329fdebb3739205de56f7e5f145df246e68819810db793e5415e4cf3d9 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/166274 Fri, 20 Jan 2023 10:12:31 -0000 https://status.ppro.dev/incident/166274#e19bff7b27063f25db73b4dd5059a15072d570a98b459a9c70ed9074f8ce436a BrovaPh ups status went down. https://status.ppro.dev/incident/166274 Fri, 20 Jan 2023 10:09:06 -0000 https://status.ppro.dev/incident/166274#6f2c259221a8579c5dc05868b5b7013907043bc361c8b98ec625f82bfc5edbe3 BrovaPh2 ups status went down. https://status.ppro.dev/incident/166274 Fri, 20 Jan 2023 02:46:12 -0000 https://status.ppro.dev/incident/166274#8fe21734befff030fc6d092b6d1fc98f53e1df777dc8e8d39e1e0d98f3138350 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/166274 Fri, 20 Jan 2023 02:44:37 -0000 https://status.ppro.dev/incident/166274#a5f2ff45bf3bf4fd9b263ab16f4a8a72a182df55c9b1ffa3eb893a8e0894b47c BrovaPh ups status recovered. https://status.ppro.dev/incident/166274 Fri, 20 Jan 2023 02:27:30 -0000 https://status.ppro.dev/incident/166274#11cb6c58701c28407f9737dfa609e21389a1b84bdaf2e54f46f5906e5b63073c BrovaPh ups status went down. https://status.ppro.dev/incident/166274 Fri, 20 Jan 2023 02:24:04 -0000 https://status.ppro.dev/incident/166274#f599b43c810e8c689f438f27b4704bdf4f09972bf518c86606b9ae07f6a0563b BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Thu, 19 Jan 2023 22:34:36 -0000 https://status.ppro.dev/incident/138462#5d9aaf21d7f8014c41c7f3f90d458c2d7de1fc3ffdfcdf6b3e593e26514545b9 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Thu, 19 Jan 2023 22:31:08 -0000 https://status.ppro.dev/incident/138462#9f325c85980a8c7c0b9ffbf06ed209e22c3e1090d03064bd89ef3d450a92d769 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Thu, 19 Jan 2023 22:13:03 -0000 https://status.ppro.dev/incident/138462#39e52ee0154e1a0f2a1434af8bb206d932c4cee1548b1d3e2df33f08b190aea7 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Thu, 19 Jan 2023 21:02:03 -0000 https://status.ppro.dev/incident/138462#682037eaffde70588624eef55de55629641af125115487ca1417a6c9902ec1b4 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Thu, 19 Jan 2023 20:36:59 -0000 https://status.ppro.dev/incident/138462#0fb138820ea4b0e06b1ee7065dca3f98f96835016453fb47057b45a883bfcdc5 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Thu, 19 Jan 2023 20:29:03 -0000 https://status.ppro.dev/incident/138462#598d81dd17c19ce82411c5a068f70d66754b4016070cb2bf66023ebc0a3661d5 BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Thu, 19 Jan 2023 13:36:41 -0000 https://status.ppro.dev/incident/138462#f5873bf742ac376a1967f4999d7469af1db748a66a5b0794416d69a6a87fb50a ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Thu, 19 Jan 2023 13:25:27 -0000 https://status.ppro.dev/incident/138462#a6c8fd2d5f69dba29ef60e40af0e6d1a4ccb5b64153f26b8773ae2002c5290fb ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Thu, 19 Jan 2023 12:44:09 -0000 https://status.ppro.dev/incident/138462#b94c45c97605cf32a03ce5f7c053929a4e4e06c0ee3f2d1e6e789c41137b35d3 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Thu, 19 Jan 2023 12:40:40 -0000 https://status.ppro.dev/incident/138462#cdcc92943aa867d64a4cfef4c682d77fc0ecc1761ad54294bc010a7eed2a7575 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Thu, 19 Jan 2023 12:27:05 -0000 https://status.ppro.dev/incident/138462#f07c83bd3e27f8b94822224a73574643344fbf2e0540689e2dea75ed9e615f5d BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Thu, 19 Jan 2023 12:23:38 -0000 https://status.ppro.dev/incident/138462#13b635493dcf0aa9a6751667b45488690ef492d23bf81e1054a07b69feececa8 BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Thu, 19 Jan 2023 10:30:06 -0000 https://status.ppro.dev/incident/138462#47b08a8aaa4b305f7e87f20597b5c8715094763c78b5c2c8dcd1a9bf28ae4697 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Thu, 19 Jan 2023 10:12:52 -0000 https://status.ppro.dev/incident/138462#5870f5f8cd6013f88312a893b53e57b130c5df92810a22e5921db524c426efde ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Thu, 19 Jan 2023 08:38:38 -0000 https://status.ppro.dev/incident/138462#710d6993471547fbd5adfb83452d59e4b604b7197937fef317206f7cc47e22c4 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Thu, 19 Jan 2023 08:21:34 -0000 https://status.ppro.dev/incident/138462#e7edebf4b3aca25eeeecf38667f9e0935f92474fc84d6b0443e38348229d37d0 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Thu, 19 Jan 2023 07:55:27 -0000 https://status.ppro.dev/incident/138462#9b0544547c19c5fab42004b778414838b8444ae51f0cd49f08c51ed6e94f0633 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Thu, 19 Jan 2023 07:48:10 -0000 https://status.ppro.dev/incident/138462#be564f17dc83c5d6535efcc48c9aa17320033ade432787da611f3c753726c476 BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Thu, 19 Jan 2023 07:45:42 -0000 https://status.ppro.dev/incident/138462#df87d42b16c218087018aadebe05c5bc7f30edcc76ee7e7b5294c4623fbe7ebb BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Thu, 19 Jan 2023 07:38:22 -0000 https://status.ppro.dev/incident/138462#f66d03e60fff46df47fe5480f5d72b2314f2de8c1c5aa71864d903d6d275c09b BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Thu, 19 Jan 2023 07:00:21 -0000 https://status.ppro.dev/incident/138462#d0570b73c8ba725f7d1569d5b835cfab231c59c3b4b5a4ed70aa38fa2fa0df6e BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Thu, 19 Jan 2023 06:59:43 -0000 https://status.ppro.dev/incident/138462#e2ea01bb3b3a558803a88af5f9aea79113fc13b64d4fce252555ecf7ef09a91d BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Thu, 19 Jan 2023 04:50:51 -0000 https://status.ppro.dev/incident/138462#c488a1a99281549ed53963085392f3a1e0919a4a73167d177c6d1b813648003f ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Thu, 19 Jan 2023 01:03:46 -0000 https://status.ppro.dev/incident/138462#ef0b8184c8cdaee0839f036302fdfeb798eb1f36e70900949b55f32fb9010e7a ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Wed, 18 Jan 2023 20:06:24 -0000 https://status.ppro.dev/incident/138462#005084636035157afa6f2c9a90766f0163fe6e2cc44d820cc07304c4036c66b3 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Wed, 18 Jan 2023 20:02:52 -0000 https://status.ppro.dev/incident/138462#f03d932384d0651d20eb65f0f1238d186a477a63ee52b5589a2e492418b3374b BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Wed, 18 Jan 2023 20:00:00 -0000 https://status.ppro.dev/incident/138462#883e93f1fc72c518e43458b2f9b6264c3e8b97d609f21ee36f8400a7834536bd BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Wed, 18 Jan 2023 19:59:21 -0000 https://status.ppro.dev/incident/138462#f0cde7630f504528d01f4ac4ca2348168883ff1bbceccff10d8e9f089d95623b BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Wed, 18 Jan 2023 19:53:13 -0000 https://status.ppro.dev/incident/138462#cd2fd74e6acb7376d0b6a2df00c5653528413f14f0c688f944a447560307b329 BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Wed, 18 Jan 2023 19:51:27 -0000 https://status.ppro.dev/incident/138462#ed6bd4d4989088def8af487c8755d1d37ccc55bab943d83c29f53461f1a3b026 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Wed, 18 Jan 2023 19:00:39 -0000 https://status.ppro.dev/incident/138462#88f5a66c46b900cb147f4bb1177d82efd604dcac91785d690b83e459905773f0 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Wed, 18 Jan 2023 18:59:29 -0000 https://status.ppro.dev/incident/138462#64a3a913db5265d5fe0a11f9262102dda703f85d354937b3f7ce7af52ccee089 fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Wed, 18 Jan 2023 18:48:39 -0000 https://status.ppro.dev/incident/138462#4e12a07f86597384ab5b25e368ce80b67da1f3adb0337dcdd476f6398310012e smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Wed, 18 Jan 2023 18:48:17 -0000 https://status.ppro.dev/incident/138462#313e20da57e5f380e77821411184e627e2c4e65056eb7d785adbac358d178eeb fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Wed, 18 Jan 2023 17:40:19 -0000 https://status.ppro.dev/incident/138462#f1caf133e605ad14eb7f62e11cd6237564d6aabd1baa13556f322063b1451eab smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Wed, 18 Jan 2023 17:13:37 -0000 https://status.ppro.dev/incident/138462#6f135e990d71849b40e4c0809ea7b4a4ba07490d437210f050baef501395e290 fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Wed, 18 Jan 2023 17:08:24 -0000 https://status.ppro.dev/incident/138462#535b61e0f3d9e715aa09370f43d30e887611ed75af5eb300263649455e934fed smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Wed, 18 Jan 2023 17:05:24 -0000 https://status.ppro.dev/incident/138462#430d1f28c470ebb3dd0c9c30863ecc27226bbf70da320a91e00f92b7fe691a3f fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Wed, 18 Jan 2023 12:37:23 -0000 https://status.ppro.dev/incident/138462#c013c57d9397e2efa9b0abc20e4dbfd456c8ed29ea96bcd8c2a5571ecaa4cf5a BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Wed, 18 Jan 2023 12:30:35 -0000 https://status.ppro.dev/incident/138462#167f11a18e2b4c5d0cfac9271c4e74e40272a966ba2754ceef547d410bf4d088 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Wed, 18 Jan 2023 12:07:31 -0000 https://status.ppro.dev/incident/138462#9ff9180a4ad817244b37cda1f0117ecf73c8c375a0a8dcbb859b27265c61cced BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Wed, 18 Jan 2023 11:45:26 -0000 https://status.ppro.dev/incident/138462#a67b86327cf94333c03ac1cf38688c90dacc80c1380efe164a1a23b96451dff8 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Wed, 18 Jan 2023 11:37:24 -0000 https://status.ppro.dev/incident/138462#5b90d93386b4ec855158f446c4f9cd23d15fd395cdeb12d6e37c7d1284585a5d BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Wed, 18 Jan 2023 11:30:32 -0000 https://status.ppro.dev/incident/138462#faf55afddaa95e9d06dc97be417948874f1dc7eb449370972505549767bde549 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Wed, 18 Jan 2023 11:22:40 -0000 https://status.ppro.dev/incident/138462#bacdea73ec3ef365a5ab36bf5650a94352096b0060dc7e2241fa82b123c3d805 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Wed, 18 Jan 2023 11:13:36 -0000 https://status.ppro.dev/incident/138462#8d5a78009e5a8b206107de9f48f72d5f154893df21e7f6f2e1902359fd7d4d13 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Wed, 18 Jan 2023 10:45:14 -0000 https://status.ppro.dev/incident/138462#4f3bf57a9a228b0794e545384392bd0dbf6e40c2a6593aaf5a9b337037a1f4d3 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Wed, 18 Jan 2023 10:43:28 -0000 https://status.ppro.dev/incident/138462#071c62c6d86109b76ff29200458bed30b8d6b90b841e5085a5b7eeb947d10021 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Wed, 18 Jan 2023 10:32:22 -0000 https://status.ppro.dev/incident/138462#886a44acae9828e9f5d90ea65a733669fd9109b4fbc5e922a4240209c409b9f0 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Wed, 18 Jan 2023 08:57:14 -0000 https://status.ppro.dev/incident/138462#3bcaa4e9939b9e1ada9fed9f78586d34208e80c59ed0855e3cb54e967889fc24 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Wed, 18 Jan 2023 08:28:33 -0000 https://status.ppro.dev/incident/138462#9e11b1ce4752bd7a04c6389f9d1c28787b3065291244b0a989635566d2d61dc4 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Wed, 18 Jan 2023 08:10:14 -0000 https://status.ppro.dev/incident/138462#c6ad779dbe489f26058b220948c14c0c8231c9de975c6db5de336467b43b236b BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Wed, 18 Jan 2023 08:02:22 -0000 https://status.ppro.dev/incident/138462#074fd47234956fa12aecc707ed452fa700c9ecabf95a7e94e417344766171ceb ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Wed, 18 Jan 2023 06:52:13 -0000 https://status.ppro.dev/incident/138462#7421dd7dbe1780511f6f5d58bfa0481de503c81873c6829eb13ad4b554e73b68 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Wed, 18 Jan 2023 01:22:27 -0000 https://status.ppro.dev/incident/138462#03af0447d745a7bb0f1ce6e5288e83ca6d0c751d624f6b543f82950086022461 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Tue, 17 Jan 2023 22:08:21 -0000 https://status.ppro.dev/incident/138462#9d5054597580a4ce8e320c27bb34ede04e2f88d0165e21557fc6a580ba2ded8c ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Tue, 17 Jan 2023 20:25:05 -0000 https://status.ppro.dev/incident/138462#de85c35a9d65cbe4b0c4c748286f3382ae5012f5fb35ffc17ab5d42659cc9399 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Tue, 17 Jan 2023 17:19:17 -0000 https://status.ppro.dev/incident/138462#547517ea493fcda5274929e87c2fc0c3a085fada564677e954b8c5816f66cf03 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Tue, 17 Jan 2023 17:12:09 -0000 https://status.ppro.dev/incident/138462#840c6918adcbf0b0a04506fd5a44b8f22b92f7a3024edd54983ba3a0dcea664a BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Tue, 17 Jan 2023 17:08:15 -0000 https://status.ppro.dev/incident/138462#7e0a6fa68ee18f4b3782228d7e0c7784e30907e786155f91799c5b90e8222fde ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Tue, 17 Jan 2023 16:35:06 -0000 https://status.ppro.dev/incident/138462#3afbc545bad2ef5df96948ef3d0f66f0cd988828dc00e2ac635cddff99920135 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Tue, 17 Jan 2023 15:52:12 -0000 https://status.ppro.dev/incident/138462#b171785885e5853d5a08d593ed35f8f310fc007665fe682c459c014625b2e5d4 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Tue, 17 Jan 2023 15:44:11 -0000 https://status.ppro.dev/incident/138462#00edcb0edfd2c9f40aee6345081359b69dc8cda1d7ea9907ff6c33110b99a576 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Tue, 17 Jan 2023 13:31:11 -0000 https://status.ppro.dev/incident/138462#20e62295d8824169b767758deefd360c98b02601ac102fa2212e0edbad1c26a5 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Tue, 17 Jan 2023 13:01:59 -0000 https://status.ppro.dev/incident/138462#a5763849395050e415938db46fb6a4618282ecb5656a27edd456f8489ab320e3 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Tue, 17 Jan 2023 04:35:11 -0000 https://status.ppro.dev/incident/138462#ad281c88b5779563681422c4dfb206f43e3cc1a4eb6352d52aa64ab12e16d57e BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Tue, 17 Jan 2023 00:17:46 -0000 https://status.ppro.dev/incident/138462#71d94204d215846444b62927c24c16bb153b6c269b1f1fd57ba37e54a3f28a2a BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Mon, 16 Jan 2023 22:14:52 -0000 https://status.ppro.dev/incident/138462#cbf95f2508927892ad49aafe355c07dc9b0bf3f0aac92dfb35baacca5bc5fccf BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Mon, 16 Jan 2023 18:32:50 -0000 https://status.ppro.dev/incident/138462#ee4a28bef2bab1fea32fb17aaa3ffd985cffcfba6a6d32e819e3df0992ee605a BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Mon, 16 Jan 2023 14:24:53 -0000 https://status.ppro.dev/incident/138462#1729d01d97e49b30d5296619921f64dff778a2e6d3da0ca3cd0ffc1e7469bee0 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Mon, 16 Jan 2023 14:17:47 -0000 https://status.ppro.dev/incident/138462#dc38ab03cd2bcf9eebf6813b583e7d177f36d5c9708050a9a2ddab4e0ac16e08 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Mon, 16 Jan 2023 13:59:21 -0000 https://status.ppro.dev/incident/138462#4b16f8ab4e6e0bd3216eefe77036d91578a9df907bc87f0352c3fe24ff44d589 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Mon, 16 Jan 2023 13:48:07 -0000 https://status.ppro.dev/incident/138462#59e564401af1ff1471b40a3f0b9ffb779b78d2a1ed0a9150f45728afa3fc8dc8 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Mon, 16 Jan 2023 10:21:38 -0000 https://status.ppro.dev/incident/138462#b058290aeffeeb1a7d6117319e39b85391166070a8c539e533b9e818eb28ea94 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Mon, 16 Jan 2023 10:04:25 -0000 https://status.ppro.dev/incident/138462#d97ec2cf99fd51779020a1a804f0bf9070da21b9e6d4afe53dfda90e83aa8e92 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Mon, 16 Jan 2023 09:17:52 -0000 https://status.ppro.dev/incident/138462#16a1861a5a6c8717f3fd57da30b5347dee1b4a8e2b1e7c52b1a5aff8377f2cf7 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Mon, 16 Jan 2023 09:10:48 -0000 https://status.ppro.dev/incident/138462#9e48a454b4905361d2dcd8db92a5a919d50d627c6e91a7b195291d9211ecc766 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Mon, 16 Jan 2023 07:42:50 -0000 https://status.ppro.dev/incident/138462#b14e329378b3b3d1a16d9eacf3f35dff0430dc37522ab259fe3b480c01e5d54d BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Mon, 16 Jan 2023 07:30:48 -0000 https://status.ppro.dev/incident/138462#f8b7cd9801dfabdae57bda7d8ee7fc0bf93aa1a0b0a5461d374207a87d6a9580 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Mon, 16 Jan 2023 06:57:50 -0000 https://status.ppro.dev/incident/138462#4f3e95a420d43c99ffa1ce5ef76eb8f94310d5b5500dcf4e83b22cc32f45b782 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Mon, 16 Jan 2023 05:06:38 -0000 https://status.ppro.dev/incident/138462#d1ec686719140770d27749cbf18f175bbd886493c84b0db6344801fe656bf9f2 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Mon, 16 Jan 2023 01:22:28 -0000 https://status.ppro.dev/incident/138462#d750589282f0bb0e2fcd68d72f8c1615e6dffae8e9af063569aa28cde8ff3869 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Sun, 15 Jan 2023 13:30:23 -0000 https://status.ppro.dev/incident/138462#f1798308939f910e6fc62c6581c896f4aa307a2e82446fc198d2734ae037dcfe ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Sun, 15 Jan 2023 10:04:19 -0000 https://status.ppro.dev/incident/138462#3ae4d4bf99682b430f49e4a4a7517f74415d7d1d32c620c2f6f6de0f1c139e33 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Sun, 15 Jan 2023 00:20:48 -0000 https://status.ppro.dev/incident/138462#f62913b30e02e5682b92bdeb9259b5d2fabc25728f721dd9b01470d675afcd06 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Sat, 14 Jan 2023 21:57:53 -0000 https://status.ppro.dev/incident/138462#0efbb5dde1d5a15fd518a7ff249b1dce3d1184f05c20846f617deaa62acb34d2 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Sat, 14 Jan 2023 18:50:48 -0000 https://status.ppro.dev/incident/138462#7d51a313c091287dfd2d15b49fa172258620a7ee81fe1562fb859f9e0e4f414a BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Sat, 14 Jan 2023 17:27:53 -0000 https://status.ppro.dev/incident/138462#411cdfaef94e62158b282489707383da4f9b975e47fc35bfa68d432bc58ed7c9 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Sat, 14 Jan 2023 04:55:47 -0000 https://status.ppro.dev/incident/138462#6f2b9c795b7acf5cc06bdf8089f7fd40c2c0703cc9a43ec36f9ccc635cc41969 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Sat, 14 Jan 2023 04:07:53 -0000 https://status.ppro.dev/incident/138462#e97c06712879ef618b8a7e1546c3d0ed5d2b1f09145725dee81a14a58a01d647 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Sat, 14 Jan 2023 02:35:46 -0000 https://status.ppro.dev/incident/138462#f945f44af9955f41d9f1178032cb9be8c1b96e1255e179973f10a29f3c0a4f26 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Sat, 14 Jan 2023 01:27:25 -0000 https://status.ppro.dev/incident/138462#e0c7eaa7390ecbda29309befbeb3c560b39213bb8fcba987b1eeb15a7cfad218 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Fri, 13 Jan 2023 22:12:46 -0000 https://status.ppro.dev/incident/138462#a414a148dbaae8bb5e3d880103a5ae5bfd99fdc56bd36ec3b6d29455b8503163 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Fri, 13 Jan 2023 22:10:03 -0000 https://status.ppro.dev/incident/138462#f9e0302b8b51ce3145eadc50e4b4e33ed5f895a9054a7c8efdb54df168982760 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Fri, 13 Jan 2023 18:15:41 -0000 https://status.ppro.dev/incident/138462#c8cbeb59dff7dad9b46551f3bb74538223e4fb24a06d78e73ccb6d77013c15d4 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Fri, 13 Jan 2023 16:29:42 -0000 https://status.ppro.dev/incident/138462#28796591c7343abccd86887589397194381d2703d6d70c14276845465261ab9f ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Fri, 13 Jan 2023 16:18:43 -0000 https://status.ppro.dev/incident/138462#2151929dc558855f00b3c5d70cdbfc9544a795a4a393f81f01a36bfab3e88254 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Fri, 13 Jan 2023 10:49:43 -0000 https://status.ppro.dev/incident/138462#7b14d92c72247325018c0f172fea4163c8f1f131da2ee5defdabdca753f71fed ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Fri, 13 Jan 2023 10:35:59 -0000 https://status.ppro.dev/incident/138462#58f65de5b3ff5bab205c7a65de24c14473709c88711954650517ba6d7f9f7018 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Fri, 13 Jan 2023 07:25:29 -0000 https://status.ppro.dev/incident/138462#94ddbed864ae058209df127862e2c2c074b44ecb97c8ed3af1676a5cb6e48f01 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Fri, 13 Jan 2023 06:46:00 -0000 https://status.ppro.dev/incident/138462#5c17b638cf143ad4b6ab77f1f3d10ce314871d3934a9785a93743fba617df453 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Fri, 13 Jan 2023 06:34:14 -0000 https://status.ppro.dev/incident/138462#61a7c2b7940efe3a01c8b4a0372509a302e8419a1313ffd7b1f9c69f2d371d5f BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Fri, 13 Jan 2023 05:44:17 -0000 https://status.ppro.dev/incident/138462#c82e481c3e556d6d28fd19a07e95344a76b6466af5241ac13ee9d871a218c044 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Fri, 13 Jan 2023 04:21:00 -0000 https://status.ppro.dev/incident/138462#7e31bfb84c7e734aa02632321ff1c315d052724cdcb9c8d01406a4ff3c7a8093 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Fri, 13 Jan 2023 02:48:53 -0000 https://status.ppro.dev/incident/138462#a4e07933b078d29822af75a45840c012439b87f288aa779c163636f757fbddf4 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Fri, 13 Jan 2023 02:40:52 -0000 https://status.ppro.dev/incident/138462#653933bd2ae715f8c01d6f67e2fc549ca3c2bb22cd19aba02d35f2bfc43f450c fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Fri, 13 Jan 2023 02:35:01 -0000 https://status.ppro.dev/incident/138462#4e5d2a3a8722f6c5edd33798f71828085688497ea3a0e1f410d3d1b1db87a788 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Thu, 12 Jan 2023 22:25:13 -0000 https://status.ppro.dev/incident/138462#1597f6ae9752f921add69b1bc48bb061cd73da2d3fcd64b86387aca387318d9a BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Thu, 12 Jan 2023 20:48:11 -0000 https://status.ppro.dev/incident/138462#2499fd4e3be321efd3d8d8a946245e1480e55e38d3c25d7f89b1a8eddc062b4a BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Thu, 12 Jan 2023 20:00:23 -0000 https://status.ppro.dev/incident/138462#b6152e79ef6702e570588dec4a0e68fc6e2f31c0776e50dc84846bb030ff445a ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Thu, 12 Jan 2023 16:36:16 -0000 https://status.ppro.dev/incident/138462#bfa4443d1fe4730fdc2c9ef0676a3aa969a4f790e2e5a96ddd7573540e21987e ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Thu, 12 Jan 2023 13:29:34 -0000 https://status.ppro.dev/incident/138462#884b080478b0f80089cbfa4b4f60389d4d35fa1cd3615080571a416974bfe26d ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Thu, 12 Jan 2023 13:17:00 -0000 https://status.ppro.dev/incident/138462#0d9fc6284e8db6b9895c30d57c1c9c4ab93c36ef79a50f732f88bece51ceeafe ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Thu, 12 Jan 2023 12:51:03 -0000 https://status.ppro.dev/incident/138462#0fc17d28098e811052df18545b31c06956a38ba1d3cadacec5a9bf6cdcff7559 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Thu, 12 Jan 2023 12:36:56 -0000 https://status.ppro.dev/incident/138462#95cdf457622a56019155db2d5068667f53f9ae7f1dfeaf63102e070fada39e27 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Thu, 12 Jan 2023 10:30:05 -0000 https://status.ppro.dev/incident/138462#aca0551c46cbafb71ab3baf6895eaa97b9563a0e34774e2575393d8889d5232c ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Thu, 12 Jan 2023 10:06:51 -0000 https://status.ppro.dev/incident/138462#0b4aa28101110481c67b4f55bf98542afd33a5188e86d33376c1810d661871d9 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Thu, 12 Jan 2023 08:19:35 -0000 https://status.ppro.dev/incident/138462#fcf7a51788fa895cf0bc387f74563701fa75b1cbf56d67404a9e26467df8cb60 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Thu, 12 Jan 2023 08:12:46 -0000 https://status.ppro.dev/incident/138462#8ebbbdb6f1aec5b1ccc3922cc7831a3a288b7c1213d3de422064ee24e69cf767 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Thu, 12 Jan 2023 06:49:45 -0000 https://status.ppro.dev/incident/138462#c6812c0ce7c0df1a39ded0d956caf3d0138e1951d6160ff1a6388de1f1047a9a BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Thu, 12 Jan 2023 04:47:03 -0000 https://status.ppro.dev/incident/138462#5d0747b83ea882c5da122c9e3fd491be310d271ec445c3adfd3df19ef815066f BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Thu, 12 Jan 2023 03:59:26 -0000 https://status.ppro.dev/incident/138462#018fc15bd54580680e1c6b44e131445156c804aa2542991b9d4486e5ece1add9 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Thu, 12 Jan 2023 01:57:48 -0000 https://status.ppro.dev/incident/138462#abeecb84008592ef1cc08d50d968864bb1fe1dfe96426c0e37b1d316b5625e21 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Thu, 12 Jan 2023 00:04:17 -0000 https://status.ppro.dev/incident/138462#0655d737f998575a13ef313b2ce722b32f0a01f182afb35049d88779aa279ea8 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Wed, 11 Jan 2023 22:47:04 -0000 https://status.ppro.dev/incident/138462#67933cdda7148142fa7af720ed232a513bc9252d9672a6c95ea9b8de94bab4a1 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Wed, 11 Jan 2023 22:04:20 -0000 https://status.ppro.dev/incident/138462#1d6023587c0e3605b4e85f8fff44047aef040859753499d9879f95bb7a63d315 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Wed, 11 Jan 2023 20:07:18 -0000 https://status.ppro.dev/incident/138462#9583082a3ca1f7bee2514757e3fae80cf76a5549e3afb9f88414abeb5119e018 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Wed, 11 Jan 2023 19:54:00 -0000 https://status.ppro.dev/incident/138462#7d0362e6a7f8b1a3ee644c3e7d59ec90f65541d43997a39bb0bb27e132be3adc BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Wed, 11 Jan 2023 19:14:18 -0000 https://status.ppro.dev/incident/138462#6736027cb9ca0f64ca4f2bf710d0321898b75ea660aa101a87cb0d393f087c68 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Wed, 11 Jan 2023 15:49:53 -0000 https://status.ppro.dev/incident/138462#f05b2737756c2d65dac60bbf798397133a7703ad21524134c53435956a61a9ed ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Wed, 11 Jan 2023 15:16:20 -0000 https://status.ppro.dev/incident/138462#ef102597b66b621f5014a061c95dd242df8489423e3ed11beacb8c928514fbf9 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Wed, 11 Jan 2023 14:58:06 -0000 https://status.ppro.dev/incident/138462#2d253087023ad8113e08a32334ffdac7bd32571997802917ef87c7c0cd6fbaef ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Wed, 11 Jan 2023 14:53:09 -0000 https://status.ppro.dev/incident/138462#3e1c259c50e340d33dbbc7c04d2e8efc13c403add44252ac31b556dca721fd40 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Wed, 11 Jan 2023 13:37:08 -0000 https://status.ppro.dev/incident/138462#0653cc02c1f847f01db6ebb4ebb9b36fe321189aaca3d8916dd373ee2ab84dc7 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Wed, 11 Jan 2023 13:20:03 -0000 https://status.ppro.dev/incident/138462#6910ba7ca8ee604dbe514a4396201f3d21acd0f092fc7a34f7a5752402e3a737 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Wed, 11 Jan 2023 11:16:04 -0000 https://status.ppro.dev/incident/138462#b528c150a06c42374e5ccdd277c5ae0194e1226ca96542488531807985dc359f ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Wed, 11 Jan 2023 11:05:03 -0000 https://status.ppro.dev/incident/138462#8c5db987082e7f7d2ddb570b8cd19d48709192a6fd806eaa64544c7a575cf2dc ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Wed, 11 Jan 2023 10:34:15 -0000 https://status.ppro.dev/incident/138462#8b6c4b3e2c91bfe9012f4c222b563b5e2cd3cd119d0efc0e734e9065d68f77ca ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Wed, 11 Jan 2023 10:26:04 -0000 https://status.ppro.dev/incident/138462#fb55e2bc55833b18f2da77b984529f3528b3d8eccd3cfb3cc7fab45c54d15fe3 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Wed, 11 Jan 2023 10:09:53 -0000 https://status.ppro.dev/incident/138462#0d1ed8d7ff8e6d5e628c5534b188e6ecc86f56a4c8152eeb694afd8c360053b4 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Wed, 11 Jan 2023 09:27:23 -0000 https://status.ppro.dev/incident/138462#ba04921f5871b8e6ff2d6377d2209b59aff67ccbb9c7f8f552d68e0beaa3a8ca smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Wed, 11 Jan 2023 08:21:32 -0000 https://status.ppro.dev/incident/138462#1efab4b717067ab45c4b5832de26030f977f4fa2f7a30989b79a13a8e3c79da5 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Wed, 11 Jan 2023 07:57:14 -0000 https://status.ppro.dev/incident/138462#b196bf0170c73d6761c2d69664fdf1c08320b9bd2efc6e697f738005c234ec02 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Wed, 11 Jan 2023 07:50:20 -0000 https://status.ppro.dev/incident/138462#58feb5fc641d76602da8fd3591dbccb98f28da36f158e8a18ecda1a9c3196554 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Wed, 11 Jan 2023 06:39:39 -0000 https://status.ppro.dev/incident/138462#c5b15dd8b3cbed817d26e0d9f47fd1c678588bfd110c5174b16723e9364fb912 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Tue, 10 Jan 2023 21:22:23 -0000 https://status.ppro.dev/incident/138462#72dc12b51659c065905a9fc12b96cb4e58f455eb8b9a8fa2dc22079130f4babb BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Tue, 10 Jan 2023 17:42:33 -0000 https://status.ppro.dev/incident/138462#6bed1ffe02a18410bd67e2321dcbdad0ad6cf27770566b2802a6b26ca8a622f6 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Tue, 10 Jan 2023 16:40:11 -0000 https://status.ppro.dev/incident/138462#7c628e203f4ff01dc05c98a50a535d21a241b9f8bc2e9930506f08f58c6c65c1 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Tue, 10 Jan 2023 16:13:29 -0000 https://status.ppro.dev/incident/138462#7be12bc72c3858eaecf1d76b882b601850b8d2b2167647b48a3c582e3b32616f ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Tue, 10 Jan 2023 10:44:24 -0000 https://status.ppro.dev/incident/138462#c8edbe944a718088efcff8b2739afe0fdcc001dd2539ce3d0b9c22a8cfcb787a ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Tue, 10 Jan 2023 10:38:17 -0000 https://status.ppro.dev/incident/138462#e8cf90e67ecb96aae19ffeb8efcacb9a9c0f6b1ca7bb06158736fb2475a0bc32 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Tue, 10 Jan 2023 07:04:51 -0000 https://status.ppro.dev/incident/138462#3be0d0c5549d6747cc557b856de3e20f0a0f03086eb9a1b717f1c33d57e80d18 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Mon, 09 Jan 2023 20:43:11 -0000 https://status.ppro.dev/incident/138462#c7a0d3bb43befaeb64a7eff352c36fe465db1b8b6004ae73ba81b4b8339b3db7 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Mon, 09 Jan 2023 18:12:38 -0000 https://status.ppro.dev/incident/138462#8c29da6e8899ef8f24dec6e5f470081e0ed1b3884cb05e2bdf89e0b8c1cd6296 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Mon, 09 Jan 2023 16:55:29 -0000 https://status.ppro.dev/incident/138462#890d4d7746b9801b92e1791c8f629e96c479fcf9ae7eb98d6fcb3c51410f0068 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Mon, 09 Jan 2023 16:18:40 -0000 https://status.ppro.dev/incident/138462#c7504b2fdc9594c4635ee888e444f9baf2ca53eb419c4eed1bfcab66baba5573 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Mon, 09 Jan 2023 15:59:17 -0000 https://status.ppro.dev/incident/138462#6d84395cb0ba0da7fd62ff7a2e02a9e6166f1668b42bc4e09dd1de733a46ff93 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Mon, 09 Jan 2023 14:54:15 -0000 https://status.ppro.dev/incident/138462#d10c1c69714bc011d43a20d7d2bb863d5bd6df4145d8eeede1276886c0a48282 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Mon, 09 Jan 2023 14:42:22 -0000 https://status.ppro.dev/incident/138462#3e1e1a170ba2fb054b307930391574f573455ee6d04ea29fc451dfcec01f5488 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Mon, 09 Jan 2023 13:54:35 -0000 https://status.ppro.dev/incident/138462#30ec34b91634ad13ef6e0cb4367a1b255fa85c3b5a4ad7c8d8be40d3e068ee36 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Mon, 09 Jan 2023 13:43:32 -0000 https://status.ppro.dev/incident/138462#1a90907276f46dda657802ca1e39a749bbd31265aa14ca8ed9cf0ebfe4e9f6bc ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Mon, 09 Jan 2023 10:12:17 -0000 https://status.ppro.dev/incident/138462#c9418c88358a8e12038dcff3120a525d450158bf2d13794b4ced57d401d0b60f ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Mon, 09 Jan 2023 10:07:21 -0000 https://status.ppro.dev/incident/138462#a8d1c25612a263e75a3bec8a590d5f3b687b38af5fade3de0d2c97113b6b5dc0 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Mon, 09 Jan 2023 08:30:10 -0000 https://status.ppro.dev/incident/138462#aa12d21de220cf958b0ebb4736f8f9aba901e255f36258309d38250f19edc32d ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Mon, 09 Jan 2023 08:16:16 -0000 https://status.ppro.dev/incident/138462#dfb5eb56c4695e28016f43983ba144c6b8bab787b11780c4d5f5a8f60c0f3ff6 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Mon, 09 Jan 2023 06:44:13 -0000 https://status.ppro.dev/incident/138462#d87118ad225d12a82c28a1944583bdf4b58be3e137ea9f42ac2cf72c89987552 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Sun, 08 Jan 2023 20:03:10 -0000 https://status.ppro.dev/incident/138462#d185f5814646afce1c8cdc4cabe94669ef41834505b392eefd013bdf2786e69d ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Sun, 08 Jan 2023 20:02:29 -0000 https://status.ppro.dev/incident/138462#54bc170829463103532982b95bef30d2818457375359ab7a7bf43c03354fdc8f fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Sun, 08 Jan 2023 20:01:22 -0000 https://status.ppro.dev/incident/138462#c169b5b85d176ad1298c61521b01061cd1caa09f3a5b95fb32f10d12818718df smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Sun, 08 Jan 2023 19:54:00 -0000 https://status.ppro.dev/incident/138462#067ff60ebf7f8e14069bb3972397159d8c15791efef46438cc38ea1efcc58f43 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Sun, 08 Jan 2023 19:52:09 -0000 https://status.ppro.dev/incident/138462#028b93600aa9a4bad82416838430b4969f008bd5ea33ee924f25953355c177d8 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Sun, 08 Jan 2023 19:51:09 -0000 https://status.ppro.dev/incident/138462#22aa2fcdc36d638852aaad7596a5efb0a859315e77abb2f7f23dae0ab0a56e2b fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Sun, 08 Jan 2023 18:46:49 -0000 https://status.ppro.dev/incident/138462#afc2a3332ce1bf498585ebc183b572a7f052c610dd70f8ab180d8cd9c68fd4ac BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Sun, 08 Jan 2023 12:18:49 -0000 https://status.ppro.dev/incident/138462#ae51c671f3d5175f820b1cdf8f949ed151491b7a970f6b6ede485e35ecd12f0b BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Sun, 08 Jan 2023 11:11:51 -0000 https://status.ppro.dev/incident/138462#9624eff9ad0be23b446e5aa7c9cbc238c4243032715ecd5d7c79c620fb1b13ea BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Sat, 07 Jan 2023 22:35:31 -0000 https://status.ppro.dev/incident/138462#253855f5f0e55e35811ed72fff4ca827c731354cba397a9aa99286ae7f426b29 fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Sat, 07 Jan 2023 22:30:21 -0000 https://status.ppro.dev/incident/138462#97f6b5276a6873cb99f1563288a4d907e1c1cde541d89f5962cbc6084d5376d8 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Sat, 07 Jan 2023 20:28:54 -0000 https://status.ppro.dev/incident/138462#174f62fa459fd8443e9f0a323b78a3b43bd0fb00d3b0cbcee71964b1aa25f5ab BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Sat, 07 Jan 2023 18:56:49 -0000 https://status.ppro.dev/incident/138462#e6c470e621d78ef289b53d8b596b71ada5189e3044dad27a15889095bdbb5412 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Sat, 07 Jan 2023 12:03:53 -0000 https://status.ppro.dev/incident/138462#3177b3926ede0e16ce088fffd20bf7c6ef56bd7258a385e4b55fe6b7f5bd315d BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Sat, 07 Jan 2023 11:01:50 -0000 https://status.ppro.dev/incident/138462#a05b1b7593ac13588e8d3b8ad9032ee559671cbfc388d676c12ce5656078a464 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Sat, 07 Jan 2023 02:23:50 -0000 https://status.ppro.dev/incident/138462#17e1a9ae5a7d168346070f9e1ada32938c4cb8c3a9b3beaaebc945ba91b534fc BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Sat, 07 Jan 2023 02:01:55 -0000 https://status.ppro.dev/incident/138462#e853e982f7270442c47db8c7476a4e0cc172f46045a4b1fe62143ec1170f7d53 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Fri, 06 Jan 2023 21:18:53 -0000 https://status.ppro.dev/incident/138462#ac95f99fde02f171dc711d159e10162d88d3de2a510eaa24ca85e3e8339a12ab BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Fri, 06 Jan 2023 19:06:46 -0000 https://status.ppro.dev/incident/138462#9c954bcf5b63f128bc9147513e9e3fa7e0d73c278519584472a3b6409d0695b5 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Fri, 06 Jan 2023 07:12:03 -0000 https://status.ppro.dev/incident/138462#cec44790181d512e77cf7a43ab8f9990bad3b286eb3063b47278a9500c6a69b8 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Thu, 05 Jan 2023 21:39:12 -0000 https://status.ppro.dev/incident/138462#78e0238635f731b98d7ca416d64a6671807f7867817b6c8ab7afd2eef8ba22f4 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Thu, 05 Jan 2023 21:08:38 -0000 https://status.ppro.dev/incident/138462#78b7f2f280692c0177311fe92c1c8fd841f14a05e9c84294e0e0632cfd1b45f3 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Thu, 05 Jan 2023 20:46:27 -0000 https://status.ppro.dev/incident/138462#2e681655cdda23b7cedd4a78b67078a23fb2173384ee151f37b1be7f645bfe18 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Wed, 04 Jan 2023 06:56:42 -0000 https://status.ppro.dev/incident/138462#6c1585eeae466d70195c6f820d9c251b3dcefe6e2ca7d2360be9df634cffd79d BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Tue, 03 Jan 2023 23:23:37 -0000 https://status.ppro.dev/incident/138462#959dc5a1cf5585b8af0e47c96be4fea870791ae0b459aabb4600cd159f550fed BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Mon, 02 Jan 2023 13:36:36 -0000 https://status.ppro.dev/incident/138462#0130abdef90e184ae9572d725c3fecd3e60f335ea5bef7a3710fea528177be8d ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Mon, 02 Jan 2023 11:34:35 -0000 https://status.ppro.dev/incident/138462#822dfd62dbbc4e214a64a2ee9037a7a3a37df5dec851352935c1f996c54723df ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Mon, 02 Jan 2023 10:39:37 -0000 https://status.ppro.dev/incident/138462#d4201701475ecbead7971d78cbcbbe4081e4ed68d14bd2abc612d4ceee78bc41 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Mon, 02 Jan 2023 10:16:32 -0000 https://status.ppro.dev/incident/138462#d64f438b47230c7c72b15d509fff5f4bc4147ce1412079e6ba64f8df705e36a0 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Fri, 30 Dec 2022 20:09:02 -0000 https://status.ppro.dev/incident/138462#35817449ad96ee1794fabcb09933ec6dcbed57d4edb69771e2b582c4519c8d3c BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Fri, 30 Dec 2022 19:01:59 -0000 https://status.ppro.dev/incident/138462#d6ddab78a06195963bcb76106b7f2d12a64f31a065ef1f5e7c602d24c4b5c040 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Fri, 30 Dec 2022 15:41:09 -0000 https://status.ppro.dev/incident/138462#91ea20d8f752d9b2a31a0682cece625c5176b496c0ebb487f9b5a5607fe7729a ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Fri, 30 Dec 2022 15:24:08 -0000 https://status.ppro.dev/incident/138462#b71c4eeede5f26bb2678d31c6861c2397c3e85bcff7f0c60d726e9fb525e5726 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Fri, 30 Dec 2022 14:56:04 -0000 https://status.ppro.dev/incident/138462#e05733b77cc6ff23da849c83f9e38a557c813f39671784e57cc05f8a547324d0 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Fri, 30 Dec 2022 14:38:58 -0000 https://status.ppro.dev/incident/138462#adb0e735479eaf29c81e77d3751d52113c27283df552b4dc671fdc89039c1b55 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Fri, 30 Dec 2022 13:35:09 -0000 https://status.ppro.dev/incident/138462#699606baaf49e119bb200e1afdf38c3f894386d247545af17a4582457e6bd689 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Fri, 30 Dec 2022 13:15:10 -0000 https://status.ppro.dev/incident/138462#f4a9a257f8da9124ff423d4ba9941fd153e03b14e2ddbffa0b08f418f21111e0 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Thu, 29 Dec 2022 08:13:47 -0000 https://status.ppro.dev/incident/138462#ecf5e9acaf50cd27d90fcac0587452ff677d593cfdf2f473f6c9fdf49e161fac BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Thu, 29 Dec 2022 07:31:41 -0000 https://status.ppro.dev/incident/138462#9441fcb419897047835da58fd74e4515ab1c2d7b5ff51fe490ac2ea7e29898b4 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Thu, 29 Dec 2022 07:31:00 -0000 https://status.ppro.dev/incident/138462#34e545fa863aaf14a12d8290288b2160bb1d0caed91e249e2c0c06195909b16d smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Thu, 29 Dec 2022 06:53:50 -0000 https://status.ppro.dev/incident/138462#d7c1c8ce86ccade12302ebf101d23cc5a176f66b8252d6283653ecc33934a08b BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Thu, 29 Dec 2022 06:32:46 -0000 https://status.ppro.dev/incident/138462#bbca723c63c9fa3e892f2793fa2479a306ff3619b055dae97323fc2668fc0c24 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Wed, 28 Dec 2022 19:59:11 -0000 https://status.ppro.dev/incident/138462#78ce33eb4cc75c2d55536371dadb302d407899f6d9062243fbb61146cdb5f844 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Wed, 28 Dec 2022 16:18:00 -0000 https://status.ppro.dev/incident/138462#701b404605777166e57ed9898d3b10bdb6aeec3c7acdc0ebdb5cdcafb99380d4 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Wed, 28 Dec 2022 10:37:59 -0000 https://status.ppro.dev/incident/138462#0dbe2f55fed206abef510952b490d2133f09d6c2c2e4b5fcac99d39efdd80f2a ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Wed, 28 Dec 2022 10:20:56 -0000 https://status.ppro.dev/incident/138462#d909c2b6bf4006d4c93efc3f97bdfd3ac96f89b7d0f8ccba995061f254cf71e1 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Wed, 28 Dec 2022 09:02:36 -0000 https://status.ppro.dev/incident/138462#9f9018c20e1067e0d284e8948d872363c174f3cab4fc312e2ae80ceb7fa35ade ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Wed, 28 Dec 2022 08:41:52 -0000 https://status.ppro.dev/incident/138462#0997b3ee989131a7098f914391fa682a894ff9a657e614ed0ef5c3832e973991 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Tue, 27 Dec 2022 16:43:55 -0000 https://status.ppro.dev/incident/138462#8f47ab3e0af98eaaf9d2a8d10903fc33d50636f32d7d6894097c720f1107fc8b ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Tue, 27 Dec 2022 15:53:53 -0000 https://status.ppro.dev/incident/138462#3260d38eeb47063d0dd136e77ad3476bbaa882fe0fd61511c546e175c360d080 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Tue, 27 Dec 2022 14:05:00 -0000 https://status.ppro.dev/incident/138462#2c9748069843c6f6edcdd71e7578ffd263a221d4e4138babb8ef07ecc5a18a04 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Tue, 27 Dec 2022 13:41:53 -0000 https://status.ppro.dev/incident/138462#35693ce98555ece1e9317da60edd2e29239649c48558638ebf40b12f3a4ee6ba ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Tue, 27 Dec 2022 11:02:06 -0000 https://status.ppro.dev/incident/138462#e299c9fe8b9806d89fda64b4f63c787db28d5e11b17a8f8de7d85e69ee09f6f2 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Tue, 27 Dec 2022 10:56:55 -0000 https://status.ppro.dev/incident/138462#ab93513e9794ae036029bdebe47093abb246be45fb511fad21700c3c6e6238dc ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Mon, 26 Dec 2022 23:18:43 -0000 https://status.ppro.dev/incident/138462#6927d116fad94c8c36127ef520378908fa85c3a22a90b5b05467c98a41df102f smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Mon, 26 Dec 2022 21:26:08 -0000 https://status.ppro.dev/incident/138462#e847e13f3b0315342a87cb53eba5c61df611a2892ffb6a2fdb0b6ab8326acc85 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Mon, 26 Dec 2022 19:56:53 -0000 https://status.ppro.dev/incident/138462#b8a1f6da8f4a1f2a61e4346f4acd41ee29964c2e7340e32413850ed8cb05897b ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Mon, 26 Dec 2022 13:37:35 -0000 https://status.ppro.dev/incident/138462#c7bd5903a3110dfd81fe0c9629110192c60110d8f407d7f4a2372ffe3f66cfd8 BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Mon, 26 Dec 2022 13:31:56 -0000 https://status.ppro.dev/incident/138462#dc6cc8499cf015e7164ac406cb37aa76189e524f6e55420dfc953da99164cf34 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Mon, 26 Dec 2022 13:18:38 -0000 https://status.ppro.dev/incident/138462#9ef63858615f6ce1caaceb9ab33ef511007f6b6c7302c699c2ea3f1a4aaeccb2 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Mon, 26 Dec 2022 13:15:04 -0000 https://status.ppro.dev/incident/138462#6b3e7bf9245fb5c4d7c5faf2d1c980381d6b11225deb1c88784dfa1ddbbe80a8 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Mon, 26 Dec 2022 13:11:34 -0000 https://status.ppro.dev/incident/138462#38e60b12d8a130f43b8305737003a5583998945bc1215f9c86ca361c7caa3cf5 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Mon, 26 Dec 2022 13:10:06 -0000 https://status.ppro.dev/incident/138462#55001f503aab17208aeb64ee0a2c129e29615f2ada67b9ddc97b43f312fca8cd BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Mon, 26 Dec 2022 10:34:57 -0000 https://status.ppro.dev/incident/138462#44efe998ddeec572ef26330416664cdf2d55ba66fdfd63fe2963134083eacc93 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Mon, 26 Dec 2022 10:17:56 -0000 https://status.ppro.dev/incident/138462#e7cfc60daafb4ec78686afa63cabcb5c3557bab7b6abc90d699d4553b231403c ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Sat, 24 Dec 2022 08:38:30 -0000 https://status.ppro.dev/incident/138462#494f23cdf223d424665fad134911fa3ddbd252250d942161534f2d735eab9d49 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Sat, 24 Dec 2022 06:52:05 -0000 https://status.ppro.dev/incident/138462#89996e66a3116f9889d56be319203b187911af7461c0a3d91c5a9ae56308a40b fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Sat, 24 Dec 2022 06:43:46 -0000 https://status.ppro.dev/incident/138462#f7cbd806ac888559f3b7f7e7297f1521faa44dbfb177cbeec96fe2e01c4988b0 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Sat, 24 Dec 2022 03:06:27 -0000 https://status.ppro.dev/incident/138462#74fe542ffbcd874b2de7aae92520b409b7877cb77c4da520970fa877384f35d3 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Fri, 23 Dec 2022 18:59:10 -0000 https://status.ppro.dev/incident/138462#8101e1d0fc63c5d70b78bee5fc8df15add3b929ad99857bab63609ef8ee94b53 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Fri, 23 Dec 2022 15:01:52 -0000 https://status.ppro.dev/incident/138462#ffd6e73a6ec7c630dad204d6d27836841f76a6cc019800aebdc240c53682471b BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Fri, 23 Dec 2022 13:42:55 -0000 https://status.ppro.dev/incident/138462#f8f0077f826fecc4554f174195f179335bc5b2d6b039b5672f496d0c2130dd48 BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Fri, 23 Dec 2022 13:04:59 -0000 https://status.ppro.dev/incident/138462#9b3a3258f523071e982781bac9647fa1257577fd838bcd402a94fb4d967c5767 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Fri, 23 Dec 2022 12:57:57 -0000 https://status.ppro.dev/incident/138462#65b87cb33cdc1686ad0cc9128ef0f90834186a07e02eac112ab7909c30f68ffb BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Fri, 23 Dec 2022 12:30:17 -0000 https://status.ppro.dev/incident/138462#076a5a506343d17cc7ab5393e03f4116e0bdea8f37647c6cd74ec84f7e7f7ab1 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Fri, 23 Dec 2022 12:18:27 -0000 https://status.ppro.dev/incident/138462#ed04bd1907a26ece916d3b4b875f398ec6a682a7e584cfb7ffb771b6209cfbd9 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Fri, 23 Dec 2022 12:11:23 -0000 https://status.ppro.dev/incident/138462#44b3724a61898a66916ad3b81d0f21dc39008ec3877b34bf4d9c28b87ddaf99c BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Fri, 23 Dec 2022 10:32:55 -0000 https://status.ppro.dev/incident/138462#0585bb1ff4a1eb1859a8aa8655dee63598fc6b87851e7db79d307bf4db63291e BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Fri, 23 Dec 2022 10:25:05 -0000 https://status.ppro.dev/incident/138462#debae17b407d09188a923188a6c32987b110d8fdf8a2344c0b77f8223fa98f09 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Fri, 23 Dec 2022 07:27:37 -0000 https://status.ppro.dev/incident/138462#0a2354521717aa90eeaa0741b86536b9825c370d2c8c0fe1fc6eb3ac2502e282 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Fri, 23 Dec 2022 07:20:34 -0000 https://status.ppro.dev/incident/138462#4d6c45eb9f287ba64f2c9b8ab9163cfb7754a5413b5a05a94ee640e0a4b9e583 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Fri, 23 Dec 2022 00:22:40 -0000 https://status.ppro.dev/incident/138462#7cafed0261fdab2e1e35e06e84f05872a4ac3aac2fc6c1fd7e541c25f235a05c BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Thu, 22 Dec 2022 22:52:15 -0000 https://status.ppro.dev/incident/138462#e5db260a4dc95a2672bbd4b4c10be8079598aa7456011dfc065ea8c58e2c380e ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Thu, 22 Dec 2022 19:32:05 -0000 https://status.ppro.dev/incident/138462#bedced2394006e92a3e5ee147b3f11e6aae379a68921445be0da1a34ff5d9442 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Thu, 22 Dec 2022 19:05:34 -0000 https://status.ppro.dev/incident/138462#d7f0d6e6ee6ed71259c9214e0e76330d63bf911ac484564adaf4deed60d69a72 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Thu, 22 Dec 2022 19:02:24 -0000 https://status.ppro.dev/incident/138462#102900a42692038de61e52a78cffc3af962a404ac3ea4f13d1baa5e22465d1dd BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Thu, 22 Dec 2022 18:39:15 -0000 https://status.ppro.dev/incident/138462#dcb382245853ab325d13efb8d767c025b1348b084960d887f495a7fe05cede39 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Thu, 22 Dec 2022 17:26:41 -0000 https://status.ppro.dev/incident/138462#17917c35b19c24c6ce78fbe1e3f69bde7a1ea807d391d8d4c2fbdacc6640f0ed BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Thu, 22 Dec 2022 17:18:41 -0000 https://status.ppro.dev/incident/138462#a23622aa451aa69308e574d52b10b8e604554810b49d4a87f460465d87a7da77 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Thu, 22 Dec 2022 16:56:37 -0000 https://status.ppro.dev/incident/138462#455eb2e163bd4038aa9165bccba0eb9bdefab6cff9a3ced03cca03115f2d85ed BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Thu, 22 Dec 2022 16:48:44 -0000 https://status.ppro.dev/incident/138462#c83db60903afb43e1d3b76de5c6387f3db9fd8084352a90fd077d0574a1caa7a BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Thu, 22 Dec 2022 15:51:37 -0000 https://status.ppro.dev/incident/138462#d22414d2fa6466cb253644265579180d14a0aad864de99bcc187a674604a59a4 BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Thu, 22 Dec 2022 15:38:39 -0000 https://status.ppro.dev/incident/138462#dd83a51a32c7aafc10d2cbaeee87fef674210b75f20c0b7508ef6a796313be1c BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Thu, 22 Dec 2022 14:02:23 -0000 https://status.ppro.dev/incident/138462#3079d9cd02670cf98ef5eec452e810106b770b1a18e7a6cdb09f14066650c99d BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Thu, 22 Dec 2022 13:55:10 -0000 https://status.ppro.dev/incident/138462#d2ae7e9a33d145774e55bf0f93f4d5182cba15689591ed466f992a07b28bfedd BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Thu, 22 Dec 2022 11:16:38 -0000 https://status.ppro.dev/incident/138462#19c73b12a968f399eb382a77c44554c4e4547e5e3da1461b8371fe68a63f757d BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Thu, 22 Dec 2022 11:13:50 -0000 https://status.ppro.dev/incident/138462#53aca953cd6b3f3683bf4c8383f1e840e1fbbefed1e1ba61f149f20aa0834959 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Thu, 22 Dec 2022 11:06:38 -0000 https://status.ppro.dev/incident/138462#5d45637d1944e876310e085bb3604e842b572cfc3f0d0527385f524bf337ba34 BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Thu, 22 Dec 2022 10:09:02 -0000 https://status.ppro.dev/incident/138462#5753785b12e41db4f9bc582accb8dd8f34032166b68e19098c4b518c44e1b686 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Thu, 22 Dec 2022 08:26:01 -0000 https://status.ppro.dev/incident/138462#bcb12119a0bb8d010408d7f53a1dc500ebc4a079aa93149297230c3a514ca6e3 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Thu, 22 Dec 2022 07:03:10 -0000 https://status.ppro.dev/incident/138462#1c4af10a03100a4935dfe72e73199be5b88311930f74073e80d52fe89e1d9ab0 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Thu, 22 Dec 2022 06:35:18 -0000 https://status.ppro.dev/incident/138462#346ce5d1c06e6b13b05ffefd2f8b58656c2685ad0754f8b431f447589fd1207b BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Thu, 22 Dec 2022 02:43:06 -0000 https://status.ppro.dev/incident/138462#b54f5d9f31abde4e057f1aaea89afd63dec4ca70acc4863e9ed8b4aaa949cd8b BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Wed, 21 Dec 2022 19:35:10 -0000 https://status.ppro.dev/incident/138462#7e78aab50cca78eb718b8d5b90925f660002d67ea6182e5371fdad6b0f068ed0 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Wed, 21 Dec 2022 19:28:08 -0000 https://status.ppro.dev/incident/138462#5a1faed78a766a009ac4a2bb4062ab84a2750b59fe49180055f0a4e0f6f9260f BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Wed, 21 Dec 2022 16:45:12 -0000 https://status.ppro.dev/incident/138462#70b36ed3dc9903a5ab5e8cd2e2fcd16735ebca949db9be8c8d2c638c1fe6911e BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Wed, 21 Dec 2022 16:38:05 -0000 https://status.ppro.dev/incident/138462#03f991689fbd697649c3199ed82a89e77f0ef34c8c75029d6991fe0deb0b090c BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Wed, 21 Dec 2022 15:24:37 -0000 https://status.ppro.dev/incident/138462#bff1d6ba5febe20c9c746654ec0b3c48c0e5ab5551e3694bb1e43a14bc8d7b78 BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Wed, 21 Dec 2022 15:16:49 -0000 https://status.ppro.dev/incident/138462#357c46410a28b6b8a2265acdafd34f495916d7f3de81922d6bae52d24a857cae BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Wed, 21 Dec 2022 13:24:46 -0000 https://status.ppro.dev/incident/138462#3fed7c76ef1f4f5d870db04205e50c3f7cab20cea8cbec1ffa3e1ecdc3f76aca BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Wed, 21 Dec 2022 13:16:49 -0000 https://status.ppro.dev/incident/138462#79ecad25b55ce35b52fde9a7d623640541a60093a546deb7d762e1be225862eb BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Wed, 21 Dec 2022 11:44:46 -0000 https://status.ppro.dev/incident/138462#9d61c508c54424c26e9f7cc72291b96dff823cb5b5e1bc6376891444524447c2 BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Wed, 21 Dec 2022 11:36:51 -0000 https://status.ppro.dev/incident/138462#2d323a3b9ad0727a576cee0f35686b8ca1cfeeb06ad161741be07017cc468af7 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Wed, 21 Dec 2022 10:50:09 -0000 https://status.ppro.dev/incident/138462#e15df70002fc291cd99c5733632c9fe15773845d4fbb393ad9ce8cf1cf20f02a BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Tue, 20 Dec 2022 21:37:26 -0000 https://status.ppro.dev/incident/138462#d0d8959c56410858addb2514331e7368d46e52cd32f0c3050cfc418c63549c11 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Tue, 20 Dec 2022 14:37:55 -0000 https://status.ppro.dev/incident/138462#2ae12ffc83248c1e995fc9732a9f0072813c14adc4385d793089b070e405ee9a BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Tue, 20 Dec 2022 14:10:06 -0000 https://status.ppro.dev/incident/138462#15a0323befadf273f088fe624979de83d437cf4c4d88b73bbdf527fa70d85033 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Tue, 20 Dec 2022 14:02:53 -0000 https://status.ppro.dev/incident/138462#6404172486275e5f17979ada75da2bbf8b5b10e98536fa9d9fa1538065150f2a BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Tue, 20 Dec 2022 13:02:15 -0000 https://status.ppro.dev/incident/138462#c894e77b706735812c82458fb637081b297354b11f2b2dbd04fde9f0e0568fd8 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Tue, 20 Dec 2022 09:50:07 -0000 https://status.ppro.dev/incident/138462#09cea13e2ef66cad54a100ce07ebe1b1dd623aecddee90026b0e1ee1cfe34a8c BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Tue, 20 Dec 2022 09:03:03 -0000 https://status.ppro.dev/incident/138462#1ee9b96d87ce6b56b71d5cc48443edb3d32ffe49e327a90b1e963d645b607c8c BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Tue, 20 Dec 2022 08:07:18 -0000 https://status.ppro.dev/incident/138462#9c985681ca6c9a1dbc7810196a9877a5854222f5c8792bee0de4ebb7f5d867f7 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Tue, 20 Dec 2022 07:04:47 -0000 https://status.ppro.dev/incident/138462#48e439a271865d75b591a9d7dc9abf88fde94fba339d2afb14ebb7bdaee10345 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Tue, 20 Dec 2022 06:57:30 -0000 https://status.ppro.dev/incident/138462#25385516388cc811c492634093769ac61f975ec2efea4ceef505b2ff9a27dede BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Tue, 20 Dec 2022 05:25:40 -0000 https://status.ppro.dev/incident/138462#79a5a00669cab94dfd8ff10afddbbbd41e2710e8df997434786b85f07d05d482 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Tue, 20 Dec 2022 01:19:31 -0000 https://status.ppro.dev/incident/138462#1d81d426b18a387f9eaa1693464f6bab1f210abb6afc1c575a943a5030eb726c BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Mon, 19 Dec 2022 22:03:46 -0000 https://status.ppro.dev/incident/138462#c9acb74c777fe1bff69ae8a5513a79f44d775ead6437150f55d62fbd43f739d6 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Mon, 19 Dec 2022 19:52:30 -0000 https://status.ppro.dev/incident/138462#954020df7f508da10ac2e05a876175ecfce873a9cfef2627f4206f602961c601 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Mon, 19 Dec 2022 15:29:38 -0000 https://status.ppro.dev/incident/138462#c99c197acfbb018e9240db3c5f64b392985bd5e255bd77df9ccbd6f9debb3b19 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Mon, 19 Dec 2022 15:29:01 -0000 https://status.ppro.dev/incident/138462#33b990b9043b0d021aee0403724c0348a34a9a8266bbb4bc7977249a773c0120 BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Mon, 19 Dec 2022 14:50:52 -0000 https://status.ppro.dev/incident/138462#1da44264d9e853f254602856be1df00aa18a220951c1a8354b5a8ef905d57eb2 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Mon, 19 Dec 2022 14:17:26 -0000 https://status.ppro.dev/incident/138462#2296b08e7010ae477781cfd6e008066c6d27fab40f8e71ca01d47d6cf0785aa7 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Mon, 19 Dec 2022 13:04:38 -0000 https://status.ppro.dev/incident/138462#b3c7a49b9fe737eecb5124d314c010812c32f75c5817632e65501c0582d973a7 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Mon, 19 Dec 2022 12:39:29 -0000 https://status.ppro.dev/incident/138462#b2d1d0c7775989e06cb2efb658e190f14ddb51c768db4e518ffeac51da9eeb8e BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Mon, 19 Dec 2022 10:35:59 -0000 https://status.ppro.dev/incident/138462#7b5f94c6a448bf0e20656cabeb53d7826d0b60b5b421b3045a45666bf22109c8 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Mon, 19 Dec 2022 10:24:46 -0000 https://status.ppro.dev/incident/138462#0ddb2f600171a0de68d6c0bf43319afa0baca39eee0bc203445a628404240769 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Mon, 19 Dec 2022 10:05:35 -0000 https://status.ppro.dev/incident/138462#7a6af98d5d2fde4c44ac36fbb840cfa8336057a9ce9b9c9fefbf50f76e06fe06 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Mon, 19 Dec 2022 06:44:03 -0000 https://status.ppro.dev/incident/138462#76c0f306da3087af9b94d5b3ec6714da35f65cc4bc2035287f8e5642425737c8 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Mon, 19 Dec 2022 01:14:21 -0000 https://status.ppro.dev/incident/138462#a4b3ea23a080a0a74c4ccfbf5248f83f6923a1d985cf3c4ba1451ca461f68da5 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Sun, 18 Dec 2022 22:11:59 -0000 https://status.ppro.dev/incident/138462#786a785e8f13bfe11073f2df88d5c3c0d9e240647c7cf6984ef29ad03f9b499a smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Sun, 18 Dec 2022 21:34:08 -0000 https://status.ppro.dev/incident/138462#e593e71fa27203b1621166c729745288e5c766fd24439f11386ee5bde020699a smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Sun, 18 Dec 2022 20:55:26 -0000 https://status.ppro.dev/incident/138462#2498f5aa547468a4acb18e2db125e81606f6f03e991dd91296595029763742aa ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Sun, 18 Dec 2022 20:22:02 -0000 https://status.ppro.dev/incident/138462#f65246a21a5765e14c91edc1add7a20df963f66bf4777ac7b432b33bf97e3e6f smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Sun, 18 Dec 2022 19:23:19 -0000 https://status.ppro.dev/incident/138462#504f728682d6b2475782658f8021cdd449276897ab4e3053c016c2af072f4de3 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Sun, 18 Dec 2022 13:40:19 -0000 https://status.ppro.dev/incident/138462#faa664d2de742b10f8beb6b20dc9a31e008aa932c921643a3b6faf8b436e7216 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Sun, 18 Dec 2022 10:37:39 -0000 https://status.ppro.dev/incident/138462#e88b4c1516522072cb487102ffa8f8db2afe8ee47321cd0580646623b9edea4e ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Sun, 18 Dec 2022 03:33:32 -0000 https://status.ppro.dev/incident/138462#116d01a6f59d71b4a00fd6cbd2586197b38f0fec7103815079d4bb1fb39ce0d8 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Sun, 18 Dec 2022 03:33:02 -0000 https://status.ppro.dev/incident/138462#a9b33bf22f1759074ca23b3ef6536da73db5aecf83a3d5b6457ea1f09227701d fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Sun, 18 Dec 2022 03:00:50 -0000 https://status.ppro.dev/incident/138462#5f1cba0efe4d56525280e7ccc1bfab506858ddd3563eb408409446ebb01438ce smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Sun, 18 Dec 2022 03:00:28 -0000 https://status.ppro.dev/incident/138462#251175f8a7e40a0d5f639daf74f9c1a0f17f5f093419ac6a60b0b95e7b240a7a fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Sat, 17 Dec 2022 23:45:45 -0000 https://status.ppro.dev/incident/138462#92885c320c31f3d72065a011e67db460c85ae82629686b915443e35e42190ea4 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Sat, 17 Dec 2022 22:49:42 -0000 https://status.ppro.dev/incident/138462#8dfa7aed30b3efc84f3d4f5b1a66a1b92bd1f96d488abb67232cbe1ca05185ed ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Sat, 17 Dec 2022 17:42:50 -0000 https://status.ppro.dev/incident/138462#e9a177ae05c2d0fb8bf63c10a2b36181761968fd57245efc911cd9ef048a2fdb ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Sat, 17 Dec 2022 14:07:38 -0000 https://status.ppro.dev/incident/138462#4703b2d99e01dbda0f7a1244cbc1b388fa0fb5b340bf5b574e4df55b592428da ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Sat, 17 Dec 2022 12:43:33 -0000 https://status.ppro.dev/incident/138462#2ad0acbf8881ee8f899d4f0f0a3c4136df840a6fafea6c99fc105b5dbebd1d59 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Sat, 17 Dec 2022 12:27:12 -0000 https://status.ppro.dev/incident/138462#8a260a4e61b167afeab74f4a613be0c9ce6457a3b3a1e94bd0af2bc92fa74de4 fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Sat, 17 Dec 2022 12:09:42 -0000 https://status.ppro.dev/incident/138462#d57b8343f198893e53a42e208e0a0027dc820c5f029c183d8ad98c264c93b4aa fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Sat, 17 Dec 2022 11:30:26 -0000 https://status.ppro.dev/incident/138462#091f8c08a90c711078b36b1b18b42ff01a8717b91c6907399d69e01a0b95dfb4 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Sat, 17 Dec 2022 08:09:12 -0000 https://status.ppro.dev/incident/138462#c76f9abfad882d6043479de2cb04762ab4fc5caa88d7ca83d130b33386a6de6b ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Sat, 17 Dec 2022 07:01:43 -0000 https://status.ppro.dev/incident/138462#505b7267c187d168e17f57cff45ecbc9a40256ec186807fb6e0dd93e00704974 fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Sat, 17 Dec 2022 06:41:26 -0000 https://status.ppro.dev/incident/138462#459a18b884b0d0c70ba3c2d5fd6e60f2f37fb9834188940c44577dc73d1a90a1 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Sat, 17 Dec 2022 02:37:31 -0000 https://status.ppro.dev/incident/138462#8a3dc5978dcd3212ab4716f22b41e0bebf1cfae447e54b3b0de28e09c46331f9 fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Sat, 17 Dec 2022 01:41:13 -0000 https://status.ppro.dev/incident/138462#99a3a30d7f05ffe016adcade2040f51a12f90a22912f66a5ef73c587a797fd4f ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Sat, 17 Dec 2022 00:23:22 -0000 https://status.ppro.dev/incident/138462#0bfa53e63be73d578db41f6ddc4f793c71e6809ae2e1e0c3c46977bdbdcd0da3 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Fri, 16 Dec 2022 23:50:00 -0000 https://status.ppro.dev/incident/138462#a51f04ddc1a83fc27f6ef96d1916935d1b8d4e83b3ca072eb6d13394b460c736 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Fri, 16 Dec 2022 21:09:09 -0000 https://status.ppro.dev/incident/138462#3bd206d468ef492aa513ef9ad74d432bd7eedeac2dd376daf40369ade9f95089 fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Fri, 16 Dec 2022 21:04:14 -0000 https://status.ppro.dev/incident/138462#27daebee24c914e579a60226ee36fe11f38c496a414a5f158378cf6283664d5c fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Fri, 16 Dec 2022 18:18:37 -0000 https://status.ppro.dev/incident/138462#c1ab513a30f20e6dfe475c59a96830245aaeded9feab3fef53c06cf080e6c342 fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Fri, 16 Dec 2022 16:58:58 -0000 https://status.ppro.dev/incident/138462#fda56b10c13eab02cf42526096e15b3c1a4749d5fc43d493ff916262af35feae fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Fri, 16 Dec 2022 16:04:43 -0000 https://status.ppro.dev/incident/138462#7dad5854aaafb58cb8301df28494e88633b155da068f40e7dcf08527a6fea09d ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Fri, 16 Dec 2022 15:46:14 -0000 https://status.ppro.dev/incident/138462#5f860095fa57bfe1a9b213d3ed8ce48e65debf43d4e5cb5ef1bd6443e878f31c ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Fri, 16 Dec 2022 15:36:52 -0000 https://status.ppro.dev/incident/138462#befe94f2cb19ce44bb70d358eac454733cecf21e75560fa2f022f655ba93180b ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Fri, 16 Dec 2022 15:15:18 -0000 https://status.ppro.dev/incident/138462#59fb8dc1758f223a7d736469afe3b74bed35a21430474f515f1f401cbe273398 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Fri, 16 Dec 2022 14:39:22 -0000 https://status.ppro.dev/incident/138462#bddbcf3426a73f0efc9a2fa5e0b4f2b6f088cacf4f203b5089cd0c8d93b7a687 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Fri, 16 Dec 2022 13:54:58 -0000 https://status.ppro.dev/incident/138462#6f760aec82b9b4ddb60eb5f08bed1be1e5d578c3b6d7977940ac87d350175e1e ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Fri, 16 Dec 2022 12:54:01 -0000 https://status.ppro.dev/incident/138462#f0b67496885c0db4abc65591dfbcae52ad8bc71eacde010d777222cb9be09114 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Fri, 16 Dec 2022 08:38:05 -0000 https://status.ppro.dev/incident/138462#c8b9badecea183e1f5b6dde56819aeda42a9ce61348425d4d106c7946df60112 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Fri, 16 Dec 2022 07:44:58 -0000 https://status.ppro.dev/incident/138462#7dd06982f3952900f45c4ff947ee5655a4f0eded29f7c60db2c486944395e5a4 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Fri, 16 Dec 2022 07:38:48 -0000 https://status.ppro.dev/incident/138462#cc5c5135442e4a11280009259dc5ea467a6f33afe5062c16b3afb3b0645ae418 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Fri, 16 Dec 2022 06:57:27 -0000 https://status.ppro.dev/incident/138462#141025dc4dba30f5b1a9caad84227de78675eca5094af38ecd78ebc7e26ee653 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Fri, 16 Dec 2022 05:20:49 -0000 https://status.ppro.dev/incident/138462#35c6d9588fc6178aa1fb59fef2ddae397b93dfcbadeeff978ea9cbc5b4298bed fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Fri, 16 Dec 2022 02:43:44 -0000 https://status.ppro.dev/incident/138462#c3ee2d811ad680fc72433356759996a7d0f1b04bf56dd726b919d8d2f2565a48 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Fri, 16 Dec 2022 01:59:34 -0000 https://status.ppro.dev/incident/138462#26f48cbe13e5c952b1ebd24f85660f24b84e51a7ec04c422151e0733c1fefba2 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Thu, 15 Dec 2022 21:07:50 -0000 https://status.ppro.dev/incident/138462#20d165568cb88272eceafd60c85ee6d66f6cbbe183bd828b9008204bde38e03c ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Thu, 15 Dec 2022 19:41:41 -0000 https://status.ppro.dev/incident/138462#aa3922c21aac4c64b6fc0c3edaa4444907bb2b4cb098a9d0666b579559baa0c7 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Thu, 15 Dec 2022 18:41:24 -0000 https://status.ppro.dev/incident/138462#322f5b75e531e8cbae017ad2633c022e4a357c1eab4bdc82303b4b325179d074 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Thu, 15 Dec 2022 15:40:27 -0000 https://status.ppro.dev/incident/138462#980d976302756d4b5c4572364363d2d1af690273755f0fbe98bf7f51bb373238 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Thu, 15 Dec 2022 15:38:59 -0000 https://status.ppro.dev/incident/138462#2f4bf3b110b1ca195306589c3e98d3e4d23b8274f68cc5e125d6c4f56160ea78 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Thu, 15 Dec 2022 15:29:19 -0000 https://status.ppro.dev/incident/138462#589bcba88a7a93b54a4a89202255b512d8cfc7bd8e366f4d4abec9c69a0dab58 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Thu, 15 Dec 2022 15:10:22 -0000 https://status.ppro.dev/incident/138462#58944f2b2e34d5085a1eae7a3afbe0d20b3251eca1905e8cfc0760cf3057b0e2 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Thu, 15 Dec 2022 15:05:19 -0000 https://status.ppro.dev/incident/138462#22f0b0c18aa8a0c9739d88f47d959debd99f10d19045871986202963068a9296 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Thu, 15 Dec 2022 14:22:26 -0000 https://status.ppro.dev/incident/138462#6e4f414df78e76e62a0440c7d82b4e2cab9b8079df5260f82f096f4eab2f5300 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Thu, 15 Dec 2022 14:21:04 -0000 https://status.ppro.dev/incident/138462#4aec20a3c718f7732430145781c90bbee285a706d772760e461ad15d55b9e6a1 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Thu, 15 Dec 2022 14:04:00 -0000 https://status.ppro.dev/incident/138462#1105af8621e2a7b53ce3cbfbf8c66ed3bd0c260b10723de7af06424e9c21d868 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Thu, 15 Dec 2022 13:41:21 -0000 https://status.ppro.dev/incident/138462#4dfe0cfa63a014b6a75eee4d33cd678bec26802ce6522911933b09a899f2152d ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Thu, 15 Dec 2022 12:21:03 -0000 https://status.ppro.dev/incident/138462#40f9c080e7c4ee63bf3ee58891e860b5b63a13e3b9ae20ee31ae2b536c481926 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Thu, 15 Dec 2022 12:13:23 -0000 https://status.ppro.dev/incident/138462#295bee1823c7fc995274e35b0750eae011fc00ae05a61caaa7b61a96aa6a1eb4 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Thu, 15 Dec 2022 12:09:11 -0000 https://status.ppro.dev/incident/138462#c7c3de6b57e6866ae2ff0b2532ddd0032bf029868ad77db65e3e265f44a511fb ppro: hz wireguard & myst recovered. https://status.ppro.dev/incident/138462 Thu, 15 Dec 2022 12:03:59 -0000 https://status.ppro.dev/incident/138462#52c26e0c15a816e5605678a85e987e2319aa95cf16b70047913e387e57fdc53e BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Thu, 15 Dec 2022 12:03:10 -0000 https://status.ppro.dev/incident/138462#08990cf2098821fc710aec197df6061f272f040f9d05a76df6edfdbf32f75c52 ppro: hz wireguard & myst went down. https://status.ppro.dev/incident/138462 Thu, 15 Dec 2022 11:25:51 -0000 https://status.ppro.dev/incident/138462#a52c2036a1bcc189e5ee4592dc752a4c6d8fbc301944e68c8411edcb6a437ba8 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Thu, 15 Dec 2022 10:27:49 -0000 https://status.ppro.dev/incident/138462#85d49357657638fd9ddf1274fe9c7c12eeb18a2e48f808d903e5f32646b444e8 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Thu, 15 Dec 2022 10:07:50 -0000 https://status.ppro.dev/incident/138462#249a43361d67291fa711c1b416ba192b101ed9a38000f6330a8fe31c7294226b ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Thu, 15 Dec 2022 07:20:40 -0000 https://status.ppro.dev/incident/138462#0166b912199b55a58dc8b966dcbdfd0a42716f5f53eed2c52520dbd3d815c3bd BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Thu, 15 Dec 2022 07:13:31 -0000 https://status.ppro.dev/incident/138462#f821fdd5b042236aba6dbeb08b99ffe77979161bf62c27c77c27e68d0a36f970 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Thu, 15 Dec 2022 06:55:42 -0000 https://status.ppro.dev/incident/138462#9f61ebaf2253906e42b7f984669e62ada347f67f7d34fc97d9608920985965a0 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Thu, 15 Dec 2022 06:51:20 -0000 https://status.ppro.dev/incident/138462#8083716eaa10711e9e64e86f825d80c773a470a71e53a208af910d138e55f8ed fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Thu, 15 Dec 2022 06:33:57 -0000 https://status.ppro.dev/incident/138462#f2154daf858106a53c81193910b788b313c02164599554218fc2edcd17c51682 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Thu, 15 Dec 2022 02:42:13 -0000 https://status.ppro.dev/incident/138462#9198a81b3f218c7873ea18464e7ee5e166639c22e8a86bb09644e894666ef7c4 fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Wed, 14 Dec 2022 19:27:54 -0000 https://status.ppro.dev/incident/138462#f1eda5c970c83e9f06c7011045bb3d89580169a4814c7abfe8c669f10c3f69fa fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Wed, 14 Dec 2022 19:00:50 -0000 https://status.ppro.dev/incident/138462#3610ee6871ea27368a30dc726112924fbd71adfecb9a628f4f9b4b2fa9afc1f1 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Wed, 14 Dec 2022 18:03:28 -0000 https://status.ppro.dev/incident/138462#3598ecdc55bf2b54273f50138803c96c7088b4d3e093586deea31816b4e2d1d2 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Wed, 14 Dec 2022 16:19:50 -0000 https://status.ppro.dev/incident/138462#480536e33d55133a4edcd822667367a12d5037c1d9d9be8d7cedd67cfcd1cee1 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Wed, 14 Dec 2022 14:50:22 -0000 https://status.ppro.dev/incident/138462#ad903e1d0314465cd37902d13e0de70bb8bf995c533418fc5d3db5ea0fb045e5 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Wed, 14 Dec 2022 14:43:17 -0000 https://status.ppro.dev/incident/138462#7dd398c1793f5e503033debe43d58f9765d2ffa321e167d92f42128ffd89af18 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Wed, 14 Dec 2022 14:35:08 -0000 https://status.ppro.dev/incident/138462#040b5e2735ac4c1c96b479824f5d2055cd19796d1ec198035db8f11da2f680ff BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Wed, 14 Dec 2022 14:34:26 -0000 https://status.ppro.dev/incident/138462#45fe93a7a9d7f287a8cd3a720f9cc3a019b56eaaf94185eb1333f42e58f898ae BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Wed, 14 Dec 2022 14:26:20 -0000 https://status.ppro.dev/incident/138462#0429d974346d4fa255f6e8a8fcdc6dff9cbd931c8d30169e4cc9712e60454c7e BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Wed, 14 Dec 2022 14:17:40 -0000 https://status.ppro.dev/incident/138462#af2985c525657b5b0381124f54b91b6ff9628e7986842cc49f457506864a4df7 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Wed, 14 Dec 2022 11:24:08 -0000 https://status.ppro.dev/incident/138462#a0172f58f3a1b2d752de39e273dd256a933a2d5d0b0877582b1a7cbd2ddf0ddc ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Wed, 14 Dec 2022 10:45:05 -0000 https://status.ppro.dev/incident/138462#5ce068fe1e4c38dfc60ed2c46386b997259422e552ecf010bd827a5a8bbfb90b BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Wed, 14 Dec 2022 10:22:30 -0000 https://status.ppro.dev/incident/138462#edbc71353b0579268544d74e0ac2bf737e8f97ed2c54e85f6eb6c3ae60709397 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Wed, 14 Dec 2022 08:21:50 -0000 https://status.ppro.dev/incident/138462#eb0bc04eeb1ed0278c905a6a55333cc359ed6a4aeeafd70162f7a4838b461988 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Wed, 14 Dec 2022 06:44:45 -0000 https://status.ppro.dev/incident/138462#799b7ec6e1c1b54c6e00a4d3098d2db59d832275b1e099f8bb621756cce25659 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Wed, 14 Dec 2022 03:38:18 -0000 https://status.ppro.dev/incident/138462#db27620254aaea73249e334972717265dd966077c7d05b8a9765a5d9076aeb57 fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Wed, 14 Dec 2022 02:45:03 -0000 https://status.ppro.dev/incident/138462#e2cbd24ff00fa35535fa582da23e12a00e0e0a971e2b3486b5b8d6f44eb18e94 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Tue, 13 Dec 2022 17:57:30 -0000 https://status.ppro.dev/incident/138462#fc2f0bec7f1205901701e4502bd8bc3ece49937fb77c841505e853a34a08a0a1 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Tue, 13 Dec 2022 16:49:27 -0000 https://status.ppro.dev/incident/138462#db3ed9a2790643f8851eb52a55b22b6842006083ac2b9ab046922d2fd4b8e8db BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Tue, 13 Dec 2022 15:51:49 -0000 https://status.ppro.dev/incident/138462#ed337e42a80263836749cca01ac9d6a27017297172cb1018770999e5122b79e8 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Tue, 13 Dec 2022 14:59:16 -0000 https://status.ppro.dev/incident/138462#9274b893ead1ea3f460eed562a0965741f2c512a39236fe18fbed5da6c99d9bb ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Tue, 13 Dec 2022 14:44:00 -0000 https://status.ppro.dev/incident/138462#38addc85107f487c491f641850553e35ba00fecc31534a7846f114a87116aaf1 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Tue, 13 Dec 2022 14:11:50 -0000 https://status.ppro.dev/incident/138462#174fcd8145ecaedb884c2d3a3c1ddcd5ebe8f880ab3f3678f2159e793429f486 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Tue, 13 Dec 2022 13:43:55 -0000 https://status.ppro.dev/incident/138462#0a47743f53835a6e0947adb4843e678045313b623ed79c79c847418ec1e1e62d BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Tue, 13 Dec 2022 13:36:51 -0000 https://status.ppro.dev/incident/138462#3a31a98f7d8284f300f46379d680194d336dea76d62ac6dd148faf973b0da98f BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Tue, 13 Dec 2022 13:09:08 -0000 https://status.ppro.dev/incident/138462#179756582d86cbdf870b21b751f57941df460f55bea9a9d923dd3f6dde514161 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Tue, 13 Dec 2022 12:21:05 -0000 https://status.ppro.dev/incident/138462#3031e330068dbb95297f5a87a5c492ba6a1837e9623bec9b186a3b56ba3b0dec smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Tue, 13 Dec 2022 12:13:02 -0000 https://status.ppro.dev/incident/138462#bf8dc9e7bcd73dc9cc012432ed1f552c82add0be63122cabd82e90ace7a086b8 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Tue, 13 Dec 2022 11:18:51 -0000 https://status.ppro.dev/incident/138462#30b9d3406f86c597281441a9343ff97992c1b12a16317ee83c0bce819b3465a1 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Tue, 13 Dec 2022 11:06:48 -0000 https://status.ppro.dev/incident/138462#9f84892e4b89c949493eb6563c46f06c174fa8321055d901a07a342a63a0bb1f BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Tue, 13 Dec 2022 10:54:00 -0000 https://status.ppro.dev/incident/138462#f4de931fdccacd9f1ee08306bb2a102a2923ca96c357af3d7587c33aceea2ba5 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Tue, 13 Dec 2022 10:53:16 -0000 https://status.ppro.dev/incident/138462#9414e258351fbcb4b63314d2e6929a1e973faf7e56081e4e0a49c5320f575de5 BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Tue, 13 Dec 2022 08:09:56 -0000 https://status.ppro.dev/incident/138462#7649a62dbd0b410d196a2f1012f8ca22bfd84b9bacb02bbb6055c5f48de88c92 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Tue, 13 Dec 2022 08:01:17 -0000 https://status.ppro.dev/incident/138462#9ac680a0c2648870bd365cbfe04ba3104624bc8e39e9930dea374377747178d5 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Tue, 13 Dec 2022 07:48:19 -0000 https://status.ppro.dev/incident/138462#6d7801764d32ae5ed79b6a1dc633bf67661ce6744c1959db1b2a170070c716b9 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Tue, 13 Dec 2022 07:31:19 -0000 https://status.ppro.dev/incident/138462#479d26f00b4ecae95fdd2c9b5c723c10ce57f9c3f494f3a677bc6bde69234b19 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Tue, 13 Dec 2022 02:33:18 -0000 https://status.ppro.dev/incident/138462#57fdea7ddcb804e87816678f73382d3916e3ea8a20e782e2eb044c4f55196af1 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Tue, 13 Dec 2022 02:32:44 -0000 https://status.ppro.dev/incident/138462#677423fc69852b0ff1dcbcb03cba155bae63fd3ddd8edc69b66b2a109a436c2a BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Tue, 13 Dec 2022 00:48:51 -0000 https://status.ppro.dev/incident/138462#a2cd8d7fd012e07ae84fcf94f8d1631ed378afe24179d09e98190d192d64b457 fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Tue, 13 Dec 2022 00:44:49 -0000 https://status.ppro.dev/incident/138462#1bc2276cc72af2a3874027d679624e85f4e51c65712515d5b24ffda6fa6f715a BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Mon, 12 Dec 2022 23:50:34 -0000 https://status.ppro.dev/incident/138462#f8a12de57c92d974aee58dcb3581deeac34d3fd6c51a5e9369fec389870a4ee0 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Mon, 12 Dec 2022 23:18:26 -0000 https://status.ppro.dev/incident/138462#e019cfd749a1f9eb59fed57861df292d85a0f1d613cca21971cf1ba6cfe68f3d smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Mon, 12 Dec 2022 22:30:30 -0000 https://status.ppro.dev/incident/138462#6f9c07396b7af21e0d7848f7e0f18af76bc7cef15b41bd1c85cefedc82f7bd65 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Mon, 12 Dec 2022 22:03:24 -0000 https://status.ppro.dev/incident/138462#6902decff52ca425514bb93f912669e3d16bbe4cf714d3b5540cbea3574afb9b smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Mon, 12 Dec 2022 21:28:40 -0000 https://status.ppro.dev/incident/138462#0974305c17274a62ed14cb619046da9e878a041f0a67b5cf8404d31bfadf2ee1 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Mon, 12 Dec 2022 19:17:34 -0000 https://status.ppro.dev/incident/138462#e3ab4f7d9c1d157cd78686d0025178cbf18240f9ca1a8055aba533b341f228df ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Mon, 12 Dec 2022 18:41:18 -0000 https://status.ppro.dev/incident/138462#2149d2bdfc13db986abbc2ee9d140da3b3daabded3cec05f82bcaf656489295d BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Mon, 12 Dec 2022 18:37:44 -0000 https://status.ppro.dev/incident/138462#d0872449339f4f1f90b1c3f0f5f5d3a3192663f2bab8ddd747cbbba0487ee0f6 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Mon, 12 Dec 2022 14:28:29 -0000 https://status.ppro.dev/incident/138462#7dd804a86a5a47e568150a7a5d2cb4cc2edd5811431ccb9cd0428ae1a1845c05 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Mon, 12 Dec 2022 14:21:13 -0000 https://status.ppro.dev/incident/138462#94f9b12b49a79b9f5874fa39b2499f689ccaed7f4ead3a220963b6d1d6bce133 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Mon, 12 Dec 2022 13:46:36 -0000 https://status.ppro.dev/incident/138462#8adf7c666a9d02efc3f42452129322d732eaba84ede82c3e66778838374478e9 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Mon, 12 Dec 2022 12:08:29 -0000 https://status.ppro.dev/incident/138462#8e77f685bc6adfcfad23d23a91c76b1654429160ef8a35561be6a018b287a0a9 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Mon, 12 Dec 2022 10:25:58 -0000 https://status.ppro.dev/incident/138462#bbe55f0454db2c4b9314ba77c3ce6db9e2aebebf5301cc55be683374c1b119fa BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Mon, 12 Dec 2022 08:14:04 -0000 https://status.ppro.dev/incident/138462#43a6dfd0ba0002294a4b5a3f71ec10530ced6aca98e2ba8d8859ede751f16170 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Mon, 12 Dec 2022 02:01:09 -0000 https://status.ppro.dev/incident/138462#ca874dadba54e9150d93fb483d297c932d1ac33e65c954af33ca54cdb037c704 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Sun, 11 Dec 2022 22:59:59 -0000 https://status.ppro.dev/incident/138462#976b657453da3b33125552818afb03c62a8029e3c304d91d1fcdb37690763916 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Sun, 11 Dec 2022 22:45:20 -0000 https://status.ppro.dev/incident/138462#8da8180e75345341a2181d187c31fb80d6f1751541e35a0a93c578c8b7efa7dd fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Sun, 11 Dec 2022 22:43:56 -0000 https://status.ppro.dev/incident/138462#ea1ae6537ec81639645bef4048d234aa84136517dafdbde9be66d9a6406c5133 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Sun, 11 Dec 2022 22:07:51 -0000 https://status.ppro.dev/incident/138462#e4dfcd4eec9a4c5212c4a1b786052879c3919b0ab337c616ae35de78355ce895 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Sun, 11 Dec 2022 21:42:52 -0000 https://status.ppro.dev/incident/138462#5ff54d6ca00866392cbb8ed79ea46d740a9b6bdd7284f9540eb49f737d006035 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Sun, 11 Dec 2022 21:06:36 -0000 https://status.ppro.dev/incident/138462#614b5a9bb75c46b1637300653642ba1ae38061dc3e9a611f49069b8b298ca780 BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Sun, 11 Dec 2022 19:59:20 -0000 https://status.ppro.dev/incident/138462#7b6abe05e0f72bcade86d51426765bf0fd1b050c2dda6b3ec49d73a7c18e75c2 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Sun, 11 Dec 2022 19:50:40 -0000 https://status.ppro.dev/incident/138462#27c3898bb8eb52cd66b688bb65d8ddb61de572bf65384bd07f94223ddc491165 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Sun, 11 Dec 2022 18:36:35 -0000 https://status.ppro.dev/incident/138462#cb09eb15af05d7525ee7340843ff673779686ba7db147c789f3158cdf62f572c fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Sun, 11 Dec 2022 15:27:13 -0000 https://status.ppro.dev/incident/138462#fbf0fa3673ffd77c06ca5dda72b9d63e50f339b2ed00325e60c3f56b28df13e6 fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Sun, 11 Dec 2022 14:51:35 -0000 https://status.ppro.dev/incident/138462#d47c0a971e0f8d396cadb9b724fa2e1c057f96e67a9756b510ee5d88ea378459 BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Sun, 11 Dec 2022 14:37:35 -0000 https://status.ppro.dev/incident/138462#dd0b37c6689d827770cc58263de56241cac6b13196b1a2367e605ad8b12e2ec3 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Sun, 11 Dec 2022 13:40:04 -0000 https://status.ppro.dev/incident/138462#3a22d41a8868aa13c3110764c0849a0dfee0f3268202a36f767323bb395d9e46 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Sun, 11 Dec 2022 13:32:42 -0000 https://status.ppro.dev/incident/138462#bb032e7a2f3ad542b28740294e9fddf7b551141bcdacb607d76823ac0c8977d5 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Sun, 11 Dec 2022 13:29:51 -0000 https://status.ppro.dev/incident/138462#08536bf0cb029f2c3d42630fe6a4eddc9cf003331bec03c21aaac7f4c95fa22f smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Sun, 11 Dec 2022 13:09:57 -0000 https://status.ppro.dev/incident/138462#2fe09d73bafa3b7caad75a7af03b918e158550b94c7455e643b0d880b99ca3f1 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Sun, 11 Dec 2022 13:02:55 -0000 https://status.ppro.dev/incident/138462#389c2ccd126ec76068d37ab73b5bcc90ce0652efa499b202346395c74e18f2a7 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Sun, 11 Dec 2022 11:29:07 -0000 https://status.ppro.dev/incident/138462#3cf154a5e832c0fe3a07c1e0a3a91ce9907dfccf25843cff190f125319ceca55 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Sun, 11 Dec 2022 11:20:30 -0000 https://status.ppro.dev/incident/138462#a348670b573198f12a1a1e7de3e5d17584f2ef00637a9b2c8625fad21612ec3b BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Sun, 11 Dec 2022 10:32:02 -0000 https://status.ppro.dev/incident/138462#10ffdcdb97acb521203b037b063276cd870588fd9839135351cf3333fafd9cf0 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Sun, 11 Dec 2022 10:30:55 -0000 https://status.ppro.dev/incident/138462#d5582837006b37701e66d32cac81e547781cca812d6e15afc3af0242236e9b87 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Sun, 11 Dec 2022 06:15:07 -0000 https://status.ppro.dev/incident/138462#68178de85b2b147818277fb90c8bc358fcbc1d95269ca7a239eb549ada9a93dc smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Sun, 11 Dec 2022 06:13:08 -0000 https://status.ppro.dev/incident/138462#0c420de27e9b8e4e49af05114a81f917cf9a1910c9a9386a8370df58b597fec0 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Sun, 11 Dec 2022 06:12:02 -0000 https://status.ppro.dev/incident/138462#fb5a16870fad47c840fbb5a56ca585af45704354daabaf6a1c70c0fc385ef820 BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Sun, 11 Dec 2022 05:34:08 -0000 https://status.ppro.dev/incident/138462#677836cd55f4d015e9f8b43681177905244ff8e06992825a479899ee3319c368 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Sun, 11 Dec 2022 05:30:09 -0000 https://status.ppro.dev/incident/138462#c5bbc436efc841f25bbdcc3728e96e7a6b440c1c739c8d0eb0f46769bc2f537a fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Sun, 11 Dec 2022 05:20:29 -0000 https://status.ppro.dev/incident/138462#dcfa2a91380ae785cebc1ed409d4c3ae0aa3ac3d8dafd0d29175d476c27fa8d1 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Sun, 11 Dec 2022 04:49:06 -0000 https://status.ppro.dev/incident/138462#37cf050eedfc9ed9b3ac0d9bf2d7b602e24dab2e077b9484388c9ceb3a044ced ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Sun, 11 Dec 2022 03:30:50 -0000 https://status.ppro.dev/incident/138462#412c7b7187007fb0c65539da518a185b76febabe3fed48b8b1fb5473acc47a8e fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Sun, 11 Dec 2022 03:27:03 -0000 https://status.ppro.dev/incident/138462#28a43ca91fa851b28f5c93a463071cba2bb6d3f353e45d0e2c4d500ebeec365d fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Sun, 11 Dec 2022 02:30:51 -0000 https://status.ppro.dev/incident/138462#ec47bced82a1b1818ddb8aeeed1ae16d7df065650c493f24b0be5a558d6bb774 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Sun, 11 Dec 2022 02:03:02 -0000 https://status.ppro.dev/incident/138462#13cf9c26bf5cb69a769248acf54f371542e1130c4fdc14e3be0d6e362790fa9d smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Sun, 11 Dec 2022 01:44:00 -0000 https://status.ppro.dev/incident/138462#a594df2c5e2316e4e8fac909bba52c847210cd683b119a42ca82898eb9f39afb ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Sat, 10 Dec 2022 19:19:06 -0000 https://status.ppro.dev/incident/138462#f15f4d13db606469a00560197fc724de6481d591e09a338e5a877fc71eb69f8b ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Sat, 10 Dec 2022 18:37:40 -0000 https://status.ppro.dev/incident/138462#02ec97ee9b70f12e8ef93fd9be1c632ff414b1b3a4e5550ce34788ae93dae9ff BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Sat, 10 Dec 2022 18:33:10 -0000 https://status.ppro.dev/incident/138462#1d495dbc60ecdd475144e71ab826e72ad6124acccb9774738154bdea5f7eb284 fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Sat, 10 Dec 2022 18:31:59 -0000 https://status.ppro.dev/incident/138462#6a52c7b7fe84f4582df2b703b0e7b460b366a15c90ef321c450404327af12465 BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Sat, 10 Dec 2022 16:09:12 -0000 https://status.ppro.dev/incident/138462#af23aef189d9640ddb0d5b65f0bef50c75350f434ba8e9f81a2a31d63d6822d5 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Sat, 10 Dec 2022 15:28:00 -0000 https://status.ppro.dev/incident/138462#5a7400a3a12c873712290d7f89baf1ea6e8736d43d179e0f2b7d27988e019e12 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Sat, 10 Dec 2022 14:00:28 -0000 https://status.ppro.dev/incident/138462#b95045c6a40685f7a783f4917ced174dd3d5480b5b10fa7ebca2cf276bd82eb7 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Sat, 10 Dec 2022 13:20:00 -0000 https://status.ppro.dev/incident/138462#e38f63783f47fb1c4fdebf22adfa9e379331033763749391d200247fc09ce195 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Sat, 10 Dec 2022 11:37:35 -0000 https://status.ppro.dev/incident/138462#67b1de0150f68d5a360d86d27fad0dd6c310d52f3c67ba4ad05e86d2e46e2330 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Sat, 10 Dec 2022 10:31:13 -0000 https://status.ppro.dev/incident/138462#aefedc2a2c56341269eeb3e2b7b7c3f564585bae5c4bf6fb4202aaf71074f9b5 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Sat, 10 Dec 2022 08:39:45 -0000 https://status.ppro.dev/incident/138462#5afca762bffb25c943e0db8240f07c42d5a82591216a1618c6f554275bab86f8 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Sat, 10 Dec 2022 08:27:42 -0000 https://status.ppro.dev/incident/138462#abacf5bd23f7e61546ad19198eb7c0e2a513936a9c490f24f6315efc2421c1e8 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Sat, 10 Dec 2022 07:44:00 -0000 https://status.ppro.dev/incident/138462#af1c08fe1a60e9789406d3c6c1497cda723e312cf04f213c13e55807756aecf2 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Sat, 10 Dec 2022 06:58:02 -0000 https://status.ppro.dev/incident/138462#3714f27afa0a2f4c8c8175f687c9f48e845974acf3f946575128f93faff1c34a ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Sat, 10 Dec 2022 06:05:31 -0000 https://status.ppro.dev/incident/138462#85f543ccf06fd19a9a8f72b882aa0f294cad0715f55e9b8139aa1cdeb59dbdbd BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Sat, 10 Dec 2022 04:07:51 -0000 https://status.ppro.dev/incident/138462#1a0f92789b9fefe77117e0d483433d5f38c0daeae5251ea280e5dfad8338b86c ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Sat, 10 Dec 2022 02:57:52 -0000 https://status.ppro.dev/incident/138462#69cb8f3f2339daa4bc0b02ff7686e6591a67ffc56d2400e7d46c8db7c73108e8 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Sat, 10 Dec 2022 02:24:09 -0000 https://status.ppro.dev/incident/138462#3c3a4af71e5c49d70af88b274db1c18d57ff81b24353c186c165cdc86c03f562 fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Fri, 09 Dec 2022 18:55:28 -0000 https://status.ppro.dev/incident/138462#7ea340c0d9f8c857f823509270925cd21bc3255f1a8274d37f304dc58918da1f BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Fri, 09 Dec 2022 18:27:28 -0000 https://status.ppro.dev/incident/138462#63934f6882cb01dcd887ba87340393826f8f3139fbce873d139b1c3bd9e23bb3 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Fri, 09 Dec 2022 17:07:34 -0000 https://status.ppro.dev/incident/138462#742f55ce8b454489a2fe026f73524bf6b6cd7b0494a89f63daf98f04f74153fb BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Fri, 09 Dec 2022 16:54:57 -0000 https://status.ppro.dev/incident/138462#45bf70c9997dbce12d3c008c79100290d53be3b817740a7d3e108be9662e32b9 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Fri, 09 Dec 2022 15:15:10 -0000 https://status.ppro.dev/incident/138462#753a6887b5af666718d38cf69c6fe1b44705343d327dc05f67cec177ef561932 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Fri, 09 Dec 2022 10:57:19 -0000 https://status.ppro.dev/incident/138462#94e257c2bb31bf8bf2bfef4a2222c310a2d0f0c6962fd9778c252747db31a99a BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Fri, 09 Dec 2022 10:25:04 -0000 https://status.ppro.dev/incident/138462#bcb30701af36c6b562284f5f937c0e1b0152b89b4871d833624a37312b4afe7d BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Fri, 09 Dec 2022 10:22:25 -0000 https://status.ppro.dev/incident/138462#33c1aefab636278792ed8952f8e1ae23a8a696ca97eba74f01895b37b9a58a08 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Fri, 09 Dec 2022 09:39:00 -0000 https://status.ppro.dev/incident/138462#d93b093549cb169cb377fdf2642791eb5ed840a5cd1c64a07ea9ff690d05d2e9 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Fri, 09 Dec 2022 09:21:33 -0000 https://status.ppro.dev/incident/138462#53e06175ade6dc6f020b8b0e11ee969b476e4845b0a72a64d9d4dfb798607890 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Fri, 09 Dec 2022 08:11:20 -0000 https://status.ppro.dev/incident/138462#9beb701b48fb8d2a9f0695ae34a5751571fb2b6aee765c3b8b701dd74a79a24b BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Fri, 09 Dec 2022 07:38:54 -0000 https://status.ppro.dev/incident/138462#69b2b1d55733cdd747aa923efc26b9763134f7f03bfdc0373356458e3db30ed9 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Fri, 09 Dec 2022 07:18:49 -0000 https://status.ppro.dev/incident/138462#16c01e41b29399fa4f50694e731289a04d9c326250e71b7da0e471dbcce64fc4 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Fri, 09 Dec 2022 05:41:28 -0000 https://status.ppro.dev/incident/138462#87d5c2521a887ac89079ee916da54b0b6f147588c17eb9638daa80605583ff74 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Fri, 09 Dec 2022 05:16:52 -0000 https://status.ppro.dev/incident/138462#95552dc74db38596616487a0bb25fd6f0f77311764b8e772b186d65e60acb6a5 fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Fri, 09 Dec 2022 05:06:50 -0000 https://status.ppro.dev/incident/138462#dedd704f977214883cdfa8ffafc53f16bc1746932c7c2073638b92a86d6ba78c ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Fri, 09 Dec 2022 02:44:49 -0000 https://status.ppro.dev/incident/138462#2c40661e2b3a688dc7b1058991fd12eeb8363eaa53a867c307864c5cf7934a20 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Fri, 09 Dec 2022 02:09:17 -0000 https://status.ppro.dev/incident/138462#7bde300e8d055743c5d000613a55499f46435fa56f72006ebeb1ce54d8a5b914 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Thu, 08 Dec 2022 22:35:53 -0000 https://status.ppro.dev/incident/138462#15acc3b68d683f483d83a4c47e79806955f6f0a29c462e9e3db8c9869d40eb15 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Thu, 08 Dec 2022 21:03:30 -0000 https://status.ppro.dev/incident/138462#71755d48c241019d60f00d2e9551c99ba93a775f77f4a62d00ae56a516e36758 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Thu, 08 Dec 2022 19:26:23 -0000 https://status.ppro.dev/incident/138462#cefb667a79b12ac24e55c7187d53796d6dad0a27ffc09c9bbf612e64be8365d4 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Thu, 08 Dec 2022 19:24:51 -0000 https://status.ppro.dev/incident/138462#6818b129ac6be173fc225579fd50a2f926506e2fc83efbe8e2ab001b978ac190 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Thu, 08 Dec 2022 19:21:00 -0000 https://status.ppro.dev/incident/138462#1712046ebf7d74252ec8155abdddb64e758bff3b6ef1b5cb85026dac94452056 BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Thu, 08 Dec 2022 19:18:01 -0000 https://status.ppro.dev/incident/138462#a6185c7af2e4a067afdbadc0a253d7d07dabebc1614013387e771eb22584eac4 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Thu, 08 Dec 2022 17:51:29 -0000 https://status.ppro.dev/incident/138462#e45370318b0645020bed96fa3bc151a6c884a17286ee68c643e17f04a18c6685 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Thu, 08 Dec 2022 17:11:09 -0000 https://status.ppro.dev/incident/138462#9620796f21e07e137a4b5b248e71064ff7cd6bf53a0008142e59bffd8ac50f50 fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Thu, 08 Dec 2022 16:56:53 -0000 https://status.ppro.dev/incident/138462#8f9170bf1e71b13a78fbb6472fc61c6b42e13e770be94d2d6b9d0671344867fb fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Thu, 08 Dec 2022 14:38:45 -0000 https://status.ppro.dev/incident/138462#8c26a30f1a190a75b0401ccf1393daf87ad35ae97a0ecd14b814c765801e91a0 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Thu, 08 Dec 2022 14:11:03 -0000 https://status.ppro.dev/incident/138462#ab55bdc99e44f8c5037bd2b399788bdc16a8d792cce39f231c1ae82616dd38e5 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Thu, 08 Dec 2022 12:50:41 -0000 https://status.ppro.dev/incident/138462#380c67deb2d3407f6ca4011bfc8f29fc74329b3fdc0648ef4ca9da29ba36b67f BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Thu, 08 Dec 2022 12:33:36 -0000 https://status.ppro.dev/incident/138462#9d2ad76ac6d92232a4bf171d8629389a2f9d70b7dcf6652d69c3a092b68ec7c6 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Thu, 08 Dec 2022 10:23:21 -0000 https://status.ppro.dev/incident/138462#da194d5a1a8271b92d06c23ed16e6b7a023aef73137167e7d832cfeddc6d86ff ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Thu, 08 Dec 2022 10:15:10 -0000 https://status.ppro.dev/incident/138462#b0785e3dca625c7cd488b939d5d1b0590cfae37e54f70142febf39ef40aa3f5b BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Thu, 08 Dec 2022 10:14:29 -0000 https://status.ppro.dev/incident/138462#2371c4c0632072c589b16144741a2892f7123215124af656af16461c6067482e BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Thu, 08 Dec 2022 09:27:10 -0000 https://status.ppro.dev/incident/138462#39ceb1a637328ba310288d9b5ccd3aa61d1888fd0d240cf1e60bd2601493aa32 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Thu, 08 Dec 2022 09:01:51 -0000 https://status.ppro.dev/incident/138462#54100f908f7d3d8e71d80383ab828202a22c6404c66d4f887c44db48ac233330 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Thu, 08 Dec 2022 08:53:00 -0000 https://status.ppro.dev/incident/138462#5b7bb19aa9165bcdfb106d1ffc7b4cdf7cbef24f9f822a4131aaa84932395952 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Thu, 08 Dec 2022 06:55:05 -0000 https://status.ppro.dev/incident/138462#828eeb18664ecf3b804f523ff971e282cfa042a72f36ce04190f1f17bdfd4416 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Thu, 08 Dec 2022 06:54:36 -0000 https://status.ppro.dev/incident/138462#59156fdd406d7f43c5cff695469c1c7702d8f45470e312a944f27d3ea9ff14df fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Thu, 08 Dec 2022 06:30:04 -0000 https://status.ppro.dev/incident/138462#d7dcfb7c3d3948725ba4473c6e038c5c07096944acfea628012627e605690121 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Thu, 08 Dec 2022 06:22:26 -0000 https://status.ppro.dev/incident/138462#e20f3991d7a621d3aab75c9062d91f8846b883dc16b2820eebc6bb6dc2b4b64e fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Thu, 08 Dec 2022 06:12:58 -0000 https://status.ppro.dev/incident/138462#0070fc8f68fe6cdb5d280932326337b73111bc3df4f43a9bd5212b249b0ebeb0 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Thu, 08 Dec 2022 04:37:32 -0000 https://status.ppro.dev/incident/138462#bf870bfe7028092b724b0d0a7d259481d939505ccc53d1901f896a7a66ba9b98 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Thu, 08 Dec 2022 02:39:58 -0000 https://status.ppro.dev/incident/138462#5128ce3ba7290abd8a2bef16aad9e3fbc307da81ceb6c9a73be96d40204d1a0c BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Thu, 08 Dec 2022 02:17:08 -0000 https://status.ppro.dev/incident/138462#f67d23fe8582a9c90f8c1df81350ef4c95b7c976b5ca7708c3c3ef8591c39b58 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Thu, 08 Dec 2022 02:06:43 -0000 https://status.ppro.dev/incident/138462#a7c0eb5e764c93be5b74f3af066d731a68e6187ff2cfcd537eb48e3b270195b0 fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Thu, 08 Dec 2022 01:44:33 -0000 https://status.ppro.dev/incident/138462#7465d366ed9e8e2e8d589f158f2ea030eff08d6f0b96cf83774d2fb91848068a smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Wed, 07 Dec 2022 23:08:26 -0000 https://status.ppro.dev/incident/138462#9deba34b01ecfd292e4d35f6cffb06e59bf8dd97a8cf65d56986ae08ca71d0b1 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Wed, 07 Dec 2022 21:42:09 -0000 https://status.ppro.dev/incident/138462#1fb94df17f5f7ff571870320346ad0f30e69233d23b46fb69cf43ada6bffa6d1 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Wed, 07 Dec 2022 20:01:31 -0000 https://status.ppro.dev/incident/138462#7a26b9bb6e36edb45d4e154e2a0ffac5a36be857bff1283e8aec1df8e2770e83 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Wed, 07 Dec 2022 19:10:06 -0000 https://status.ppro.dev/incident/138462#6daba721db92ef9c0fdfd3b2711799d3d86bb0d597ac13618f0676fcf87a8153 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Wed, 07 Dec 2022 18:17:08 -0000 https://status.ppro.dev/incident/138462#5c0c905d3ac9a9b2db6746458c00982bf01ac2bdc716aeef7f39fdfc976fa78d smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Wed, 07 Dec 2022 18:16:18 -0000 https://status.ppro.dev/incident/138462#15d0c0142d219ade36efa757292eeb0bce409c0cdbd15bb339892208d1e150f3 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Wed, 07 Dec 2022 18:09:07 -0000 https://status.ppro.dev/incident/138462#b3dd0921cd3afa612418a2c4f383f40ef4c7e10820c9f2bbaeafb2767f0950ac smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Wed, 07 Dec 2022 17:57:56 -0000 https://status.ppro.dev/incident/138462#237c30ecde2286ab1bfe5f13a471b3da23d2bf2eddd83dbed21742156ab7a9eb BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Wed, 07 Dec 2022 17:08:19 -0000 https://status.ppro.dev/incident/138462#6b3b9e08e24eb9782a77c3ef7627c902d5ba29e78cab58a1dfc1ac6ee098823c ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Wed, 07 Dec 2022 14:21:42 -0000 https://status.ppro.dev/incident/138462#71add04355878393513b1b3e242d958d2d4cdb5b9333acd0925ecc77b5395881 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Wed, 07 Dec 2022 14:09:39 -0000 https://status.ppro.dev/incident/138462#96c96ac827eec0056383f4ad9e16f65e26faa747532374b36210bbd736edd5db smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Wed, 07 Dec 2022 14:09:31 -0000 https://status.ppro.dev/incident/138462#4e110d8df4b31e006c677ee4793ef526e664f25c9d2d9eef309cd3c0616cbf05 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Wed, 07 Dec 2022 14:02:39 -0000 https://status.ppro.dev/incident/138462#eba12ce3d99c8cc42d5f156e0de80554342189c9eb1fca81d5a2f78339911592 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Wed, 07 Dec 2022 11:30:55 -0000 https://status.ppro.dev/incident/138462#39eb784aa4a6e692bc774713a414187a31a8b0cb601956240efda7191925b020 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Wed, 07 Dec 2022 10:49:32 -0000 https://status.ppro.dev/incident/138462#21a507c5a81b522ee8a712882e5ee53cc56115ab3da5a157ec932e53ee92c4ad BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Wed, 07 Dec 2022 10:42:38 -0000 https://status.ppro.dev/incident/138462#a3222cc2fb6fed4cb4ac09ac1d0b06306c7a8cee5bb7b7983823a1aaf44266a4 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Wed, 07 Dec 2022 10:39:31 -0000 https://status.ppro.dev/incident/138462#e228c41d96c59d278dc51ade4c8e5a835509b0c55cd61256432bc1b1ab220a1e BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Wed, 07 Dec 2022 10:22:39 -0000 https://status.ppro.dev/incident/138462#3132c4eb25bc99555b5df84fe39b4a50ed118ae23911bc475cd51912d9cb0121 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Wed, 07 Dec 2022 09:46:52 -0000 https://status.ppro.dev/incident/138462#f211ce4d6ba87bc902bb7eea6749ff8199750bec52b19f2388e2a8bddd67b8d2 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Wed, 07 Dec 2022 07:31:45 -0000 https://status.ppro.dev/incident/138462#b8f96a0dce041ba31ec2e5e2a255ae2bd8e2ef8b19bbdfb90f355052668b03cb smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Wed, 07 Dec 2022 06:34:38 -0000 https://status.ppro.dev/incident/138462#bbd44255218477889fa0532dd7bf6026268fa83214748cc96fab58c26e5ff382 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Wed, 07 Dec 2022 06:19:47 -0000 https://status.ppro.dev/incident/138462#23155b822adad374330cf33d467c2d272253217f18fcf3db8ec31cbe26ea9646 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Wed, 07 Dec 2022 06:15:13 -0000 https://status.ppro.dev/incident/138462#4eea952158c7d935914fdbe2d89c1ce5528930456d9d491567d788e34d0c1e9c fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Wed, 07 Dec 2022 06:00:52 -0000 https://status.ppro.dev/incident/138462#0c0f3a16480364cdfa6f0d88451c88f8f8af82a658c41046019739c74d2e7db8 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Wed, 07 Dec 2022 03:30:27 -0000 https://status.ppro.dev/incident/138462#c3efba4ff66f20e5d2925ecc52c752ade400d8b65ffb7ae96348a81ed64a0e81 fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Wed, 07 Dec 2022 02:15:53 -0000 https://status.ppro.dev/incident/138462#fdc1b0e26721b751d2ed282ba99d74b325b8645a0ae1586ff290fb2a68187ee6 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Wed, 07 Dec 2022 02:12:31 -0000 https://status.ppro.dev/incident/138462#ee9dd93854f26c452937229b9f7ac21c37dcae047b8da87ed5fb9082c702538f BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Wed, 07 Dec 2022 01:45:54 -0000 https://status.ppro.dev/incident/138462#b1858018e249f873ae8ec02e312ec1bc5ff4dc42785edbad8eee5f28ce1685c8 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Wed, 07 Dec 2022 00:27:14 -0000 https://status.ppro.dev/incident/138462#77d369abd3529b6bba5c23ebfacd0a358d04bd2593f8fe566a0d55f6e42aa0f4 fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Wed, 07 Dec 2022 00:24:37 -0000 https://status.ppro.dev/incident/138462#f6205a729551731e2f30a4ff35a7ce1779ecd27729ee34ad24b12b03cf4ceafa BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Tue, 06 Dec 2022 22:56:54 -0000 https://status.ppro.dev/incident/138462#c969360966e5cd2977d1aa7338577c80e0b5f6fa812a3e226f378b3dc412e51a smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Tue, 06 Dec 2022 22:49:40 -0000 https://status.ppro.dev/incident/138462#bb60ae6d14b49ce8af1490773b07df2dc205b82f2ca3713e60556200b664136c smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Tue, 06 Dec 2022 22:46:50 -0000 https://status.ppro.dev/incident/138462#352d1e66ae04461aad1a5cb8ca6b527fe6b14096bbbc2c7dcad061f492e06eaf ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Tue, 06 Dec 2022 22:28:03 -0000 https://status.ppro.dev/incident/138462#42a2ab467749b46d8664b00f5478fce12b9919e81d1254a747788ddc599e2524 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Tue, 06 Dec 2022 22:17:29 -0000 https://status.ppro.dev/incident/138462#741ef2021d3a6e99f6955a00d138371306f65a5a108334ef0ff79b9ebf366d98 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Tue, 06 Dec 2022 18:44:30 -0000 https://status.ppro.dev/incident/138462#343622523fc5a4f40b7ec12d772160073bf87015fff045af2ad855977dc7c23c BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Tue, 06 Dec 2022 18:37:29 -0000 https://status.ppro.dev/incident/138462#35ab00fb490c2db6b0560cf089c84146003d5b4d0e03c9fe51b2716c254a8013 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Tue, 06 Dec 2022 18:26:41 -0000 https://status.ppro.dev/incident/138462#64c419cd3f886b0eebbfd9dd8e17f979a9bdaa08c629c057112bfea5f88707ac smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Tue, 06 Dec 2022 18:18:15 -0000 https://status.ppro.dev/incident/138462#02d4f2e28715af19448e4d9dc0b697d8c45ef66a9b9e1c7391c1053cf274c000 fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Tue, 06 Dec 2022 17:03:59 -0000 https://status.ppro.dev/incident/138462#ee3849e2549e20301d9e01fc4f637d17d008adc82f33530c638ab4027bfe5f77 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Tue, 06 Dec 2022 16:45:51 -0000 https://status.ppro.dev/incident/138462#8a0c448926caf51a5015b7f081813ac5fe467e04999e201969e9561cec237bc4 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Tue, 06 Dec 2022 15:59:11 -0000 https://status.ppro.dev/incident/138462#878d6084ab3327cb1c5ab939ff88b2cf0deb8dbcf5add3a934abd561b9cb30ef smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Tue, 06 Dec 2022 14:38:11 -0000 https://status.ppro.dev/incident/138462#06bc65864ecf3731a06048ab028bbfe4e0a1289dde9e55b3a5983ea3df18b41e BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Tue, 06 Dec 2022 14:31:07 -0000 https://status.ppro.dev/incident/138462#8e36238b9a7e9b77225820f727106832627b67edd72b2ea2d3f9764ee5e1e06d BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Tue, 06 Dec 2022 13:26:57 -0000 https://status.ppro.dev/incident/138462#9e6ca323c574808c0d4fd077d77c0d5fea08997de09d6805d51d6bb83e49feed ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Tue, 06 Dec 2022 13:24:45 -0000 https://status.ppro.dev/incident/138462#5389449a04d08f505bbc4e18f9e5d535e5c4a3215fafcb9a0e2267466f1b8548 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Tue, 06 Dec 2022 13:17:36 -0000 https://status.ppro.dev/incident/138462#2f6b8158f055e4ac7a12b9c1f54de18c2812ada3914b190a2155390127155199 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Tue, 06 Dec 2022 13:14:48 -0000 https://status.ppro.dev/incident/138462#3e36aadb42a20aaff09ad69b8d2e03b00328169810f72c6b97c9ad9ee2e203ae smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Tue, 06 Dec 2022 13:06:46 -0000 https://status.ppro.dev/incident/138462#d5c2a1c66429c95f87e7a58ef6b8a96f4d6f4941528fc567af99d01ccb08d16b smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Tue, 06 Dec 2022 12:31:18 -0000 https://status.ppro.dev/incident/138462#4bd52b627f15a41bb865d745f3f1edc624bd75ebdcb9f84e87f256e250dedd09 fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Tue, 06 Dec 2022 12:22:57 -0000 https://status.ppro.dev/incident/138462#ec1c51431629d1ea2593e80d67eca94ed1d5b0ec9c861e4651d06f81d95744b5 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Tue, 06 Dec 2022 08:33:52 -0000 https://status.ppro.dev/incident/138462#3038d6a566b0377fd5d80e83426c72cb7062e527f17c0fde215c33c1b2597efc smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Tue, 06 Dec 2022 07:27:53 -0000 https://status.ppro.dev/incident/138462#f60f25d5e4d8fff5e836020a6741ce0b3ae75aef46b4790884ffa5a505137f8d ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Tue, 06 Dec 2022 06:56:21 -0000 https://status.ppro.dev/incident/138462#a6e05b1de033de804d03cef5dc8758c55baf230585d4354fe62dd5f5c3510232 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Tue, 06 Dec 2022 06:44:31 -0000 https://status.ppro.dev/incident/138462#32b89fdcbd27a69035fbbba485163e46b353657531f9cd62de8b976baabcb640 fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Tue, 06 Dec 2022 06:33:57 -0000 https://status.ppro.dev/incident/138462#3187a34b8e4b077eee8a2454cfa13a31c289903cc6b79eb4c375b11230c83f9b BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Tue, 06 Dec 2022 06:24:19 -0000 https://status.ppro.dev/incident/138462#99dfeaf33bfed3d8f7d81c1c1c3cfc1e1881ca6bf65f70f9dcf8dbe2cc62cc69 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Tue, 06 Dec 2022 06:05:59 -0000 https://status.ppro.dev/incident/138462#2b167fa8260ead879570f375de92d158bd0e8a3746f24d277439cf529e25b961 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Tue, 06 Dec 2022 05:48:54 -0000 https://status.ppro.dev/incident/138462#e8af32264f3513e8f50460f18441c25b2128bdfad06f1e156193efec28082977 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Tue, 06 Dec 2022 05:16:14 -0000 https://status.ppro.dev/incident/138462#da504bb12fa8af101d28611e4e49c4a58f86736313485468d74981726f0d65ac smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Tue, 06 Dec 2022 04:40:16 -0000 https://status.ppro.dev/incident/138462#e12260f550be8c9dd97c4002a16da154ac17b3aa00d16a30bbb4db1a393553d9 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Tue, 06 Dec 2022 03:06:07 -0000 https://status.ppro.dev/incident/138462#b1461214ecd53733450f0b50c920b722ca573881fb1565cd2f6a70493bafe792 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Tue, 06 Dec 2022 02:35:46 -0000 https://status.ppro.dev/incident/138462#5f7ca900dc1fd4d1c0d3a0b6299b9b966f0f2482a3d7bcd2ab0632b7a7ddfbaa fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Tue, 06 Dec 2022 01:09:22 -0000 https://status.ppro.dev/incident/138462#1cf66d6561dc2a807c89cade6877824d044b42a07eff877f35427b61172a8406 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Mon, 05 Dec 2022 23:18:17 -0000 https://status.ppro.dev/incident/138462#6ffda076a89cfd4ca8f7ed3cb498672ba3552ac0cc78c874ec0a409c83739a4c smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Mon, 05 Dec 2022 23:10:54 -0000 https://status.ppro.dev/incident/138462#30562e8c54d8ec36ba4b4645fb2c1ce0baccc36887f2824eff2d8957bf2650cc smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Mon, 05 Dec 2022 22:47:32 -0000 https://status.ppro.dev/incident/138462#52ca581f085694758ae9322f1f2bee02c8fc19f8d7a3b7ab8e7a2863e477b0dd fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Mon, 05 Dec 2022 22:39:28 -0000 https://status.ppro.dev/incident/138462#f31f0c5fda7e1b5a2ab8beb2b7a14f7f6936a46e51da8b0be481ab4b7ea19659 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Mon, 05 Dec 2022 19:07:09 -0000 https://status.ppro.dev/incident/138462#4d4953085d24d0a89b2053247e01e82f64dbfbd615b4efdd8b85455d903ec050 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Mon, 05 Dec 2022 18:47:59 -0000 https://status.ppro.dev/incident/138462#169036f675ab7a25b41c4150c34a27dc6bbf96c5a9f813d5158baf733f14a5fd smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Mon, 05 Dec 2022 18:40:58 -0000 https://status.ppro.dev/incident/138462#fed62f062b9de61e1155855f46000d070b8cc120b47a401ecbd4c6206fb02313 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Mon, 05 Dec 2022 18:18:50 -0000 https://status.ppro.dev/incident/138462#9024849f392efba0299da13b3c2588fcfa589a53e870d057966686dcab3e089e BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Mon, 05 Dec 2022 18:12:21 -0000 https://status.ppro.dev/incident/138462#eb3180bc59fa66829c4752d46c1610cd9d17f2496565d45b987f3ba00175eda2 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Mon, 05 Dec 2022 13:42:10 -0000 https://status.ppro.dev/incident/138462#fc8a65f7bafb37141e6df70d470541fe7f3a1bccc7bf46df426161016d64606d smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Mon, 05 Dec 2022 13:35:25 -0000 https://status.ppro.dev/incident/138462#7a5dbec8c6bf6a29689dbdb66b98e2c95dbbda3d9c5566534223cc9ce958aa92 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Mon, 05 Dec 2022 13:34:04 -0000 https://status.ppro.dev/incident/138462#6ee0ae5882670105f51397a8988078ad3801e5e7ba03ddea89bc2553f8f019c9 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Mon, 05 Dec 2022 12:32:13 -0000 https://status.ppro.dev/incident/138462#916dcb60b02a2de17e2a53e639f1339d02cfc1bfa055cf657acf756519c071c8 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Mon, 05 Dec 2022 12:24:26 -0000 https://status.ppro.dev/incident/138462#bcb4231ee44a0bdafcade1e410716450ad4c62b76029f77cecddef0bba9374bb smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Mon, 05 Dec 2022 11:45:08 -0000 https://status.ppro.dev/incident/138462#f5d66f896bb14cfbebc8a6b0d4d32699ac0c551850ea7b05e8b9e38e187c3e63 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Mon, 05 Dec 2022 11:27:54 -0000 https://status.ppro.dev/incident/138462#d3ca2b328b0b8683881a24b1905953fcfefeab0074163ec9328f515cc93ed2ae BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Mon, 05 Dec 2022 11:10:04 -0000 https://status.ppro.dev/incident/138462#f7fe279a1bda9f8985b30e0cea9f968477f5dea3a054b86e437d706f48516e66 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Mon, 05 Dec 2022 11:02:57 -0000 https://status.ppro.dev/incident/138462#f832fbf5223849936c0a037a792025b9d7f8b2607e88c5a22dad7da413172800 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Mon, 05 Dec 2022 10:24:25 -0000 https://status.ppro.dev/incident/138462#d62845562cb5d02e5f7a94e82e22a6e84daa3a78cd8089d31057ac7c054fd9f7 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Mon, 05 Dec 2022 06:57:06 -0000 https://status.ppro.dev/incident/138462#b9c62356083e7651008dc0523185dd2003f9ebf162edf5605e88ff22555be440 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Mon, 05 Dec 2022 05:39:57 -0000 https://status.ppro.dev/incident/138462#8a9ab622911b1eccde998a40e26a9c69eb6838490135a0a08043bfa46f0d012e BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Mon, 05 Dec 2022 05:39:30 -0000 https://status.ppro.dev/incident/138462#443df3977d1874b711a8b06b54ea71864b99ef7d8defbe71f726f90148cc01ee smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Mon, 05 Dec 2022 02:27:47 -0000 https://status.ppro.dev/incident/138462#99a11b2a938bbf695b850f044bb42d3d06d28ab8ef7c27dea3eafb500a4364c3 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Sun, 04 Dec 2022 23:37:02 -0000 https://status.ppro.dev/incident/138462#ff2e4068a1aef20e86b5c7c1dcabbf69eb78ff662804d06a8d3c48f3bfff3329 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Sun, 04 Dec 2022 23:29:02 -0000 https://status.ppro.dev/incident/138462#026450cceb180b182f365fa50d8425e9b219b1420f1e21ed2c028bbc2c8af653 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Sun, 04 Dec 2022 14:25:42 -0000 https://status.ppro.dev/incident/138462#0d08e9c38c7237451942931a584284d6cdced744b288af733d4b0f89f02c206c fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Sun, 04 Dec 2022 11:44:51 -0000 https://status.ppro.dev/incident/138462#3680944975de845d5e00b072fe558b46a83fe5a2154325b7ed0b7fa83154ac71 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Sun, 04 Dec 2022 11:27:45 -0000 https://status.ppro.dev/incident/138462#78456d8c5d007409110f58b4d5d3cfeb3b75984e739163a41b63af0dbdbddb9f BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Sun, 04 Dec 2022 10:34:51 -0000 https://status.ppro.dev/incident/138462#52b36842729b9d59aef61f63e8734d50e857dabc3b7e8670cb39ae0cebfa43e7 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Sun, 04 Dec 2022 10:17:16 -0000 https://status.ppro.dev/incident/138462#1af591a24f801747fcf2cc3dd562952df73dc2b8e0742729857c5b2ac7084895 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Sun, 04 Dec 2022 10:07:46 -0000 https://status.ppro.dev/incident/138462#1e41a77381716c649c8513079593c02a7f8ae047f519669f020f592a52dbc3e7 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Sun, 04 Dec 2022 07:07:03 -0000 https://status.ppro.dev/incident/138462#0c1fb7626c2080ec270a8c8a8343fb0f3ebc40afce874da6e81f986cbf410249 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Sun, 04 Dec 2022 04:46:25 -0000 https://status.ppro.dev/incident/138462#5a7c3eeca09a6efe6494ff8df3966fc13afbc770479930c58cde521ca698f6e0 fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Sun, 04 Dec 2022 04:35:05 -0000 https://status.ppro.dev/incident/138462#a7f16eae22ee25ca459a856706a9e0859312a2fbce7c5e4a3d33707bab7745cd BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Sun, 04 Dec 2022 02:49:49 -0000 https://status.ppro.dev/incident/138462#e27fe60f3090afb1dc4de067bc95ca0ddcad1e66990da3cc0d1ac5cd567504e7 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Sun, 04 Dec 2022 02:29:21 -0000 https://status.ppro.dev/incident/138462#c91d3274eb448c228e1b4ed28acbf9ad25a029504a20ae75aa1de306adfb32cc fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Sun, 04 Dec 2022 02:17:42 -0000 https://status.ppro.dev/incident/138462#f25e6ff24f3b34a7ef220983327fe965b0957d341d3e2db5feca1298d782645f BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Sat, 03 Dec 2022 20:53:06 -0000 https://status.ppro.dev/incident/138462#a43e809e0ed36d0603b200978155fdf1f263a04fad4b3afdecb07faf758a5825 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Sat, 03 Dec 2022 18:36:52 -0000 https://status.ppro.dev/incident/138462#61115e42b041dd546c0fbcb6129e49bf9378feab08882eb64283753f2952cce5 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Sat, 03 Dec 2022 18:31:31 -0000 https://status.ppro.dev/incident/138462#8fb427215b42abad3cecac85b38de8ce4d0df05b104c8bfa1cceae922a143845 fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Sat, 03 Dec 2022 18:19:53 -0000 https://status.ppro.dev/incident/138462#df528914b0d98e34c43aabdaebefa367cb416ed6876405e8d2c89ac67b708332 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Sat, 03 Dec 2022 16:21:00 -0000 https://status.ppro.dev/incident/138462#eb3d885b91136e9804d31884c36805ae20f18d173c6744d03391d8003b008be6 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Sat, 03 Dec 2022 15:59:48 -0000 https://status.ppro.dev/incident/138462#3d37c318cfe82d86b9eea55ca87fad5fe7029048d4e0fa22778da7e2ca839211 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Sat, 03 Dec 2022 14:17:00 -0000 https://status.ppro.dev/incident/138462#234d7b0ce976b4e46e83be5efccb0caca811ab5c93e3c35d4d84389b0fb75439 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Sat, 03 Dec 2022 14:07:50 -0000 https://status.ppro.dev/incident/138462#ca13ffae7281c84208ce2ef3818d0dfafa69e062658871dca563fbed0077a7d9 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Sat, 03 Dec 2022 10:39:42 -0000 https://status.ppro.dev/incident/138462#45733563817e7b882498994f251d8c056fe4f5fa2fd3b0d035f2209097f161a1 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Sat, 03 Dec 2022 10:25:24 -0000 https://status.ppro.dev/incident/138462#88b94482f6e517d67a69b972f25b7b61f9a0a211d898b91cbf0a481c4e20a88f fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Sat, 03 Dec 2022 10:20:04 -0000 https://status.ppro.dev/incident/138462#8e2f60c4267e22ce294c938d4af1304a0a7163799384f1dbd990c2f06b556de7 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Sat, 03 Dec 2022 08:27:01 -0000 https://status.ppro.dev/incident/138462#d329cfc59fa75e07a394b53009d3f8d348d8f13359caaa62206513799c2ab49d smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Sat, 03 Dec 2022 08:09:00 -0000 https://status.ppro.dev/incident/138462#7931dfd2001dff7f3738bfef92d6edd2db027c2fdeef5f40ee3cd169003a47f6 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Sat, 03 Dec 2022 07:41:20 -0000 https://status.ppro.dev/incident/138462#0f2adeb8a732b3f7620979fc0a99aa2cc02c0630c66b1881923293ea6ce039fe fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Sat, 03 Dec 2022 07:28:24 -0000 https://status.ppro.dev/incident/138462#9e04edcac4af7eb1dbc6098193c426cee5d4efef61b120c01e922927fd8bd429 fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Sat, 03 Dec 2022 06:27:25 -0000 https://status.ppro.dev/incident/138462#f82e95ac44c47a68bb0a7e73045792a9ff7e15360e9a6567e7b6c496f89f72ec BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Sat, 03 Dec 2022 06:07:49 -0000 https://status.ppro.dev/incident/138462#6fcb75de5c6b4dbdd1ff47e8a78db0c94a1750f87dad1d5cce97a3196b5ff343 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Sat, 03 Dec 2022 02:04:28 -0000 https://status.ppro.dev/incident/138462#e0dff2b286eae3ca726e43d00def1f75ff91f9d90e87351556ec477431e4988f BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Sat, 03 Dec 2022 02:00:58 -0000 https://status.ppro.dev/incident/138462#9fa4482baecf0e5936bfb21addfdc6917aabfdcaf71e0aac583e372ba955a763 fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Fri, 02 Dec 2022 23:17:23 -0000 https://status.ppro.dev/incident/138462#632a56ae2eed5d71ea94685f4dab386cdcf155b802e08b1f32a442da73dc4406 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Fri, 02 Dec 2022 22:49:30 -0000 https://status.ppro.dev/incident/138462#66aa00e06541d9c931e4479764f949293428f30b81ff6893a2f1e9f7df5be016 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Fri, 02 Dec 2022 20:59:33 -0000 https://status.ppro.dev/incident/138462#9d1e83ac0074f04a7c3be6368a2424d954dfd17d65ccb2a149faa65ca10d9fbd BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Fri, 02 Dec 2022 19:49:54 -0000 https://status.ppro.dev/incident/138462#5df88f786c89186c8bb77af283ef1341fb9a36578d234fa01453263e6c1f76e2 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Fri, 02 Dec 2022 18:51:37 -0000 https://status.ppro.dev/incident/138462#365fc145208db0d56203bf2f128a4cd25177bf2f704cb2659d978fa279cf933b smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Fri, 02 Dec 2022 18:44:12 -0000 https://status.ppro.dev/incident/138462#ab52eca5fce16562d714fd59e77cae2ac016a1b9a76be29a447ab26ff3fc239d smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Fri, 02 Dec 2022 18:07:22 -0000 https://status.ppro.dev/incident/138462#c1b8a9666f35e9ff7412b624a500700e8972e1911b8b88d42650132b5295c4f5 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Fri, 02 Dec 2022 17:40:43 -0000 https://status.ppro.dev/incident/138462#21156672c1f6a852368cdaa7c8bfc3ea607fb2bb6831e407a2e2ebba0d5cf8f2 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Fri, 02 Dec 2022 14:51:14 -0000 https://status.ppro.dev/incident/138462#3d8f739654769be330e5317bb6ee58b6a750d23e07fd8a08bc04fe8f4ebeab7f smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Fri, 02 Dec 2022 13:16:47 -0000 https://status.ppro.dev/incident/138462#7d16bc0fe59c4ac4f76876a818b617785e52f0a916de0a81d3260999186b6cfe ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Fri, 02 Dec 2022 12:37:55 -0000 https://status.ppro.dev/incident/138462#576a1287dcc30b0f0902d8166963dc0ed8a465689876da5d47bef58f0e04bc0c BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Fri, 02 Dec 2022 12:32:53 -0000 https://status.ppro.dev/incident/138462#8f31e8c29e3952b4e07a5311cfe83972706a98b03ff90c4c6854ed02c62529b8 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Fri, 02 Dec 2022 12:30:53 -0000 https://status.ppro.dev/incident/138462#c18a0b20616dae77ad7cc9e287009a636acb284eb12c0dd01c830742d9b472f0 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Fri, 02 Dec 2022 10:27:53 -0000 https://status.ppro.dev/incident/138462#d8587b9719b8266af6e70779be7371733a4c84c100d2baf7f44ecadd0cd3f16e BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Fri, 02 Dec 2022 10:10:44 -0000 https://status.ppro.dev/incident/138462#6f8ff74135b1fdee4f7a1594a5ea274ceccac93d999be60ae23cc6e2e55dea8c BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Fri, 02 Dec 2022 06:41:24 -0000 https://status.ppro.dev/incident/138462#a4ccac525352e46ba62ea6081e58f21fc618dfdcbd9939687327a623c0fd76eb BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Fri, 02 Dec 2022 06:35:45 -0000 https://status.ppro.dev/incident/138462#12b05a4130dbea8e78b53c8af3ecf3791c8548a426cb7fd0eaa5a25837970f67 BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Fri, 02 Dec 2022 06:32:49 -0000 https://status.ppro.dev/incident/138462#61c0aa6ed2ae8db89aed0e775fea83b4ddb379cd532bc4c39832c9e72d420338 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Fri, 02 Dec 2022 02:58:30 -0000 https://status.ppro.dev/incident/138462#df4f4f7c2d26db3a000caefca410a8f5e0fc136d5af474e999e800b9493729d3 fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Thu, 01 Dec 2022 22:54:11 -0000 https://status.ppro.dev/incident/138462#bff9374c2698527cb8e82cda8f7a56e109fa16d99bde1f8144e3597e172e21f2 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Thu, 01 Dec 2022 22:46:54 -0000 https://status.ppro.dev/incident/138462#3b9ff0f8b770b4c05099964870f00b8dd3260bc4602874d3626b13b9dd5238b1 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Thu, 01 Dec 2022 22:33:50 -0000 https://status.ppro.dev/incident/138462#1dd93fcdb0c4c1cd89df0a2a6a90dac6c5a7bc54c262c2fcf87431ee566c0f29 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Thu, 01 Dec 2022 22:24:16 -0000 https://status.ppro.dev/incident/138462#2505c390e9c372f733dde007626c7a058c59cfa8b5bdba98c73a562e90bad963 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Thu, 01 Dec 2022 22:20:37 -0000 https://status.ppro.dev/incident/138462#04028f0cd2f07286df60eebecd78a018096b3f05b032163aa1ad5beb6b225b07 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Thu, 01 Dec 2022 18:11:34 -0000 https://status.ppro.dev/incident/138462#5d2267d6a5c9828a7c6a63d8439d1a8340dbac28b030dd5d94b2534653713ed7 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Thu, 01 Dec 2022 18:05:41 -0000 https://status.ppro.dev/incident/138462#4dfefee89b036779856e6fd8f93906270487938e2d74e839c81c8f50cd5f4479 BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Thu, 01 Dec 2022 17:07:28 -0000 https://status.ppro.dev/incident/138462#e0ad8c6ba0b7fea668eac5571cfe39b49aa6efdd3399a38ea03f1dbbed85798a ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Thu, 01 Dec 2022 16:03:01 -0000 https://status.ppro.dev/incident/138462#d236b1d20163c5e59774cd78e31eb0ae41f35935dda0ce94cb4be88edfc42523 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Thu, 01 Dec 2022 15:54:28 -0000 https://status.ppro.dev/incident/138462#cc337ef4a327dea5852a52b463c6ae1b41df8534f952e2609e9451887c8fc6ed BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Thu, 01 Dec 2022 14:38:33 -0000 https://status.ppro.dev/incident/138462#d88d53671e1e8af4a0d89b60ed1c33b76b00bc808ee90502e7c35f46a5036abd ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Thu, 01 Dec 2022 10:20:19 -0000 https://status.ppro.dev/incident/138462#19e444eb74e1dd5e6400659f88d88ae978ba30bd363ba01a7a052e5086190a82 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Thu, 01 Dec 2022 10:14:36 -0000 https://status.ppro.dev/incident/138462#df31e01b635278ba3e4ba63858d4a7665f5e5d0db019a15c2a347e8605540e83 BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Thu, 01 Dec 2022 09:56:55 -0000 https://status.ppro.dev/incident/138462#3effed3e9a2076cd8d39a85fe079f45d8c1e47106e4289c01c99bac8d10cea2a BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Thu, 01 Dec 2022 09:48:04 -0000 https://status.ppro.dev/incident/138462#b5a2435bd4a2af82e98226004d47dca0392dcd39bb8d568b7bef65df01a05a60 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Thu, 01 Dec 2022 07:22:30 -0000 https://status.ppro.dev/incident/138462#1856bcf8ace9c04a30a0e40d04cfd6568fb69c037686fd1c61420713b7e7ecf2 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Thu, 01 Dec 2022 06:55:21 -0000 https://status.ppro.dev/incident/138462#b82116ec0ad9bca7850deb31432b88c17967968648cf5a11ffb70c9388338bf5 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Thu, 01 Dec 2022 06:02:53 -0000 https://status.ppro.dev/incident/138462#eb222958cfb097dbd3ff56da19024e9d00351b22c2d57c14f6cb95bbab1e3c25 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Thu, 01 Dec 2022 02:09:52 -0000 https://status.ppro.dev/incident/138462#ade294533a805962fcf369d378f6d06c77b9b4a9100c60f574b96a70d7e61f5b BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Wed, 30 Nov 2022 23:54:57 -0000 https://status.ppro.dev/incident/138462#3d2ac3e3d6bb8d1fc00dfdbae7fae77ddbd691b88b914b6e0116f35451696ddb smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Wed, 30 Nov 2022 23:54:10 -0000 https://status.ppro.dev/incident/138462#2fb37f9e2551e08a55e8cde3c8f3aaac449d2b8b41396a4f7210a9aaa99d2435 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Wed, 30 Nov 2022 23:42:21 -0000 https://status.ppro.dev/incident/138462#6012dbc63208d329de5f13dd773c2b16d3844417a49afdb1fd29411e6c01b1bd ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Wed, 30 Nov 2022 23:30:14 -0000 https://status.ppro.dev/incident/138462#21a7afeed1e5e1ebea55b5cfa661487a34ab63b2261a06e8eecb4431e89782ff ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Wed, 30 Nov 2022 23:21:17 -0000 https://status.ppro.dev/incident/138462#3a4968d86ebd9c81f46cc6378a7b616612891a04dd64dc21e3893aafea94861e ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Wed, 30 Nov 2022 22:48:28 -0000 https://status.ppro.dev/incident/138462#2c3249675d925a3c36a7ba579d415a7f65b1088219c820b214df8a9eae2da0bd ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Wed, 30 Nov 2022 22:27:28 -0000 https://status.ppro.dev/incident/138462#55ce2af3a9fa58b63cb371a18fb4c18055acbe02b57b9941d679504b198d6f40 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Wed, 30 Nov 2022 21:52:10 -0000 https://status.ppro.dev/incident/138462#342c75e475eed8d0fde8fad2db374b8dd08fcbbc08bedec5e5a1154594bbcf59 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Wed, 30 Nov 2022 21:24:10 -0000 https://status.ppro.dev/incident/138462#564fd71da6f50351e6d30659ed15001688574a16a54258aedeeaf43581faa71c ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Wed, 30 Nov 2022 18:39:48 -0000 https://status.ppro.dev/incident/138462#585bfd4f8f67833b5ca27530651c040533f8014e40175bdb8735b5410b139107 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Wed, 30 Nov 2022 18:07:40 -0000 https://status.ppro.dev/incident/138462#b9beb212d6abf62191d2e16d14c9250f30e22c2ab8f672dc13433d7acc9884f0 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Wed, 30 Nov 2022 17:26:36 -0000 https://status.ppro.dev/incident/138462#b29be7e3603c1ed6723f340864f49ac077a6d907b0373fc59277d44c7bad5d26 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Wed, 30 Nov 2022 17:04:26 -0000 https://status.ppro.dev/incident/138462#3c354bf844dd57fded6b95dae3df06a0bde0cfd61e13d44daea8ece2c2929be8 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Wed, 30 Nov 2022 16:36:47 -0000 https://status.ppro.dev/incident/138462#c29671916eaf7659ed395c9fe5800f52fe494f5e6773b69d9acd9f5373bd990f ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Wed, 30 Nov 2022 14:33:39 -0000 https://status.ppro.dev/incident/138462#5a306aff9204c25bedae44cc95a577e02fd79225e98ee2fb6ac092c9ff06081a BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Wed, 30 Nov 2022 14:22:10 -0000 https://status.ppro.dev/incident/138462#4ed15e1b827d2b62a41eaa036faa3cc7b27669a38923f2cc07fa1d610cd1904b BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Wed, 30 Nov 2022 12:22:34 -0000 https://status.ppro.dev/incident/138462#8003f48ad1a87dec0ba05588ddca0377c03b1d1faf7965c7fdff3a7154dab1ea ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Wed, 30 Nov 2022 10:47:58 -0000 https://status.ppro.dev/incident/138462#84624158d3c61510638ba30f51c84916d61f3a79082790e7d37f5afbc15bbcbc BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Wed, 30 Nov 2022 10:31:02 -0000 https://status.ppro.dev/incident/138462#54b3fd2ea0de2b774f02dc547f6dd503c7bfac961f463a5eb9129be0fe46adc7 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Wed, 30 Nov 2022 10:23:00 -0000 https://status.ppro.dev/incident/138462#88e916502fd19f43feafbbcb384a151f03f4ec03cc28e3134ea7639dc8787a67 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Wed, 30 Nov 2022 10:16:01 -0000 https://status.ppro.dev/incident/138462#06918752bb63f34852b2a3458c5355a512d25deb0ba6022ef31a5aee3f421503 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Wed, 30 Nov 2022 07:28:55 -0000 https://status.ppro.dev/incident/138462#3d31dc134702d799f59f1bb08c48ee9267ee45969d37dc5d4c69e48e7885af44 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Wed, 30 Nov 2022 06:07:40 -0000 https://status.ppro.dev/incident/138462#8e9ae38407162317e9b20a1588a2d9e6f5dca1b64a95c4e9da15991d040cdfdc BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Wed, 30 Nov 2022 05:59:44 -0000 https://status.ppro.dev/incident/138462#573dfa1c5b3ca54b5dbe135a21a60d68dc939e68618b07e5fc5893285a2f7f6b smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Wed, 30 Nov 2022 05:47:42 -0000 https://status.ppro.dev/incident/138462#2d61217c3251328a6d23115f2fd89a4030df623ca38b6f4ff29286bfb173001b smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Wed, 30 Nov 2022 01:04:54 -0000 https://status.ppro.dev/incident/138462#18653f4a873d0cf61ed27291d8d12e0942eb61f822928b0530fc40d40606e895 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Wed, 30 Nov 2022 00:27:52 -0000 https://status.ppro.dev/incident/138462#c317479e2642758ac87a4627b4dd530feb0cd39d54355b33f72a413631fc4985 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Wed, 30 Nov 2022 00:24:20 -0000 https://status.ppro.dev/incident/138462#c5190d9026d40ff9416cc56350e4a9352dc106705a05a21c846c0608f99abdfb fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Tue, 29 Nov 2022 22:34:00 -0000 https://status.ppro.dev/incident/138462#3639183cb262f2b2486704e8b84f602c7228a2a88632512aeb5de6c047833526 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Tue, 29 Nov 2022 22:22:31 -0000 https://status.ppro.dev/incident/138462#5bc3a6e5467e1baca2921b45f58de3b6fb12a7a286be8fa73e7b138d90a18654 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Tue, 29 Nov 2022 20:24:42 -0000 https://status.ppro.dev/incident/138462#8ea8f7e7daaaa5d5a706b24a41428a769cd8208c6c4f3c614fb39d5a808a87c3 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Tue, 29 Nov 2022 20:12:37 -0000 https://status.ppro.dev/incident/138462#c79985b40071cbc4eb89c470f17f3164fa403cadbc198f3ba0aa86e6fae0f6b5 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Tue, 29 Nov 2022 19:35:27 -0000 https://status.ppro.dev/incident/138462#b23827a5cff8399a7439505c057a7be73fb1c41c1700bf931d439521a29c9c3c BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Tue, 29 Nov 2022 18:27:10 -0000 https://status.ppro.dev/incident/138462#add2b631f07b34d82f914a764745f9ecc2393de65415522dc7e45da20c6b2884 fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Tue, 29 Nov 2022 18:24:42 -0000 https://status.ppro.dev/incident/138462#8592b2fa3c371650c062d43f4cff603104ac540801a47d07d10e38c021e49451 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Tue, 29 Nov 2022 17:16:10 -0000 https://status.ppro.dev/incident/138462#9d2ff6207eb646bf52e97e6e1ca6fe2caf866bd23475c1643a62ad0861bdbbf2 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Tue, 29 Nov 2022 16:30:47 -0000 https://status.ppro.dev/incident/138462#71630c8cda33a81c032a57e37e9509008b53cc50782625eff1485218b500fb04 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Tue, 29 Nov 2022 15:22:06 -0000 https://status.ppro.dev/incident/138462#e4b0b63a6586aa190be8faf2fcb230cc134598ae50e61869150e02d502fa350a smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Tue, 29 Nov 2022 15:02:50 -0000 https://status.ppro.dev/incident/138462#593746705b239c076a7467d280e4a1dada75c01374c57b586cfa80652fb93d43 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Tue, 29 Nov 2022 14:24:50 -0000 https://status.ppro.dev/incident/138462#2bff83c84dde39d7a6010640e9f6ed24d8e7909afc6d366cf4f8aa33790cbfd1 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Tue, 29 Nov 2022 13:37:17 -0000 https://status.ppro.dev/incident/138462#65c88658a828dabd7293ea0ea97d90ec15ee98f9b4bbcc62096bf430851c089d ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Tue, 29 Nov 2022 12:32:02 -0000 https://status.ppro.dev/incident/138462#7d857985d468ccc15c053e129b2e13fedb69dee6df62cfe66e7eac9a81ae25be BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Tue, 29 Nov 2022 12:19:47 -0000 https://status.ppro.dev/incident/138462#228c13bcde63c21b9fef721f704e811b6050345da731fa9229b956e8bbb7e74d BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Tue, 29 Nov 2022 08:14:35 -0000 https://status.ppro.dev/incident/138462#81477413ec4b8d40fd5451f5b69b0bb108d837d645a0de595305f92a5234add5 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Tue, 29 Nov 2022 07:27:27 -0000 https://status.ppro.dev/incident/138462#3158a3bf950fba169fa804c53db4cf57c722f45b5176a9120c1ac12a3348e854 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Tue, 29 Nov 2022 07:11:50 -0000 https://status.ppro.dev/incident/138462#6351a8a6e26e8f2e040d9e48d234485c7bf2b4a175afb9be07bda890b44abc39 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Tue, 29 Nov 2022 07:04:47 -0000 https://status.ppro.dev/incident/138462#5aa2365bb189cf49bdbdac8e98bdbce0169074e5882100787bd77e2798c0d76a BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Tue, 29 Nov 2022 06:56:50 -0000 https://status.ppro.dev/incident/138462#f325c763b5e28fae5fabbd6b5f3c474c869cd21892d17753531c63974c5607b0 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Tue, 29 Nov 2022 06:22:17 -0000 https://status.ppro.dev/incident/138462#abd876c7bd66b95d371b71723048109288012a0461882922cca59e191eb5b136 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Tue, 29 Nov 2022 05:34:15 -0000 https://status.ppro.dev/incident/138462#86a0db11f59deee7ad0ac834a4a970eb3fd7f70dee63eaf6d38602882b87223d ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Tue, 29 Nov 2022 03:14:16 -0000 https://status.ppro.dev/incident/138462#0d313d80112760f8a6c556ca8f46a5cf1c60ccf4f0a0ac855f37e6408d555917 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Tue, 29 Nov 2022 02:23:33 -0000 https://status.ppro.dev/incident/138462#8d930dfeb4537712bf49a929a844b2e868badfac90ac7861ee2995bbb27a7d83 fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Tue, 29 Nov 2022 01:15:26 -0000 https://status.ppro.dev/incident/138462#a37ae6f1f7c352cf2ea04dbd9c8d9384c13b1ee16d4d35b8d76e8163404a8314 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Tue, 29 Nov 2022 00:26:33 -0000 https://status.ppro.dev/incident/138462#44f388318ca3c9d9f2fdbeabe9fceb175a870adaf64ea521d17f8fc0ecbe78ef fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 22:06:04 -0000 https://status.ppro.dev/incident/138462#076f7ce7db8aadba70f299627e200a5463773491bc14df91eeefbae33eff69ab smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 21:30:16 -0000 https://status.ppro.dev/incident/138462#50c67fb680ad1f383d486737117b2f367e3137d80c096bea58a849ff321a1f4e ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 20:54:19 -0000 https://status.ppro.dev/incident/138462#c018a77d4a2fa463f4075868e8fc3dfc6fa1b76b665b726fa05cebf1229cbd31 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 19:09:05 -0000 https://status.ppro.dev/incident/138462#848e6eab0b8c74485a81a056c2e5e8d7af9c778cbd8de8efd3e91568a370f21b smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 19:07:04 -0000 https://status.ppro.dev/incident/138462#de6a4ae42bd7e4b693edb1946117d66ede1b51295dcdd65ca9b0656c0f7842f0 ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 18:49:38 -0000 https://status.ppro.dev/incident/138462#9c3bcb176fb3d149eefc442a22b82a71138622a5bd1f7ba8613499fc083b57aa BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 18:24:35 -0000 https://status.ppro.dev/incident/138462#97a3900723cfeb0f94256510bc66ffa04f3e0114795444a42ac84de96307161b smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 16:35:36 -0000 https://status.ppro.dev/incident/138462#274acb826473ed37bef3be22c5453953886bd0276e8b7d24e8f74f1746543787 ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 15:20:14 -0000 https://status.ppro.dev/incident/138462#9c187952dd55a4f4d65b212ff48559a0263f32379209f4ed4c2705987aba6626 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 15:03:20 -0000 https://status.ppro.dev/incident/138462#7c5217109b5cd586895901003426a36e27b8156065f5f7a7df0d0ed67244c315 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 14:58:30 -0000 https://status.ppro.dev/incident/138462#563b3398f961bb724459df1b623558cf45ac72846bf55bd9d545e994d7c27220 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 14:50:31 -0000 https://status.ppro.dev/incident/138462#a82f9ee5f99f21b927507cdf4dddf399632e14a4846b9f8465b74f8ceb122060 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 14:43:19 -0000 https://status.ppro.dev/incident/138462#e1e8bc91522dfa72c241529691c09aaaac69a454dcbe01835af8e1d330c64445 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 14:30:15 -0000 https://status.ppro.dev/incident/138462#6af10a7d7779240908a3e05c9a408876c6d3a5d6bb668b6964a7b2a8f5d95d2e BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 14:29:48 -0000 https://status.ppro.dev/incident/138462#f6ff92c1ed5a7a2641c8e3c4dd18a3d6722bc01ccbba23bcec33c520ca271474 BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 14:01:47 -0000 https://status.ppro.dev/incident/138462#db81cb7188feb084e872e212a9e26ca6e1804d334b3a8d97f875e935c5b3695e BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 13:54:46 -0000 https://status.ppro.dev/incident/138462#c590997f1f90d1d5af30e0d1e5af3f5d7078ee00e518c86e9e1b1d6c93ec0a55 BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 13:27:12 -0000 https://status.ppro.dev/incident/138462#9ac8b54588b39528265a413bb81060590534b1f0e657a008298e66cc0389783d BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 13:18:11 -0000 https://status.ppro.dev/incident/138462#8dc28e24cc15663b7d2ad1f5907dd4d2adf6b1a4a32361fa9ba3fa23fc936fe4 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 12:34:34 -0000 https://status.ppro.dev/incident/138462#5316f156adc1ba4ab76828ec32b9b01a2a593fff2c5ffd32453b65a6065a046e smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 11:46:44 -0000 https://status.ppro.dev/incident/138462#5bb4c1c5bb2a972cd3ffe157fcb292ff28c4a52372a5ebbd673a9ad318ab7a6c ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 10:54:42 -0000 https://status.ppro.dev/incident/138462#b3c72ba121c1c4e9a0c710023cfcbc240169ac139603bd75fba29c03ad510e83 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 10:53:52 -0000 https://status.ppro.dev/incident/138462#8f554c78779b5bdc1998858ee8f080c78b2f728a1bdf51d43861522d207a10d5 BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 10:41:13 -0000 https://status.ppro.dev/incident/138462#20c482b452cd213196b2e32aa9e31589ac932331f61500d400c9f23e382cca8b BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 10:33:54 -0000 https://status.ppro.dev/incident/138462#5d0ba3617a70b60d3cb05bdf5e9d572d9b6dd304679cb41e02f5daa43b3f85b7 BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 09:21:13 -0000 https://status.ppro.dev/incident/138462#bd68aee477b3a7844a55d4808814572bd746f243fb73edbacb25928db30e0055 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 09:13:52 -0000 https://status.ppro.dev/incident/138462#04187eef3d1eb1b03e1ceb83d31c510897883e19bc0bd510ca4da4594ab9360b BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 08:21:24 -0000 https://status.ppro.dev/incident/138462#4d02059d0bb2f04d9cf3e3554c3a320ee5c373dfdda69a77e1ae99cd24dc3dd9 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 08:07:33 -0000 https://status.ppro.dev/incident/138462#7b50431ad4fa235fb584c73e745c12158a0bd2aa90a8d05aa1e0e5887fbcfd45 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 07:04:46 -0000 https://status.ppro.dev/incident/138462#f8c5ee6d70d663ea53389d7b7cd4672961b1a9994ad5c39073de99806d421545 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 06:41:50 -0000 https://status.ppro.dev/incident/138462#b36187db5444123c20102eb2c386945d1c7c56615c95befbb714c45ea3ea5852 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 06:24:57 -0000 https://status.ppro.dev/incident/138462#014b3351199cb20fb9130f9c2c260b96bd6eca5a6191bdf7724e414464613b2f ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 06:24:31 -0000 https://status.ppro.dev/incident/138462#36e8343808983a14de75038a8eb67eeb93b6d636e0d8675c42a2d0a792de5a9b smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 06:01:42 -0000 https://status.ppro.dev/incident/138462#fc5b1ce7fc4f8075114b1bc3881266104aded6e537d3fc68be6d80bf94166b6d ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 05:52:22 -0000 https://status.ppro.dev/incident/138462#48073563dadf4607114b86ec47ac938f258afa43919323a8d5632f8da35a01f2 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 04:26:42 -0000 https://status.ppro.dev/incident/138462#cc1186692e2f756339050754091e4ca6dea6bdfbd534874fd285f20775dbb881 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 00:09:31 -0000 https://status.ppro.dev/incident/138462#d8abcf568b25779409948adcd8a8eda15de29842107fc40544e7c0e57026a07f BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Mon, 28 Nov 2022 00:08:50 -0000 https://status.ppro.dev/incident/138462#77747df950939102f5be34c8c224e27f296743de4ad8cd3dd7b429fc2c4298b2 BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Sun, 27 Nov 2022 22:39:49 -0000 https://status.ppro.dev/incident/138462#50cfaac5b6448d2e609aa5a9f4e1f78f45dee6b40104fef52b37a79ea127c85e ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Sun, 27 Nov 2022 22:38:59 -0000 https://status.ppro.dev/incident/138462#2f30c1202b472899c520a6ebb6b95fa42f40c1e5f0d244975c3f64311fc8f855 fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Sun, 27 Nov 2022 22:21:09 -0000 https://status.ppro.dev/incident/138462#bd30dcb7e041514472b4a11a4517175d43dc1262f543ffb71ceee7ee26d12c9d BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Sun, 27 Nov 2022 20:49:36 -0000 https://status.ppro.dev/incident/138462#8fde8304ad0006909d770a4ccec0c54a111f223ba0ff243e5f27a6720009228a smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Sun, 27 Nov 2022 19:31:48 -0000 https://status.ppro.dev/incident/138462#d3b436f9c4b0ca5d55d3c32ccf9972325aa22b30906400111a42576448840d1f ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Sun, 27 Nov 2022 18:17:13 -0000 https://status.ppro.dev/incident/138462#3b6a3dbcd8667fe8d156e7ea903b6d7ba2b45295585a847224540afdac2e292a BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Sun, 27 Nov 2022 16:42:37 -0000 https://status.ppro.dev/incident/138462#c472990a684e0ff9800a6c65e004c400fc9ae9d84657f39da0c23e90b8f0befe ppro: ovm myst server recovered. https://status.ppro.dev/incident/138462 Sun, 27 Nov 2022 15:56:24 -0000 https://status.ppro.dev/incident/138462#cfda6e4feb6e54e93a4bd6966d1ee46966bbc0714d056d48b3d90477bce6ed3f smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Sun, 27 Nov 2022 15:49:25 -0000 https://status.ppro.dev/incident/138462#a3c34600ee7d8b0c025cbc6498cfcb488c506eeff2a51ad7aba83cccdc418044 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Sun, 27 Nov 2022 14:19:22 -0000 https://status.ppro.dev/incident/138462#5bd001f60237451ab7e71ee07e9fafb6e492cfdc67538d69e6c3481cc5291ccc BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Sun, 27 Nov 2022 14:13:44 -0000 https://status.ppro.dev/incident/138462#68ee23550cea0839ccdb87ea9a095afae67a10da73bf6c460a4e0fb4946e525f BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Sun, 27 Nov 2022 13:21:26 -0000 https://status.ppro.dev/incident/138462#900443f3c11125c3ae1f7879b786019250d418d3105bbabc0c1aef1c582be82b smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Sun, 27 Nov 2022 12:20:51 -0000 https://status.ppro.dev/incident/138462#5670b279239e56854f97cff23e3c85970fa0c9b123da477f8d4e6d292356dbd7 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Sun, 27 Nov 2022 12:12:13 -0000 https://status.ppro.dev/incident/138462#3092837b7c707a0967d21068ac966cb6c6e5b9991d09c176b279058eb4d2632b BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Sun, 27 Nov 2022 11:14:20 -0000 https://status.ppro.dev/incident/138462#e4de92fc2499fe3d53484db7bdab6c3d7b81e02b0bcfbb68a72fbadda3087c40 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Sun, 27 Nov 2022 10:54:18 -0000 https://status.ppro.dev/incident/138462#f5fcf8431d9d93b08d36a3a8c33db0dfa4d340c2fc777ba02d119c5663ca4f6f smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Sun, 27 Nov 2022 10:46:28 -0000 https://status.ppro.dev/incident/138462#c8bc666003ad81b1050923ed5130947e5c72d57dab644f28e69b8f5ca71c345b ppro: ovm myst server went down. https://status.ppro.dev/incident/138462 Sun, 27 Nov 2022 10:33:38 -0000 https://status.ppro.dev/incident/138462#03792a527375f00c95c0626c7068cdaf67bf8035bf923ba4574b7886c0d890f8 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Sun, 27 Nov 2022 10:12:09 -0000 https://status.ppro.dev/incident/138462#235da8c8d54bce719c26fcadddb2c0ef3f5c080897d4304bf02c4237711a1b87 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Sun, 27 Nov 2022 07:36:20 -0000 https://status.ppro.dev/incident/138462#875c30ea70e315111cd21de146ed8e482c955076c1b36d8d62ea88f302f01923 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Sun, 27 Nov 2022 06:53:54 -0000 https://status.ppro.dev/incident/138462#50b4ec64f060af1b0a623913daf65c32a9c26d3d93203199e6167a47682d35c5 Synology and fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Sun, 27 Nov 2022 06:49:26 -0000 https://status.ppro.dev/incident/138462#aa41dc42a00929a7bbec677f3b202d9081f549d82fce60ad76b3c6f28c463587 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Sun, 27 Nov 2022 06:48:38 -0000 https://status.ppro.dev/incident/138462#d13f74a4108e47ef1d93ecf9fd07d359eb1d5ee8e06b9d042793b31c190899a1 BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Sun, 27 Nov 2022 06:30:49 -0000 https://status.ppro.dev/incident/138462#510f3e67ea4bc5732b9ef7e812d7f35f33c8190846eb9db75c95d9496018926c BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Sun, 27 Nov 2022 04:30:39 -0000 https://status.ppro.dev/incident/138462#6fc7df7daa6f45cc29e250b1fb724e75f91991a88dd8eff74d570190368bf6b3 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Sun, 27 Nov 2022 04:24:08 -0000 https://status.ppro.dev/incident/138462#cac69001cae6cbce57e3f98e2abba5545cd211863cbb8b488f708a2d2cbf9bbd fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Sun, 27 Nov 2022 03:03:45 -0000 https://status.ppro.dev/incident/138462#bf07e84dd9eec23949dae4a8eff88cd7f9f47f28ea3830589d2bb6b040fcdb2d fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Sun, 27 Nov 2022 02:22:07 -0000 https://status.ppro.dev/incident/138462#4b789969810d0c8e65b146d42be9896abd71246ccaf4de807516ffd2d1c6027b BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Sun, 27 Nov 2022 02:09:25 -0000 https://status.ppro.dev/incident/138462#1c1c8471f8c31f051cada019ec7340e86de0adf6f9b9e49a1116e42b015fb619 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Sun, 27 Nov 2022 00:24:29 -0000 https://status.ppro.dev/incident/138462#dda4168db98d9958e12107c5a95165df2e61d9f5ffbc37b295a673bb4e9e9de9 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Sun, 27 Nov 2022 00:23:46 -0000 https://status.ppro.dev/incident/138462#0a74e089dada89b6a87ebfb0c2002990fc0b4af5f367c14de468801ccf672ad1 BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Sun, 27 Nov 2022 00:20:55 -0000 https://status.ppro.dev/incident/138462#9bc0af53e0244bd1da6bcafb9f90c37c1e1708aa715b2dc7745eeb72d4c73567 BrovaPh2 ups status recovered. https://status.ppro.dev/incident/138462 Sun, 27 Nov 2022 00:06:28 -0000 https://status.ppro.dev/incident/138462#88ce330df85ece1b17b542a76b5c824794af38a45e7b534165b0e2f4b26d83ca smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Sat, 26 Nov 2022 22:24:19 -0000 https://status.ppro.dev/incident/138462#d57d7671013f492c4f3bdba150d1743276dc2988c7fcfcb435e3f82463b84d9f smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Sat, 26 Nov 2022 22:07:11 -0000 https://status.ppro.dev/incident/138462#9ac03b7edf1969dda7abf271733c8b7340be7481d2623fea12d26cd46cad0474 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Sat, 26 Nov 2022 20:46:21 -0000 https://status.ppro.dev/incident/138462#f39a8487a4820f870cb9e615f0f3efe96d19b9425cd4c82019d0c006a3026a41 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Sat, 26 Nov 2022 20:39:18 -0000 https://status.ppro.dev/incident/138462#5e159094f8662980f5a6421ab4ab18400465f8ec098d9b2b9536a5d04a65258c smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Sat, 26 Nov 2022 20:19:30 -0000 https://status.ppro.dev/incident/138462#6157dc02f6ce2815cf35dc8bef9f20d932de39a2a60df5402735e64fb131ba19 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Sat, 26 Nov 2022 20:11:21 -0000 https://status.ppro.dev/incident/138462#463781d93e3b75173e0fee6cfe52a1483dc3d3ad7ae610883286673dceeafa12 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Sat, 26 Nov 2022 16:32:33 -0000 https://status.ppro.dev/incident/138462#7240c1eef298e411cf6e5f38109c7f2d588b0fa4ed65b0ff98dbd73c63f06d99 fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Sat, 26 Nov 2022 16:16:45 -0000 https://status.ppro.dev/incident/138462#d26f415e2d370ee8680ab6e80f0f9d6198fda08a4cb48be652dc690e3109abb8 BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Sat, 26 Nov 2022 15:18:57 -0000 https://status.ppro.dev/incident/138462#61a3e9b029043670c7f4ea221363fec0d1e2c54675e8ba7cd62ed21137dcb525 BrovaPh ups status recovered. https://status.ppro.dev/incident/138462 Sat, 26 Nov 2022 14:46:42 -0000 https://status.ppro.dev/incident/138462#51ece1df87ad13c5324b13f8b042f5692bfdebd9050636271e0bf0297f7f2a8d BrovaPh ups status went down. https://status.ppro.dev/incident/138462 Sat, 26 Nov 2022 14:03:14 -0000 https://status.ppro.dev/incident/138462#8212bc1fb3099553f8c83fc46284c57895de1c257ba975a989a58d2bd4ad4ec5 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Sat, 26 Nov 2022 13:45:41 -0000 https://status.ppro.dev/incident/138462#e466752af31408e41e677236e0df0f2b0894941b7904d5685f1bfe08c41a1fcb BrovaPh2 ups status went down. https://status.ppro.dev/incident/138462 Sat, 26 Nov 2022 11:23:25 -0000 https://status.ppro.dev/incident/138462#c71e04ffcdf154b8ea794896e696bde54a25cb40832fc389d412190504ecf6d9 fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Sat, 26 Nov 2022 05:54:04 -0000 https://status.ppro.dev/incident/138462#0ad7f10b7cdad1034ba670673dc13c12be1054a35a212390b222b0f3bf8414b2 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Sat, 26 Nov 2022 05:36:14 -0000 https://status.ppro.dev/incident/138462#2c011a9dc64ffbf7270ccddda6e98ecfc7c31d1eb870527e0b3fa50d92a930e6 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Fri, 25 Nov 2022 22:23:25 -0000 https://status.ppro.dev/incident/138462#76e660dd3306d850cb5673b4e6d118503e69128b827f24e0c912bd0209a561af fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Fri, 25 Nov 2022 22:21:08 -0000 https://status.ppro.dev/incident/138462#f615410b15ee931d3969ac15f8c0a8a7ab531e2f25b7789bbeb669e0012f4e53 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Fri, 25 Nov 2022 20:59:11 -0000 https://status.ppro.dev/incident/138462#f017205012bbb8c9a644a6ea4352e6af260acc70520eb644a3346fb812173708 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Fri, 25 Nov 2022 19:06:12 -0000 https://status.ppro.dev/incident/138462#74a1c376739df13c79651a99d848d972bde871485183a2e9f3abc5199cc33d88 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Fri, 25 Nov 2022 14:41:11 -0000 https://status.ppro.dev/incident/138462#6b68830513bc6fa9d94c24f50e9471cd39fefac7c748e3b512751dd85b760faa smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Fri, 25 Nov 2022 13:26:31 -0000 https://status.ppro.dev/incident/138462#cec5251b013656e4c158ac5c6b30e2661eac15ff7523811c5c083bbe3031c5a5 fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Fri, 25 Nov 2022 10:59:38 -0000 https://status.ppro.dev/incident/138462#cedb543ce42d8a0043042053da433fb759ea95c5869ee1d1adccc842d875569c fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Thu, 24 Nov 2022 14:23:26 -0000 https://status.ppro.dev/incident/138462#36d4090fa1047a816e2c177ee78fa1eadba6bc8ec708ffc9c88e74b294620b23 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Thu, 24 Nov 2022 14:00:33 -0000 https://status.ppro.dev/incident/138462#4eb128d43d49ed693a48ae0c9500e3017e16af31b5763a448c0fa4cf8103d1e1 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Thu, 24 Nov 2022 13:33:37 -0000 https://status.ppro.dev/incident/138462#fb29bd5b7c7ba2ee27e0b004b466a5321de58386e09d8e4749dbe3f5a44b44f0 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Thu, 24 Nov 2022 13:30:30 -0000 https://status.ppro.dev/incident/138462#2f2de854d3d513841d36346f383b0c5a920409fada93fa8152a5873e0c2aff83 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Thu, 24 Nov 2022 13:22:29 -0000 https://status.ppro.dev/incident/138462#1708244f2550d3e3c77e9b9b10804dd47972831d79beadb1b721ff68d3d654e4 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Thu, 24 Nov 2022 09:30:29 -0000 https://status.ppro.dev/incident/138462#bd83239b8d11f3b1c13a89df0aaf48171233a700ac1fa47404469b8b0d7bc5dd smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Thu, 24 Nov 2022 01:19:56 -0000 https://status.ppro.dev/incident/138462#5bdf2ff7aeeb279d1770d5ac25fce396f0eff4117da60850db6f6d1dc90e74b3 fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Thu, 24 Nov 2022 00:44:47 -0000 https://status.ppro.dev/incident/138462#ed5827b4baff4bfcc49994b0c9b02e12177742230517781e38303afe4925b1ff fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Thu, 24 Nov 2022 00:28:49 -0000 https://status.ppro.dev/incident/138462#1a9811ca85787bfb5858ce0b4277ed35dc8c969aa1d834fcbb1dd0a08f19de72 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Thu, 24 Nov 2022 00:11:12 -0000 https://status.ppro.dev/incident/138462#4a230435c381566245ef9d91c691bc1f089e4a57e71bbe60ae9f4cdf525779ca fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Wed, 23 Nov 2022 20:53:38 -0000 https://status.ppro.dev/incident/138462#a32fb1ecadec96141dfc13e59b950c20cabe3ec5ba2791533b9be36e7b043418 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Wed, 23 Nov 2022 19:10:29 -0000 https://status.ppro.dev/incident/138462#e04d8c57af51370a6b7252cd541e706569cd1d00545d5156f9c9f6a86ba726cf smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Wed, 23 Nov 2022 19:02:28 -0000 https://status.ppro.dev/incident/138462#3d10095faccf541c2d2002ffd81279d2d5c7e65888449d6113ffeced79518d97 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Wed, 23 Nov 2022 19:02:12 -0000 https://status.ppro.dev/incident/138462#1543ae9a61d7d6c6bd5c10ec21fbf4832a2ac0bd39a9bf0c43477cf4f08f1604 fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Wed, 23 Nov 2022 17:08:25 -0000 https://status.ppro.dev/incident/138462#3936fb2dbfd671fd0d41774c0030fb48a7520f6d9a005f631f3f82955ed02e39 fj: jpyther docker service went down. https://status.ppro.dev/incident/138462 Wed, 23 Nov 2022 14:29:26 -0000 https://status.ppro.dev/incident/138462#c66def2942ebed3593a4a37f7fa848af61aba2bede8a18a03dcae4dad847fe20 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/138462 Wed, 23 Nov 2022 14:28:09 -0000 https://status.ppro.dev/incident/138462#8eec11fa3b56a72a1dfea7d2921e37205d8caf0023c5035dd6f6b3ff94f8cf62 fj: jpyther docker service recovered. https://status.ppro.dev/incident/138462 Wed, 23 Nov 2022 14:21:56 -0000 https://status.ppro.dev/incident/138462#f0a79d9e9ce05b9b5a04fe60f73bdcdc6366e1e3673f02850f2eb33f6fd308d7 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/138462 Wed, 23 Nov 2022 14:19:47 -0000 https://status.ppro.dev/incident/138462#a1d77eabbf0ebe85463ffa878736b58d810ba08baf3b5578a42e8b8b976838ba fj: jpyther docker service went down. https://status.ppro.dev/incident/137670 Tue, 22 Nov 2022 10:46:41 -0000 https://status.ppro.dev/incident/137670#bcc3c3383ed5f056f17f357ba1219f975ca9b55c51c6cbb25d525d06f499f2e5 fj: jpyther docker service recovered. https://status.ppro.dev/incident/137670 Tue, 22 Nov 2022 10:32:33 -0000 https://status.ppro.dev/incident/137670#61ec022b61bd04a356772d767cb8bf0d71732630f387098274db6047ce683847 fj: jpyther docker service went down. https://status.ppro.dev/incident/137670 Tue, 22 Nov 2022 02:24:30 -0000 https://status.ppro.dev/incident/137670#c82f80fc8ebdbaf25b3544bcb26d1821c8dadfe042313b43828a252bc2b79607 fj: jpyther docker service recovered. https://status.ppro.dev/incident/137670 Tue, 22 Nov 2022 01:00:37 -0000 https://status.ppro.dev/incident/137670#0975119f171770d30702fc18e9a8f25e5ff2c9aae9a8e7cd9a292717bf8175bc fj: jpyther docker service went down. https://status.ppro.dev/incident/137670 Tue, 22 Nov 2022 00:30:35 -0000 https://status.ppro.dev/incident/137670#8ae0185e0d18652ee807617b83906d8806d7ee8958799bda69b9f55abeb05493 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/137670 Tue, 22 Nov 2022 00:18:27 -0000 https://status.ppro.dev/incident/137670#6ba77d421b168e3acf0066b84c96cdf3d14f67a5e34ba59145d4f7d49116e651 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/137670 Tue, 22 Nov 2022 00:05:23 -0000 https://status.ppro.dev/incident/137670#b631c6940c4cd955583896b05e5bc15f987f3011dfcfc18f6d87ba6c2e084720 fj: jpyther docker service recovered. https://status.ppro.dev/incident/137670 Mon, 21 Nov 2022 23:39:25 -0000 https://status.ppro.dev/incident/137670#df42588ed38ec2cc76404cf70adad34c27b8c067c0126aa9bd7773d4c187f146 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/137670 Mon, 21 Nov 2022 23:05:23 -0000 https://status.ppro.dev/incident/137670#1923aba402420fb076994bf2867962241f3de56620132a42a0db9abf43499ec4 fj: jpyther docker service went down. https://status.ppro.dev/incident/137670 Mon, 21 Nov 2022 20:38:32 -0000 https://status.ppro.dev/incident/137670#12e7560c89ffd8a5141465ae053d0058d95f45bc01bcf61f2c394197dd85f209 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/137670 Mon, 21 Nov 2022 20:16:34 -0000 https://status.ppro.dev/incident/137670#3b6f4eec57747889c99815ad71b39e75ae3844753ca2c57abced4cb5629f8aef smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/137670 Mon, 21 Nov 2022 19:34:25 -0000 https://status.ppro.dev/incident/137670#989b12110e28641f5549459131f7a35b9a9622d314aa5ac02226b0423371b91c smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/137670 Mon, 21 Nov 2022 19:21:22 -0000 https://status.ppro.dev/incident/137670#f021b2c0f8a2ad5544bf052a845518d411732cae9437459f26557347351d29fd smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/137670 Mon, 21 Nov 2022 19:09:28 -0000 https://status.ppro.dev/incident/137670#a0b599c9280fc354acaa4e43bbd9a3af4c5d90083c7b0d33b32504c92e40a9f7 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/137670 Mon, 21 Nov 2022 18:41:19 -0000 https://status.ppro.dev/incident/137670#9dce2d616200e95cbe01e1896b5393b9bb6ee39485c74db10eb61c031d80b242 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/137670 Mon, 21 Nov 2022 18:33:27 -0000 https://status.ppro.dev/incident/137670#d4312723246d65481b5f0cf1cb6a0f6a2a6f2daae3643403fa2268e41ba35e57 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/137670 Mon, 21 Nov 2022 17:41:00 -0000 https://status.ppro.dev/incident/137670#9d0beabbc078bf0dc75d404ca5b9e7df7b26c6f1beacd1513838ca218b44aa53 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/137670 Mon, 21 Nov 2022 17:32:56 -0000 https://status.ppro.dev/incident/137670#acb3e22cefc4801551184a58d0a5ba4d53c86f45f4a5f673c78791347398fd24 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/137670 Mon, 21 Nov 2022 16:40:53 -0000 https://status.ppro.dev/incident/137670#8fc167793f30be2cfa3eae3c6d927c432742fa7cff7a2230a8656e414ccfdfde smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/137670 Mon, 21 Nov 2022 06:21:16 -0000 https://status.ppro.dev/incident/137670#e1fa7a2497b6261f58006284b52aa9c84fd33c243954e455cbcecc7711233cf9 fj: jpyther docker service recovered. https://status.ppro.dev/incident/137670 Mon, 21 Nov 2022 03:46:07 -0000 https://status.ppro.dev/incident/137670#a37afccba3f9ad8aa5939b29104b8b42dfcc2efa55f302f057809084efc78f43 fj: jpyther docker service went down. https://status.ppro.dev/incident/137670 Sun, 20 Nov 2022 22:12:13 -0000 https://status.ppro.dev/incident/137670#3e44b7a223bd0dfd9daa342d320dac8bdc86d7726184568602436da60099c687 fj: jpyther docker service recovered. https://status.ppro.dev/incident/137670 Sun, 20 Nov 2022 18:46:08 -0000 https://status.ppro.dev/incident/137670#b948505a9ffd8e6924f4561eccaf51d2b4949ee380e7873266df4d8b8f22b86d fj: jpyther docker service went down. https://status.ppro.dev/incident/137670 Sun, 20 Nov 2022 13:13:44 -0000 https://status.ppro.dev/incident/137670#94f9bf68c20e341683ff01189a4897899e783c3b3c64ad757ff9ba739521c490 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/137439 Sat, 19 Nov 2022 20:24:47 -0000 https://status.ppro.dev/incident/137439#827a4b7c72ca3ce64e1e6321d821ec4d461959b0ff1f91155f53541bec55ae71 smvs.chubynske.org.ua recovered. https://status.ppro.dev/incident/137439 Sat, 19 Nov 2022 20:16:45 -0000 https://status.ppro.dev/incident/137439#24d03b179b600eb71cc5de66fc03b7cebb4c63fd8442743055541c0ce2ee9c46 smvs.chubynske.org.ua went down. https://status.ppro.dev/incident/137439 Sat, 19 Nov 2022 17:09:13 -0000 https://status.ppro.dev/incident/137439#221dd4b1ed22f1b66aac1ec313a0a24163749f2d21d304c8bbf60265f39cee5b fj: jpyther docker service recovered. https://status.ppro.dev/incident/137439 Sat, 19 Nov 2022 15:52:08 -0000 https://status.ppro.dev/incident/137439#95003aa5d520d82345b99a48a8fe8b29a3ecbedcb48501392afb91d670dfd3a5 fj: jpyther docker service went down. https://status.ppro.dev/incident/136047 Fri, 18 Nov 2022 00:27:12 -0000 https://status.ppro.dev/incident/136047#8f171fee906feec777d16aa69cd00e3f12756f7f72a02fa8ec132fa796703819 fj: jpyther docker service recovered. https://status.ppro.dev/incident/136047 Thu, 17 Nov 2022 23:21:57 -0000 https://status.ppro.dev/incident/136047#c953bb50eb951a146c78def0129e79a1fc49b3cba26e26d0008d21151f4128bb fj: jpyther docker service went down. https://status.ppro.dev/incident/136047 Thu, 17 Nov 2022 21:45:10 -0000 https://status.ppro.dev/incident/136047#b9f4b67575427991c75f3cfd74c3ed9faba0458f79543620bf885eeafa53e37e fj: jpyther docker service recovered. https://status.ppro.dev/incident/136047 Tue, 15 Nov 2022 15:11:05 -0000 https://status.ppro.dev/incident/136047#8908432932534b654889cf4751ae5b18bfb486a78337c807cdbacef555414506 fj: jpyther docker service went down. https://status.ppro.dev/incident/136047 Tue, 15 Nov 2022 14:25:23 -0000 https://status.ppro.dev/incident/136047#b7bdec8ea1718208469c05e186fb4cca5a3f838058882bb13429753725b72748 fj: jpyther docker service recovered. https://status.ppro.dev/incident/136047 Tue, 15 Nov 2022 14:19:45 -0000 https://status.ppro.dev/incident/136047#040d7084fc83ab0f4a87fb997366d10d39d07d4dc0fd99663e1a884a040125f3 fj: jpyther docker service went down. https://status.ppro.dev/incident/136047 Tue, 15 Nov 2022 06:54:55 -0000 https://status.ppro.dev/incident/136047#156baa29e0db728699a91272d223dee536a2c8cd9cea14746e9dbf84eb37e31a fj: jpyther docker service recovered. https://status.ppro.dev/incident/136047 Tue, 15 Nov 2022 06:31:54 -0000 https://status.ppro.dev/incident/136047#82e3dc41af4de01d5a7654e362b920965c882489d12c0cebc8a3d075bb820dee fj: jpyther docker service went down. https://status.ppro.dev/incident/135643 Mon, 14 Nov 2022 06:14:34 -0000 https://status.ppro.dev/incident/135643#789c96bfe92bbb2f998a5a86db93091a71bf0d303b386a6933972a2663393ad5 fj: jpyther docker service recovered. https://status.ppro.dev/incident/135643 Mon, 14 Nov 2022 04:42:19 -0000 https://status.ppro.dev/incident/135643#59c6793d3a081968d524aceb9b2cdf139fd147b7ec77943c62fd62e150d346b4 fj: jpyther docker service went down. https://status.ppro.dev/incident/134857 Sun, 13 Nov 2022 14:22:58 -0000 https://status.ppro.dev/incident/134857#4b79373d18f470ac0835d6b0fe05d03a18b95fb0d04066b004f2a2ce9114b75f fj: jpyther docker service recovered. https://status.ppro.dev/incident/134857 Sat, 12 Nov 2022 23:13:36 -0000 https://status.ppro.dev/incident/134857#bed953779e9fef2a0ab1f7c1d5abf29f7d5fb934848eb32c9f67c58bc4ed0d2c fj: jpyther docker service went down. https://status.ppro.dev/incident/134857 Sat, 12 Nov 2022 18:18:49 -0000 https://status.ppro.dev/incident/134857#53a574b8a7da8c6a467492021223609eb6d954494f2c820be3f775f81f8b8166 fj: jpyther docker service recovered. https://status.ppro.dev/incident/134857 Sat, 12 Nov 2022 14:58:36 -0000 https://status.ppro.dev/incident/134857#6092df6c3aea5c50298bff071a8f279e46398c1cb2b2bf48bcf519853500097b fj: jpyther docker service went down. https://status.ppro.dev/incident/134857 Sat, 12 Nov 2022 10:15:39 -0000 https://status.ppro.dev/incident/134857#0af990c415a441aacff09f453c075f31cb1aa03dc668184e4ef74c2161a43741 fj: jpyther docker service recovered. https://status.ppro.dev/incident/134857 Sat, 12 Nov 2022 06:43:26 -0000 https://status.ppro.dev/incident/134857#2292e530fd841b04b2cea19408c6e2a646252411f668b8ca1c7a1fc83e804449 fj: jpyther docker service went down. https://status.ppro.dev/incident/134857 Fri, 11 Nov 2022 22:18:37 -0000 https://status.ppro.dev/incident/134857#d24d89d34a9082213d1e986da50997320d2f2477621cde119e9248c6072bbdd9 fj: jpyther docker service recovered. https://status.ppro.dev/incident/134857 Fri, 11 Nov 2022 18:43:35 -0000 https://status.ppro.dev/incident/134857#5d63f584e83bb70fdcaee4ff45a1788e845c950b53a31ae5e309d689620fd8b5 fj: jpyther docker service went down. https://status.ppro.dev/incident/134857 Fri, 11 Nov 2022 06:49:17 -0000 https://status.ppro.dev/incident/134857#12f46bc585a19378630c97a4dd39a56ee259e6f1e17cb7bdc37d2ac46c59ba24 fj: jpyther docker service recovered. https://status.ppro.dev/incident/134857 Fri, 11 Nov 2022 02:50:02 -0000 https://status.ppro.dev/incident/134857#69cdd2d24c0b77fd0e9b1295717d4369b5649acd0f54044b852afd2ea0313f63 fj: jpyther docker service went down. https://status.ppro.dev/incident/134207 Thu, 10 Nov 2022 17:16:14 -0000 https://status.ppro.dev/incident/134207#b42572dde699275ba4a1fd16ab7f50ffff89df75f34b254868e0514f85d8f760 fj: jpyther docker service recovered. https://status.ppro.dev/incident/134207 Thu, 10 Nov 2022 16:46:59 -0000 https://status.ppro.dev/incident/134207#6964152162242b5a63869dfc44c60a52846641462b1d2c3752374ed75a1b7c1d fj: jpyther docker service went down. https://status.ppro.dev/incident/134207 Thu, 10 Nov 2022 06:53:29 -0000 https://status.ppro.dev/incident/134207#d05561ac63f18512591828e0025992f3e9c3bb7783a5f57f06b1f47523ea39b8 fj: jpyther docker service recovered. https://status.ppro.dev/incident/134207 Thu, 10 Nov 2022 06:18:21 -0000 https://status.ppro.dev/incident/134207#70c10dc4da23d8d00f298a37a8f362afea4cc185a85916dd4b00d718df4b018d fj: jpyther docker service went down. https://status.ppro.dev/incident/134207 Wed, 09 Nov 2022 20:20:20 -0000 https://status.ppro.dev/incident/134207#b642b9aa31a0732d11054b353b1be39e6a2e60224db122a97144e810b7d6602e fj: jpyther docker service recovered. https://status.ppro.dev/incident/134207 Wed, 09 Nov 2022 18:42:09 -0000 https://status.ppro.dev/incident/134207#214383d6cc53f6327c77a05a6e1a1d852ccd384e701030186e4098355a76954b fj: jpyther docker service went down.