CodeTwo Outage History
7 incidents recorded over the last 365 days, 7 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded CodeTwo Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 26, 2026 | Outlook add-in service disruptionOur investigation confirmed that the issue was caused by the new SSL certificate issued by GoDaddy. The certificate used a new certificate authority chain that was not yet trusted by some operating systems, particularly… | 1h 38m | Resolved |
| Jun 2, 2026 | [Germany] Delays in email deliveryMicrosoft reports in EX1331830 that their configuration changes have reached approximately 50% of the affected infrastructure and message queues are steadily improving. This is also confirmed by our telemetry. More… | 9h 40m | Resolved |
| Mar 18, 2026 | [Global] Email delivery issues# Summary On March 18, 2026, a small subset of CodeTwo customers experienced temporary issues with email delivery. The incident was caused by a Microsoft networking and DNS‑related issue within Microsoft 365… | 2h 50m | Resolved |
| Feb 7, 2026 | [West US] Delayed email delivery caused by Azure availability issuesThis incident has been resolved. | 1h 47m | Resolved |
| Jan 22, 2026 | [US] Email delivery delays due to Exchange Online Protection unavailabilityThe fix implemented by the MS Exchange Online team worked and our service is fully operational again. The most recent update from Microsoft: "We’re continuing to see steady improvements in service availability for… | 8h 12m | Resolved |
| Jan 12, 2026 | [UK] Sign-in issues due to Azure backend communication problemsThis incident has been resolved. | 45 min | Resolved |
| Nov 6, 2025 | [Global] Image loading problems in email signatures inserted by add-insMicrosoft has published official information about this incident on the Service Health Dashboard (SHD) under ID: EX1183800. Please refer to the SHD for more details. Since this officially confirms that the issue was… | 36h 54m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next CodeTwo incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This CodeTwo Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before CodeTwo acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single CodeTwo outage in this window ran 1d 12h, against a mean recovery of 8h 49m. If you depend on CodeTwo in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.