客户报告与外交部编码有关的问题
Issues轻微事件
受影响的组件
Paubox Dashboard
- investigating
我们正在调查一个没有收到外交部守则的问题.
- identified
我们已查明这一问题,并正在设法解决问题。 TOTP(认证软件)和密码选项在我们进行这项工作时都具有功能.
- resolved
大约133个代码卡在了我们的内部排队中——它们已经发布,外交部服务现在正在如预期的那样运作。 本季度正在重写后端,以确保问题无法重现.
自动翻译自官方事件更新。
57 Paubox incidents · 2023年5月 — official updates, affected components, duration and resolution details.
我们正在调查一个没有收到外交部守则的问题.
我们已查明这一问题,并正在设法解决问题。 TOTP(认证软件)和密码选项在我们进行这项工作时都具有功能.
大约133个代码卡在了我们的内部排队中——它们已经发布,外交部服务现在正在如预期的那样运作。 本季度正在重写后端,以确保问题无法重现.
自动翻译自官方事件更新。
一些出站和营销客户可能在仪表板的邮件日志和Paubox营销区看到信息不完整或缺失,而营销页面可能加载或超时. 电子邮件发送不受影响。 信件通常在发送、接收、过滤和加密。 没有丢失客户数据,这只影响最近的活动显示方式。 我们已经查明了邮件日志问题的原因,并已定案。 我们仍在调查营销问题。 我们将不断更新这一页.
用外出电子邮件和营销显示问题已解决 .
自动翻译自官方事件更新。
We have identified an issue blocking log in to our admin app and should have a fix in place shortly.
A fix has been implemented and we are monitoring the results - log in is confirmed functional again.
The incident has been resolved.
我们正在调查来自一些入境安全客户的报告 他们的入境检疫是空白的 尽管邮件被标记为 检疫在其邮件日志.
没有发现缺陷,也没有运送任何更改。 顾客可能遇到两个原因: 1) Paubox 几乎是日常的运运改进 - 如果突然有不可用的东西, 您可能需要登录/ 返回以刷新您的访问权限 。 2)为使出入境检疫显示结果,必须选择"所有类别"或至少一个类别. 如果没有选择分类,则页面将显示没有结果.
自动翻译自官方事件更新。
我们目前正在调查这一问题.
这一事件已经得到解决.
自动翻译自官方事件更新。
客户报告入境安全隔离放行不起作用 正在修复中.
一项措施已经到位,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
Beginning at 6AM UTC today, Microsoft began presenting an updated certificate on some of their hosted mail accounts, and our outbound servers' list of trusted authorities doesn't yet include the new one. As a result, a portion of outbound emails to recipients hosted on Microsoft 365 are currently being routed through the Paubox Secure Message Center instead of delivered directly to the recipient's inbox. Affected recipients receive a notification with a secure link to view the message in our portal. No emails have been lost and no data security has been compromised — the Secure Message Center fallback is operating as designed to protect message content when direct delivery cannot be verified. We are updating the certificate and should have a resolution shortly.
We are rolling out a new cert server by server and monitoring.
Direct delivery to Microsoft 365 recipients has been restored. Messages sent during the incident were delivered securely via the Paubox Secure Message Center; no mail was lost. Thank you for your patience.
Some customers using our hosted/webmail reported certificate issues blocking access on mobile devices. We have refreshed our certificates again - if you are still seeing an error, please clear your cookies and cache. If this does not resolve your issue, take a screenshot and email [email protected] so we can isolate your specific issue.
This incident has been resolved.
We have had a few calls from some Google Workspace customers report inbound & outbound delays on internal emails which Down Dectector corroborates - see https://downdetector.com/status/gmail/ - we will continue to monitor this.
Google has updated this site with more details: https://support.cloud.google.com/portal/system-status?product=WORKSPACE&cssp=true We will continue to monitor.
Google has published this https://www.google.com/appsstatus/dashboard/incidents/224ozRqzW4sFBDK8hLnT We continue to monitor.
Google has been releasing backed up mail - we expect resolution by 3pm PDT (their resolution estimate).
Google has marked this issue resolved.
We are currently investigating outbound delays for Hosted mail & SMTP server solution customers. We have not observed issues for any other outbound customers at present.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
Queues have recovered and delays as resolved.
We are currently investigating inbound mail delays.
We have identified a database issue and are implementing a fix.
A fix is in place and we are monitoring results.
We are continuing to monitor - the deferred mail queue has dropped ~60% from the highest spike and new mail is flowing. We anticipate full resolution within the hour.
Inbound queues are healthy again. We'll complete an internal post mortem tomorrow and have an RCA available upon request.
Customers using our hosted/webmail platform and smtp server solution have reported all their mail in logs is marked as queued. We are investigating.
We have identified the cause and are implementing a fix.
A fix has been implemented and we are monitoring results.
We observed status updates universally, but we discovered 2 customers still experiencing too many "queued" emails. Because the larger issue is resolved, we'll close this incident - but we are working on a fix and will communicate directly with the affected parties.
Outbound email customers are reporting delays in excess of 10 minutes. We are investigating.
The issue has been identified and a fix is in progress.
A fix has been implemented and we are monitoring results - current email testing is coming in under 5 minutes.
This incident has been resolved. Queues have returned to normal and delayed mail is being delivered.
We are investigating why users are unable to verify MFA codes and begin fresh sessions in our admin app. If you are already logged in, you can navigate as usual.
The issue has been isolated and a fix is in progress.
A fix has been implemented & we are monitoring results.
The issue has been resolved.
We are observing intermittent delivery delays affecting a limited subset of outbound messages to certain external domains (including hotmail.com and outlook.com). Our systems remain fully operational. We are actively monitoring and adjusting sending patterns as needed.
We are no longer observing intermittent delays - all mail that was deferred yesterday has been delivered.
Inbound email customers have reported a delay in their quarantine log propagation. Emails are marked quarantine in their mail log, but do not appear in quarantine until hours later. There is no mail flow or data loss issue, but we have identified a problem with timestamps and are working to correct it.
We have shipped a correction and are monitoring the results.
This incident has been resolved.
Microsoft365 outage reported on the Microsoft Service Health Status page
This incident has been resolved. Microsoft Service Health Status - https://status.cloud.microsoft/m365/referrer=serviceStatusRedirect
Some customers report outbound mail delays in excess of 10 min - we are investigating
We have identified the issue and are working on a fix.
We're continuing to work on the fix for this issue.
A fix is in place a new mail is flowing normally - we expect another 3-4 hours for the deferred queue to unspool. We'll continue to monitor and update you if anything changes.
Customers are reporting missing outbound mail log data - we are investigating.
Mail log data has been restored. We are continuing to monitor the deferred queue while it processes the backlog.
The deferral queue has cleared and outbound is functioning normally.
Some customers are reporting outbound deferrals from Yahoo & affiliates - we are keeping an eye on this.
We are continuing to monitor reports of Yahoo deferrals independent of today's incident.
Email to yahoo.com and affiliates (aol.com, verizon.net, att.net, sbcglobal.net, cox.net, etc) is delivering as normal.
We are investigating reports of HTTP response timeouts on Email API.
We have identified the issue and are working on a fix.
We have implemented a fix and are monitoring the results.
We have been unable to recreate timeout errors post update.