tag:status.ripe.net,2005:/historyRIPE NCC Status - Incident History2024-03-28T15:43:16ZRIPE NCCtag:status.ripe.net,2005:Incident/203591152024-04-04T11:30:00Z2024-03-26T09:24:09ZRPKI Dashboard planned maintenance<p><strong>THIS IS A SCHEDULED EVENT Apr <var data-var='date'>4</var>, <var data-var='time'>11:30</var> - <var data-var='time'>13:00</var> UTC</strong></p><p><small>Mar <var data-var='date'>26</var>, <var data-var='time'>08:46</var> UTC</small><br><strong>Scheduled</strong> - We will be undergoing scheduled maintenance during this time.</p>tag:status.ripe.net,2005:Incident/203786692024-03-28T15:18:28Z2024-03-28T15:18:28ZGM Registration issue<p><small>Mar <var data-var='date'>28</var>, <var data-var='time'>15:18</var> UTC</small><br><strong>Resolved</strong> - We have now resolved the issues with GM registration and confirmation emails.</p><p><small>Mar <var data-var='date'>28</var>, <var data-var='time'>15:15</var> UTC</small><br><strong>Update</strong> - We are continuing to monitor for any further issues.</p><p><small>Mar <var data-var='date'>27</var>, <var data-var='time'>16:50</var> UTC</small><br><strong>Monitoring</strong> - There was an issue with the GM registration confirmation email. Registration for the General Meeting (GM) is open and registrants will not receive a confirmation email. We are working on resolving this issue and follow up confirmation emails will follow.</p><p><small>Mar <var data-var='date'>27</var>, <var data-var='time'>15:21</var> UTC</small><br><strong>Investigating</strong> - We are having issues with General Meeting (GM) registration in the LIR Portal. We are investigating the issue.</p>tag:status.ripe.net,2005:Incident/203495372024-03-28T10:21:06Z2024-03-28T10:21:06ZPlanned Maintenance: RIPE NCC Certified Professionals<p><small>Mar <var data-var='date'>28</var>, <var data-var='time'>10:21</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Mar <var data-var='date'>28</var>, <var data-var='time'>09:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Mar <var data-var='date'>25</var>, <var data-var='time'>10:28</var> UTC</small><br><strong>Scheduled</strong> - We will carry out planned maintenance on the RIPE NCC Certified Professionals website. During this time, the registration page will be unavailable.</p>tag:status.ripe.net,2005:Incident/203624352024-03-27T16:05:04Z2024-03-27T16:05:05ZPlanned Maintenance: ripe.net Website<p><small>Mar <var data-var='date'>27</var>, <var data-var='time'>16:05</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Mar <var data-var='date'>27</var>, <var data-var='time'>16:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Mar <var data-var='date'>26</var>, <var data-var='time'>15:29</var> UTC</small><br><strong>Scheduled</strong> - We will carry out planned maintenance on the ripe.net website. During this time, the ripe.net website and RIPE Labs will be unavailable or not fully functional.</p>tag:status.ripe.net,2005:Incident/203108922024-03-20T17:43:57Z2024-03-20T17:43:57ZRIPE NCC Access (SSO) will be unavailable because of maintenance<p><small>Mar <var data-var='date'>20</var>, <var data-var='time'>17:43</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Mar <var data-var='date'>20</var>, <var data-var='time'>17:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Mar <var data-var='date'>20</var>, <var data-var='time'>14:39</var> UTC</small><br><strong>Scheduled</strong> - We will be using this downtime to perform an upgrade to Keycloak (the existing SSO back end of RIPE NCC Access).<br />Downtime is expected to last no longer than 1 hour.</p>tag:status.ripe.net,2005:Incident/202920282024-03-20T12:00:56Z2024-03-20T12:00:56ZRIPE NCC Access (SSO) will be unavailable because of maintenance<p><small>Mar <var data-var='date'>20</var>, <var data-var='time'>12:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Mar <var data-var='date'>20</var>, <var data-var='time'>11:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Mar <var data-var='date'>18</var>, <var data-var='time'>14:35</var> UTC</small><br><strong>Scheduled</strong> - We will be using this downtime to perform an upgrade to Keycloak (the existing SSO back end of RIPE NCC Access).<br />Downtime is expected to last no longer than 1 hour.</p>tag:status.ripe.net,2005:Incident/201554112024-03-11T11:00:56Z2024-03-11T11:00:56ZRPKI Dashboard: Monthly maintenance<p><small>Mar <var data-var='date'>11</var>, <var data-var='time'>11:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Mar <var data-var='date'>11</var>, <var data-var='time'>10:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Mar <var data-var='date'>11</var>, <var data-var='time'>09:11</var> UTC</small><br><strong>Scheduled</strong> - We will be undergoing scheduled maintenance during this time.</p>tag:status.ripe.net,2005:Incident/201545322024-03-04T22:42:27Z2024-03-04T22:42:27ZRIPE Atlas processing delay<p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>22:42</var> UTC</small><br><strong>Resolved</strong> - The Atlas processing delay is going back to normal values.</p><p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>11:50</var> UTC</small><br><strong>Monitoring</strong> - Delay is still decreasing. We are monitoring the situation.</p><p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>08:24</var> UTC</small><br><strong>Identified</strong> - We have identified a problematic node in the backend cluster.<br />The delay is slowly decreasing.</p><p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>07:02</var> UTC</small><br><strong>Investigating</strong> - We have noticed an increasing delay in the processing of atlas data. We are investigating.</p>tag:status.ripe.net,2005:Incident/201558732024-03-04T10:23:38Z2024-03-04T10:46:34ZIssues with RIPE NCC Services [LIR Portal]<p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>10:23</var> UTC</small><br><strong>Resolved</strong> - This morning between 09:48 and 10:29 Amsterdam time, LIR Portal did not function properly.<br /><br />At 09:48, we released a dependency upgrade which broke the front-end code. <br /><br />Moreover, the alerts which would normally signal this problem were not delivered as expected. This was because of an issue in alerting system. <br /><br />On 10:29, we have fixed the issue with LIR Portal by reverting the dependency upgrade.<br /><br />We are currently investigating the issue about our alerting system.<br /><br />LIR Portal is now working as expected.</p>tag:status.ripe.net,2005:Incident/201286622024-03-01T12:05:25Z2024-03-01T12:05:25ZRIPE Atlas, DNSMON, and RIPE IPmap unavailable<p><small>Mar <var data-var='date'> 1</var>, <var data-var='time'>12:05</var> UTC</small><br><strong>Resolved</strong> - RIPE Atlas, DNSMON and RIPE IPmap are operating normally. The cause was a failure in the high availability setup for the PostgreSQL database, triggered by a network glitch. Ongoing RIPE Atlas measurements, including for DNSMON, continued running as normal during the outage.</p><p><small>Mar <var data-var='date'> 1</var>, <var data-var='time'>11:35</var> UTC</small><br><strong>Monitoring</strong> - The issue with the database server has been fixed, and the services are available again. We are monitoring to make sure that there are no remaining issues.</p><p><small>Mar <var data-var='date'> 1</var>, <var data-var='time'>11:12</var> UTC</small><br><strong>Investigating</strong> - Starting at about 10:44 UTC, our RIPE Atlas, DNSMON and RIPE IPmap services are unavailable. This appears to be caused by an issue with our RIPE Atlas database server. We are investigating.</p>tag:status.ripe.net,2005:Incident/200197142024-02-21T16:00:56Z2024-02-21T16:00:56Zrrc10.ripe.net hardware replacement<p><small>Feb <var data-var='date'>21</var>, <var data-var='time'>16:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Feb <var data-var='date'>21</var>, <var data-var='time'>08:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Feb <var data-var='date'>19</var>, <var data-var='time'>11:10</var> UTC</small><br><strong>Scheduled</strong> - Hardware replacement of rrc10.ripe.net, hosted at MIX - Milan Internet eXchange.<br /><br />AS12654<br />217.29.66.6<br />2001:7f8:b:100:1d1:a5d1:2654:6<br /><br />Work start: 2024-02-21 08:00 UTC<br />Work end: 2024-02-21 16:00 UTC<br /><br />Expected consequences during the maintenance window:<br />BGP sessions down;<br />RIS raw data (MRT files) for this collector not produced;<br />RIS Live data for this collector not available.</p>tag:status.ripe.net,2005:Incident/199305252024-02-21T11:11:08Z2024-02-21T11:11:08ZPlanned maintenance: RPKI Dashboard and API<p><small>Feb <var data-var='date'>21</var>, <var data-var='time'>11:11</var> UTC</small><br><strong>Completed</strong> - We have finished the migration. The RPKI dashboard and API are available again.</p><p><small>Feb <var data-var='date'>21</var>, <var data-var='time'>07:30</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Feb <var data-var='date'> 7</var>, <var data-var='time'>13:32</var> UTC</small><br><strong>Scheduled</strong> - We are migrating the RPKI environment to new online Hardware Security Modules (HSMs) as the current HSMs are reaching the End-Of-Life. These HSMs contain all the keys for the certificates issued by the RIPE NCC. They will be migrated from the current HSMs (nShield Connect+) to new HSMs (nShield 5C). <br /><br />To ensure that no new keys are created during the maintenance, we require some downtime of the RPKI dashboard and API. The current RPKI keys and objects will not change and this migration will not affect users except for this planned downtime. <br /><br />We plan to do a final rehearsal of the process in our production environment on 20 February 2024. The production migration itself is planned on 21 February 2024.<br /><br />We are planning the following maintenance windows:<br /><br />20 February 2024: 07:30-9:30 UTC<br />21 February 2024: 07:30-18:30 UTC<br /><br />This maintenance will only affect the RPKI CA system and availability of the RPKI dashboard and API that are used to create/edit objects. The validity of RPKI objects under our Trust Anchor will not be affected. Furthermore, the RRDP and rsync repositories will be available as usual.</p>tag:status.ripe.net,2005:Incident/199305192024-02-20T08:24:27Z2024-02-20T08:24:27ZPlanned maintenance: RPKI Dashboard and API<p><small>Feb <var data-var='date'>20</var>, <var data-var='time'>08:24</var> UTC</small><br><strong>Completed</strong> - We have completed the maintenance steps that were planned for this morning.</p><p><small>Feb <var data-var='date'>20</var>, <var data-var='time'>07:30</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Feb <var data-var='date'> 7</var>, <var data-var='time'>13:31</var> UTC</small><br><strong>Scheduled</strong> - We are migrating the RPKI environment to new online Hardware Security Modules (HSMs) as the current HSMs are reaching the End-Of-Life. These HSMs contain all the keys for the certificates issued by the RIPE NCC. They will be migrated from the current HSMs (nShield Connect+) to new HSMs (nShield 5C). <br /><br />To ensure that no new keys are created during the maintenance, we require some downtime of the RPKI dashboard and API. The current RPKI keys and objects will not change and this migration will not affect users except for this planned downtime. <br /><br />We plan to do a final rehearsal of the process in our production environment on 20 February 2024. The production migration itself is planned on 21 February 2024.<br /><br />We are planning the following maintenance windows:<br /><br />20 February 2024: 07:30-9:30 UTC<br />21 February 2024: 07:30-18:30 UTC<br /><br />This maintenance will only affect the RPKI CA system and availability of the RPKI dashboard and API that are used to create/edit objects. The validity of RPKI objects under our Trust Anchor will not be affected. Furthermore, the RRDP and rsync repositories will be available as usual.</p>tag:status.ripe.net,2005:Incident/199466212024-02-14T11:02:02Z2024-02-14T11:02:02ZRIPE NCC Access (SSO) will be unavailable because of maintenance<p><small>Feb <var data-var='date'>14</var>, <var data-var='time'>11:02</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Feb <var data-var='date'>14</var>, <var data-var='time'>10:30</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Feb <var data-var='date'> 9</var>, <var data-var='time'>09:54</var> UTC</small><br><strong>Scheduled</strong> - On Wednesday 14 February at 10:30 UTC we will face a maintenance downtime.<br /><br />We will be using this downtime to perform a major upgrade to Keycloak (the existing SSO back end of RIPE NCC Access).<br />Downtime is expected to last no longer than 1 hour.<br /><br />This upgrade enables us from staying in the supported versions of the community and gain new functionalities added to the release.<br /><br />This downtime will also affect functionality which is dependent on SSO, such as RIPE Database updates, LIR Portal, RIPE Academy, My Atlas.</p>tag:status.ripe.net,2005:Incident/199289452024-02-12T12:00:56Z2024-02-12T12:00:56ZPlanned maintenance: RPKI Dashboard<p><small>Feb <var data-var='date'>12</var>, <var data-var='time'>12:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Feb <var data-var='date'>12</var>, <var data-var='time'>11:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Feb <var data-var='date'> 7</var>, <var data-var='time'>09:09</var> UTC</small><br><strong>Scheduled</strong> - The RPKI Dashboard will be unavailable for an hour due to scheduled maintenance.</p>tag:status.ripe.net,2005:Incident/198671672024-02-01T10:51:01Z2024-02-13T16:06:28ZIssues with RIPE Atlas Infrastructure<p><small>Feb <var data-var='date'> 1</var>, <var data-var='time'>10:51</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Feb <var data-var='date'> 1</var>, <var data-var='time'>10:49</var> UTC</small><br><strong>Update</strong> - The backlog has been processed, this incident has been resolved.</p><p><small>Jan <var data-var='date'>31</var>, <var data-var='time'>17:05</var> UTC</small><br><strong>Update</strong> - The probes' connections have been stabilised, the system continues to process the backlog.</p><p><small>Jan <var data-var='date'>30</var>, <var data-var='time'>16:02</var> UTC</small><br><strong>Monitoring</strong> - We have identified and fixed the underlying issue, and are recovering now. Normal status, including processing backlogs will likely take some time. We are monitoring the situation.</p><p><small>Jan <var data-var='date'>30</var>, <var data-var='time'>14:27</var> UTC</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Jan <var data-var='date'>30</var>, <var data-var='time'>14:26</var> UTC</small><br><strong>Investigating</strong> - Our RIPE Atlas infrastructure has been having issues since approximately 13:10 CET. <br /><br />We are working to find a solution.</p>tag:status.ripe.net,2005:Incident/198177072024-01-24T19:12:39Z2024-01-24T19:12:39ZRIS data processing delay<p><small>Jan <var data-var='date'>24</var>, <var data-var='time'>19:12</var> UTC</small><br><strong>Resolved</strong> - RIS services have been restored.</p><p><small>Jan <var data-var='date'>24</var>, <var data-var='time'>14:49</var> UTC</small><br><strong>Monitoring</strong> - The hardware problem has been fixed. The data flow is going back to normal conditions.<br />We are still observing not up-to-date information on the RIS Looking Glass.</p><p><small>Jan <var data-var='date'>24</var>, <var data-var='time'>13:21</var> UTC</small><br><strong>Investigating</strong> - As a consequence of a hardware problem affecting a broker, the RIS service has been experiencing delay in the data processing since this morning.<br />The delay is affecting the creation of MRT files (RIS Raw Data).<br />Furthermore, you may observe that data provided by RIPE Stat are not up-to-date.<br />We are currently working to resolve the issue.</p>tag:status.ripe.net,2005:Incident/197364462024-01-18T20:00:42Z2024-01-18T20:00:42ZPlanned Maintenance: www.ripe.net<p><small>Jan <var data-var='date'>18</var>, <var data-var='time'>20:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Jan <var data-var='date'>18</var>, <var data-var='time'>17:02</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jan <var data-var='date'>17</var>, <var data-var='time'>10:44</var> UTC</small><br><strong>Scheduled</strong> - We will carry out planned maintenance on www.ripe.net. During this time, our website might be unavailable or not fully functional. This maintenance will take place only for webpages on www.ripe.net and should not affect any other services and subdomains hosted on the ripe.net domain.</p>tag:status.ripe.net,2005:Incident/196446432024-01-18T17:10:08Z2024-01-18T17:10:08ZPlanned Maintenance: LIR Portal, RIPE NCC Access, RPKI Dashboard, Billing & Payments, RIPE Database<p><small>Jan <var data-var='date'>18</var>, <var data-var='time'>17:10</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Jan <var data-var='date'>18</var>, <var data-var='time'>17:01</var> UTC</small><br><strong>Update</strong> - Scheduled maintenance is finished earlier than planned, all the services mentioned are operational.</p><p><small>Jan <var data-var='date'>18</var>, <var data-var='time'>16:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jan <var data-var='date'> 8</var>, <var data-var='time'>10:52</var> UTC</small><br><strong>Scheduled</strong> - We will carry out planned maintenance on LIR Portal, RIPE NCC Access, RPKI Dashboard, Billing & Payments, RIPE Database. During this time, these services will be unavailable or not fully functional.</p>tag:status.ripe.net,2005:Incident/196870142024-01-18T12:02:20Z2024-01-18T12:02:20ZPlanned Maintenance: Document library system<p><small>Jan <var data-var='date'>18</var>, <var data-var='time'>12:02</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Jan <var data-var='date'>18</var>, <var data-var='time'>11:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jan <var data-var='date'>12</var>, <var data-var='time'>10:55</var> UTC</small><br><strong>Scheduled</strong> - We will carry out planned maintenance on our document library system on the 18 of January the time window for the maintenance is 11:00 UTC - 12:00 UTC. During this time, the tickets section in the LIR portal will be unavailable or not fully functional.</p>tag:status.ripe.net,2005:Incident/197303132024-01-17T10:21:23Z2024-01-17T10:21:23ZRIPE Atlas processing issue<p><small>Jan <var data-var='date'>17</var>, <var data-var='time'>10:21</var> UTC</small><br><strong>Resolved</strong> - The Atlas result processing is working normally.</p><p><small>Jan <var data-var='date'>16</var>, <var data-var='time'>23:59</var> UTC</small><br><strong>Monitoring</strong> - We identified a problem in a backend node that caused a stop of the Atlas result processing.<br />The exclusion of the problematic node from the cluster helped resolving the issue.<br />The result processing restarted around 23.20 UTC. Delays are decreasing.</p><p><small>Jan <var data-var='date'>16</var>, <var data-var='time'>22:42</var> UTC</small><br><strong>Investigating</strong> - Around 21.00 UTC the result processing of RIPE Atlas stopped.<br />We are current investigating the cause.</p>tag:status.ripe.net,2005:Incident/196014282024-01-08T11:00:21Z2024-01-08T11:00:21ZRPKI monthly maintenance<p><small>Jan <var data-var='date'> 8</var>, <var data-var='time'>11:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Jan <var data-var='date'> 8</var>, <var data-var='time'>10:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jan <var data-var='date'> 3</var>, <var data-var='time'>11:41</var> UTC</small><br><strong>Scheduled</strong> - We will be undergoing scheduled maintenance during this time.</p>tag:status.ripe.net,2005:Incident/195965382024-01-03T06:49:50Z2024-01-03T06:49:50ZNot possible to see invoices because of an issue on a third party invoicing system<p><small>Jan <var data-var='date'> 3</var>, <var data-var='time'>06:49</var> UTC</small><br><strong>Resolved</strong> - The issue is resolved. The third party billing system is operational again.</p><p><small>Jan <var data-var='date'> 2</var>, <var data-var='time'>22:49</var> UTC</small><br><strong>Identified</strong> - At the moment, in LIR portal, it is not possible to see invoices for LIRs. This is caused by an issue on the third party invoicing system we use (AFAS). In AFAS status page, it is announced that they are experiencing an issue and are working on resolving it.</p>tag:status.ripe.net,2005:Incident/194949672023-12-21T11:12:02Z2023-12-21T11:12:02ZDelays in Atlas result processing<p><small>Dec <var data-var='date'>21</var>, <var data-var='time'>11:12</var> UTC</small><br><strong>Resolved</strong> - Atlas processing delay is back to normal</p><p><small>Dec <var data-var='date'>21</var>, <var data-var='time'>08:21</var> UTC</small><br><strong>Monitoring</strong> - We have identified the backend server that caused the problem. Delays are decreasing. We are constantly monitoring.</p><p><small>Dec <var data-var='date'>21</var>, <var data-var='time'>05:20</var> UTC</small><br><strong>Investigating</strong> - Due to problems affecting the backend, Atlas results processing is delayed since 2am UTC. <br />We are investigating.</p>tag:status.ripe.net,2005:Incident/194877042023-12-20T12:40:52Z2023-12-20T12:40:52Zaccess.ripe.net unavailable impacting multiple services<p><small>Dec <var data-var='date'>20</var>, <var data-var='time'>12:40</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Dec <var data-var='date'>20</var>, <var data-var='time'>10:24</var> UTC</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Dec <var data-var='date'>20</var>, <var data-var='time'>10:15</var> UTC</small><br><strong>Identified</strong> - An issue affecting two underlying services has been identified. We are continue working on the issue. Services are partially available at the moment.</p><p><small>Dec <var data-var='date'>20</var>, <var data-var='time'>10:06</var> UTC</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Dec <var data-var='date'>20</var>, <var data-var='time'>09:55</var> UTC</small><br><strong>Identified</strong> - We have found a failure in a second system and are working on a fix.</p><p><small>Dec <var data-var='date'>20</var>, <var data-var='time'>09:52</var> UTC</small><br><strong>Monitoring</strong> - The service has been restored. We fill follow up with more details later.</p><p><small>Dec <var data-var='date'>20</var>, <var data-var='time'>09:40</var> UTC</small><br><strong>Investigating</strong> - We are currently investigating the issue.<br /><br />This downtime is unrelated to the earlier maintenance to the RPKI services.</p>