nicholasdev Status - Incident history https://status.nicholas.dev nicholasdev Mon, 13 Feb 2023 21:47:21 +0000 Nodes - VELOCITYNODE2 isn't accessible at the moment (automated) Type: Incident Affected Components: VELOCITYNODE2 Feb 13, 21:47:21 GMT+0 - Investigating - Nodes - VELOCITYNODE2 cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Affected Components:

<p><small>Feb <var data-var='date'> 13</var>, <var data-var='time'>21:47:21</var> GMT+0</small><br><strong>Investigating</strong> - Nodes - VELOCITYNODE2 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> ]]> Mon, 13 Feb 2023 21:47:21 +0000 https://status.nicholas.dev/incident/cle3cj1n81000728iboezk8wu735 https://status.nicholas.dev/incident/cle3cj1n81000728iboezk8wu735 Services - Plex Server isn't accessible at the moment (automated) Type: Incident Affected Components: Plex Server Feb 13, 21:39:56 GMT+0 - Investigating - Services - Plex Server cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Affected Components:

<p><small>Feb <var data-var='date'> 13</var>, <var data-var='time'>21:39:56</var> GMT+0</small><br><strong>Investigating</strong> - Services - Plex Server cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> ]]> Mon, 13 Feb 2023 21:39:56 +0000 https://status.nicholas.dev/incident/cle3c9iem962633g2n7jlqej030 https://status.nicholas.dev/incident/cle3c9iem962633g2n7jlqej030 Services - Plex Server isn't accessible at the moment (automated) Type: Incident Duration: 4 days, 22 hours and 51 minutes Affected Components: Plex Server Feb 13, 21:39:56 GMT+0 - Resolved - Services - Plex Server is now operational! This update was created by an automated monitoring service. Feb 7, 17:41:05 GMT+0 - Investigating - Services - Plex Server cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 4 days, 22 hours and 51 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 13</var>, <var data-var='time'>21:39:56</var> GMT+0</small><br><strong>Resolved</strong> - Services - Plex Server is now operational! This update was created by an automated monitoring service..</p> <p><small>Feb <var data-var='date'> 7</var>, <var data-var='time'>17:41:05</var> GMT+0</small><br><strong>Investigating</strong> - Services - Plex Server cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> ]]> Tue, 7 Feb 2023 17:41:05 +0000 https://status.nicholas.dev/incident/clduj38od385722i3lqzguh2jp6 https://status.nicholas.dev/incident/clduj38od385722i3lqzguh2jp6 Nodes - VELOCITYNODE2 isn't accessible at the moment (automated) Type: Incident Duration: 4 days, 22 hours and 52 minutes Affected Components: VELOCITYNODE2 Feb 13, 21:39:56 GMT+0 - Resolved - Nodes - VELOCITYNODE2 is now operational! This update was created by an automated monitoring service. Feb 7, 17:41:05 GMT+0 - Investigating - Nodes - VELOCITYNODE2 cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 4 days, 22 hours and 52 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 13</var>, <var data-var='time'>21:39:56</var> GMT+0</small><br><strong>Resolved</strong> - Nodes - VELOCITYNODE2 is now operational! This update was created by an automated monitoring service..</p> <p><small>Feb <var data-var='date'> 7</var>, <var data-var='time'>17:41:05</var> GMT+0</small><br><strong>Investigating</strong> - Nodes - VELOCITYNODE2 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> ]]> Tue, 7 Feb 2023 17:41:05 +0000 https://status.nicholas.dev/incident/clduj38er373409iplqoj3kpttf https://status.nicholas.dev/incident/clduj38er373409iplqoj3kpttf Services - Plex Server isn't accessible at the moment (automated) Type: Incident Duration: 26 days, 10 hours and 13 minutes Affected Components: Plex Server Jan 31, 05:24:42 GMT+0 - Investigating - Services - Plex Server cannot be accessed at the moment. This incident was created by an automated monitoring service. Feb 7, 17:34:54 GMT+0 - Resolved - Services - Plex Server is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 26 days, 10 hours and 13 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 31</var>, <var data-var='time'>05:24:42</var> GMT+0</small><br><strong>Investigating</strong> - Services - Plex Server cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Feb <var data-var='date'> 7</var>, <var data-var='time'>17:34:54</var> GMT+0</small><br><strong>Resolved</strong> - Services - Plex Server is now operational! This update was created by an automated monitoring service..</p> ]]> Tue, 31 Jan 2023 05:24:42 +0000 https://status.nicholas.dev/incident/cldjsp9tb24431240oka417fkxd https://status.nicholas.dev/incident/cldjsp9tb24431240oka417fkxd Nodes - VELOCITYNODE2 isn't accessible at the moment (automated) Type: Incident Duration: 26 days, 10 hours and 13 minutes Affected Components: VELOCITYNODE2 Jan 31, 05:24:42 GMT+0 - Investigating - Nodes - VELOCITYNODE2 cannot be accessed at the moment. This incident was created by an automated monitoring service. Feb 7, 17:34:54 GMT+0 - Resolved - Nodes - VELOCITYNODE2 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 26 days, 10 hours and 13 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 31</var>, <var data-var='time'>05:24:42</var> GMT+0</small><br><strong>Investigating</strong> - Nodes - VELOCITYNODE2 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Feb <var data-var='date'> 7</var>, <var data-var='time'>17:34:54</var> GMT+0</small><br><strong>Resolved</strong> - Nodes - VELOCITYNODE2 is now operational! This update was created by an automated monitoring service..</p> ]]> Tue, 31 Jan 2023 05:24:42 +0000 https://status.nicholas.dev/incident/cldjsp9su128824iqo9436hv8rq https://status.nicholas.dev/incident/cldjsp9su128824iqo9436hv8rq Services - Plex Server isn't accessible at the moment (automated) Type: Incident Duration: 7 days, 10 hours and 49 minutes Affected Components: Plex Server Jan 28, 13:54:55 GMT+0 - Investigating - Services - Plex Server cannot be accessed at the moment. This incident was created by an automated monitoring service. Jan 31, 05:17:44 GMT+0 - Resolved - Services - Plex Server is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 7 days, 10 hours and 49 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 28</var>, <var data-var='time'>13:54:55</var> GMT+0</small><br><strong>Investigating</strong> - Services - Plex Server cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Jan <var data-var='date'> 31</var>, <var data-var='time'>05:17:44</var> GMT+0</small><br><strong>Resolved</strong> - Services - Plex Server is now operational! This update was created by an automated monitoring service..</p> ]]> Sat, 28 Jan 2023 13:54:55 +0000 https://status.nicholas.dev/incident/cldg0lvbm5410251jol9bqadapq https://status.nicholas.dev/incident/cldg0lvbm5410251jol9bqadapq Nodes - VELOCITYNODE2 isn't accessible at the moment (automated) Type: Incident Duration: 7 days, 10 hours and 51 minutes Affected Components: VELOCITYNODE2 Jan 28, 13:54:53 GMT+0 - Investigating - Nodes - VELOCITYNODE2 cannot be accessed at the moment. This incident was created by an automated monitoring service. Jan 31, 05:17:44 GMT+0 - Resolved - Nodes - VELOCITYNODE2 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 7 days, 10 hours and 51 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 28</var>, <var data-var='time'>13:54:53</var> GMT+0</small><br><strong>Investigating</strong> - Nodes - VELOCITYNODE2 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Jan <var data-var='date'> 31</var>, <var data-var='time'>05:17:44</var> GMT+0</small><br><strong>Resolved</strong> - Nodes - VELOCITYNODE2 is now operational! This update was created by an automated monitoring service..</p> ]]> Sat, 28 Jan 2023 13:54:53 +0000 https://status.nicholas.dev/incident/cldg0lty35408791joly1xmzbsv https://status.nicholas.dev/incident/cldg0lty35408791joly1xmzbsv Nodes - VELOCITYNODE1 isn't accessible at the moment (automated) Type: Incident Affected Components: VELOCITYNODE1 Jan 28, 11:47:03 GMT+0 - Investigating - Nodes - VELOCITYNODE1 cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Affected Components:

<p><small>Jan <var data-var='date'> 28</var>, <var data-var='time'>11:47:03</var> GMT+0</small><br><strong>Investigating</strong> - Nodes - VELOCITYNODE1 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> ]]> Sat, 28 Jan 2023 11:47:03 +0000 https://status.nicholas.dev/incident/cldfw1fr0924889i0oe7hh7odf0 https://status.nicholas.dev/incident/cldfw1fr0924889i0oe7hh7odf0 Nodes - VELOCITYNODE1 isn't accessible at the moment (automated) Type: Incident Duration: 27 days, 2 hours and 29 minutes Affected Components: VELOCITYNODE1 Jan 17, 21:38:13 GMT+0 - Investigating - Nodes - VELOCITYNODE1 cannot be accessed at the moment. This incident was created by an automated monitoring service. Jan 28, 11:40:42 GMT+0 - Resolved - Nodes - VELOCITYNODE1 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 27 days, 2 hours and 29 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 17</var>, <var data-var='time'>21:38:13</var> GMT+0</small><br><strong>Investigating</strong> - Nodes - VELOCITYNODE1 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Jan <var data-var='date'> 28</var>, <var data-var='time'>11:40:42</var> GMT+0</small><br><strong>Resolved</strong> - Nodes - VELOCITYNODE1 is now operational! This update was created by an automated monitoring service..</p> ]]> Tue, 17 Jan 2023 21:38:13 +0000 https://status.nicholas.dev/incident/cld0rbbcn673162g7n3zo3vst6x https://status.nicholas.dev/incident/cld0rbbcn673162g7n3zo3vst6x Services - Plex Server isn't accessible at the moment (automated) Type: Incident Duration: 26 days, 3 hours and 56 minutes Affected Components: Plex Server Nov 14, 14:07:43 GMT+0 - Investigating - Services - Plex Server cannot be accessed at the moment. This incident was created by an automated monitoring service. Jan 28, 13:47:39 GMT+0 - Resolved - Services - Plex Server is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 26 days, 3 hours and 56 minutes

Affected Components:

<p><small>Nov <var data-var='date'> 14</var>, <var data-var='time'>14:07:43</var> GMT+0</small><br><strong>Investigating</strong> - Services - Plex Server cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Jan <var data-var='date'> 28</var>, <var data-var='time'>13:47:39</var> GMT+0</small><br><strong>Resolved</strong> - Services - Plex Server is now operational! This update was created by an automated monitoring service..</p> ]]> Mon, 14 Nov 2022 14:07:43 +0000 https://status.nicholas.dev/incident/clagv1fnw352576vilsq0fouzho https://status.nicholas.dev/incident/clagv1fnw352576vilsq0fouzho Nodes - VELOCITYNODE2 isn't accessible at the moment (automated) Type: Incident Duration: 26 days, 11 hours and 28 minutes Affected Components: VELOCITYNODE2 Nov 14, 14:00:12 GMT+0 - Investigating - Nodes - VELOCITYNODE2 cannot be accessed at the moment. This incident was created by an automated monitoring service. Jan 28, 13:47:39 GMT+0 - Resolved - Nodes - VELOCITYNODE2 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 26 days, 11 hours and 28 minutes

Affected Components:

<p><small>Nov <var data-var='date'> 14</var>, <var data-var='time'>14:00:12</var> GMT+0</small><br><strong>Investigating</strong> - Nodes - VELOCITYNODE2 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Jan <var data-var='date'> 28</var>, <var data-var='time'>13:47:39</var> GMT+0</small><br><strong>Resolved</strong> - Nodes - VELOCITYNODE2 is now operational! This update was created by an automated monitoring service..</p> ]]> Mon, 14 Nov 2022 14:00:12 +0000 https://status.nicholas.dev/incident/clagurrvb377192wdmwk7mh5pgs https://status.nicholas.dev/incident/clagurrvb377192wdmwk7mh5pgs Nodes - VELOCITYNODE2 isn't accessible at the moment (automated) Type: Incident Duration: 26 days, 22 hours and 11 minutes Affected Components: VELOCITYNODE2 Nov 14, 14:00:12 GMT+0 - Resolved - Nodes - VELOCITYNODE2 is now operational! This update was created by an automated monitoring service. Aug 16, 08:26:01 GMT+0 - Investigating - Nodes - VELOCITYNODE2 cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 26 days, 22 hours and 11 minutes

Affected Components:

<p><small>Nov <var data-var='date'> 14</var>, <var data-var='time'>14:00:12</var> GMT+0</small><br><strong>Resolved</strong> - Nodes - VELOCITYNODE2 is now operational! This update was created by an automated monitoring service..</p> <p><small>Aug <var data-var='date'> 16</var>, <var data-var='time'>08:26:01</var> GMT+0</small><br><strong>Investigating</strong> - Nodes - VELOCITYNODE2 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> ]]> Tue, 16 Aug 2022 08:26:01 +0000 https://status.nicholas.dev/incident/cl6vx7clu13109949uoi5taof0l9 https://status.nicholas.dev/incident/cl6vx7clu13109949uoi5taof0l9 Services - Plex Server isn't accessible at the moment (automated) Type: Incident Duration: 26 days, 22 hours and 10 minutes Affected Components: Plex Server Aug 16, 08:26:00 GMT+0 - Investigating - Services - Plex Server cannot be accessed at the moment. This incident was created by an automated monitoring service. Nov 14, 14:00:09 GMT+0 - Resolved - Services - Plex Server is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 26 days, 22 hours and 10 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 16</var>, <var data-var='time'>08:26:00</var> GMT+0</small><br><strong>Investigating</strong> - Services - Plex Server cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Nov <var data-var='date'> 14</var>, <var data-var='time'>14:00:09</var> GMT+0</small><br><strong>Resolved</strong> - Services - Plex Server is now operational! This update was created by an automated monitoring service..</p> ]]> Tue, 16 Aug 2022 08:26:00 +0000 https://status.nicholas.dev/incident/cl6vx7bfr130813797omhadzsmaa https://status.nicholas.dev/incident/cl6vx7bfr130813797omhadzsmaa Nodes - VELOCITYNODE2 isn't accessible at the moment (automated) Type: Incident Duration: 15 days, 9 hours and 10 minutes Affected Components: VELOCITYNODE2 Jul 4, 11:22:04 GMT+0 - Investigating - Nodes - VELOCITYNODE2 cannot be accessed at the moment. This incident was created by an automated monitoring service. Aug 16, 08:19:13 GMT+0 - Resolved - Nodes - VELOCITYNODE2 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 15 days, 9 hours and 10 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 4</var>, <var data-var='time'>11:22:04</var> GMT+0</small><br><strong>Investigating</strong> - Nodes - VELOCITYNODE2 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Aug <var data-var='date'> 16</var>, <var data-var='time'>08:19:13</var> GMT+0</small><br><strong>Resolved</strong> - Nodes - VELOCITYNODE2 is now operational! This update was created by an automated monitoring service..</p> ]]> Mon, 4 Jul 2022 11:22:04 +0000 https://status.nicholas.dev/incident/cl56nk46y33656eeof7t2w198i https://status.nicholas.dev/incident/cl56nk46y33656eeof7t2w198i Services - Plex Server isn't accessible at the moment (automated) Type: Incident Duration: 15 days, 9 hours and 12 minutes Affected Components: Plex Server Aug 16, 08:19:16 GMT+0 - Resolved - Services - Plex Server is now operational! This update was created by an automated monitoring service. Jul 4, 11:22:04 GMT+0 - Investigating - Services - Plex Server cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 15 days, 9 hours and 12 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 16</var>, <var data-var='time'>08:19:16</var> GMT+0</small><br><strong>Resolved</strong> - Services - Plex Server is now operational! This update was created by an automated monitoring service..</p> <p><small>Jul <var data-var='date'> 4</var>, <var data-var='time'>11:22:04</var> GMT+0</small><br><strong>Investigating</strong> - Services - Plex Server cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> ]]> Mon, 4 Jul 2022 11:22:04 +0000 https://status.nicholas.dev/incident/cl56nk44u42175feogb9tbc4az https://status.nicholas.dev/incident/cl56nk44u42175feogb9tbc4az Services - Plex Server isn't accessible at the moment (automated) Type: Incident Duration: 8 days, 21 hours and 21 minutes Affected Components: Plex Server Jun 26, 19:32:12 GMT+0 - Resolved - Services - Plex Server is now operational! This update was created by an automated monitoring service. Jun 24, 15:58:51 GMT+0 - Investigating - Services - Plex Server cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 8 days, 21 hours and 21 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 26</var>, <var data-var='time'>19:32:12</var> GMT+0</small><br><strong>Resolved</strong> - Services - Plex Server is now operational! This update was created by an automated monitoring service..</p> <p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>15:58:51</var> GMT+0</small><br><strong>Investigating</strong> - Services - Plex Server cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> ]]> Fri, 24 Jun 2022 15:58:51 +0000 https://status.nicholas.dev/incident/cl4sn1jj91186282l0opcoxu1h6u https://status.nicholas.dev/incident/cl4sn1jj91186282l0opcoxu1h6u Nodes - VELOCITYNODE2 isn't accessible at the moment (automated) Type: Incident Duration: 8 days, 21 hours and 25 minutes Affected Components: VELOCITYNODE2 Jun 26, 19:32:15 GMT+0 - Resolved - Nodes - VELOCITYNODE2 is now operational! This update was created by an automated monitoring service. Jun 24, 15:58:51 GMT+0 - Investigating - Nodes - VELOCITYNODE2 cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 8 days, 21 hours and 25 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 26</var>, <var data-var='time'>19:32:15</var> GMT+0</small><br><strong>Resolved</strong> - Nodes - VELOCITYNODE2 is now operational! This update was created by an automated monitoring service..</p> <p><small>Jun <var data-var='date'> 24</var>, <var data-var='time'>15:58:51</var> GMT+0</small><br><strong>Investigating</strong> - Nodes - VELOCITYNODE2 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> ]]> Fri, 24 Jun 2022 15:58:51 +0000 https://status.nicholas.dev/incident/cl4sn1jh91316485r4mwsqtmodv4 https://status.nicholas.dev/incident/cl4sn1jh91316485r4mwsqtmodv4 Services - Plex Server isn't accessible at the moment (automated) Type: Incident Duration: 24 days, 2 hours and 7 minutes Affected Components: Plex Server Jun 21, 14:36:53 GMT+0 - Resolved - Services - Plex Server is now operational! This update was created by an automated monitoring service. Jun 19, 16:58:47 GMT+0 - Investigating - Services - Plex Server cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 24 days, 2 hours and 7 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 21</var>, <var data-var='time'>14:36:53</var> GMT+0</small><br><strong>Resolved</strong> - Services - Plex Server is now operational! This update was created by an automated monitoring service..</p> <p><small>Jun <var data-var='date'> 19</var>, <var data-var='time'>16:58:47</var> GMT+0</small><br><strong>Investigating</strong> - Services - Plex Server cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> ]]> Sun, 19 Jun 2022 16:58:47 +0000 https://status.nicholas.dev/incident/cl4ljzcki35911euoj59ggtpsb https://status.nicholas.dev/incident/cl4ljzcki35911euoj59ggtpsb Nodes - VELOCITYNODE2 isn't accessible at the moment (automated) Type: Incident Duration: 24 days, 2 hours and 8 minutes Affected Components: VELOCITYNODE2 Jun 19, 16:58:46 GMT+0 - Investigating - Nodes - VELOCITYNODE2 cannot be accessed at the moment. This incident was created by an automated monitoring service. Jun 21, 14:36:54 GMT+0 - Resolved - Nodes - VELOCITYNODE2 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 24 days, 2 hours and 8 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 19</var>, <var data-var='time'>16:58:46</var> GMT+0</small><br><strong>Investigating</strong> - Nodes - VELOCITYNODE2 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Jun <var data-var='date'> 21</var>, <var data-var='time'>14:36:54</var> GMT+0</small><br><strong>Resolved</strong> - Nodes - VELOCITYNODE2 is now operational! This update was created by an automated monitoring service..</p> ]]> Sun, 19 Jun 2022 16:58:46 +0000 https://status.nicholas.dev/incident/cl4ljzc8w35834euoj4bein0jk https://status.nicholas.dev/incident/cl4ljzc8w35834euoj4bein0jk Services - Plex Server isn't accessible at the moment (automated) Type: Incident Duration: 2 days, 5 hours and 29 minutes Affected Components: Plex Server Jun 6, 20:28:36 GMT+0 - Resolved - Services - Plex Server is now operational! This update was created by an automated monitoring service. Jun 6, 19:35:08 GMT+0 - Investigating - Services - Plex Server cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 2 days, 5 hours and 29 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 6</var>, <var data-var='time'>20:28:36</var> GMT+0</small><br><strong>Resolved</strong> - Services - Plex Server is now operational! This update was created by an automated monitoring service..</p> <p><small>Jun <var data-var='date'> 6</var>, <var data-var='time'>19:35:08</var> GMT+0</small><br><strong>Investigating</strong> - Services - Plex Server cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> ]]> Mon, 6 Jun 2022 19:35:08 +0000 https://status.nicholas.dev/incident/cl434ucij108228evljgyspntw4 https://status.nicholas.dev/incident/cl434ucij108228evljgyspntw4 Nodes - VELOCITYNODE2 isn't accessible at the moment (automated) Type: Incident Duration: 2 days, 5 hours and 28 minutes Affected Components: VELOCITYNODE2 Jun 6, 20:28:35 GMT+0 - Resolved - Nodes - VELOCITYNODE2 is now operational! This update was created by an automated monitoring service. Jun 6, 19:35:07 GMT+0 - Investigating - Nodes - VELOCITYNODE2 cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 2 days, 5 hours and 28 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 6</var>, <var data-var='time'>20:28:35</var> GMT+0</small><br><strong>Resolved</strong> - Nodes - VELOCITYNODE2 is now operational! This update was created by an automated monitoring service..</p> <p><small>Jun <var data-var='date'> 6</var>, <var data-var='time'>19:35:07</var> GMT+0</small><br><strong>Investigating</strong> - Nodes - VELOCITYNODE2 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> ]]> Mon, 6 Jun 2022 19:35:07 +0000 https://status.nicholas.dev/incident/cl434uc6a1575240cwlkm367ig47 https://status.nicholas.dev/incident/cl434uc6a1575240cwlkm367ig47 Nodes - VELOCITYNODE1 isn't accessible at the moment (automated) Type: Incident Duration: 13 days, 3 hours and 41 minutes Affected Components: VELOCITYNODE1 Jan 16, 21:52:19 GMT+0 - Investigating - Nodes - VELOCITYNODE1 cannot be accessed at the moment. This incident was created by an automated monitoring service. Jan 17, 21:31:59 GMT+0 - Resolved - Nodes - VELOCITYNODE1 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 13 days, 3 hours and 41 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 16</var>, <var data-var='time'>21:52:19</var> GMT+0</small><br><strong>Investigating</strong> - Nodes - VELOCITYNODE1 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Jan <var data-var='date'> 17</var>, <var data-var='time'>21:31:59</var> GMT+0</small><br><strong>Resolved</strong> - Nodes - VELOCITYNODE1 is now operational! This update was created by an automated monitoring service..</p> ]]> Sun, 16 Jan 2022 21:52:19 +0000 https://status.nicholas.dev/incident/ckyhsnnmn1025615p9oamqs1i82v https://status.nicholas.dev/incident/ckyhsnnmn1025615p9oamqs1i82v Services - Pterodactyl Panel isn't accessible at the moment (automated) Type: Incident Affected Components: Pterodactyl Panel Jan 16, 21:47:20 GMT+0 - Investigating - Services - Pterodactyl Panel cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Affected Components:

<p><small>Jan <var data-var='date'> 16</var>, <var data-var='time'>21:47:20</var> GMT+0</small><br><strong>Investigating</strong> - Services - Pterodactyl Panel cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> ]]> Sun, 16 Jan 2022 21:47:20 +0000 https://status.nicholas.dev/incident/ckyhsh98v358192oforb45f35gc https://status.nicholas.dev/incident/ckyhsh98v358192oforb45f35gc Services - Pterodactyl Panel isn't accessible at the moment (automated) Type: Incident Duration: 1 day and 51 minutes Affected Components: Pterodactyl Panel Jan 2, 14:53:14 GMT+0 - Investigating - Services - Pterodactyl Panel cannot be accessed at the moment. This incident was created by an automated monitoring service. Jan 2, 15:18:05 GMT+0 - Resolved - Services - Pterodactyl Panel is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 1 day and 51 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 2</var>, <var data-var='time'>14:53:14</var> GMT+0</small><br><strong>Investigating</strong> - Services - Pterodactyl Panel cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Jan <var data-var='date'> 2</var>, <var data-var='time'>15:18:05</var> GMT+0</small><br><strong>Resolved</strong> - Services - Pterodactyl Panel is now operational! This update was created by an automated monitoring service..</p> ]]> Sun, 2 Jan 2022 14:53:14 +0000 https://status.nicholas.dev/incident/ckxxdisg1430912mvmx8pwy7mby https://status.nicholas.dev/incident/ckxxdisg1430912mvmx8pwy7mby