Snapshot 317433

Document
Status page
URL
https://status.duocircle.com/
Fetched
HTTP status
200
Content type
text/html;charset=UTF-8
Fetch mode
browser
Size
73175 bytes
SHA-256 (raw)
1e5548473feab6bb0461cf34265ac0bfcaef7a922ea0306514ae988eb52cbf50
SHA-256 (normalized text)
0506c3dc07de65c66f5a9735d6d41646024bbb6b299b07ffd29da50457a3c6e4

Normalized text

Scripts and page chrome removed; this is what change detection compares.

Active Incident
Discontinuation of TLS 1.0 and 1.1 on SMTP
This incident has been open for 3 days 13 hours.
Incident Start Time
Nov 17, 2026 02:00:00 PM UTC
Affected Components
Inbound - mx1.eu.mailhop.org, Inbound - mx1.mailhop.org, outbound.mailhop.org, Inbound - mx2.mailhop.org, Inbound - mx1.eu.mailhop.org
Incident Status Updates
In Progress
On 9 December 2026, both Inbound and Outbound mail servers will stop support for TLS 1.0 and TLS 1.1. After that date, our servers accept only TLS 1.2 and TLS 1.3.
What changes
During STARTTLS, our servers will accept only TLS 1.2 and TLS 1.3. TLS 1.0 and TLS 1.1 have known security problems.
We also remove anonymous cipher suites. These suites do not authenticate the server, so they do not protect your SMTP password.
The change applies to all ports: Inbound port 25, and Outbound ports 25, 465, 587 and 2525.
Our hostnames and certificates do not change.
Do you need to do anything?
Outbound customers: A mail client, application or device that supports only TLS 1.0 or 1.1 will not be able to send email after the change.
These systems often use TLS 1.0 or 1.1:
Windows Server 2008 R2 or older, and Windows 7 or older
Applications built on .NET Framework 4.5 or older
Applications that use Java 7 or older, or OpenSSL 1.0.0 or older
Printers, scanners and copiers with old firmware
To check a system, send a test message from it through Outbound. Find the message in the Message Log Viewer at logs.duocircle.com, and open its "Text log". The line "<smtpd> STARTTLS enabled ..." must show TLSv1.2 or TLSv1.3.
Inbound customers: You do not need to change anything. A server that sends to you with TLS 1.0 or 1.1 must use TLS 1.2 or newer after the change. If it cannot, it sends without encryption or cannot deliver. This depends on the configuration of the sending server.
Schedule
All times are UTC. We will update this notice after each step.
Date and time (UTC)
Change
Tue 17 Nov 2026 @ 14:00–14:15
15 minute test, then we enable TLS 1.0 and 1.1 again
Tue 24 Nov 2026 @ 14:00–15:00
1-hour test, then we enable TLS 1.0 and 1.1 again
Thu 26 Nov 2026 @14:00–18:00
4-hour test, then we enable TLS 1.0 and 1.1 again
Tue 1 Dec 2026 @ 14:00–18:00
4-hour test, then we enable TLS 1.0 and 1.1 again
Wed 9 Dec 2026 @ 14:00
Permanent change
If you see a problem
If you see TLS errors with Mailhop during or after these steps, contact support@duocircle.com. Tell us the time, the server hostname, the port, and the full error message.
Posted on Nov 17, 2026 at 02:00:00 PM UTC (3 days 13 hours ago)
Component Summary
Component Name
Component Status
Inbound - mx1.eu.mailhop.org
Under Maintenance
Inbound - mx1.eu.mailhop.org
Under Maintenance
Inbound - mx1.mailhop.org
Under Maintenance
Inbound - mx2.mailhop.org
Under Maintenance
outbound.mailhop.org
Under Maintenance
Customer Portal
Operational
Phish - Portal - Website Check
Operational
Phish - Portal - Website Check - Page Load Time
Operational
Phish - URLF - Website Check
Operational
Component Status History
Nov 21 to Nov 15
Nov 21 to Nov 15
Component Name	Uptime	Nov 21	Nov 20	Nov 19	Nov 18	Nov 17	Nov 16	Nov 15
Inbound - mx1.eu.mailhop.org	100%
Inbound - mx1.eu.mailhop.org	100%
Inbound - mx1.mailhop.org	100%
Inbound - mx2.mailhop.org	100%
outbound.mailhop.org	100%
Customer Portal	100%
Phish - Portal - Website Check	100%
Phish - Portal - Website Check - Page Load Time	100%
Phish - URLF - Website Check	100%
Operational
Informational
Under Maintenance
Degraded Performance
Partial Outage
Major Outage
Incident History
Nov 21, 2026
No incidents have been reported.
Nov 20, 2026
No incidents have been reported.
Nov 19, 2026
No incidents have been reported.
Nov 18, 2026
No incidents have been reported.
Nov 17, 2026
No incidents have been reported.
Nov 16, 2026
No incidents have been reported.
Nov 15, 2026
Maintenance: DuoCircle customer portal and API
Incident Duration
From Nov 15, 2026 12:30:00 AM to 1:03:12 AM UTC (33 mins 12 secs)
Affected Components
Customer Portal
Incident Status Updates
Completed
The scheduled maintenance is complete.
Posted on Nov 15, 2026 at 01:03:12 AM UTC
In Progress
When: Sunday 2026-11-15, 00:30 to 01:30 UTC
We will do maintenance on the servers of the DuoCircle customer portal and API.
Impact: These services are not available during the work:
portal.duocircle.com: login, billing, invoices, payments, and account changes
api.duocircle.com: all API calls
We expect the outage to be 30 minutes or less, non-contiguous, in the window.
Not affected: Email filtering and delivery continue as usual.
You do not have to do anything. We will update this page when the work is complete.
Posted on Nov 15, 2026 at 12:30:00 AM UTC
Timezone Information
All times are shown in UTC time zone.