Notice history

Jan 2025

Feb 2025

Mar 2025

Jan 2025

Feb 2025

Mar 2025

Jan 2025

Feb 2025

Mar 2025

Jan 2025

Feb 2025

Mar 2025

Jan 2025

Feb 2025

Mar 2025

Jan 2025

Feb 2025

Mar 2025

Jan 2025

Feb 2025

Mar 2025

Jan 2025

Feb 2025

Mar 2025

Jan 2025

Feb 2025

Mar 2025

Jan 2025

Feb 2025

Mar 2025

Jan 2025

Feb 2025

Mar 2025

Jan 2025

Feb 2025

Mar 2025

Jan 2025

Feb 2025

Mar 2025

Jan 2025

Feb 2025

Mar 2025

Jan 2025

Feb 2025

Mar 2025

Jan 2025

Feb 2025

Mar 2025

Jan 2025

Feb 2025

Mar 2025

Jan 2025

Feb 2025

Mar 2025

Operational

Mar 2025

Resolved
March 26, 2025 at 3:46 AM
Resolved
March 26, 2025 at 3:46 AM
RFC-Editor is now operational! This update was created by an automated monitoring service.
Investigating
March 26, 2025 at 3:41 AM
Investigating
March 26, 2025 at 3:41 AM
RFC-Editor cannot be accessed at the moment. This incident was created by an automated monitoring service.

Resolved
March 25, 2025 at 9:39 PM
Resolved
March 25, 2025 at 9:39 PM
RFC-Editor is now operational! This update was created by an automated monitoring service.
Investigating
March 25, 2025 at 9:34 PM
Investigating
March 25, 2025 at 9:34 PM
RFC-Editor cannot be accessed at the moment. This incident was created by an automated monitoring service.

Resolved
March 18, 2025 at 1:24 PM
Resolved
March 18, 2025 at 1:24 PM
Datatracker is now operational! This update was created by an automated monitoring service.
Investigating
March 18, 2025 at 1:09 PM
Investigating
March 18, 2025 at 1:09 PM
Datatracker cannot be accessed at the moment. This incident was created by an automated monitoring service.

Resolved
March 11, 2025 at 3:31 AM
Resolved
March 11, 2025 at 3:31 AM
At 23:00:00 UTC March 10, we performed what we expected to be a very
safe maintenance reboot/move of our new mail service instance onto a
more performant processor and file system. The reboot did not go as
smoothly as expected and we had to perform some low-level recovery steps
that took some time. We had exceptional help with that recovery from
both our new hosting provider (Panix) and our new Sysadmin provider (New
Machine Futures).

While we were recovering, mail was spooled and delayed - we believe that
no messages were lost during this event.

Recovery was complete around 0200 UTC March 11. Messages queued from the
datatracker were resubmitted for delivery by 0230 UTC.

After the unexpected disruption, the result is mail operations on a much
more powerful underlying system in preparation for IETF 122.

We continue to monitor the system closely. If you see anything that
doesn't look as expected, please send a report to support@ietf.org.
Monitoring
March 11, 2025 at 2:42 AM
Monitoring
March 11, 2025 at 2:42 AM
We implemented a fix and are currently monitoring the result.
Investigating
March 10, 2025 at 11:30 PM
Investigating
March 10, 2025 at 11:30 PM
We are currently investigating this incident.

Resolved
March 10, 2025 at 2:43 PM
Resolved
March 10, 2025 at 2:43 PM
Datatracker is now operational! This update was created by an automated monitoring service.
Investigating
March 10, 2025 at 2:38 PM
Investigating
March 10, 2025 at 2:38 PM
Datatracker cannot be accessed at the moment. This incident was created by an automated monitoring service.

Feb 2025

Resolved
February 27, 2025 at 5:32 AM
Resolved
February 27, 2025 at 5:32 AM
RFC-Editor is now operational! This update was created by an automated monitoring service.
Investigating
February 27, 2025 at 5:27 AM
Investigating
February 27, 2025 at 5:27 AM
RFC-Editor cannot be accessed at the moment. This incident was created by an automated monitoring service.

IETF email service transition

Completed
February 24, 2025 at 12:00 PM
Completed
February 24, 2025 at 12:00 PM
Maintenance has completed successfully
In progress
February 24, 2025 at 9:00 AM
In progress
February 24, 2025 at 9:00 AM
Maintenance is now in progress
Planned
February 24, 2025 at 9:00 AM
Planned
February 24, 2025 at 9:00 AM
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, iab.org, irtf.org, iesg.org, and 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. 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

Resolved
February 15, 2025 at 3:31 PM
Resolved
February 15, 2025 at 3:31 PM
RFC-Editor is now operational! This update was created by an automated monitoring service.
Investigating
February 15, 2025 at 3:21 PM
Investigating
February 15, 2025 at 3:21 PM
RFC-Editor cannot be accessed at the moment. This incident was created by an automated monitoring service.

Resolved
February 09, 2025 at 6:24 PM
Resolved
February 09, 2025 at 6:24 PM
Datatracker is now operational! This update was created by an automated monitoring service.
Investigating
February 09, 2025 at 6:19 PM
Investigating
February 09, 2025 at 6:19 PM
Datatracker cannot be accessed at the moment. This incident was created by an automated monitoring service.

Resolved
February 09, 2025 at 6:18 PM
Resolved
February 09, 2025 at 6:18 PM
Datatracker is now operational! This update was created by an automated monitoring service.
Investigating
February 09, 2025 at 6:08 PM
Investigating
February 09, 2025 at 6:08 PM
Datatracker cannot be accessed at the moment. This incident was created by an automated monitoring service.

Jan 2025

Resolved
January 10, 2025 at 12:14 PM
Resolved
January 10, 2025 at 12:14 PM
IETF Website is now operational! This update was created by an automated monitoring service.
Investigating
January 10, 2025 at 12:04 PM
Investigating
January 10, 2025 at 12:04 PM
IETF Website cannot be accessed at the moment. This incident was created by an automated monitoring service.

Resolved
January 09, 2025 at 9:15 PM
Resolved
January 09, 2025 at 9:15 PM
Mail Archive is now operational! This update was created by an automated monitoring service.
Investigating
January 09, 2025 at 9:10 PM
Investigating
January 09, 2025 at 9:10 PM
Mail Archive cannot be accessed at the moment. This incident was created by an automated monitoring service.

Resolved
January 07, 2025 at 4:21 AM
Resolved
January 07, 2025 at 4:21 AM
IETF Website is now operational! This update was created by an automated monitoring service.
Investigating
January 07, 2025 at 4:11 AM
Investigating
January 07, 2025 at 4:11 AM
IETF Website cannot be accessed at the moment. This incident was created by an automated monitoring service.

Resolved
January 06, 2025 at 10:47 PM
Resolved
January 06, 2025 at 10:47 PM
Datatracker is now operational! This update was created by an automated monitoring service.
Investigating
January 06, 2025 at 10:42 PM
Investigating
January 06, 2025 at 10:42 PM
Datatracker cannot be accessed at the moment. This incident was created by an automated monitoring service.

Resolved
January 05, 2025 at 2:32 PM
Resolved
January 05, 2025 at 2:32 PM
Datatracker is now operational! This update was created by an automated monitoring service.
Investigating
January 05, 2025 at 2:27 PM
Investigating
January 05, 2025 at 2:27 PM
Datatracker cannot be accessed at the moment. This incident was created by an automated monitoring service.

Jan 2025 to Mar 2025

IETF - Notice history

All systems operational

Notice history

Mar 2025

Feb 2025

Jan 2025