All Systems Operational

About This Site

Routine server maintenance
Please note: Inxmail performs client, server and infrastructure updates during regular maintenance slots. Maintenance slots are scheduled between 5:30 and 7:30 AM on Thursdays. On average a downtime of approximately 10 minutes can be expected.

Unscheduled downtime
Temporary restrictions outside our maintenance slots will occur very rarely. We are constantly improving the performance and reliability of our systems.
Still, it is important to us that you know in case there should be any limitations.

This status page informs you about temporary restrictions of our programs. Subscribe to our RSS or Atom feed to be up to date or see the online help for more information.

Uptime over the past 90 days. View historical uptime.
New Xperience Operational
90 days ago
100.0 % uptime
Today
New Xperience Operational
90 days ago
100.0 % uptime
Today
Inxmail Professional Operational
90 days ago
99.98 % uptime
Today
Inxmail Professional ? Operational
90 days ago
99.97 % uptime
Today
API Operational
90 days ago
100.0 % uptime
Today
Inxmail Commerce / Mail Relay Operational
90 days ago
100.0 % uptime
Today
Inxmail Commerce Operational
90 days ago
100.0 % uptime
Today
Mail Relay Operational
90 days ago
100.0 % uptime
Today
API Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Past Incidents
Feb 15, 2025

No incidents reported today.

Feb 14, 2025

No incidents reported.

Feb 13, 2025
Latest release of Microsoft Defender may temporarily cause loading time issues when working with Inxmail Professional
Resolved - With today's release, this issue has been resolved for all customers in our regular update slots.
Feb 13, 09:33 CET
Monitoring - Wichtige Information: Verzögerung beim Öffnen von Mailings

Aktuell kann es zu mehreren Minuten Verzögerung beim Öffnen Deiner Mailings kommen. Dieses Problem tritt auf, wenn die neueste Version des Microsoft Defenders installiert ist, da dieser eine von uns verwendete Komponente – den JxBrowser/Chromium – auf Integrität prüft.

Wir sind bereits dabei, auf dieses Update zu reagieren, und arbeiten mit Hochdruck an einer schnellen Lösung. Diese wird voraussichtlich nächste Donnerstag (13.02.2025) ausgespielt.

Ein Workaround ist für die Übergangszeit verfügbar, bitte wende dich für weitere Details an deiner Ansprechperson.
__________________________________

Important information: Delay when opening mailings

There may currently be a delay of several minutes when opening your mailings. This problem occurs when the latest version of Microsoft Defender is installed, as it checks the integrity of the component - the JxBrowser/Chromium.

We are already responding to this update and are working hard to find a quick solution. This is expected to be rolled out next Thursday (13/02/2025).

A workaround is available for the transition period, please get in touch with your contact person for further details.
Feb 5, 17:10 CET
Feb 12, 2025

No incidents reported.

Feb 11, 2025

No incidents reported.

Feb 10, 2025

No incidents reported.

Feb 9, 2025

No incidents reported.

Feb 8, 2025

No incidents reported.

Feb 7, 2025

No incidents reported.

Feb 6, 2025

No incidents reported.

Feb 5, 2025
Feb 4, 2025

No incidents reported.

Feb 3, 2025
Inxmail Professionel Webspace temporarily unavailable
Resolved - From approximately 13:50 to 15:40 your Inxmail Professional webspaces and some adjacent applications may have been temporarily restricted.
This was due to a third party error, which our techniciens identified and were able to resolved with our partner.
Should you still have image display issues in the web view, we recommend to delete your browser cache.
Thank you for your understanding. This incident has been resolved.
Feb 3, 14:00 CET
Feb 2, 2025

No incidents reported.

Feb 1, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage