Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- The original official post confirms only external-domain sending and receiving delays, an identified cause, and mitigation in progress. It does not disclose the root cause, affected regions, or completion time.
- Preserve sender, recipient, subject, send time, Message-ID, NDR, and the business reference before retries create duplicate notifications, orders, or invoices.
- Use three minimal tests—internal to internal, internal to external, and external to internal—to establish scope, then run Message trace in Exchange admin center.
- Message trace status can lag actual processing by 5–10 minutes. An absent result shortly after sending does not prove the message never entered Exchange Online.
- During an official incident, do not change MX, SPF, connectors, transport rules, or proxy exits without evidence. Such changes complicate diagnosis and may introduce another failure.
- A consistent exit keeps administrative access and retest conditions comparable; it cannot repair Microsoft 365's server-side mail queues.
Official Scope: EX1467029 Reported at 20:37, With Mitigation Underway
At 20:37 Beijing time on September 4, 2026, @MSFT365Status reported EX1467029: users might experience delays sending to and receiving from external domains. Microsoft said it had identified the cause and was applying mitigation expected to finish shortly. The public post did not disclose the root cause, proportion of affected tenants, regions, backlog size, or exact recovery time.
The public X post is an incident signal, not a substitute for tenant-level status. Administrators should sign into Microsoft 365 admin center and check Health > Service health for tenant-scoped EX1467029 updates. Users without administrator access should give their organization's administrator sample times and Message-IDs.
Contain the Impact: Do Not Repeatedly Send or Immediately Change Domain Settings
For order confirmations, sign-in codes, support replies, invoices, payments, and cross-border store notifications, first pause any expansion of automatic retries. Classify tasks as confirmed delivered, explicitly failed, still waiting, or outcome unknown. Do not immediately resend messages with unknown outcomes: original and retry messages may arrive together after mitigation.
For each sample, record at least sender, recipient, subject, Beijing time, Message-ID, whether an NDR appeared, client, and the related business reference. Redact screenshots and tickets; do not publicly expose email addresses, message bodies, customer identities, order numbers, or authentication information.
Three-Direction Test Matrix: Establish Whether Only External Domains Are Affected
Choose a unique test subject that cannot trigger orders, payments, or automation. Test within the same tenant, from Microsoft 365 to an external domain, and from an external domain to Microsoft 365. Send one message per direction and record send time, first appearance in Message trace, arrival time, and final status.
If internal mail works while both cross-domain directions are delayed, the symptoms match the official incident's scope. If only one domain, connector, or sender fails, do not attribute everything to EX1467029. Handle explicit NDR, 550, SPF, certificate, or connector errors separately at their corresponding layer.
Message Trace: Inspect Received, Pending, Failed, and Delivered States
In Exchange admin center, open Mail flow > Message trace and search by sender, recipient, time range, or full Message-ID. Microsoft's documentation says Message trace can show whether the service received, rejected, deferred, or delivered a message, together with processing actions leading to its final state.
Trace data for new messages commonly lags by 5–10 minutes, so an immediate absence is not a reason to resend. Record status, event time, direction, connector name, and Network Message ID. If trace reports delivered but the message is absent from the inbox, check junk mail, quarantine, forwarding, transport rules, and the receiving system.
Separate Microsoft Service Failures, Domain Configuration, and Proxy Networking
Service-incident evidence includes EX1467029 covering the current tenant and time, simultaneous delays across several external domains, and consistent pending or transport delays in Message trace. Domain configuration problems usually concentrate on one domain with MX, SPF, certificate, connector, or NDR evidence. Microsoft recommends validating connectors in Exchange admin center and checking SPF and MX separately.
Proxy or local network problems mainly affect access to Outlook, Exchange admin center, or DNS resolution and connections to target addresses. They cannot clear mail already backed up in Microsoft 365's transport pipeline. Use the proxy connection troubleshooting checklist only with independent evidence such as DNS, TLS, connection timeout, or proxy 407 errors. Keep the same device, account, and fixed exit throughout the comparison.
Business Continuity: Prepare Alternate Channels for Orders and Verification Codes
For time-sensitive orders, payments, account verification, and customer support, use in-site notices, established support tickets, or another verified channel to explain that email may be delayed. Do not publish sensitive order information on social media. Alternate channels should convey status and next steps without bypassing existing identity verification.
Pause automation that continues only after an email arrives, and retain event IDs, business idempotency keys, and original sending records. If a message relates to an order, refund, password reset, or account permission, query the business system before resuming. An email missing from the inbox does not mean the underlying action was never executed.
Recovery Criteria: Allow the Queue to Drain After the Official Update
After mitigation completes or the incident is marked resolved, first observe whether older messages are arriving, then repeat the three-direction test with new unique subjects. Before gradually restoring bulk notifications and automatic retries, confirm at least an updated Service health status, no persistently pending trace results, and cross-domain delivery times back at the team's baseline.
If only one domain still fails after official recovery, investigate its DNS, SPF, connectors, certificates, rules, or receiving system. If the admin portal also fails only on one network, compare using a fixed exit. To learn about static residential IPs for repeatable administrative-network conditions, visit the PuppyIP website, but do not describe an IP change as a fix for an Exchange Online service incident.
Sources
Frequently Asked Questions
What does EX1467029 affect?
Microsoft's public post reports delays for some users sending to or receiving from external domains. It does not say every tenant, every region, or internal mail is affected.
Can I immediately resend an email that has not arrived?
Check Message trace and preserve Message-ID first. Resending an unknown-outcome message may create duplicate notifications, codes, orders, or invoices when the queue recovers.
Why is a newly sent message temporarily absent from Message trace?
Microsoft documents a possible 5–10 minute lag between actual processing and trace status. Wait through that window, then narrow the search using the full Message-ID, sender, recipient, and time range.
Should I change MX, SPF, or connectors?
Not solely because an official incident exists. Make scoped, reversible changes only when evidence points to a single-domain problem, explicit NDR, DNS issue, or failed connector validation.
Can a different proxy or IP restore cross-domain email?
It cannot repair Microsoft 365's server-side transport delays. A fixed exit helps keep administrative access and retest conditions consistent, but investigate the proxy only with network evidence such as DNS, TLS, connection timeout, or 407 errors.
Can I resend everything once Microsoft says mitigation is complete?
That is not recommended. Confirm the old queue has drained and Message trace has returned to baseline, then validate small samples in all three directions. Reconcile unknown business outcomes before gradually resuming batches.