v0.12.22
- fix: disable content-visibility on Windows message rows so long subjects truncate 48ef1c91da10d602be7d4fd912537dc3aba5e3de - fix: resolve new-mail sender from all WS payload shapes and reconcile...
v2.12.1
- fix(test): convert test files from node:test to ava b3c6d3027 - fix: revert perf regressions from 4e3341f (concurrency, buffer copy, batch mode) 1b40b7f67 - perf: bulletproof graceful shutdow...
v2.12.0
- fix(otp): prevent auto-submit race on 2FA enable + add E2E IMAP tests 83aac65e2 - fix: reject early during graceful shutdown to prevent contradictory 421 901963d44 - fix(sieve): RFC 5703 MIME...
v0.12.21
- perf: advance reader immediately on delete, sync to server in background baf71af59418602f75d704ca80eec51ac06fddd5 - fix: never save empty drafts; discard drafts emptied before close c6978f64d38...
v0.12.20
- fix: harden push timeout handling and Tauri stub guard test 8fabb3a4b2339a139ac84fd659602e833ce783d7 - perf: optimistic calendar, contact, folder, and tab deletes 6db88be6ffc6c80c8698d5fb2a5dd5...
v0.12.19
- fix(web): lazy-load @tauri-apps/api/core in unified-push and restore web-build guards 308c407945ba4040ca09d1a41de95c8daafa8485 - docs: refresh release screenshots [skip ci] 60343cfd3df75e30b298...
v2.11.4
- perf: paginate fetch queries, defer non-vacuum maintenance, remove FTS5 rebuild c5b3f598a - fix: run maintenance inline and re-fetch handle after VACUUM 751d5a12e --- https://github.com/...
v0.12.18
- Revert "fix: lazy-load Tauri core to prevent blank page on web and add regression guards" c2e9724dc565fa472867c68ef193c49fddf718af - Revert "fix: fixed linting" 64c4652c08e22b9a73de14dc5121330c...
v0.12.16
- Revert "fix: restore screenshots and bound native push registration" c9778166655b10451fd10878cbdea88a987cdb2d --- https://github.com/forwardemail/mail.forwardemail.net/compare/v0.12.15...v0.12.16
✓ Webmail issue
Webmail at https://mail.forwardemail.net is temporarily unavailable as we fix an issue with our build pipeline. The current page is blank and will be resolved shortly.
v0.12.15
- fix: restore screenshots and bound native push registration e604a4b8e136bde9843a9d1c5d0fa44120a3e7e1 --- https://github.com/forwardemail/mail.forwardemail.net/compare/v0.12.14...v0.12.15
v0.12.14
- fix: avoid secret-scan false positive in APNS test 92c6ee0acdd79c4540cfba6e97ef697941026876 --- https://github.com/forwardemail/mail.forwardemail.net/compare/v0.12.13...v0.12.14
v0.12.13
- feat: add end-to-end mobile push notification management 9de410562273c27de4928b084fcdd7d162174e37 - fix: fixed linting f80d65b1096e486bb0bad798d7ea7f6bb7d9e7d7 - perf: add lightweight=true to a...
v2.11.3
- perf: optimize sqlite pipeline with lightweight mode, FTS5, attachment cache, and inline maintenance bc4b18b74 - perf(sqlite): comprehensive tmp/sync pipeline optimization aa0cdf272 - perf(sq...
v0.12.12
- fix: harden mobile UX and release automation 2237a96ed55b62fa5a80007d77ad302c9b08b195 - docs: synchronize CI credentials and release workflow guidance 1f44e54b48d27de8503917dd1224e78ff9075fee ...
v2.11.2
- perf(sqlite): release page cache for semi-idle DBs via PRAGMA shrink_memory b82886378 - fix: fixed test failure 1e9887beb - fix: cap worker memory to prevent GC-induced TTI, fix on-store _sto...
v0.12.11
- fix: preserve demo warning during blocked bulk delete 770612f59a40417542aa4bb792cbb1571cbcdf27 --- https://github.com/forwardemail/mail.forwardemail.net/compare/v0.12.10...v0.12.11
v0.12.8
- docs: synchronize release, push, and store guidance c2b258dc8f81824b66dfab9430f274e3818bfeca - fix: repair v0.12.7 release regression and consolidate Android to single dual-provider APK 16c5632...
v2.11.1
- fix: overhaul rate limiting with tiered system, fixed-window burst, per-recipient cap, and safe decrements 2701c2b40 - fix: redesign welcome-mailbox email with varied emoji and section headers ...
v2.11.0
- fix: prevent duplicate welcome emails and break SQLITE_NOTADB deletion loop 241aa4a1d - feat: add transport-neutral push notification fan-out 4b159e9fe --- https://github.com/forwardemai...
v2.10.9
- fix: prevent vacation responders for ARF reports, exempt truth sources from burst limit, and prevent denylisting allowlisted IPs ac40446ee - fix: ignore json file b8af9829c - fix: enforce new...
v0.12.6
- fix: guard missing message IDs during forwarding 7dedfb59de7debb136b6bdef4aff9b8c7b288f77 --- https://github.com/forwardemail/mail.forwardemail.net/compare/v0.12.5...v0.12.6
v2.10.8
- fix: harden CalDAV attachment upload, UnifiedPush SSRF, sieve ReDoS, FTS5 injection, webhook timing, ManageSieve DoS, domain-categorization SSRF, and autodiscover XML injection 2c1672517 - fix:...
v2.10.7
- fix: atomic rate limiting with burst detection, prevent duplicate payments f30827c7c - fix: TTI deadlock — dual IMAP connections per provider for parallel getMessage f13530cf4 --- https:...
v2.10.6
- fix: dummyproof SQLite resilience, suppress transient errors, fix TTI 461770505 --- https://github.com/forwardemail/forwardemail.net/compare/v2.10.5...v2.10.6
v2.10.5
- fix: bytes shadowing, ws rate-limit guard, notifier TOCTOU, POP3 STORE check, WSP response guards - on-data-mx.js: rename local 'bytes' to 'responseSize' to avoid shadowing the ...
v2.10.4
- fix: comprehensive security audit and bug fixes (30 bugs) 558f50842 --- https://github.com/forwardemail/forwardemail.net/compare/v2.10.3...v2.10.4
v0.12.5
- perf: optimistic event updates and creation 55c8950aa84849de698212fd26fe92ae13abf3af - perf: optimistic task completion and event deletion 5f22bc7d91536dba204dd62517e76a78aaf7140f - fix: visibl...
v2.10.3
- fix: IMAP correctness, POP3 safety, and server lifecycle improvements 7b9c04e9d - perf(sqlite): VACUUM INTO safety guards, temp DB LRU, debounce reduction 9dea8b226 - fix: correct case-insens...
v0.12.4
- fix: show the reply indicator immediately after replying efe24ab676cc3697ee012bfc944dfadecbfbc161 --- https://github.com/forwardemail/mail.forwardemail.net/compare/v0.12.3...v0.12.4
v0.12.3
- fix: fatal errors in search-from-URL and compose/search inputs ed7537d104cd29493f7bb1488f648d30c100fdff - fix: visible checkbox fill in light mode on touch devices 295b585e14e273631093d3feb9ec6...
✓ IMAP/POP3/CalDAV/CardDAV Connection Issues and Delays
We're investigating an issue where connections to our IMAP and POP3 services experience intermittent delays.
@fwdemail: @Azure @satyanadella @scottgu @kevin_scott @shanselman @AzureSupport @msdev Another one, signing ...
@Azure @satyanadella @scottgu @kevin_scott @shanselman @AzureSupport @msdev Another one, signing up at https://t.co/SO9D2xkuL4 doesn't work either. @satyanadella @scottgu @kevin_scott @shanselman @Azure @AzureSupport @msdev https://t.co/GDFcu9s5HZ
@fwdemail: @Azure This is absurd - no error message, no details...
@Azure This is absurd - no error message, no details... @satyanadella @scottgu @kevin_scott @shanselman @Azure @AzureSupport @msdev https://t.co/f5ytBYfUxx
@fwdemail: We tried to set up @Azure Artifact Signing to code-sign our open-source desktop app.
We tried to set up @Azure Artifact Signing to code-sign our open-source desktop app. Identity validation silently fails. No error message. No email. Clicking the validation ID for details? 404 - page not found. Support confirmed: "broken 404 links are a known issue." The fix? https://t.co/ZTqXZCJvxV
✓ Investigating Outlook.com / Microsoft 365 service issues
Currently monitoring an issue with **Outlook.com / Microsoft 365** that may affect email delivery. ## Incident Details | Field | Value | |-------|-------| | **Provider** | Microsoft | | **Service** | Outlook.com / Microsoft 365 | | **Incident ID** | `d877055a-9792-4472-ad4d-7be14c664768` | | **Status** | 🔴 Active | ## Description User impact: Admins may not have been able to view Service Health Dashboard (SHD) and Message Center posts in the admin center. Final Status: While we were in the process of attempting to redeploy our service resources to the affected section of infrastructure, system monitoring indicated that the service had returned to normal health. We've confirmed that the problem is no longer occurring, and we'll continue to monitor the service to ensure that the problem does not happen again. Scope of impact: Impact was specific to any admin attempting to view SHD and Message Center posts in the Microsoft 365 admin center operated by 21Vianet. Start time: Sunday, June 21, 2026, at 8:03 AM UTC End time: Tuesday, June 23, 2026, at 6:30 AM UTC Root cause: A section of infrastructure that facilitates access to SHD and Message Center posts in the Microsoft 365 admin center operated by 21Vianet performed suboptimally, resulting in impact Next steps: - We're ana ## Official Status Page https://status.cloud.microsoft/ --- > **Note:** Forward Email users may experience delays when sending to or receiving from Outlook.com / Microsoft 365 during this incident. *This issue was automatically created by the external mail provider monitor.*
✓ Investigating Outlook.com / Microsoft 365 service issues
Currently monitoring an issue with **Outlook.com / Microsoft 365** that may affect email delivery. ## Incident Details | Field | Value | |-------|-------| | **Provider** | Microsoft | | **Service** | Outlook.com / Microsoft 365 | | **Incident ID** | `2e4fb7b0-fa8a-43c9-ac68-18bcb815f008` | | **Status** | 🔴 Active | ## Description User impact: Admins may not been able to view SHD and Message Center posts in the Microsoft 365 admin center operated by 21Vianet. Final Status: After a period of monitoring, we confirmed that the impacted infrastructure self-restored, and service returned to expected performance levels. We closely monitored the service to ensure that it remained healthy. Scope of impact: Any admin might have been impacted and might not have been able to view SHD and Message Center posts in the Microsoft 365 admin center operated by 21Vianet. This section could have been updated as the investigation continued. Start time: Sunday, June 21, 2026, at 8:03 AM UTC End time: Tuesday, June 23, 2026, at 7:17 AM UTC Root cause: A portion of the infrastructure performed suboptimally, resulting in impact. Next steps: - We're analyzing performance data and trends on the affected infrastructure to help prevent this problem from happening again. This is the final upda ## Official Status Page https://status.cloud.microsoft/ --- > **Note:** Forward Email users may experience delays when sending to or receiving from Outlook.com / Microsoft 365 during this incident. *This issue was automatically created by the external mail provider monitor.*
✓ Investigating Outlook.com / Microsoft 365 service issues
Currently monitoring an issue with **Outlook.com / Microsoft 365** that may affect email delivery. ## Incident Details | Field | Value | |-------|-------| | **Provider** | Microsoft | | **Service** | Outlook.com / Microsoft 365 | | **Incident ID** | `d156b9f6-2109-46a9-99c5-e9400f203465` | | **Status** | 🔴 Active | ## Description Current status: We've identified a problem that may be preventing some admins from viewing the Microsoft 365, operated by 21Vianet, Service Health Dashboard (SHD) and/or Message Center (MC). We’re working to restore access to the SHD and MC, and we'll provide more information when we’ve isolated the root cause. Next update by: Tuesday, June 23, 2026, at 7:00 AM UTC ## Official Status Page https://status.cloud.microsoft/ --- > **Note:** Forward Email users may experience delays when sending to or receiving from Outlook.com / Microsoft 365 during this incident. *This issue was automatically created by the external mail provider monitor.*
@fwdemail: Just shipped wildcard subdomain forwarding.
Just shipped wildcard subdomain forwarding. Configure once at your root domain → automatically covers every subdomain. No more adding separate DNS records for each sub. Use %SUBDOMAIN% and %HOST% tokens in your forwarding rules for dynamic routing. So https://t.co/JQKi5B8zc7, https://t.co/qt2R3CuLW0
@fwdemail: Last week we responsibly disclosed 7 vulnerabilities our team found in another open source email ...
Last week we responsibly disclosed 7 vulnerabilities our team found in another open source email project. Hoping to see more open source email services and alternatives emerge. The space needs healthy competition and innovation (and not a graveyard: https://t.co/f3FiMSVoB7)
✓ Investigating Outlook.com / Microsoft 365 service issues
Currently monitoring an issue with **Outlook.com / Microsoft 365** that may affect email delivery. ## Incident Details | Field | Value | |-------|-------| | **Provider** | Microsoft | | **Service** | Outlook.com / Microsoft 365 | | **Incident ID** | `e2bff449-ce7b-4c53-b175-2dc52a8c9896` | | **Status** | 🔴 Active | ## Description User impact: Users are unable to access Microsoft 365 Copilot Chat or portal.office.com. More info: Admins may be able to access the Microsoft 365 admin center via admin.cloud.microsoft as a temporary solution. Current status: This is a continuation of a communication posted under CW1387674. We’ve identified an issue with a recent deployment for Microsoft Copilot. We’re reverting to a previous build to remediate impact as soon as possible. We expect this to be completed in the next 30 minutes. Scope of impact: Our investigation indicates that any user or admin may be affected by this event. This section is subject to change as the investigation continues. Start time: Thursday, June 11, 2026, at 8:00 PM UTC Estimated time to resolve: We expect the reversion to be complete in the next 30 minutes. Root cause: The root cause is still being investigated. We will provide more information in our next update. Next update by: Thur ## Official Status Page https://status.cloud.microsoft/ --- > **Note:** Forward Email users may experience delays when sending to or receiving from Outlook.com / Microsoft 365 during this incident. *This issue was automatically created by the external mail provider monitor.*
✓ IMAP/POP3/SMTP Delays Investigation
We are continuing to investigate the underlying cause of the queue delays. In the interim, we'll keep the queue flowing, but emails may be delayed 5-10+ mins in the interim. This is an extremely rare occurrence, note our status page has had remarkable uptime – rest assured we are actively working to resolve this as quick as possible.
✓ Investigating SMTP queue delays
Investigating SMTP queue delays
@fwdemail: @cure53berlin Direct link: https://t.co/A8wzsRd8ZD
@cure53berlin Direct link: https://t.co/A8wzsRd8ZD
@fwdemail: @cure53berlin https://t.co/15E8q9mxkl
@cure53berlin https://t.co/15E8q9mxkl
@fwdemail: 🤯 Our @cure53berlin security audit is live 🔗📰👇
🤯 Our @cure53berlin security audit is live 🔗📰👇 Big thank you to Dr. Mario Heiderich and team 🙏 Looking forward to working with them again. Now we're the only 100% open-source email service and the only that's been 3rd party audited. Read the audit: 👉
✓ Investigating Gmail service issues
Currently monitoring an issue with **Gmail** that may affect email delivery. ## Incident Details | Field | Value | |-------|-------| | **Provider** | Google | | **Service** | Gmail | | **Incident ID** | `CzVZ5zk2Gf2ixPSt6RT3` | | **Status** | 🔴 Active | | **Started** | 2026-05-21 07:00 | ## Description We are experiencing an issue with Gmail beginning on Thursday, 2026-05-21 at 00:00 PDT. Mitigation efforts are currently underway by our engineering team. ## Official Status Page https://www.google.com/appsstatus/dashboard/incidents/CzVZ5zk2Gf2ixPSt6RT3 --- > **Note:** Forward Email users may experience delays when sending to or receiving from Gmail during this incident. *This issue was automatically created by the external mail provider monitor.*
✓ Investigating Gmail service issues
Currently monitoring an issue with **Gmail** that may affect email delivery. ## Incident Details | Field | Value | |-------|-------| | **Provider** | Google | | **Service** | Gmail | | **Incident ID** | `kWSuRqLdsXGzT7Qxjdmz` | | **Status** | 🔴 Active | | **Started** | 2026-05-06 16:00 | ## Description We are experiencing an issue with Gmail beginning on Saturday 2026-05-06. Our engineering team continues to investigate the issue. ## Official Status Page https://www.google.com/appsstatus/dashboard/incidents/kWSuRqLdsXGzT7Qxjdmz --- > **Note:** Forward Email users may experience delays when sending to or receiving from Gmail during this incident. *This issue was automatically created by the external mail provider monitor.*
@fwdemail: 📬 Forward Email by the numbers:
📬 Forward Email by the numbers: 320K+ lines of JavaScript 35 Ansible playbooks, 974 infra tasks 2,024 automated tests 71 RESTful API endpoints 283 RFC specs compliant Protocols: SMTP, IMAP, POP3, CalDAV, CardDAV, DKIM, SPF, DMARC, MTA-STS, DANE, ARC, SRS, TLS-RPT, BIMI, WKD,
@fwdemail: Calendar & Contacts now have push support on iOS native apps 🎉
Calendar & Contacts now have push support on iOS native apps 🎉 Mail push has been working — now all three sync instantly. iOS won't display "Push" for Contacts (known iOS bug) but it works. Mail & Calendar show Push correctly. To enable: remove your account in Settings → VPN
✓ 🛑 forwardemail.net:443 (SSL) is down
In [`24b6947`](https://github.com/forwardemail/status.forwardemail.net/commit/24b6947c8e3fa3a6011bc5999320235b4296507a ), forwardemail.net:443 (SSL) (forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
@fwdemail: Just finished a 3rd party audit from the best of the best (publishing soon).
Just finished a 3rd party audit from the best of the best (publishing soon). Still the only 100% open-source email provider and email infrastructure platform. Still the only one with perfect 100% scores on both https://t.co/yzmZeRPhuA site and mail tests. No plans to go
A Decade of Impact: How Our npm Packages Hit 1 Billion Downloads and Shaped JavaScript
JavaScript와 Node.js 환경에서는 매일 수백만 번 다운로드되고 전 세계 앱을 구동하는 필수적인 패키지들이 있습니다. 이러한 도구 뒤에는 오픈 소스 품질 향상에 집중하는 개발자들이 있습니다. 오늘은 JavaScript 생태계의 핵심 요소로 자리 잡은 npm 패키지를 어떻게 빌드하고 유지 관리하는지 보여드리겠습니다.
Building a Privacy-First AI Support Agent with LanceDB & Ollama
LanceDB, Ollama 및 Node.js를 사용하여 자체 호스팅 AI 고객 지원 에이전트를 구축하는 방법을 배우세요. GDPR 준수, 개인정보 우선, 완전한 제어 가능.
Case Study: Gov/Federal Section 889 Email Compliance
정부 이메일 규정 준수에 대한 저희의 노력은 최근 미국 해군사관학교가 Forward Email에 연락하면서 실제로 실행되었습니다. Forward Email은 안전한 이메일 전달 서비스와 889조 준수를 포함한 연방 규정 준수를 확인하는 서류를 요구했습니다.
Case Study: How Ubuntu Powers Email Management with Forward Email's Open-Source Enterprise Solution
Canonical이 원활한 SSO 통합을 갖춘 Forward Email의 오픈 소스, 양자 저항 엔터프라이즈 솔루션을 사용하여 Ubuntu, Kubuntu, Lubuntu 및 Edubuntu 도메인에서 이메일 관리를 어떻게 간소화했는지 알아보세요.
Case Study: How the Linux Foundation Optimizes Email Management Across 250+ Domains with Forward Email
Linux Foundation은 linux.com 및 jQuery.com을 포함하여 250개 이상의 도메인에 걸쳐 900개 이상의 오픈소스 프로젝트를 관리합니다. 이 사례 연구에서는 Forward Email과 협력한 방법을 살펴봅니다.
Complete Email API with IMAP, CardDAV & CalDAV REST Endpoints
이메일 관리를 위한 최초의 완벽한 REST API. 연락처, 캘린더, 메시지 및 폴더에 대한 20개의 엔드포인트를 지원합니다. IMAP의 복잡성 없이 간편한 인증 기능을 제공합니다.
Email Protocols & RFC Compliance: IMAP, SMTP, POP3 Comparison
이메일 프로토콜 및 RFC 준수에 대한 완벽한 가이드입니다. IMAP, SMTP, POP3, DKIM, SPF, DMARC, ARC 표준을 비교하세요. 이메일 보안, CalDAV, 암호화 및 공급자별 프로토콜 지원을 배우세요.
How to Optimize Node.js Production Infrastructure: Best Practices
매일 수백만 건의 요청을 처리하는 실전 테스트를 거친 인프라에서 얻은 Node.js 프로덕션 배포 모범 사례입니다.
Introducing Crypto Payments: Enhanced Privacy for Your Email Service
이제 Stripe의 암호화폐 결제 통합을 통해 암호화폐 결제를 허용합니다.
PayPal's 11-Year API Disaster: Missing Features & Broken Promises
PayPal이 11년간 개발자 피드백을 무시하고, 기본 구독 API를 누락하고, 임원 교체를 강요하고, 우회책을 강요한 과정. 전체 타임라인.
Quantum Resistant Email Service
Encrypted quantum-resistant mailboxes to protect your privacy. Secure email for business and custom domains with post-quantum cryptography and 100% open-source software. Future-proof your communications against quantum computing threats with NIST-approved encryption algorithms.
SQLite Performance Optimization: Production PRAGMA Settings
실제 벤치마크 데이터를 포함한 완벽한 SQLite 최적화 가이드. Forward Email의 프로덕션 PRAGMA 설정, ChaCha20 암호화, WAL 모드 튜닝, 그리고 Node.js 버전별 성능 학습.
The Email Startup Graveyard: Why Most Email Companies Fail
이메일 스타트업 실패 사례에 대한 종합적인 분석. 대부분의 이메일 회사가 실패하고, 수백만 달러의 벤처 캐피털 투자를 날리고, 결국 문을 닫는 이유. 실제로 효과적인 방법을 알아보세요.
The Trifecta Approach: How Forward Email Built a Bulletproof Payment System with Stripe and PayPal
당사 개발팀이 전체 시스템에서 1:1 실시간 정확성을 보장하는 3중 접근법을 사용하여 Stripe와 PayPal을 어떻게 통합했는지 알아보세요.
✓ 🛑 smtp.forwardemail.net:2587 (IPv6) is down
In [`0056f1d`](https://github.com/forwardemail/status.forwardemail.net/commit/0056f1d58f85d14c0a3830b9a5e0c79669f9ec8b ), smtp.forwardemail.net:2587 (IPv6) (smtp.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ Investigating Outlook.com / Microsoft 365 service issues
Currently monitoring an issue with **Outlook.com / Microsoft 365** that may affect email delivery. ## Incident Details | Field | Value | |-------|-------| | **Provider** | Microsoft | | **Service** | Outlook.com / Microsoft 365 | | **Incident ID** | `ce46279f-4c16-4d69-9515-2a2019645832` | | **Status** | 🔴 Active | ## Description Title: Users may be unable to access Microsoft 365 web-based services correctly when using Google Chrome User impact: Users may be unable to access Microsoft 365 web-based services correctly when using Google Chrome. More info: Impacted users may experience Microsoft 365 web apps and portals not rendering as expected when accessed via the Google Chrome browsers. This may include, but is not limited to: - Microsoft 365 admin center failing to load or missing UI elements such as search bars or pages - An inability to open Excel or PowerPoint files through Microsoft 365 web pages - Issues accessing apps such as OneDrive and Planner through the browser Other browsers, including Microsoft Edge, appear to be unaffected. As a workaround, impacted users can use the Microsoft Edge browser. Additionally, desktop based clients are unaffected, and users may be able to leverage these services. Current status: We are updating the authentication components across various s ## Official Status Page https://status.cloud.microsoft/ --- > **Note:** Forward Email users may experience delays when sending to or receiving from Outlook.com / Microsoft 365 during this incident. *This issue was automatically created by the external mail provider monitor.*
✓ Investigating iCloud Mail service issues
Currently monitoring an issue with **iCloud Mail** that may affect email delivery. ## Incident Details | Field | Value | |-------|-------| | **Provider** | Apple | | **Service** | iCloud Mail | | **Incident ID** | `1000005583` | | **Status** | 🔴 Active | | **Started** | 2026-04-13T16:54:00.000Z | | **Impact** | Some users are affected | ## Description Some users may be experiencing issues with this service. ## Official Status Page https://www.apple.com/support/systemstatus/ --- > **Note:** Forward Email users may experience delays when sending to or receiving from iCloud Mail during this incident. *This issue was automatically created by the external mail provider monitor.*
✓ Investigating Gmail service issues
Currently monitoring an issue with **Gmail** that may affect email delivery. ## Incident Details | Field | Value | |-------|-------| | **Provider** | Google | | **Service** | Gmail | | **Incident ID** | `224ozRqzW4sFBDK8hLnT` | | **Status** | 🔴 Active | | **Started** | 2026-04-08 13:30 | ## Description Incident began at 2026-04-08 13:30 (times are in Coordinated Universal Time (UTC) ). Title: Customers may experience delays in receiving and sending emails. Description: We are aware of an issue with Gmail users experiencing delays in receiving and sending emails beginning at Wednesday, 2026-04-08 06:30 PDT. Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide an update by Wednesday, 2026-04-08 12:00 PDT with current details. Symptoms: Customers may experience delays in receiving and sending emails. Workaround: None at this time. Affected products: Gmail ## Official Status Page https://www.google.com/appsstatus/dashboard/incidents/224ozRqzW4sFBDK8hLnT --- > **Note:** Forward Email users may experience delays when sending to or receiving from Gmail during this incident. *This issue was automatically created by the external mail provider monitor.*
✓ Investigating Outlook.com / Microsoft 365 service issues
Currently monitoring an issue with **Outlook.com / Microsoft 365** that may affect email delivery. ## Incident Details | Field | Value | |-------|-------| | **Provider** | Microsoft | | **Service** | Outlook.com / Microsoft 365 | | **Incident ID** | `79c3b43a-e549-42bc-b17d-9f1e957fa466` | | **Status** | 🔴 Active | ## Description User impact: A subset of admins in North America may be unable to access the Microsoft 365 admin center. Current status: The impacting update has been successfully reverted on the majority of the affected infrastructure. We anticipate that the remaining impact will be remediated by our next scheduled update. Scope of impact: A small subset of admins in North America who are attempting to access the Microsoft 365 admin center may be impacted. Start time: Monday, April 6, 2026, at 5:45 PM UTC Preliminary root cause: A recent deployment introduced a code issue which introduced errors in the code path that facilitates calls to the Microsoft 365 admin center and is preventing some admins from accessing the Microsoft 365 admin center as expected. Next update: Monday, April 6, 2026, at 11:30 PM UTC ## Official Status Page https://status.cloud.microsoft/ --- > **Note:** Forward Email users may experience delays when sending to or receiving from Outlook.com / Microsoft 365 during this incident. *This issue was automatically created by the external mail provider monitor.*
✓ Investigating Outlook.com / Microsoft 365 service issues
Currently monitoring an issue with **Outlook.com / Microsoft 365** that may affect email delivery. ## Incident Details | Field | Value | |-------|-------| | **Provider** | Microsoft | | **Service** | Outlook.com / Microsoft 365 | | **Incident ID** | `409e0476-f8ab-418e-9985-620e482cd8f3` | | **Status** | 🔴 Active | ## Description Title: A small subset of admins in North America may be unable to access the Microsoft 365 admin center User impact: A subset of admins in North America may be unable to access the Microsoft 365 admin center. Current status: We confirmed that an issue in a recent update introduced errors in the code path that facilitates calls to the Microsoft 365 admin center when encountered by admins, which resulted in their inability to access the Microsoft 365 admin center. As mentioned previously, we're reverting this update to resolve the issue. The reversion was completed on a portion of infrastructure and our telemetry is showing positive trends. We're closely tracking its progress to ensure all infrastructure receives the change. Scope of impact: A small subset of admins in North America who are attempting to access the Microsoft 365 admin center may be impacted. Start time: Monday, April 6, 2026, at 5:00 PM UTC Preliminary root cause: A recent deployment introduced a code issue ## Official Status Page https://status.cloud.microsoft/ --- > **Note:** Forward Email users may experience delays when sending to or receiving from Outlook.com / Microsoft 365 during this incident. *This issue was automatically created by the external mail provider monitor.*
✓ Investigating Outlook.com / Microsoft 365 service issues
Currently monitoring an issue with **Outlook.com / Microsoft 365** that may affect email delivery. ## Incident Details | Field | Value | |-------|-------| | **Provider** | Microsoft | | **Service** | Outlook.com / Microsoft 365 | | **Incident ID** | `544b3d96-11eb-48d8-930b-b35caf749d33` | | **Status** | 🔴 Active | ## Description Title: A small subset of admins in North America may be unable to access the Microsoft 365 admin center User impact: A subset of admins in North America may be unable to access the Microsoft 365 admin center. Current status: We confirmed that an issue in a recent update introduced errors in the code path that facilitates calls to the Microsoft 365 admin center when encountered by admins, which resulted in their inability to access the Microsoft 365 admin center. As mentioned previously, we're reverting this update to resolve the issue. The reversion was completed on a portion of infrastructure and our telemetry is showing positive trends. We're closely tracking its progress to ensure all infrastructure receives the change. Scope of impact: A small subset of admins in North America who are attempting to access the Microsoft 365 admin center may be impacted. Start time: Monday, April 5, 2026, at 5:00 PM UTC Preliminary root cause: A recent deployment introduced a code issue ## Official Status Page https://status.cloud.microsoft/ --- > **Note:** Forward Email users may experience delays when sending to or receiving from Outlook.com / Microsoft 365 during this incident. *This issue was automatically created by the external mail provider monitor.*
✓ Investigating Outlook.com / Microsoft 365 service issues
Currently monitoring an issue with **Outlook.com / Microsoft 365** that may affect email delivery. ## Incident Details | Field | Value | |-------|-------| | **Provider** | Microsoft | | **Service** | Outlook.com / Microsoft 365 | | **Incident ID** | `ef19d8a8-7a5c-4035-bd3b-3ac57f24df34` | | **Status** | 🔴 Active | ## Description Title: A small subset of admins in North America may be unable to access the Microsoft 365 admin center User impact: A subset of admins in North America may be unable to access the Microsoft 365 admin center. Current status: We're observing some service recovery as our reversion of the recent deployment progresses throughout the impacted infrastructure. We'll continue to carefully monitor the service during the reversion process to confirm full restoration. Scope of impact: A small subset of admins in North America who are attempting to access the Microsoft 365 admin center may be impacted. Preliminary root cause: An issue with a recent deployment is preventing some admins from accessing the Microsoft 365 admin center as expected. We'll provide more information regarding the cause as our investigation progresses. Next update: Monday, April 4, 2026, at 8:30 PM UTC ## Official Status Page https://status.cloud.microsoft/ --- > **Note:** Forward Email users may experience delays when sending to or receiving from Outlook.com / Microsoft 365 during this incident. *This issue was automatically created by the external mail provider monitor.*
✓ Investigating Outlook.com / Microsoft 365 service issues
Currently monitoring an issue with **Outlook.com / Microsoft 365** that may affect email delivery. ## Incident Details | Field | Value | |-------|-------| | **Provider** | Microsoft | | **Service** | Outlook.com / Microsoft 365 | | **Incident ID** | `72568b02-176d-4b35-955d-dfab000b9459` | | **Status** | 🔴 Active | ## Description Title: A small subset of admins in North America may be unable to access the Microsoft 365 admin center User impact: A subset of admins in North America may be unable to access the Microsoft 365 admin center Current status: We've identified a recent deployment which we believe is contributing to impact. We're reverting this deployment and monitoring our service to confirm this resolves the issue. Scope of impact: A small subset of admins in North America who are attempting to access the Microsoft 365 admin center may be impacted. Preliminary root cause: An issue with a recent deployment is preventing some admins from accessing the Microsoft 365 admin center as expected. We'll provide more information regarding the cause as our investigation progresses. Next update: Monday, April 4, 2026, at 8:30 PM UTC ## Official Status Page https://status.cloud.microsoft/ --- > **Note:** Forward Email users may experience delays when sending to or receiving from Outlook.com / Microsoft 365 during this incident. *This issue was automatically created by the external mail provider monitor.*
✓ Investigating Outlook.com / Microsoft 365 service issues
Currently monitoring an issue with **Outlook.com / Microsoft 365** that may affect email delivery. ## Incident Details | Field | Value | |-------|-------| | **Provider** | Microsoft | | **Service** | Outlook.com / Microsoft 365 | | **Incident ID** | `cabd953e-cf88-46c9-a656-af4bb53c4927` | | **Status** | 🔴 Active | ## Description User impact: We don't have details on impact yet. We're seeing an increase in user reported issues above our alerting threshold. Current status: We are reviewing service telemetry and available information to determine if there is an issue happening and we'll update this message shortly with our latest findings. This communication serves as a preliminary notification about a potential issue affecting your service. ## Official Status Page https://status.cloud.microsoft/ --- > **Note:** Forward Email users may experience delays when sending to or receiving from Outlook.com / Microsoft 365 during this incident. *This issue was automatically created by the external mail provider monitor.*
✓ Investigating iCloud Mail service issues
Currently monitoring an issue with **iCloud Mail** that may affect email delivery. ## Incident Details | Field | Value | |-------|-------| | **Provider** | Apple | | **Service** | iCloud Mail | | **Incident ID** | `1000005563` | | **Status** | 🔴 Active | | **Started** | 2026-04-05T14:19:00.000Z | | **Impact** | Some users are affected | ## Description Some users may be experiencing issues with this service. ## Official Status Page https://www.apple.com/support/systemstatus/ --- > **Note:** Forward Email users may experience delays when sending to or receiving from iCloud Mail during this incident. *This issue was automatically created by the external mail provider monitor.*
@fwdemail: Why Forward Email is one of a kind 👇
Why Forward Email is one of a kind 👇 https://t.co/Bb6WalxlMO https://t.co/Iz9uE3unhO
✓ Investigating Outlook.com / Microsoft 365 service issues
Currently monitoring an issue with **Outlook.com / Microsoft 365** that may affect email delivery. ## Incident Details | Field | Value | |-------|-------| | **Provider** | Microsoft | | **Service** | Outlook.com / Microsoft 365 | | **Incident ID** | `57dc1843-f79e-4f07-9992-5c0d4ee9f8c1` | | **Status** | 🔴 Active | ## Description User impact: Admins may be unable to access or experience delays accessing the Microsoft 365 admin center Current status: Following our recent mitigation efforts to reroute traffic away from the affected systems, service stability has been restored. We’re continuing to closely monitor service telemetry to confirm full remediation and ensure the service remains healthy. Scope of impact: Admins hosted in US Central attempting to access the Microsoft 365 admin center may be impacted. This information may be updated as our investigation continues. Start Time: Thursday, April 2, 2026, at 6:30 PM UTC Preliminary root cause: A subset of infrastructure in the Central US datacenter entered an unexpected degraded state, resulting in disruptions to request handling. Next update by: Thursday, April 2, 2026, at 11:30 PM UTC ## Official Status Page https://status.cloud.microsoft/ --- > **Note:** Forward Email users may experience delays when sending to or receiving from Outlook.com / Microsoft 365 during this incident. *This issue was automatically created by the external mail provider monitor.*
✓ Investigating Outlook.com / Microsoft 365 service issues
Currently monitoring an issue with **Outlook.com / Microsoft 365** that may affect email delivery. ## Incident Details | Field | Value | |-------|-------| | **Provider** | Microsoft | | **Service** | Outlook.com / Microsoft 365 | | **Incident ID** | `0d1256ad-3505-44b3-8b29-9a14379d0357` | | **Status** | 🔴 Active | ## Description User impact: Admins may be unable to access or experience delays accessing the Microsoft 365 admin center Current status: We’ve identified an issue affecting a portion of the service and are actively mitigating impact by rerouting traffic away from affected systems. This action is helping to stabilize the service while we continue investigating the underlying issue. We’re closely monitoring service health as these changes take effect and will provide further updates as more information becomes available. Scope of impact: Admins hosted in US Central attempting to access the Microsoft 365 admin center may be impacted. This information may be updated as our investigation continues. Start Time: Thursday, April 2, 2026, at 6:30 PM UTC Preliminary root cause: A subset of infrastructure in the Central US datacenter entered an unexpected degraded state, resulting in disruptions to request handling. Next update by: Thursday, April 2, 2026, at 11:00 PM UTC ## Official Status Page https://status.cloud.microsoft/ --- > **Note:** Forward Email users may experience delays when sending to or receiving from Outlook.com / Microsoft 365 during this incident. *This issue was automatically created by the external mail provider monitor.*
✓ Investigating Outlook.com / Microsoft 365 service issues
Currently monitoring an issue with **Outlook.com / Microsoft 365** that may affect email delivery. ## Incident Details | Field | Value | |-------|-------| | **Provider** | Microsoft | | **Service** | Outlook.com / Microsoft 365 | | **Incident ID** | `c4cd5626-0f92-4390-aacf-063fc7f31494` | | **Status** | 🔴 Active | ## Description Current status: We completed a restart of all affected infrastructure, however; this action did not fully resolve the issue. We’ve observed that error rates are starting to decrease but remain above normal levels. We’re reviewing recent changes made in the environment to determine whether a change could be contributing to the issue. Scope of impact: Impact is primarily focused in the Central US region, any admin located in that region may be unable to access the admin center. This information may be updated as our investigation continues. Preliminary root cause: A subset of infrastructure in the Central US datacenter entered an unexpected degraded state, resulting in disruptions to request handling. Start Time: Thursday, April 2, 2026, at 6:30 PM UTC Next update by: Thursday, April 2, 2026, at 10:30 PM UTC ## Official Status Page https://status.cloud.microsoft/ --- > **Note:** Forward Email users may experience delays when sending to or receiving from Outlook.com / Microsoft 365 during this incident. *This issue was automatically created by the external mail provider monitor.*
✓ Investigating Outlook.com / Microsoft 365 service issues
Currently monitoring an issue with **Outlook.com / Microsoft 365** that may affect email delivery. ## Incident Details | Field | Value | |-------|-------| | **Provider** | Microsoft | | **Service** | Outlook.com / Microsoft 365 | | **Incident ID** | `23e09e7a-3007-4448-a12f-dd29fa0f463b` | | **Status** | 🔴 Active | ## Description User impact: Admins may be unable to access or experience delays accessing the Microsoft 365 admin center Current status: We’ve successfully restarted a portion of the affected infrastructure and are seeing improvements to service health as those systems recover. We’re continuing mitigation efforts to restore all remaining impacted infrastructure and are closely monitoring the environment to ensure service stability. Scope of impact: Impact is primarily focused in the Central US region, any admin located in that region may be unable to access the admin center. This information may be updated as our investigation continues. Preliminary root cause: A subset of infrastructure in the Central US datacenter entered an unexpected degraded state, resulting in disruptions to request handling. Start Time: Thursday, April 2, 2026, at 6:30 PM UTC Next update by: Thursday, April 2, 2025, at 10:00 PM UTC ## Official Status Page https://status.cloud.microsoft/ --- > **Note:** Forward Email users may experience delays when sending to or receiving from Outlook.com / Microsoft 365 during this incident. *This issue was automatically created by the external mail provider monitor.*
✓ Investigating Outlook.com / Microsoft 365 service issues
Currently monitoring an issue with **Outlook.com / Microsoft 365** that may affect email delivery. ## Incident Details | Field | Value | |-------|-------| | **Provider** | Microsoft | | **Service** | Outlook.com / Microsoft 365 | | **Incident ID** | `3a10ffa5-5239-4440-aeeb-46704caf340a` | | **Status** | 🔴 Active | ## Description User impact: Admins may be unable to access or experience delays accessing the Microsoft 365 admin center Current status: Our investigation identified a subset of infrastructure in the Central US datacenter that entered a degraded state. We’re conducting targeted restarts in an effort to restore expected service. We’re monitoring the results closely and will share additional updates as more information becomes available. Scope of impact: Impact is primarily focused in the Central US region, any admin located in that region may be unable to access the admin center. This information may be updated as our investigation continues. Start Time: Thursday, April 2, 2026, at 6:30 PM UTC Next update by: Thursday, April 2, 2025, at 9:30 PM UTC ## Official Status Page https://status.cloud.microsoft/ --- > **Note:** Forward Email users may experience delays when sending to or receiving from Outlook.com / Microsoft 365 during this incident. *This issue was automatically created by the external mail provider monitor.*
✓ Investigating Outlook.com / Microsoft 365 service issues
Currently monitoring an issue with **Outlook.com / Microsoft 365** that may affect email delivery. ## Incident Details | Field | Value | |-------|-------| | **Provider** | Microsoft | | **Service** | Outlook.com / Microsoft 365 | | **Incident ID** | `a84166a4-7403-4ccd-9e77-3c884d4df0df` | | **Status** | 🔴 Active | ## Description Title: Users may be unable to access or have delays accessing the Microsoft 365 admin center User impact: Users may be unable to access or have delays accessing the Microsoft 365 admin center Current status: We're investigating reports of an issue in which users may be unable to access or have delays accessing the Microsoft 365 admin center. We are reviewing service telemetry and available information to determine if there is an issue happening and we'll update this message shortly with our latest findings. Scope of impact: Any users attempting to access the Microsoft 365 admin center may be impacted. Next update by: Thursday, April 2, 2025, at 9:00 PM UTC ## Official Status Page https://status.cloud.microsoft/ --- > **Note:** Forward Email users may experience delays when sending to or receiving from Outlook.com / Microsoft 365 during this incident. *This issue was automatically created by the external mail provider monitor.*
@fwdemail: Huge thanks to our community and everyone reporting bugs or low-hanging feature requests - you ma...
Huge thanks to our community and everyone reporting bugs or low-hanging feature requests - you make us better! 🙏 We're not going anywhere. 🇪🇺 EU datacenter later this year after our 3rd party audit in May. Plus new features like newsletter campaigns, desktop + mobile apps,
@fwdemail: AWS is shutting down WorkMail by March 2027 — we just published a complete migration guide for an...
AWS is shutting down WorkMail by March 2027 — we just published a complete migration guide for anyone who needs to move off: https://t.co/1SluCRqWH3 Covers mailbox export, DNS setup, client config, and org-wide batch migration. @tweirjones @jeffbarr @tomsly (can you include
Amazon WorkMail Migration Guide: Step-by-Step Switch to Forward Email Before the 2027 Shutdown
2027년 3월 종료 전 Amazon WorkMail에서 Forward Email로 마이그레이션하는 완벽한 단계별 가이드입니다. 이메일 내보내기, DNS 구성, IMAP 설정 방법을 안내합니다.
@fwdemail: AWS WorkMail is shutting down per https://t.co/Sp2ltMXDsh 😲
AWS WorkMail is shutting down per https://t.co/Sp2ltMXDsh 😲 We're here for you. Forward Email is a reliable, self-hostable alternative that isn't going anywhere. Make the switch! https://t.co/JdrG9aoMDI
@fwdemail: You can now demo our webmail (built with Tauri for mobile/desktop)!
You can now demo our webmail (built with Tauri for mobile/desktop)! https://t.co/QS8fpvmmG5 ➡️ Click 'TRY DEMO' to explore the interface with sample data. No account required. 📧✨ https://t.co/0cyhUa40wb
@fwdemail: We just crossed 1.62M custom domains at Forward Email. That's 45% more than Proton Mail and 36x m...
We just crossed 1.62M custom domains at Forward Email. That's 45% more than Proton Mail and 36x more than Tuta Mail. We're also still the only privacy email provider that is 100% open source. Even our infrastructure hardening and LUKS encryption scripts are public. Instead of https://t.co/QQYe7YofU1
✓ Investigating Outlook.com / Microsoft 365 service issues
Currently monitoring an issue with **Outlook.com / Microsoft 365** that may affect email delivery. ## Incident Details | Field | Value | |-------|-------| | **Provider** | Microsoft | | **Service** | Outlook.com / Microsoft 365 | | **Incident ID** | `aed92473-53fb-48b1-8b56-a2666e5d5c53` | | **Status** | 🔴 Active | ## Description User impact: Users in the North American region may be unable to access multiple Microsoft 365 services. More info: Impacted services include, but are not limited to: - Microsoft 365 admin center - SharePoint Online - Microsoft Teams Current status: We've received reports that the issue is no longer occurring for some users and we're continuing our investigation to confirm full recovery. Our investigation is focused on content delivery network (CDN) configurations and interactions with third‑party network providers. Scope of impact: Impact is specific to some users located in the North American region attempting to access the Microsoft 365 admin center, Microsoft Teams and SharePoint Online. Next update by: Friday, March 6, 2025, at 6:30 PM UTC ## Official Status Page https://status.cloud.microsoft/ --- > **Note:** Forward Email users may experience delays when sending to or receiving from Outlook.com / Microsoft 365 during this incident. *This issue was automatically created by the external mail provider monitor.*
✓ Investigating Outlook.com / Microsoft 365 service issues
Currently monitoring an issue with **Outlook.com / Microsoft 365** that may affect email delivery. ## Incident Details | Field | Value | |-------|-------| | **Provider** | Microsoft | | **Service** | Outlook.com / Microsoft 365 | | **Incident ID** | `fc9c9885-0f49-428d-9e7f-4dfa9fb3670f` | | **Status** | 🔴 Active | ## Description User impact: Users in the North American region may be unable to access multiple Microsoft 365 services. More info: Impacted services include, but are not limited to: - Microsoft 365 admin center - SharePoint Online - Microsoft Teams Current status: We're retrieving additional service monitoring telemetry for review as we work to isolate the root cause and develop a remediation plan. Scope of impact: Impact is specific to some users located in North American region attempting to access the Microsoft 365 admin center, Microsoft Teams and SharePoint Online. Next update by: Friday, March 6, 2025, at 5:30 PM UTC ## Official Status Page https://status.cloud.microsoft/ --- > **Note:** Forward Email users may experience delays when sending to or receiving from Outlook.com / Microsoft 365 during this incident. *This issue was automatically created by the external mail provider monitor.*
✓ Investigating Outlook.com / Microsoft 365 service issues
Currently monitoring an issue with **Outlook.com / Microsoft 365** that may affect email delivery. ## Incident Details | Field | Value | |-------|-------| | **Provider** | Microsoft | | **Service** | Outlook.com / Microsoft 365 | | **Incident ID** | `440abdde-1e93-484b-b1f3-585c959a0366` | | **Status** | 🔴 Active | ## Description User impact: Admins in the North America region may be unable to access the Microsoft 365 admin center. Current status: We're reviewing service monitoring telemetry to isolate the root cause and develop a remediation plan. Scope of impact: Impact is specific to some admins located in the North America region attempting to access the admin center. Next update by: Friday, March 6, 2025, at 5:30 PM UTC ## Official Status Page https://status.cloud.microsoft/ --- > **Note:** Forward Email users may experience delays when sending to or receiving from Outlook.com / Microsoft 365 during this incident. *This issue was automatically created by the external mail provider monitor.*
@fwdemail: Introducing Audit Status — automated third-party auditing for code integrity verification and tra...
Introducing Audit Status — automated third-party auditing for code integrity verification and transparency. Open source, TPM 2.0 backed, tamper-proof. https://t.co/gcfK4lwQwq https://t.co/ZRyFjkaIfY
@fwdemail: Introducing the Forward Email MCP Server! 📦
Introducing the Forward Email MCP Server! 📦 Manage your email, calendars, contacts & more directly from @AnthropicAI @claudeai @OpenAI @ChatGPTapp @ollama @openclaw & any MCP client. Try it now👇 👉 https://t.co/sGmmaF8ZmY 👈 https://t.co/3hCdSZeOkT
Forward Email MCP Server - Connect AI to Your Email API
Open-source MCP server for Forward Email. 68 tools covering email, domains, aliases, contacts, calendars, and Sieve scripts. Works with Claude, ChatGPT, Cursor, and Windsurf.
@fwdemail: Whitepaper now auto-builds via GitHub releases
Whitepaper now auto-builds via GitHub releases https://t.co/6YPucIn8Ha
@fwdemail: @github @mojombo https://t.co/8ikSDVVctb
@github @mojombo https://t.co/8ikSDVVctb
@fwdemail: Thx @github for this epic bounty hunter Octocat hat & pin! 🧢 🔥 We ❤️ GitHub @fwdemail cc @...
Thx @github for this epic bounty hunter Octocat hat & pin! 🧢 🔥 We ❤️ GitHub @fwdemail cc @mojombo https://t.co/jJTXKfVW5Q
@fwdemail: 📃 Announcing Attestium - the only open-source, TPM-backed runtime verification for @nodejs (WIP)
📃 Announcing Attestium - the only open-source, TPM-backed runtime verification for @nodejs (WIP) If you run open-source infra, this is for you @supabase @calcom @documenso @bitwarden @infisical @PlausibleHQ @PostHog @planepowers @cooperx86 @JosephJacks_ https://t.co/RUIEvZFnJh https://t.co/PUgMHbQdn6
@fwdemail: @andyyen @ProtonMail @nguyenkims @SimpleLogin Thanks to Simple Login for removing the block! (co...
@andyyen @ProtonMail @nguyenkims @SimpleLogin Thanks to Simple Login for removing the block! (confirmed via Reddit DM)
✓ Investigating network issues
There appears to be network issues affecting our MongoDB primary server. This happened a few days ago, we are investigating once again. Hopefully this time we will have a permanent fix. Emails will not be lost, but retried shortly soon after.
✓ Investigating Outlook.com / Microsoft 365 service issues
Currently monitoring an issue with **Outlook.com / Microsoft 365** that may affect email delivery. ## Incident Details | Field | Value | |-------|-------| | **Provider** | Microsoft | | **Service** | Outlook.com / Microsoft 365 | | **Incident ID** | `9a5e65b5-a27b-43c5-bba2-6dc7da0a74ee` | | **Status** | 🔴 Active | ## Description User impact: Some users may experience issues accessing Microsoft 365 services, particularly during sign‑in or authentication. Current status: We’re reviewing Microsoft Entra sign‑in logs and related network telemetry following reports of 504 gateway timeout errors affecting sign‑in using Multi-Factor Authentication (MFA) for Microsoft 365 services. In parallel, we're also analyzing third-party authentication dependencies and interactions to better understand the potential source of the issue. Scope of impact: This issue may affect any user within your organization leveraging MFA for sign-in. We've confirmed the following region(s) are impacted by this issue: North America. Additional impacted region(s) may be included as our investigation continues. Next update by: Monday, February 23, 2026, at 5:30 PM UTC ## Official Status Page https://status.cloud.microsoft/ --- > **Note:** Forward Email users may experience delays when sending to or receiving from Outlook.com / Microsoft 365 during this incident. *This issue was automatically created by the external mail provider monitor.*
✓ Investigating Outlook.com / Microsoft 365 service issues
Currently monitoring an issue with **Outlook.com / Microsoft 365** that may affect email delivery. ## Incident Details | Field | Value | |-------|-------| | **Provider** | Microsoft | | **Service** | Outlook.com / Microsoft 365 | | **Incident ID** | `657c2a1f-16a2-46d9-8297-125d1ba5cdc5` | | **Status** | 🔴 Active | ## Description We're investigating an issue in the North America region where users may be experiencing 504 gateway timeout errors when trying to access services that require Multi-Factor Authentication (MFA). We're reviewing Microsoft Entra logs and network telemetry signals to isolate the potential source of the issue. This quick update is designed to give the latest information on this issue. ## Official Status Page https://status.cloud.microsoft/ --- > **Note:** Forward Email users may experience delays when sending to or receiving from Outlook.com / Microsoft 365 during this incident. *This issue was automatically created by the external mail provider monitor.*
✓ 🛑 mongo.forwardemail.net is down
In [`4f96ac1`](https://github.com/forwardemail/status.forwardemail.net/commit/4f96ac15a4502935a50a51402ac8fc9d889e039f ), mongo.forwardemail.net (mongo.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ Investigating MongoDB Server Issue
Our primary data server is being investigated at the moment. There appears to be downtime.
✓ Investigating iCloud Mail service issues
Currently monitoring an issue with **iCloud Mail** that may affect email delivery. ## Incident Details | Field | Value | |-------|-------| | **Provider** | Apple | | **Service** | iCloud Mail | | **Incident ID** | `2000005140` | | **Status** | 🔴 Active | | **Started** | 2026-02-10T19:42:00.000Z | | **Impact** | Some users are affected | ## Description Some users may be experiencing issues with this service. ## Official Status Page https://www.apple.com/support/systemstatus/ --- > **Note:** Forward Email users may experience delays when sending to or receiving from iCloud Mail during this incident. *This issue was automatically created by the external mail provider monitor.*
✓ Investigating Outlook.com / Microsoft 365 service issues
Currently monitoring an issue with **Outlook.com / Microsoft 365** that may affect email delivery. ## Incident Details | Field | Value | |-------|-------| | **Provider** | Microsoft | | **Service** | Outlook.com / Microsoft 365 | | **Incident ID** | `fdb0c3cc-5b95-4eed-8b63-bd32211dfd09` | | **Status** | 🔴 Active | ## Description Title: Some users in the North America region may be unable to access the Microsoft 365 admin center User impact: Users in the North America region may be unable to access the Microsoft 365 admin center. More info: Users able to access the admin center may be experiencing degraded functionality. As functionality is degraded, users may be unable to raise support tickets through the Microsoft 365 admin center. Additionally, users may be unable to access the M365 app. Current status: Whilst we were performing the targeted restarts, parallel root cause investigations identified a recent change to the redirection service which may have been contributing to impact. We’ve reverted the change and are monitoring the service for recovery. Telemetry indicates that the service is beginning to recover. Scope of impact: This issue impacts the North America region. Next update by: Tuesday, February 10, 2026, at 6:00 PM UTC ## Official Status Page https://status.cloud.microsoft/ --- > **Note:** Forward Email users may experience delays when sending to or receiving from Outlook.com / Microsoft 365 during this incident. *This issue was automatically created by the external mail provider monitor.*
✓ Investigating Outlook.com / Microsoft 365 service issues
Currently monitoring an issue with **Outlook.com / Microsoft 365** that may affect email delivery. ## Incident Details | Field | Value | |-------|-------| | **Provider** | Microsoft | | **Service** | Outlook.com / Microsoft 365 | | **Incident ID** | `c116f7dc-43ac-4fb9-8866-ac67e3e585b5` | | **Status** | 🔴 Active | ## Description Title: Some users in the North America region may be unable to access the Microsoft 365 admin center User impact: Users in the North America region may be unable to access the Microsoft 365 admin center. More info: Users able to access the admin center may be experiencing degraded functionality. As functionality is degraded, users may be unable to raise support tickets through the Microsoft 365 admin center. Additionally, users may be unable to access the M365 app. Current status: We’re continuing to analyze diagnostic data from the Microsoft 365 admin center infrastructure, with a current focus on usage patterns and Central Processing Unit (CPU) utilization levels. Additionally, we’re reviewing HTTP Archive (HAR) files provided by impacted users to support our investigation. Scope of impact: Initial reports indicate that the issue is occurring in the North America region. We'll provide more information once identified. Next update by: Tuesday, February 10, 2026, at 5:30 PM UTC ## Official Status Page https://status.cloud.microsoft/ --- > **Note:** Forward Email users may experience delays when sending to or receiving from Outlook.com / Microsoft 365 during this incident. *This issue was automatically created by the external mail provider monitor.*
✓ Investigating Outlook.com / Microsoft 365 service issues
Currently monitoring an issue with **Outlook.com / Microsoft 365** that may affect email delivery. ## Incident Details | Field | Value | |-------|-------| | **Provider** | Microsoft | | **Service** | Outlook.com / Microsoft 365 | | **Incident ID** | `cd07e22d-d393-40d1-b5eb-fac46006a920` | | **Status** | 🔴 Active | ## Description Title: Some users in the North America region may be unable to access the Microsoft 365 admin center User impact: Users in the North America region may be unable to access the Microsoft 365 admin center. More info: Users able to access the admin center may be experiencing degraded functionality. As functionality is degraded, users may be unable to raise support tickets through the Microsoft 365 admin center. Additionally, users may be unable to access the M365 app. Current status: We're reviewing service monitoring telemetry to isolate the root cause and develop a remediation plan. Scope of impact: Initial reports indicate that the issue is occurring in the North America region. We'll provide more information as we investigate. Next update by: Tuesday, February 10, 2026, at 4:00 PM UTC ## Official Status Page https://status.cloud.microsoft/ --- > **Note:** Forward Email users may experience delays when sending to or receiving from Outlook.com / Microsoft 365 during this incident. *This issue was automatically created by the external mail provider monitor.*
✓ Investigating Outlook.com / Microsoft 365 service issues
Currently monitoring an issue with **Outlook.com / Microsoft 365** that may affect email delivery. ## Incident Details | Field | Value | |-------|-------| | **Provider** | Microsoft | | **Service** | Outlook.com / Microsoft 365 | | **Incident ID** | `6f772852-4b5e-4e00-8e5f-310f0129ef16` | | **Status** | 🔴 Active | ## Description User impact: Users in the North America region may be unable to access the Microsoft 365 admin center. More info: Users able to access the admin center may experiencing degraded functionality. Current status: We're reviewing service monitoring telemetry to isolate the root cause and develop a remediation plan. Scope of impact: Initial reports indicate that the issue is occurring in the North America region. We'll provide more information as we investigate. Next update by: Tuesday, February 10, 2026, at 4:00 PM UTC ## Official Status Page https://status.cloud.microsoft/ --- > **Note:** Forward Email users may experience delays when sending to or receiving from Outlook.com / Microsoft 365 during this incident. *This issue was automatically created by the external mail provider monitor.*
Email Regex JavaScript and Node.js
JavaScript 및 Node.js용 이메일 주소 정규식 매칭 패턴입니다. Node.js v14 이상 및 브라우저에서 작동합니다.
Send React Emails
Send emails from React and Node.js web apps using HTML, CSS, and JSX templates. Production-ready SMTP integration guide with code examples and best practices.
URL Regex JavaScript and Node.js
JavaScript 및 Node.js용 URL 정규식 매칭 패턴입니다. CVE-2020-7661을 해결하며 Node.js v10.12.0 이상 및 브라우저에서 작동합니다.
✓ Investigating outbound SMTP connectivity issues
Currently investigating SMTP server connectivity issues since ~8 AM CST today, likely related to recent code changes to support webmail. See <https://forwardemail.net/en/event-feed>.
✓ 🛑 smtp.forwardemail.net:25 (IPv6) is down
In [`fb531d6`](https://github.com/forwardemail/status.forwardemail.net/commit/fb531d6ccfb86a7534367ec04cf1eb644e4cd78e ), smtp.forwardemail.net:25 (IPv6) (smtp.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ Emails Database Migration (Outbound SMTP)
There should be zero downtime as we are migrating now (possible 1-2 minutes), however historical emails in the queue will migrated over to our new primary database over the next 30 minutes. Upon completion we will close this issue. This is the last of our databases to merge and migrate! 🎉 Then we will be fully migrated to our bare metal servers 🙏
✓ Logs database migration
We postponed this migration until now, and are in the process of completing it. Logs will be restored from past 3-5+ days approximately in the next 30-60 minutes. Thank you for your patience as we improve our service resiliency and speed.
✓ 🛑 smtp.forwardemail.net:25 (IPv6) is down
In [`8e36c4d`](https://github.com/forwardemail/status.forwardemail.net/commit/8e36c4d3765a7520ec5e10abfa86f6c63c4b3de5 ), smtp.forwardemail.net:25 (IPv6) (smtp.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 smtp.forwardemail.net:2587 (IPv4) is down
In [`b09b901`](https://github.com/forwardemail/status.forwardemail.net/commit/b09b901805cf119756b137928331c6a32c77f701 ), smtp.forwardemail.net:2587 (IPv4) (smtp.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ REQUIRETLS Issue Resolved
We had a bug earlier deployed for ~15 minutes causing rejections to occur. This has never happened, and was the result of an edge case with us adding support for an RFC protocol for REQUIRETLS EHLO capability. The bug unfortunately passed our tests, but we caught it quickly. The one line of code causing this issue to be fixed has been patched, and all outbound SMTP messages have been re-queued for delivery. We sincerely apologize for this unexpected issue. Thank you 🙏
✓ Server RAM Upgrade
Our primary Redis and Mongo databases are being doubled in RAM. Expected downtime 5-10 mins. Currently taking place as of 12 PM ET.
✓ Scheduled MongoDB Migration
We will be migrating our database this evening during non-peak hours, likely around 11 PM ET. Expected downtime is 5-10 minutes. This should drastically improve system-wide performance as we are migrating from Digital Ocean Managed DB for MongoDB to baremetal NVMe SSD AMD Ryzen (fine-tuned via numactl) servers in Denver, CO. All of our other servers are primarily in Denver, CO region now, so latency will be drastically reduced as there is no extra hop after this. 🚀
✓ 🛑 https://forwardemail.net (curl) is down
In [`65f9ae3`](https://github.com/forwardemail/status.forwardemail.net/commit/65f9ae38c2f0ee9d237582b98cf8abc1499c9857 ), https://forwardemail.net (curl) (https://forwardemail.net) was **down**: - HTTP code: 408 - Response time: 1806 ms
✓ Investigating networking outage with Redis server
We are investigating our redis server outage, which was the direct result of production environment reliability testing. We will continue to fix and resolve the underlying networking issue.
✓ 🛑 redis.forwardemail.net is down
In [`29a1355`](https://github.com/forwardemail/status.forwardemail.net/commit/29a1355c020d04b2bccdfb11f1008a9e4ec81a46 ), redis.forwardemail.net (redis.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 https://forwardemail.net (curl) is down
In [`cd1e1e0`](https://github.com/forwardemail/status.forwardemail.net/commit/cd1e1e063ae0ff854b32fad7becc7068280cea1a ), https://forwardemail.net (curl) (https://forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ Investigating forwarding/delivery issues
We're aware of forwarding/delivery issues that started about 1 hour ago. We'll keep you posted.
✓ 🛑 https://api.forwardemail.net (curl) is down
In [`8783a62`](https://github.com/forwardemail/status.forwardemail.net/commit/8783a62ba5d9fa049d63f645dc1082dcd2f92f03 ), https://api.forwardemail.net (curl) (https://api.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 https://forwardemail.net (curl) is down
In [`68a9943`](https://github.com/forwardemail/status.forwardemail.net/commit/68a99434386a39f224b14ed84865a4b8a2869689 ), https://forwardemail.net (curl) (https://forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 https://api.forwardemail.net (curl) is down
In [`937ff31`](https://github.com/forwardemail/status.forwardemail.net/commit/937ff31830af7a1233bd95cb62272a9c803679cf ), https://api.forwardemail.net (curl) (https://api.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 https://forwardemail.net (curl) is down
In [`320e891`](https://github.com/forwardemail/status.forwardemail.net/commit/320e89199a1b8b8fae625360681ebed7c51a7805 ), https://forwardemail.net (curl) (https://forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 smtp.forwardemail.net:2525 (IPv6) is down
In [`cf7b483`](https://github.com/forwardemail/status.forwardemail.net/commit/cf7b483bcee39454c3a7c2792a68da3cf9343ebe ), smtp.forwardemail.net:2525 (IPv6) (smtp.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 https://forwardemail.net (curl) is down
In [`0097ca0`](https://github.com/forwardemail/status.forwardemail.net/commit/0097ca0bca54914bdb27c3aaeed9f34f145971c8 ), https://forwardemail.net (curl) (https://forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 smtp.forwardemail.net:587 (IPv6) is down
In [`e1aafb3`](https://github.com/forwardemail/status.forwardemail.net/commit/e1aafb376592d3674bd2dba213da93cf3540ddc0 ), smtp.forwardemail.net:587 (IPv6) (smtp.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 smtp.forwardemail.net:587 (IPv4) is down
In [`90c5477`](https://github.com/forwardemail/status.forwardemail.net/commit/90c547720cf55acfc04eba6b654a7c78bf6a6266 ), smtp.forwardemail.net:587 (IPv4) (smtp.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 smtp.forwardemail.net:587 (IPv6) is down
In [`eb48d85`](https://github.com/forwardemail/status.forwardemail.net/commit/eb48d854d30dd45d9280805d0c2c8f4e76e51533 ), smtp.forwardemail.net:587 (IPv6) (smtp.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 smtp.forwardemail.net:587 (IPv4) is down
In [`8ff7c61`](https://github.com/forwardemail/status.forwardemail.net/commit/8ff7c61fb647bb3db7ab28eedfca42de3c1b8c27 ), smtp.forwardemail.net:587 (IPv4) (smtp.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 smtp.forwardemail.net:587 (IPv6) is down
In [`bd797a1`](https://github.com/forwardemail/status.forwardemail.net/commit/bd797a1411a6f47271341227dafafe8ad9416e4e ), smtp.forwardemail.net:587 (IPv6) (smtp.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 smtp.forwardemail.net:587 (IPv4) is down
In [`1f935a9`](https://github.com/forwardemail/status.forwardemail.net/commit/1f935a9f149e7c916cd5509540fcf22af59f93f4 ), smtp.forwardemail.net:587 (IPv4) (smtp.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 smtp.forwardemail.net:587 (IPv6) is down
In [`6e78b14`](https://github.com/forwardemail/status.forwardemail.net/commit/6e78b14f0cb5d73d59212ce46c399ece579c708f ), smtp.forwardemail.net:587 (IPv6) (smtp.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 smtp.forwardemail.net:587 (IPv4) is down
In [`40c5610`](https://github.com/forwardemail/status.forwardemail.net/commit/40c5610ff626fa23a48b01605600443c3951aeca ), smtp.forwardemail.net:587 (IPv4) (smtp.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 smtp.forwardemail.net:587 (IPv6) is down
In [`32bc94a`](https://github.com/forwardemail/status.forwardemail.net/commit/32bc94ab80ea19b114bbdd52c4a08f69dc97acf6 ), smtp.forwardemail.net:587 (IPv6) (smtp.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 smtp.forwardemail.net:587 (IPv4) is down
In [`5c5d0d3`](https://github.com/forwardemail/status.forwardemail.net/commit/5c5d0d31ffc1192472cb61ff562908a02bb54ae9 ), smtp.forwardemail.net:587 (IPv4) (smtp.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ Resolving issue with Calendar and Contacts (CalDAV/CardDAV)
We recently deployed VTODO support among other things, and a migration did not succeed. We are resolving this issue now and it should be smooth shortly. You may experience disconnects and reconnects.
✓ 🛑 smtp.forwardemail.net:465 (IPv6) is down
In [`a9815cf`](https://github.com/forwardemail/status.forwardemail.net/commit/a9815cffac992bd96cecabca966913d4d462e639 ), smtp.forwardemail.net:465 (IPv6) (smtp.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 smtp.forwardemail.net:465 (IPv4) is down
In [`077fb13`](https://github.com/forwardemail/status.forwardemail.net/commit/077fb13ef3978ff450c8034e3e528ac2d481630f ), smtp.forwardemail.net:465 (IPv4) (smtp.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 smtp.forwardemail.net:465 (IPv6) is down
In [`5822fe4`](https://github.com/forwardemail/status.forwardemail.net/commit/5822fe473c31bfc88fafcdff3043818b139ba62a ), smtp.forwardemail.net:465 (IPv6) (smtp.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 smtp.forwardemail.net:465 (IPv6) is down
In [`5c36319`](https://github.com/forwardemail/status.forwardemail.net/commit/5c363197e6b2b850f485825efdccdc49d4787613 ), smtp.forwardemail.net:465 (IPv6) (smtp.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 smtp.forwardemail.net:2587 (IPv6) is down
In [`26b6054`](https://github.com/forwardemail/status.forwardemail.net/commit/26b60543237dfc52dd7b2dfa185ad9a99684ed61 ), smtp.forwardemail.net:2587 (IPv6) (smtp.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 smtp.forwardemail.net:465 (IPv6) is down
In [`aef7c0b`](https://github.com/forwardemail/status.forwardemail.net/commit/aef7c0b723b6a8dc5d500d3e6d341fa42f193674 ), smtp.forwardemail.net:465 (IPv6) (smtp.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 smtp.forwardemail.net:2587 (IPv6) is down
In [`a34c51e`](https://github.com/forwardemail/status.forwardemail.net/commit/a34c51ebff00041b50fa42510b0299e51985684c ), smtp.forwardemail.net:2587 (IPv6) (smtp.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 smtp.forwardemail.net:2587 (IPv6) is down
In [`29d562f`](https://github.com/forwardemail/status.forwardemail.net/commit/29d562faa789ce76baf0b1dce38412f213e9daad ), smtp.forwardemail.net:2587 (IPv6) (smtp.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 smtp.forwardemail.net:465 (IPv6) is down
In [`b5eaef8`](https://github.com/forwardemail/status.forwardemail.net/commit/b5eaef80712919a83c4bfb1554bafc60693756f2 ), smtp.forwardemail.net:465 (IPv6) (smtp.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 smtp.forwardemail.net:2587 (IPv4) is down
In [`2e480b0`](https://github.com/forwardemail/status.forwardemail.net/commit/2e480b09f33cc943f4822fa71206f61b92aa4a54 ), smtp.forwardemail.net:2587 (IPv4) (smtp.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 smtp.forwardemail.net:2525 (IPv6) is down
In [`542cb5d`](https://github.com/forwardemail/status.forwardemail.net/commit/542cb5df1a1719e811c54b51c4cd13585aafb807 ), smtp.forwardemail.net:2525 (IPv6) (smtp.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 smtp.forwardemail.net:2587 (IPv4) is down
In [`a584f3b`](https://github.com/forwardemail/status.forwardemail.net/commit/a584f3b80ac6fd7e29c51f3e078e48a218592eb6 ), smtp.forwardemail.net:2587 (IPv4) (smtp.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 smtp.forwardemail.net:465 (IPv6) is down
In [`b485974`](https://github.com/forwardemail/status.forwardemail.net/commit/b485974ba4e85e6232a52b3118a47cf289e38236 ), smtp.forwardemail.net:465 (IPv6) (smtp.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 smtp.forwardemail.net:2587 (IPv4) is down
In [`ab3aae0`](https://github.com/forwardemail/status.forwardemail.net/commit/ab3aae08d08f3cb6513e9c479fc3df4584c6a4bf ), smtp.forwardemail.net:2587 (IPv4) (smtp.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 smtp.forwardemail.net:2587 (IPv6) is down
In [`6da0068`](https://github.com/forwardemail/status.forwardemail.net/commit/6da00680d4c3ba10a7e70b8771f83656bfa8e768 ), smtp.forwardemail.net:2587 (IPv6) (smtp.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 smtp.forwardemail.net:2587 (IPv4) is down
In [`765eef8`](https://github.com/forwardemail/status.forwardemail.net/commit/765eef85d979d18a0ef65edf801ba014fdc36644 ), smtp.forwardemail.net:2587 (IPv4) (smtp.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 smtp.forwardemail.net:2587 (IPv6) is down
In [`b7b2d1f`](https://github.com/forwardemail/status.forwardemail.net/commit/b7b2d1f093c8fd8f9135bbc573c61a627af34438 ), smtp.forwardemail.net:2587 (IPv6) (smtp.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 smtp.forwardemail.net:2587 (IPv4) is down
In [`21bb6a4`](https://github.com/forwardemail/status.forwardemail.net/commit/21bb6a448fd664e24fa4ea027604533896badf53 ), smtp.forwardemail.net:2587 (IPv4) (smtp.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 smtp.forwardemail.net:2465 (IPv4) is down
In [`fbda071`](https://github.com/forwardemail/status.forwardemail.net/commit/fbda07156c5399648c5eac53e1ba3ebe62b1c5fc ), smtp.forwardemail.net:2465 (IPv4) (smtp.forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 forwardemail.net:443 (IPv6) is down
In [`b70e684`](https://github.com/forwardemail/status.forwardemail.net/commit/b70e6844eb3693d0065c2bdf933c2a4e56ffa403 ), forwardemail.net:443 (IPv6) (forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 forwardemail.net:443 (IPv4) is down
In [`c9229f8`](https://github.com/forwardemail/status.forwardemail.net/commit/c9229f8472a1a65c4800d37804afbc8ca19ebdce ), forwardemail.net:443 (IPv4) (forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 https://forwardemail.net (curl) is down
In [`cec1ae8`](https://github.com/forwardemail/status.forwardemail.net/commit/cec1ae8d1eacc6d2118582e7bb8bb289a5607fa3 ), https://forwardemail.net (curl) (https://forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 forwardemail.net:443 (SSL) is down
In [`54d5321`](https://github.com/forwardemail/status.forwardemail.net/commit/54d5321794fff0f84fcb438e9cafbdd120bce94f ), forwardemail.net:443 (SSL) (forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 forwardemail.net:443 (IPv6) is down
In [`a096a27`](https://github.com/forwardemail/status.forwardemail.net/commit/a096a270e63b3336066935c2d0d479e7c7d14042 ), forwardemail.net:443 (IPv6) (forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 forwardemail.net:443 (IPv4) is down
In [`07a8ff3`](https://github.com/forwardemail/status.forwardemail.net/commit/07a8ff33fbc787668d90da3fbcbc0e4a6765dab2 ), forwardemail.net:443 (IPv4) (forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 forwardemail.net:443 (IPv6) is down
In [`119ef8d`](https://github.com/forwardemail/status.forwardemail.net/commit/119ef8d37ef2dfa27710c170d21b3cd081e4b53c ), forwardemail.net:443 (IPv6) (forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 forwardemail.net:443 (SSL) is down
In [`af82151`](https://github.com/forwardemail/status.forwardemail.net/commit/af82151106ff3e8e4a0fd6bbbd613967d8fa5f76 ), forwardemail.net:443 (SSL) (forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
✓ 🛑 forwardemail.net:443 (IPv6) is down
In [`b2a9538`](https://github.com/forwardemail/status.forwardemail.net/commit/b2a953895452ec7aa2781450a55a8802786d45cb ), forwardemail.net:443 (IPv6) (forwardemail.net) was **down**: - HTTP code: 0 - Response time: 0 ms
Best Security Audit Companies
독립적인 사이버보안 연구 및 침투 테스트 회사에 대한 엄선되고 의견이 담긴 목록에서 최고의 보안 감사 회사를 찾아보세요.
Case Study: How Forward Email Powers Alumni Email Solutions for Top Universities
우리는 명문 대학과 그 동문을 대상으로 세계에서 가장 안전하고, 개인정보 보호가 강화되고, 유연한 이메일 전달 서비스를 구축했습니다.
How Email Forwarding Works: The Complete Guide to Forward Email's Service
당사 서비스를 가장 개인정보 보호에 중점을 둔 이메일 전달 솔루션 중 하나로 만들어주는 기술적 구현에 대해 알아보세요.
Introducing Our Self-Hosted Email Stack
완전한 오픈 소스, 셀프 호스팅 이메일 솔루션으로 완벽한 통제력, 투명성 및 개인 정보 보호 기능을 제공합니다.
The Ultimate Guide to Email Privacy Protection: How Forward Email Safeguards Your Communications
우리는 세계에서 가장 안전하고, 개인정보 보호가 강화되고, 유연한 이메일 전달 서비스를 구축했습니다.
Why Open-Source Email is the Future: Security, Privacy, and Transparency
오픈소스 이메일 솔루션이 폐쇄소스 대안보다 우수한 이유를 알아보세요.
Best Mail Server Providers
메일 서버(SMTP 서버) 호스팅을 위한 VPS 및 전용 서버 제공업체를 포괄적으로 비교합니다.
Best Email Spam Protection Filter
연락처 양식과 메일 서버에 대한 스팸, 피싱, 맬웨어, 광고 차단, 픽셀 추적 등을 방지합니다.
JavaScript Contact Forms Node.js
Node, React, React Native, Koa, Express, Fastify, Nodemailer SMTP를 사용하여 JavaScript 연락처 양식을 만들고 보내보세요.
Best Practices for Node.js Logging
Node.js 및 JavaScript 로깅에 대한 모범 사례, 표준 및 메타데이터에 대해 자세히 알아보세요.
Custom Fonts in Emails
Learn how to use custom fonts in HTML emails without design software. Complete guide with web font fallbacks, CSS techniques, and email client compatibility tips.
Email Testing for Browsers and iOS Simulator
여러 브라우저의 메일 클라이언트, 도구, 브라우저 및 iOS 시뮬레이터를 사용하여 이메일을 자동으로 테스트, 렌더링하고 미리 보세요.
Node.js DNS over HTTPS
Node.js 및 JavaScript 패키지를 사용하여 DNS over HTTPS 요청을 보내는 방법입니다. 완전한 코드 예제, 구성 튜토리얼, 안전한 DNS 해석을 위한 프로덕션 모범 사례를 제공합니다.
Node.js Email Templates
SMTP와 개발자 소스 코드 샘플, 예시 및 지침이 포함된 Node.js, React, Express, Koa, Nodemailer 및 JavaScript를 사용하여 이메일과 HTML/CSS 템플릿을 보내보세요.
Node.js Job Scheduler
Learn how to schedule jobs in Node.js and JavaScript using cron syntax. Complete guide with examples for task automation, recurring jobs, and production deployment.
Node.js Logging Service
Cabin은 최고의 Node.js 및 JavaScript 로깅 서비스이자 도구입니다.
Reserved Email Addresses
보안 문제로 인해 예약된 1,250개 이상의 일반, 관리자, 메일러 데몬 및 회신 불가 사용자 이름 목록입니다.