← Back to erine.email
erine.email» status

Incidents, interventions and announcements.

Last update: 2026-07-16, 20:13 UTC

🚀

The web interface and the service emails have been completely redesigned. I hope you'll enjoy this new look!

🚀

A new view popped in the web interface, to see the details of a disposable address. Among others, a new editable "comment" field. Enjoy!

🚧 Resolved

Everything is up to date. Intervention completed successfully.

🚧

The upgrade succeeded. Service up and running. Finalization in progress… (setup of the backups & monitoring, update the main Git branch, the issue, the documentation)

🚧

The major upgrade is ongoing… ETA: 17:43 UTC.

🚧

A major upgrade is planned on Thursday, 2026-04-23 between 16:00 and 20:00. During that time, a 1 hour downtime (max) is expected. During that downtime, the website will be unavailable, and the emails will be delayed (not lost).

Resolved

The email deliveries are no longer delayed. The flooding has been absorbed.

The issue will be definitively fixed in #60.

20 more minutes to recover completely from the flood. If you want to help, please unsubscribe from the Facebook & Instagram notifications you don't read.

A huge number of emails has been sent from Meta to lots of users. Delays up to 20 minutes are expected in email delivery. Recovery ETA: 19:10 UTC.

Resolved

The old server finished delivering all its emails. No more remain in queue. R.I.P, old server, the incident is over.

2.0K emails left in queue. The incident will be definitively over within an hour.

The new erine.email server continues to deliver emails instantly. This is really good news and proves its long-term stability.

The old server continues to deliver emails in queue. 80K left.

The erine.email service has been moved to another server and therefore, our IP changed. Since then, GMail no longer rejects the emails, and the new incoming emails are delivered instantly.

143K emails are still stuck on the previous server. They're being delivered at a low pace. Several days should be required to deliver them all.

The previous steps of this incident can be found on X: thread.