IETF Status - Incident history https://status.ietf.org IETF Sat, 4 Apr 2026 02:58:15 +0000 BibXML outage Type: Incident Duration: 30 minutes Affected Components: BibXML Apr 4, 02:58:15 GMT+0 - Investigating - BibXML cannot be accessed at the moment. This incident was created by an automated monitoring service. Apr 4, 03:28:16 GMT+0 - Resolved - BibXML is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 30 minutes

Affected Components:

<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> ]]> Sat, 4 Apr 2026 02:58:15 +0000 https://status.ietf.org/incident/cmnjqt8nz05uozap3ucj9a803 https://status.ietf.org/incident/cmnjqt8nz05uozap3ucj9a803 BibXML outage Type: Incident Duration: 30 minutes Affected Components: BibXML Apr 4, 02:24:15 GMT+0 - Investigating - BibXML cannot be accessed at the moment. This incident was created by an automated monitoring service. Apr 4, 02:54:16 GMT+0 - Resolved - BibXML is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 30 minutes

Affected Components:

<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> ]]> Sat, 4 Apr 2026 02:24:15 +0000 https://status.ietf.org/incident/cmnjplilk05ung8kpzyywiawv https://status.ietf.org/incident/cmnjplilk05ung8kpzyywiawv BibXML outage Type: Incident Duration: 55 minutes Affected Components: BibXML Apr 3, 06:27:15 GMT+0 - Investigating - BibXML cannot be accessed at the moment. This incident was created by an automated monitoring service. Apr 3, 07:22:16 GMT+0 - Resolved - BibXML is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 55 minutes

Affected Components:

<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> ]]> Fri, 3 Apr 2026 06:27:15 +0000 https://status.ietf.org/incident/cmniiu5xs0b87otzhw14v1mp1 https://status.ietf.org/incident/cmniiu5xs0b87otzhw14v1mp1 RFC-Editor outage Type: Incident Duration: 15 minutes Affected Components: RFC-Editor Mar 31, 14:48:10 GMT+0 - Investigating - RFC-Editor cannot be accessed at the moment. This incident was created by an automated monitoring service. Mar 31, 15:03:11 GMT+0 - Resolved - RFC-Editor is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 15 minutes

Affected Components:

<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> ]]> Tue, 31 Mar 2026 14:48:10 +0000 https://status.ietf.org/incident/cmneqesi00ct0ar2ubijnsqqa https://status.ietf.org/incident/cmneqesi00ct0ar2ubijnsqqa Zulip outage Type: Incident Duration: 10 minutes Affected Components: Zulip Mar 23, 01:09:13 GMT+0 - Investigating - Zulip cannot be accessed at the moment. This incident was created by an automated monitoring service. Mar 23, 01:19:14 GMT+0 - Resolved - Zulip is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 10 minutes

Affected Components:

<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> ]]> Mon, 23 Mar 2026 01:09:13 +0000 https://status.ietf.org/incident/cmn2hmt2w0vnphvwrt6q2lgu3 https://status.ietf.org/incident/cmn2hmt2w0vnphvwrt6q2lgu3 BibXML outage Type: Incident Duration: 1 day, 2 hours and 15 minutes Affected Components: BibXML Mar 22, 00:27:15 GMT+0 - Investigating - BibXML cannot be accessed at the moment. This incident was created by an automated monitoring service. Mar 23, 02:42:16 GMT+0 - Resolved - BibXML is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 1 day, 2 hours and 15 minutes

Affected Components:

<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> ]]> Sun, 22 Mar 2026 00:27:15 +0000 https://status.ietf.org/incident/cmn10oz9l0g06995pb3ch1sz7 https://status.ietf.org/incident/cmn10oz9l0g06995pb3ch1sz7 Datatracker outage Type: Incident Duration: 5 minutes Affected Components: Datatracker Mar 20, 15:09:10 GMT+0 - Investigating - Datatracker cannot be accessed at the moment. This incident was created by an automated monitoring service. Mar 20, 15:14:10 GMT+0 - Resolved - Datatracker is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 5 minutes

Affected Components:

<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> ]]> Fri, 20 Mar 2026 15:09:10 +0000 https://status.ietf.org/incident/cmmz1bf5o03h310lhjmwyv9og https://status.ietf.org/incident/cmmz1bf5o03h310lhjmwyv9og RFC-Editor outage Type: Incident Duration: 5 minutes Affected Components: RFC-Editor Mar 12, 10:59:10 GMT+0 - Investigating - RFC-Editor cannot be accessed at the moment. This incident was created by an automated monitoring service. Mar 12, 11:04:11 GMT+0 - Resolved - RFC-Editor is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 5 minutes

Affected Components:

<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> ]]> Thu, 12 Mar 2026 10:59:10 +0000 https://status.ietf.org/incident/cmmncv3xf014a6f2fkh8os32b https://status.ietf.org/incident/cmmncv3xf014a6f2fkh8os32b RFC-Editor outage Type: Incident Duration: 10 minutes Affected Components: RFC-Editor Mar 9, 07:15:10 GMT+0 - Investigating - RFC-Editor cannot be accessed at the moment. This incident was created by an automated monitoring service. Mar 9, 07:25:11 GMT+0 - Resolved - RFC-Editor is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 10 minutes

Affected Components:

<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> ]]> Mon, 9 Mar 2026 07:15:10 +0000 https://status.ietf.org/incident/cmmiujhmj002sm2nja5tzpn4s https://status.ietf.org/incident/cmmiujhmj002sm2nja5tzpn4s RFC-Editor outage Type: Incident Duration: 15 minutes Affected Components: RFC-Editor Mar 1, 04:24:10 GMT+0 - Investigating - RFC-Editor cannot be accessed at the moment. This incident was created by an automated monitoring service. Mar 1, 04:39:11 GMT+0 - Resolved - RFC-Editor is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 15 minutes

Affected Components:

<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> ]]> Sun, 1 Mar 2026 04:24:10 +0000 https://status.ietf.org/incident/cmm78wrk60infglvzj8sr4kse https://status.ietf.org/incident/cmm78wrk60infglvzj8sr4kse RFC-Editor outage Type: Incident Duration: 5 minutes Affected Components: RFC-Editor Feb 27, 07:08:10 GMT+0 - Investigating - RFC-Editor cannot be accessed at the moment. This incident was created by an automated monitoring service. Feb 27, 07:13:11 GMT+0 - Resolved - RFC-Editor is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 5 minutes

Affected Components:

<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> ]]> Fri, 27 Feb 2026 07:08:10 +0000 https://status.ietf.org/incident/cmm4jvyx20z15n9o04mfxs21w https://status.ietf.org/incident/cmm4jvyx20z15n9o04mfxs21w Datatracker outage Type: Incident Duration: 5 minutes Affected Components: Datatracker Feb 26, 00:43:10 GMT+0 - Investigating - Datatracker cannot be accessed at the moment. This incident was created by an automated monitoring service. Feb 26, 00:48:10 GMT+0 - Resolved - Datatracker is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 5 minutes

Affected Components:

<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> ]]> Thu, 26 Feb 2026 00:43:10 +0000 https://status.ietf.org/incident/cmm2qozwm0jzev24kw7x60kls https://status.ietf.org/incident/cmm2qozwm0jzev24kw7x60kls RFC-Editor outage Type: Incident Duration: 5 minutes Affected Components: RFC-Editor Feb 24, 22:47:10 GMT+0 - Investigating - RFC-Editor cannot be accessed at the moment. This incident was created by an automated monitoring service. Feb 24, 22:52:11 GMT+0 - Resolved - RFC-Editor is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 5 minutes

Affected Components:

<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> ]]> Tue, 24 Feb 2026 22:47:10 +0000 https://status.ietf.org/incident/cmm173z4700ehg3s9w5s8fmcn https://status.ietf.org/incident/cmm173z4700ehg3s9w5s8fmcn RFC-Editor outage Type: Incident Duration: 5 minutes Affected Components: RFC-Editor Feb 24, 06:16:10 GMT+0 - Investigating - RFC-Editor cannot be accessed at the moment. This incident was created by an automated monitoring service. Feb 24, 06:21:11 GMT+0 - Resolved - RFC-Editor is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 5 minutes

Affected Components:

<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> ]]> Tue, 24 Feb 2026 06:16:10 +0000 https://status.ietf.org/incident/cmm07pjhm0f1js46fnc6d6eu1 https://status.ietf.org/incident/cmm07pjhm0f1js46fnc6d6eu1 RFC-Editor outage Type: Incident Duration: 5 minutes Affected Components: RFC-Editor Feb 24, 02:21:10 GMT+0 - Investigating - RFC-Editor cannot be accessed at the moment. This incident was created by an automated monitoring service. Feb 24, 02:26:11 GMT+0 - Resolved - RFC-Editor is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 5 minutes

Affected Components:

<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> ]]> Tue, 24 Feb 2026 02:21:10 +0000 https://status.ietf.org/incident/cmlzzbbv60kawrospwqp4p207 https://status.ietf.org/incident/cmlzzbbv60kawrospwqp4p207 RFC-Editor outage Type: Incident Duration: 5 minutes Affected Components: RFC-Editor Feb 23, 03:40:10 GMT+0 - Investigating - RFC-Editor cannot be accessed at the moment. This incident was created by an automated monitoring service. Feb 23, 03:45:11 GMT+0 - Resolved - RFC-Editor is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 5 minutes

Affected Components:

<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> ]]> Mon, 23 Feb 2026 03:40:10 +0000 https://status.ietf.org/incident/cmlymp2je051urosp1a1tayve https://status.ietf.org/incident/cmlymp2je051urosp1a1tayve RFC-Editor outage Type: Incident Duration: 10 minutes Affected Components: RFC-Editor Feb 20, 13:29:10 GMT+0 - Investigating - RFC-Editor cannot be accessed at the moment. This incident was created by an automated monitoring service. Feb 20, 13:39:11 GMT+0 - Resolved - RFC-Editor is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 10 minutes

Affected Components:

<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> ]]> Fri, 20 Feb 2026 13:29:10 +0000 https://status.ietf.org/incident/cmluxez2m05xnv57q5agpfdt2 https://status.ietf.org/incident/cmluxez2m05xnv57q5agpfdt2 RFC-Editor outage Type: Incident Duration: 5 minutes Affected Components: RFC-Editor Feb 20, 11:50:10 GMT+0 - Investigating - RFC-Editor cannot be accessed at the moment. This incident was created by an automated monitoring service. Feb 20, 11:55:11 GMT+0 - Resolved - RFC-Editor is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 5 minutes

Affected Components:

<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> ]]> Fri, 20 Feb 2026 11:50:10 +0000 https://status.ietf.org/incident/cmlutvns200rwpaobz17c2yym https://status.ietf.org/incident/cmlutvns200rwpaobz17c2yym SMTP IPv6 Issues Type: Incident Duration: 15 minutes Affected Components: SMTP Feb 12, 02:04:19 GMT+0 - Investigating - SMTP cannot be accessed over IPv6 at the moment. This incident was created by an automated monitoring service. Feb 12, 02:19:19 GMT+0 - Resolved - SMTP is now operational over IPv6! This update was created by an automated monitoring service. Type: Incident

Duration: 15 minutes

Affected Components:

<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> ]]> Thu, 12 Feb 2026 02:04:18 +0000 https://status.ietf.org/incident/cmlitffed038h708il7mcre98 https://status.ietf.org/incident/cmlitffed038h708il7mcre98 SMTP outage Type: Incident Duration: 10 minutes Affected Components: SMTP Feb 11, 15:21:11 GMT+0 - Investigating - SMTP cannot be accessed at the moment. This incident was created by an automated monitoring service. Feb 11, 15:31:12 GMT+0 - Resolved - SMTP is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 10 minutes

Affected Components:

<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> ]]> Wed, 11 Feb 2026 15:21:11 +0000 https://status.ietf.org/incident/cmli6gd7u04a8qszgftlxq4cr https://status.ietf.org/incident/cmli6gd7u04a8qszgftlxq4cr RFC-Editor outage Type: Incident Duration: 10 minutes Affected Components: RFC-Editor Feb 10, 21:05:10 GMT+0 - Investigating - RFC-Editor cannot be accessed at the moment. This incident was created by an automated monitoring service. Feb 10, 21:15:11 GMT+0 - Resolved - RFC-Editor is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 10 minutes

Affected Components:

<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> ]]> Tue, 10 Feb 2026 21:05:10 +0000 https://status.ietf.org/incident/cmlh3avk402z3112iqtprr1yr https://status.ietf.org/incident/cmlh3avk402z3112iqtprr1yr RFC-Editor outage Type: Incident Duration: 5 minutes Affected Components: RFC-Editor Feb 10, 17:05:10 GMT+0 - Investigating - RFC-Editor cannot be accessed at the moment. This incident was created by an automated monitoring service. Feb 10, 17:10:11 GMT+0 - Resolved - RFC-Editor is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 5 minutes

Affected Components:

<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> ]]> Tue, 10 Feb 2026 17:05:10 +0000 https://status.ietf.org/incident/cmlguq8et0ahx132rlkwolakn https://status.ietf.org/incident/cmlguq8et0ahx132rlkwolakn SMTP outage Type: Incident Duration: 5 minutes Affected Components: SMTP Feb 8, 17:01:11 GMT+0 - Investigating - SMTP cannot be accessed at the moment. This incident was created by an automated monitoring service. Feb 8, 17:06:12 GMT+0 - Resolved - SMTP is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 5 minutes

Affected Components:

<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> ]]> Sun, 8 Feb 2026 17:01:11 +0000 https://status.ietf.org/incident/cmldzpes80l1f10jyn1zgoi0q https://status.ietf.org/incident/cmldzpes80l1f10jyn1zgoi0q BibXML outage Type: Incident Duration: 5 minutes Affected Components: BibXML Feb 7, 05:44:15 GMT+0 - Investigating - BibXML cannot be accessed at the moment. This incident was created by an automated monitoring service. Feb 7, 05:49:16 GMT+0 - Resolved - BibXML is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 5 minutes

Affected Components:

<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> ]]> Sat, 7 Feb 2026 05:44:15 +0000 https://status.ietf.org/incident/cmlbw30hf03fa1qtdkv02d3so https://status.ietf.org/incident/cmlbw30hf03fa1qtdkv02d3so BibXML outage Type: Incident Duration: 5 minutes Affected Components: BibXML Feb 7, 05:17:15 GMT+0 - Investigating - BibXML cannot be accessed at the moment. This incident was created by an automated monitoring service. Feb 7, 05:22:16 GMT+0 - Resolved - BibXML is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 5 minutes

Affected Components:

<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> ]]> Sat, 7 Feb 2026 05:17:15 +0000 https://status.ietf.org/incident/cmlbv4aio037zvoi5ms5tmt16 https://status.ietf.org/incident/cmlbv4aio037zvoi5ms5tmt16 Zulip migration Type: Maintenance Duration: 8 minutes Affected Components: Zulip Aug 18, 21:15:01 GMT+0 - Identified - Maintenance is now in progress Aug 18, 21:23:13 GMT+0 - Completed - Maintenance has completed successfully. Aug 18, 21:15:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Type: Maintenance

Duration: 8 minutes

Affected Components:

<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> ]]> Mon, 18 Aug 2025 21:15:00 +0000 https://status.ietf.org/maintenance/cmehm40vj000iqb6xqaa2yu64 https://status.ietf.org/maintenance/cmehm40vj000iqb6xqaa2yu64 Datatracker and Mail Archive Cloud Migration Type: Maintenance Duration: 1 hour and 8 minutes Affected Components: Datatracker, Mail Archive Aug 14, 19:00:00 GMT+0 - Identified - 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. Aug 14, 20:07:47 GMT+0 - Completed - Maintenance has completed successfully. Aug 14, 19:00:01 GMT+0 - Identified - Maintenance is now in progress Type: Maintenance

Duration: 1 hour and 8 minutes

Affected Components: ,

<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> ]]> Thu, 14 Aug 2025 19:00:00 +0000 https://status.ietf.org/maintenance/cme0m0tpq003a2lhkxs8hgdm8 https://status.ietf.org/maintenance/cme0m0tpq003a2lhkxs8hgdm8 Upgrading the infrastructure hosting datatracker.ietf.org, mailarchive.ietf.org, and www.ietf.org in preparation for IETF123 Type: Maintenance Duration: 1 hour Affected Components: IETF Website, Datatracker, Mail Archive Jul 10, 19:45:00 GMT+0 - Identified - These services will return as soon as possible. Jul 10, 20:45:00 GMT+0 - Completed - Maintenance is completed. Type: Maintenance

Duration: 1 hour

Affected Components: , ,

<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> ]]> Thu, 10 Jul 2025 19:45:00 +0000 https://status.ietf.org/maintenance/cmcxtoaf601yqh5y67m4j6qrd https://status.ietf.org/maintenance/cmcxtoaf601yqh5y67m4j6qrd IETF email service transition Type: Maintenance Duration: 3 hours Affected Components: , Mail Services → Feb 24, 12:00:00 GMT+0 - Completed - Maintenance has completed successfully Feb 24, 09:00:01 GMT+0 - Identified - Maintenance is now in progress Feb 24, 09:00:00 GMT+0 - Identified - 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) Type: Maintenance

Duration: 3 hours

Affected Components:

<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> ]]> Mon, 24 Feb 2025 09:00:00 +0000 https://status.ietf.org/maintenance/cm75a6wcz0046ac6lxqochhsd https://status.ietf.org/maintenance/cm75a6wcz0046ac6lxqochhsd IETF Mail Services Migration Type: Maintenance Duration: 11 minutes Affected Components: , Mail Services → Aug 29, 12:10:35 GMT+0 - Completed - Migration has been deferred to a future time. Aug 29, 12:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Aug 29, 12:00:01 GMT+0 - Identified - Maintenance is now in progress Type: Maintenance

Duration: 11 minutes

Affected Components:

<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> ]]> Thu, 29 Aug 2024 12:00:00 +0000 https://status.ietf.org/maintenance/cm0ejgr4t001ny98l4m8889no https://status.ietf.org/maintenance/cm0ejgr4t001ny98l4m8889no IETF Mail Services Migration Type: Maintenance Duration: 24 minutes Affected Components: , Mail Services → Aug 27, 12:24:25 GMT+0 - Completed - Migration was deferred to a future date. Aug 27, 12:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Aug 27, 12:00:01 GMT+0 - Identified - Maintenance is now in progress Type: Maintenance

Duration: 24 minutes

Affected Components:

<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> ]]> Tue, 27 Aug 2024 12:00:00 +0000 https://status.ietf.org/maintenance/cm0bguq72003qe820g0bgzsev https://status.ietf.org/maintenance/cm0bguq72003qe820g0bgzsev Datatracker Maintenance Type: Maintenance Duration: 15 minutes Affected Components: Datatracker Aug 7, 20:01:01 GMT+0 - Identified - Maintenance is now in progress Aug 7, 20:16:24 GMT+0 - Completed - Maintenance completed. Aug 7, 20:01:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Type: Maintenance

Duration: 15 minutes

Affected Components:

<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> ]]> Wed, 7 Aug 2024 20:01:00 +0000 https://status.ietf.org/maintenance/clzk9x8g6583819i8ooaq1gzeal https://status.ietf.org/maintenance/clzk9x8g6583819i8ooaq1gzeal Notes (Hedgedoc) Migration Type: Maintenance Duration: 12 minutes Affected Components: Notes (HedgeDoc) Jul 31, 02:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Jul 31, 02:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 31, 02:12:19 GMT+0 - Completed - Migration is completed. Type: Maintenance

Duration: 12 minutes

Affected Components:

<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> ]]> Wed, 31 Jul 2024 02:00:00 +0000 https://status.ietf.org/maintenance/clz971wik154332hvn5qhjrnklj https://status.ietf.org/maintenance/clz971wik154332hvn5qhjrnklj IETF Wiki migration Type: Maintenance Duration: 19 minutes Affected Components: IETF Wiki Jul 28, 05:40:46 GMT+0 - Completed - Migration completed. Jul 28, 05:22:01 GMT+0 - Identified - Maintenance is now in progress Jul 28, 05:22:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Type: Maintenance

Duration: 19 minutes

Affected Components:

<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> ]]> Sun, 28 Jul 2024 05:22:00 +0000 https://status.ietf.org/maintenance/clz5457y1166280hlodk0721tea https://status.ietf.org/maintenance/clz5457y1166280hlodk0721tea Registration website migration Type: Maintenance Duration: 29 minutes Affected Components: Registration Website Jul 26, 23:09:16 GMT+0 - Completed - Migration is completed. Jul 26, 22:40:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Jul 26, 22:40:01 GMT+0 - Identified - Maintenance is now in progress Type: Maintenance

Duration: 29 minutes

Affected Components:

<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> ]]> Fri, 26 Jul 2024 22:40:00 +0000 https://status.ietf.org/maintenance/clz3acnjz36910h4n0l7a3u6qx https://status.ietf.org/maintenance/clz3acnjz36910h4n0l7a3u6qx Migration to new cloud infrastructure Type: Maintenance Duration: 2 hours and 4 minutes Affected Components: IETF Website, Datatracker, Mail Archive Jun 20, 18:00:00 GMT+0 - Identified - 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: <https://www.ietf.org/blog/it-infrastructure-outage-2024-06-20/> The blog post will be updated once this phase of the IT infrastructure transition is complete. Jun 20, 20:04:04 GMT+0 - Completed - Datatracker, Mail Archive, [www.ietf.org](http://www.ietf.org), IMAP and rsync have been migrated successfully and are now back online. Jun 20, 18:00:01 GMT+0 - Identified - Maintenance is now in progress Type: Maintenance

Duration: 2 hours and 4 minutes

Affected Components: , ,

<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: <https://www.ietf.org/blog/it-infrastructure-outage-2024-06-20/> 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> ]]> Thu, 20 Jun 2024 18:00:00 +0000 https://status.ietf.org/maintenance/clxf1lurp77124bsos4i5jfja8 https://status.ietf.org/maintenance/clxf1lurp77124bsos4i5jfja8