<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:status.ietf.org,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://status.ietf.org"/>
  <link rel="self" type="application/atom+xml" href="https://status.ietf.org/history.atom"/>
  <title>IETF Status - Incident history</title>
  <updated>2026-04-04T02:58:15.455+00:00</updated>
  <author>
    <name>IETF</name>
  </author>
  
<entry>
  <id>tag:status.ietf.org,2005:Incident/cmnjqt8nz05uozap3ucj9a803</id>
  <published>2026-04-04T02:58:15.455+00:00</published>
  <updated>2026-04-04T02:58:15.470+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ietf.org/incident/cmnjqt8nz05uozap3ucj9a803"/>
  <title>BibXML outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 30 minutes</p>
    <p><strong>Affected Components:</strong> BibXML</p>
    <p><small>Apr <var data-var='date'> 4</var>, <var data-var='time'>02:58:15</var> GMT+0</small><br /><strong>Investigating</strong> -
  BibXML cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Apr <var data-var='date'> 4</var>, <var data-var='time'>03:28:16</var> GMT+0</small><br /><strong>Resolved</strong> -
  BibXML is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ietf.org,2005:Incident/cmnjplilk05ung8kpzyywiawv</id>
  <published>2026-04-04T02:24:15.464+00:00</published>
  <updated>2026-04-04T02:24:15.480+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ietf.org/incident/cmnjplilk05ung8kpzyywiawv"/>
  <title>BibXML outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 30 minutes</p>
    <p><strong>Affected Components:</strong> BibXML</p>
    <p><small>Apr <var data-var='date'> 4</var>, <var data-var='time'>02:24:15</var> GMT+0</small><br /><strong>Investigating</strong> -
  BibXML cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Apr <var data-var='date'> 4</var>, <var data-var='time'>02:54:16</var> GMT+0</small><br /><strong>Resolved</strong> -
  BibXML is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ietf.org,2005:Incident/cmniiu5xs0b87otzhw14v1mp1</id>
  <published>2026-04-03T06:27:15.471+00:00</published>
  <updated>2026-04-03T06:27:15.479+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ietf.org/incident/cmniiu5xs0b87otzhw14v1mp1"/>
  <title>BibXML outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 55 minutes</p>
    <p><strong>Affected Components:</strong> BibXML</p>
    <p><small>Apr <var data-var='date'> 3</var>, <var data-var='time'>06:27:15</var> GMT+0</small><br /><strong>Investigating</strong> -
  BibXML cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Apr <var data-var='date'> 3</var>, <var data-var='time'>07:22:16</var> GMT+0</small><br /><strong>Resolved</strong> -
  BibXML is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ietf.org,2005:Incident/cmneqesi00ct0ar2ubijnsqqa</id>
  <published>2026-03-31T14:48:10.440+00:00</published>
  <updated>2026-03-31T14:48:10.447+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ietf.org/incident/cmneqesi00ct0ar2ubijnsqqa"/>
  <title>RFC-Editor outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 15 minutes</p>
    <p><strong>Affected Components:</strong> RFC-Editor</p>
    <p><small>Mar <var data-var='date'> 31</var>, <var data-var='time'>14:48:10</var> GMT+0</small><br /><strong>Investigating</strong> -
  RFC-Editor cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Mar <var data-var='date'> 31</var>, <var data-var='time'>15:03:11</var> GMT+0</small><br /><strong>Resolved</strong> -
  RFC-Editor is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ietf.org,2005:Incident/cmn2hmt2w0vnphvwrt6q2lgu3</id>
  <published>2026-03-23T01:09:13.784+00:00</published>
  <updated>2026-03-23T01:09:13.792+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ietf.org/incident/cmn2hmt2w0vnphvwrt6q2lgu3"/>
  <title>Zulip outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 minutes</p>
    <p><strong>Affected Components:</strong> Zulip</p>
    <p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>01:09:13</var> GMT+0</small><br /><strong>Investigating</strong> -
  Zulip cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>01:19:14</var> GMT+0</small><br /><strong>Resolved</strong> -
  Zulip is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ietf.org,2005:Incident/cmn10oz9l0g06995pb3ch1sz7</id>
  <published>2026-03-22T00:27:15.464+00:00</published>
  <updated>2026-03-22T00:27:15.471+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ietf.org/incident/cmn10oz9l0g06995pb3ch1sz7"/>
  <title>BibXML outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 2 hours and 15 minutes</p>
    <p><strong>Affected Components:</strong> BibXML</p>
    <p><small>Mar <var data-var='date'> 22</var>, <var data-var='time'>00:27:15</var> GMT+0</small><br /><strong>Investigating</strong> -
  BibXML cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>02:42:16</var> GMT+0</small><br /><strong>Resolved</strong> -
  BibXML is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ietf.org,2005:Incident/cmmz1bf5o03h310lhjmwyv9og</id>
  <published>2026-03-20T15:09:10.140+00:00</published>
  <updated>2026-03-20T15:09:10.148+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ietf.org/incident/cmmz1bf5o03h310lhjmwyv9og"/>
  <title>Datatracker outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 minutes</p>
    <p><strong>Affected Components:</strong> Datatracker</p>
    <p><small>Mar <var data-var='date'> 20</var>, <var data-var='time'>15:09:10</var> GMT+0</small><br /><strong>Investigating</strong> -
  Datatracker cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Mar <var data-var='date'> 20</var>, <var data-var='time'>15:14:10</var> GMT+0</small><br /><strong>Resolved</strong> -
  Datatracker is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ietf.org,2005:Incident/cmmncv3xf014a6f2fkh8os32b</id>
  <published>2026-03-12T10:59:10.370+00:00</published>
  <updated>2026-03-12T10:59:10.377+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ietf.org/incident/cmmncv3xf014a6f2fkh8os32b"/>
  <title>RFC-Editor outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 minutes</p>
    <p><strong>Affected Components:</strong> RFC-Editor</p>
    <p><small>Mar <var data-var='date'> 12</var>, <var data-var='time'>10:59:10</var> GMT+0</small><br /><strong>Investigating</strong> -
  RFC-Editor cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Mar <var data-var='date'> 12</var>, <var data-var='time'>11:04:11</var> GMT+0</small><br /><strong>Resolved</strong> -
  RFC-Editor is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ietf.org,2005:Incident/cmmiujhmj002sm2nja5tzpn4s</id>
  <published>2026-03-09T07:15:10.459+00:00</published>
  <updated>2026-03-09T07:15:10.481+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ietf.org/incident/cmmiujhmj002sm2nja5tzpn4s"/>
  <title>RFC-Editor outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 minutes</p>
    <p><strong>Affected Components:</strong> RFC-Editor</p>
    <p><small>Mar <var data-var='date'> 9</var>, <var data-var='time'>07:15:10</var> GMT+0</small><br /><strong>Investigating</strong> -
  RFC-Editor cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Mar <var data-var='date'> 9</var>, <var data-var='time'>07:25:11</var> GMT+0</small><br /><strong>Resolved</strong> -
  RFC-Editor is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ietf.org,2005:Incident/cmm78wrk60infglvzj8sr4kse</id>
  <published>2026-03-01T04:24:10.374+00:00</published>
  <updated>2026-03-01T04:24:10.383+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ietf.org/incident/cmm78wrk60infglvzj8sr4kse"/>
  <title>RFC-Editor outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 15 minutes</p>
    <p><strong>Affected Components:</strong> RFC-Editor</p>
    <p><small>Mar <var data-var='date'> 1</var>, <var data-var='time'>04:24:10</var> GMT+0</small><br /><strong>Investigating</strong> -
  RFC-Editor cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Mar <var data-var='date'> 1</var>, <var data-var='time'>04:39:11</var> GMT+0</small><br /><strong>Resolved</strong> -
  RFC-Editor is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ietf.org,2005:Incident/cmm4jvyx20z15n9o04mfxs21w</id>
  <published>2026-02-27T07:08:10.502+00:00</published>
  <updated>2026-02-27T07:08:10.516+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ietf.org/incident/cmm4jvyx20z15n9o04mfxs21w"/>
  <title>RFC-Editor outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 minutes</p>
    <p><strong>Affected Components:</strong> RFC-Editor</p>
    <p><small>Feb <var data-var='date'> 27</var>, <var data-var='time'>07:08:10</var> GMT+0</small><br /><strong>Investigating</strong> -
  RFC-Editor cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Feb <var data-var='date'> 27</var>, <var data-var='time'>07:13:11</var> GMT+0</small><br /><strong>Resolved</strong> -
  RFC-Editor is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ietf.org,2005:Incident/cmm2qozwm0jzev24kw7x60kls</id>
  <published>2026-02-26T00:43:10.150+00:00</published>
  <updated>2026-02-26T00:43:10.158+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ietf.org/incident/cmm2qozwm0jzev24kw7x60kls"/>
  <title>Datatracker outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 minutes</p>
    <p><strong>Affected Components:</strong> Datatracker</p>
    <p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>00:43:10</var> GMT+0</small><br /><strong>Investigating</strong> -
  Datatracker cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>00:48:10</var> GMT+0</small><br /><strong>Resolved</strong> -
  Datatracker is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ietf.org,2005:Incident/cmm173z4700ehg3s9w5s8fmcn</id>
  <published>2026-02-24T22:47:10.470+00:00</published>
  <updated>2026-02-24T22:47:10.484+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ietf.org/incident/cmm173z4700ehg3s9w5s8fmcn"/>
  <title>RFC-Editor outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 minutes</p>
    <p><strong>Affected Components:</strong> RFC-Editor</p>
    <p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>22:47:10</var> GMT+0</small><br /><strong>Investigating</strong> -
  RFC-Editor cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>22:52:11</var> GMT+0</small><br /><strong>Resolved</strong> -
  RFC-Editor is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ietf.org,2005:Incident/cmm07pjhm0f1js46fnc6d6eu1</id>
  <published>2026-02-24T06:16:10.473+00:00</published>
  <updated>2026-02-24T06:16:10.480+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ietf.org/incident/cmm07pjhm0f1js46fnc6d6eu1"/>
  <title>RFC-Editor outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 minutes</p>
    <p><strong>Affected Components:</strong> RFC-Editor</p>
    <p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>06:16:10</var> GMT+0</small><br /><strong>Investigating</strong> -
  RFC-Editor cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>06:21:11</var> GMT+0</small><br /><strong>Resolved</strong> -
  RFC-Editor is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ietf.org,2005:Incident/cmlzzbbv60kawrospwqp4p207</id>
  <published>2026-02-24T02:21:10.481+00:00</published>
  <updated>2026-02-24T02:21:10.504+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ietf.org/incident/cmlzzbbv60kawrospwqp4p207"/>
  <title>RFC-Editor outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 minutes</p>
    <p><strong>Affected Components:</strong> RFC-Editor</p>
    <p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>02:21:10</var> GMT+0</small><br /><strong>Investigating</strong> -
  RFC-Editor cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>02:26:11</var> GMT+0</small><br /><strong>Resolved</strong> -
  RFC-Editor is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ietf.org,2005:Incident/cmlymp2je051urosp1a1tayve</id>
  <published>2026-02-23T03:40:10.394+00:00</published>
  <updated>2026-02-23T03:40:10.408+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ietf.org/incident/cmlymp2je051urosp1a1tayve"/>
  <title>RFC-Editor outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 minutes</p>
    <p><strong>Affected Components:</strong> RFC-Editor</p>
    <p><small>Feb <var data-var='date'> 23</var>, <var data-var='time'>03:40:10</var> GMT+0</small><br /><strong>Investigating</strong> -
  RFC-Editor cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Feb <var data-var='date'> 23</var>, <var data-var='time'>03:45:11</var> GMT+0</small><br /><strong>Resolved</strong> -
  RFC-Editor is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ietf.org,2005:Incident/cmluxez2m05xnv57q5agpfdt2</id>
  <published>2026-02-20T13:29:10.413+00:00</published>
  <updated>2026-02-20T13:29:10.426+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ietf.org/incident/cmluxez2m05xnv57q5agpfdt2"/>
  <title>RFC-Editor outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 minutes</p>
    <p><strong>Affected Components:</strong> RFC-Editor</p>
    <p><small>Feb <var data-var='date'> 20</var>, <var data-var='time'>13:29:10</var> GMT+0</small><br /><strong>Investigating</strong> -
  RFC-Editor cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Feb <var data-var='date'> 20</var>, <var data-var='time'>13:39:11</var> GMT+0</small><br /><strong>Resolved</strong> -
  RFC-Editor is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ietf.org,2005:Incident/cmlutvns200rwpaobz17c2yym</id>
  <published>2026-02-20T11:50:10.465+00:00</published>
  <updated>2026-02-20T11:50:10.473+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ietf.org/incident/cmlutvns200rwpaobz17c2yym"/>
  <title>RFC-Editor outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 minutes</p>
    <p><strong>Affected Components:</strong> RFC-Editor</p>
    <p><small>Feb <var data-var='date'> 20</var>, <var data-var='time'>11:50:10</var> GMT+0</small><br /><strong>Investigating</strong> -
  RFC-Editor cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Feb <var data-var='date'> 20</var>, <var data-var='time'>11:55:11</var> GMT+0</small><br /><strong>Resolved</strong> -
  RFC-Editor is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ietf.org,2005:Incident/cmlitffed038h708il7mcre98</id>
  <published>2026-02-12T02:04:18.997+00:00</published>
  <updated>2026-02-12T02:04:19.012+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ietf.org/incident/cmlitffed038h708il7mcre98"/>
  <title>SMTP IPv6 Issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 15 minutes</p>
    <p><strong>Affected Components:</strong> SMTP</p>
    <p><small>Feb <var data-var='date'> 12</var>, <var data-var='time'>02:04:19</var> GMT+0</small><br /><strong>Investigating</strong> -
  SMTP cannot be accessed over IPv6 at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Feb <var data-var='date'> 12</var>, <var data-var='time'>02:19:19</var> GMT+0</small><br /><strong>Resolved</strong> -
  SMTP is now operational over IPv6! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ietf.org,2005:Incident/cmli6gd7u04a8qszgftlxq4cr</id>
  <published>2026-02-11T15:21:11.658+00:00</published>
  <updated>2026-02-11T15:21:11.668+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ietf.org/incident/cmli6gd7u04a8qszgftlxq4cr"/>
  <title>SMTP outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 minutes</p>
    <p><strong>Affected Components:</strong> SMTP</p>
    <p><small>Feb <var data-var='date'> 11</var>, <var data-var='time'>15:21:11</var> GMT+0</small><br /><strong>Investigating</strong> -
  SMTP cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Feb <var data-var='date'> 11</var>, <var data-var='time'>15:31:12</var> GMT+0</small><br /><strong>Resolved</strong> -
  SMTP is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ietf.org,2005:Incident/cmlh3avk402z3112iqtprr1yr</id>
  <published>2026-02-10T21:05:10.467+00:00</published>
  <updated>2026-02-10T21:05:10.482+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ietf.org/incident/cmlh3avk402z3112iqtprr1yr"/>
  <title>RFC-Editor outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 minutes</p>
    <p><strong>Affected Components:</strong> RFC-Editor</p>
    <p><small>Feb <var data-var='date'> 10</var>, <var data-var='time'>21:05:10</var> GMT+0</small><br /><strong>Investigating</strong> -
  RFC-Editor cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Feb <var data-var='date'> 10</var>, <var data-var='time'>21:15:11</var> GMT+0</small><br /><strong>Resolved</strong> -
  RFC-Editor is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ietf.org,2005:Incident/cmlguq8et0ahx132rlkwolakn</id>
  <published>2026-02-10T17:05:10.420+00:00</published>
  <updated>2026-02-10T17:05:10.427+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ietf.org/incident/cmlguq8et0ahx132rlkwolakn"/>
  <title>RFC-Editor outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 minutes</p>
    <p><strong>Affected Components:</strong> RFC-Editor</p>
    <p><small>Feb <var data-var='date'> 10</var>, <var data-var='time'>17:05:10</var> GMT+0</small><br /><strong>Investigating</strong> -
  RFC-Editor cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Feb <var data-var='date'> 10</var>, <var data-var='time'>17:10:11</var> GMT+0</small><br /><strong>Resolved</strong> -
  RFC-Editor is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ietf.org,2005:Incident/cmldzpes80l1f10jyn1zgoi0q</id>
  <published>2026-02-08T17:01:11.576+00:00</published>
  <updated>2026-02-08T17:01:11.583+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ietf.org/incident/cmldzpes80l1f10jyn1zgoi0q"/>
  <title>SMTP outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 minutes</p>
    <p><strong>Affected Components:</strong> SMTP</p>
    <p><small>Feb <var data-var='date'> 8</var>, <var data-var='time'>17:01:11</var> GMT+0</small><br /><strong>Investigating</strong> -
  SMTP cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Feb <var data-var='date'> 8</var>, <var data-var='time'>17:06:12</var> GMT+0</small><br /><strong>Resolved</strong> -
  SMTP is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ietf.org,2005:Incident/cmlbw30hf03fa1qtdkv02d3so</id>
  <published>2026-02-07T05:44:15.411+00:00</published>
  <updated>2026-02-07T05:44:15.423+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ietf.org/incident/cmlbw30hf03fa1qtdkv02d3so"/>
  <title>BibXML outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 minutes</p>
    <p><strong>Affected Components:</strong> BibXML</p>
    <p><small>Feb <var data-var='date'> 7</var>, <var data-var='time'>05:44:15</var> GMT+0</small><br /><strong>Investigating</strong> -
  BibXML 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'>05:49:16</var> GMT+0</small><br /><strong>Resolved</strong> -
  BibXML is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ietf.org,2005:Incident/cmlbv4aio037zvoi5ms5tmt16</id>
  <published>2026-02-07T05:17:15.455+00:00</published>
  <updated>2026-02-07T05:17:15.470+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ietf.org/incident/cmlbv4aio037zvoi5ms5tmt16"/>
  <title>BibXML outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 minutes</p>
    <p><strong>Affected Components:</strong> BibXML</p>
    <p><small>Feb <var data-var='date'> 7</var>, <var data-var='time'>05:17:15</var> GMT+0</small><br /><strong>Investigating</strong> -
  BibXML 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'>05:22:16</var> GMT+0</small><br /><strong>Resolved</strong> -
  BibXML is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ietf.org,2005:Maintenance/cmehm40vj000iqb6xqaa2yu64</id>
  <published>2025-08-18T21:15:00.000+00:00</published>
  <updated>2025-08-18T21:15:01.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ietf.org/maintenance/cmehm40vj000iqb6xqaa2yu64"/>
  <title>Zulip migration</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 8 minutes</p>
    <p><strong>Affected Components:</strong> Zulip</p>
    <p><small>Aug <var data-var='date'> 18</var>, <var data-var='time'>21:15:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Aug <var data-var='date'> 18</var>, <var data-var='time'>21:23:13</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully..</p>
<p><small>Aug <var data-var='date'> 18</var>, <var data-var='time'>21:15:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are planning for a scheduled maintenance during that time..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ietf.org,2005:Maintenance/cme0m0tpq003a2lhkxs8hgdm8</id>
  <published>2025-08-14T19:00:00.000+00:00</published>
  <updated>2025-08-14T19:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ietf.org/maintenance/cme0m0tpq003a2lhkxs8hgdm8"/>
  <title>Datatracker and Mail Archive Cloud Migration</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 8 minutes</p>
    <p><strong>Affected Components:</strong> Datatracker, Mail Archive</p>
    <p><small>Aug <var data-var='date'> 14</var>, <var data-var='time'>19:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are planning for a scheduled maintenance during that time to allow for a change in the underlying cloud infrastructure, improving performance, reliability, and manageability of the affected services.

Datatracker and Mail Archive will be inaccessible during that time. Furthermore, authentication via Datatracker will not be possible for any service that relies on it..</p>
<p><small>Aug <var data-var='date'> 14</var>, <var data-var='time'>20:07:47</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully..</p>
<p><small>Aug <var data-var='date'> 14</var>, <var data-var='time'>19:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ietf.org,2005:Maintenance/cmcxtoaf601yqh5y67m4j6qrd</id>
  <published>2025-07-10T19:45:00.000+00:00</published>
  <updated>2025-07-10T19:45:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ietf.org/maintenance/cmcxtoaf601yqh5y67m4j6qrd"/>
  <title>Upgrading the infrastructure hosting datatracker.ietf.org, mailarchive.ietf.org, and www.ietf.org in preparation for IETF123</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> IETF Website, Datatracker, Mail Archive</p>
    <p><small>Jul <var data-var='date'> 10</var>, <var data-var='time'>19:45:00</var> GMT+0</small><br /><strong>Identified</strong> -
  These services will return as soon as possible..</p>
<p><small>Jul <var data-var='date'> 10</var>, <var data-var='time'>20:45:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance is completed..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ietf.org,2005:Maintenance/cm75a6wcz0046ac6lxqochhsd</id>
  <published>2025-02-24T09:00:00.000+00:00</published>
  <updated>2025-02-24T12:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ietf.org/maintenance/cm75a6wcz0046ac6lxqochhsd"/>
  <title>IETF email service transition</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 hours</p>
    <p><strong>Affected Components:</strong> , 
Mail Services →</p>
    <p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>12:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>09:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  The IETF email processing infrastructure transition planned for 0900-1100 UTC on 24 February may result in some delivery delays.

During the transition, delivery of messages to addresses at [ietf.org](http://ietf.org), [iab.org](http://iab.org), [irtf.org](http://irtf.org), [iesg.org](http://iesg.org), and [rfc-editor.org](http://rfc-editor.org), including email lists, will be paused. The goal is to deliver all mail sent to our addresses during the transition, once the transition is complete.

This transition is currently planned for 0900-1100 UTC 24 February 2025.

The transition is part of the project to move to a new cloud infrastructure for our email and mailing list systems. This step is being undertaken by Sirius Open Source, the [company previously selected to migrate the IETF’s email processing systems](https://mailarchive.ietf.org/arch/msg/rfp-announce/8Ar1AodThJvj6Ro0WxPnIj2SOk8/). During this step, the underlying mail processing infrastructure will remain fundamentally the same. Future work is planned to take better advantage of modern cloud technologies for our mail processing.

No other IETF systems will be affected during this transition. Further updates will be provided as soon as the transition is complete. Issues encountered after the transition should be reported to: [support@ietf.org](mailto:support@ietf.org).</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ietf.org,2005:Maintenance/cm0ejgr4t001ny98l4m8889no</id>
  <published>2024-08-29T12:00:00.000+00:00</published>
  <updated>2024-08-29T12:10:35.707+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ietf.org/maintenance/cm0ejgr4t001ny98l4m8889no"/>
  <title>IETF Mail Services Migration</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 11 minutes</p>
    <p><strong>Affected Components:</strong> , 
Mail Services →</p>
    <p><small>Aug <var data-var='date'> 29</var>, <var data-var='time'>12:10:35</var> GMT+0</small><br /><strong>Completed</strong> -
  Migration has been deferred to a future time..</p>
<p><small>Aug <var data-var='date'> 29</var>, <var data-var='time'>12:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are planning for a scheduled maintenance during that time..</p>
<p><small>Aug <var data-var='date'> 29</var>, <var data-var='time'>12:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ietf.org,2005:Maintenance/cm0bguq72003qe820g0bgzsev</id>
  <published>2024-08-27T12:00:00.000+00:00</published>
  <updated>2024-08-27T12:24:25.893+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ietf.org/maintenance/cm0bguq72003qe820g0bgzsev"/>
  <title>IETF Mail Services Migration</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 24 minutes</p>
    <p><strong>Affected Components:</strong> , 
Mail Services →</p>
    <p><small>Aug <var data-var='date'> 27</var>, <var data-var='time'>12:24:25</var> GMT+0</small><br /><strong>Completed</strong> -
  Migration was deferred to a future date..</p>
<p><small>Aug <var data-var='date'> 27</var>, <var data-var='time'>12:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are planning for a scheduled maintenance during that time..</p>
<p><small>Aug <var data-var='date'> 27</var>, <var data-var='time'>12:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ietf.org,2005:Maintenance/clzk9x8g6583819i8ooaq1gzeal</id>
  <published>2024-08-07T20:01:00.000+00:00</published>
  <updated>2024-08-07T20:01:01.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ietf.org/maintenance/clzk9x8g6583819i8ooaq1gzeal"/>
  <title>Datatracker Maintenance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 15 minutes</p>
    <p><strong>Affected Components:</strong> Datatracker</p>
    <p><small>Aug <var data-var='date'> 7</var>, <var data-var='time'>20:01:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Aug <var data-var='date'> 7</var>, <var data-var='time'>20:16:24</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance completed..</p>
<p><small>Aug <var data-var='date'> 7</var>, <var data-var='time'>20:01:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are planning for a scheduled maintenance during that time..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ietf.org,2005:Maintenance/clz971wik154332hvn5qhjrnklj</id>
  <published>2024-07-31T02:00:00.000+00:00</published>
  <updated>2024-07-31T02:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ietf.org/maintenance/clz971wik154332hvn5qhjrnklj"/>
  <title>Notes (Hedgedoc) Migration</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 12 minutes</p>
    <p><strong>Affected Components:</strong> Notes (HedgeDoc)</p>
    <p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>02:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are planning for a scheduled maintenance during that time..</p>
<p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>02:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>02:12:19</var> GMT+0</small><br /><strong>Completed</strong> -
  Migration is completed..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ietf.org,2005:Maintenance/clz5457y1166280hlodk0721tea</id>
  <published>2024-07-28T05:22:00.000+00:00</published>
  <updated>2024-07-28T05:40:46.004+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ietf.org/maintenance/clz5457y1166280hlodk0721tea"/>
  <title>IETF Wiki migration</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 19 minutes</p>
    <p><strong>Affected Components:</strong> IETF Wiki</p>
    <p><small>Jul <var data-var='date'> 28</var>, <var data-var='time'>05:40:46</var> GMT+0</small><br /><strong>Completed</strong> -
  Migration completed..</p>
<p><small>Jul <var data-var='date'> 28</var>, <var data-var='time'>05:22:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Jul <var data-var='date'> 28</var>, <var data-var='time'>05:22:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are planning for a scheduled maintenance during that time..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ietf.org,2005:Maintenance/clz3acnjz36910h4n0l7a3u6qx</id>
  <published>2024-07-26T22:40:00.000+00:00</published>
  <updated>2024-07-26T23:09:16.712+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ietf.org/maintenance/clz3acnjz36910h4n0l7a3u6qx"/>
  <title>Registration website migration</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 29 minutes</p>
    <p><strong>Affected Components:</strong> Registration Website</p>
    <p><small>Jul <var data-var='date'> 26</var>, <var data-var='time'>23:09:16</var> GMT+0</small><br /><strong>Completed</strong> -
  Migration is completed..</p>
<p><small>Jul <var data-var='date'> 26</var>, <var data-var='time'>22:40:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are planning for a scheduled maintenance during that time..</p>
<p><small>Jul <var data-var='date'> 26</var>, <var data-var='time'>22:40:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ietf.org,2005:Maintenance/clxf1lurp77124bsos4i5jfja8</id>
  <published>2024-06-20T18:00:00.000+00:00</published>
  <updated>2024-06-20T18:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ietf.org/maintenance/clxf1lurp77124bsos4i5jfja8"/>
  <title>Migration to new cloud infrastructure</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours and 4 minutes</p>
    <p><strong>Affected Components:</strong> IETF Website, Datatracker, Mail Archive</p>
    <p><small>Jun <var data-var='date'> 20</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  As part of moving to a new cloud infrastructure, the IETF Datatracker and related services will be unavailable starting at **1800 UTC on Thursday 20 June**. The outages are expected to last no more than **4 hours**; updates will be posted when availability resumes.  

The following services will transition to the new cloud infrastructure: the IETF Datatracker, the [www.ietf.org](http://www.ietf.org) website, the IETF Mailarchive, and the IMAP and rsync services.

**IMPORTANT**: Please do not plan to rely on the IETF Datatracker or the affected systems during the 4-hour window starting at 1800 UTC on Thursday 20 June.

Any service that relies on IETF Datatracker also will be affected. The following services will not be available: the IETF meeting registration system, and any interim meeting sessions that use MeetEcho integrated with the IETF Datatracker.

The following services will be impaired, with any features requiring logging in unavailable: the IETF Notes service _(editing notes will not be possible)_, IETF wikis, including [wiki.ietf.org](http://wiki.ietf.org) and [chairs.ietf.org](http://chairs.ietf.org) _(editing wiki pages will not be possible)_, and the IETF Zulip service _(any new connection will not work)_.

**OF PARTICULAR NOTE**: Posting Internet-Drafts (I-Ds) to the IETF repository will be unavailable during the outage; this includes automated posting of I-Ds via the IETF Datatracker API, such as via Github actions in repositories used to develop I-Ds.

Please see this blog post for more details:

&lt;https://www.ietf.org/blog/it-infrastructure-outage-2024-06-20/&gt; 

The blog post will be updated once this phase of the IT infrastructure transition is complete..</p>
<p><small>Jun <var data-var='date'> 20</var>, <var data-var='time'>20:04:04</var> GMT+0</small><br /><strong>Completed</strong> -
  Datatracker, Mail Archive, [www.ietf.org](http://www.ietf.org), IMAP and rsync have been migrated successfully and are now back online..</p>
<p><small>Jun <var data-var='date'> 20</var>, <var data-var='time'>18:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>

        ]]>
  </content>
</entry>

</feed>