MessageXchange Outage History

MessageXchange is up right now

MessageXchange had 2 outages in the last 2 years totaling 23h 42m of downtime — averaging 0.1 incidents per month.

There were 2 MessageXchange outages since August 21, 2025 totaling 23h 42m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.messagexchange.com

Minor September 9, 2025

MessageXchange Beta Test environment issue

Detected by Pingoru
Sep 09, 2025, 09:18 PM UTC
Resolved
Sep 10, 2025, 02:01 AM UTC
Duration
4h 42m
Affected: Beta test environment
Timeline · 4 updates
  1. investigating Sep 09, 2025, 09:18 PM UTC

    We are investigating an issue affecting our Beta Test environment, and will update with more information shortly.

  2. monitoring Sep 09, 2025, 09:28 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. monitoring Sep 09, 2025, 09:28 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Sep 10, 2025, 02:01 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 21, 2025

www.messagexchange.com certificate issues

Detected by Pingoru
Aug 21, 2025, 04:31 AM UTC
Resolved
Aug 21, 2025, 11:31 PM UTC
Duration
19h
Affected: MessageXchange web siteMessage processing
Timeline · 2 updates
  1. monitoring Aug 21, 2025, 04:31 AM UTC

    We are aware of some clients having problems connecting to www.messagexchange.com since our certificate change this morning. If you're having issues, please check that your certificate store is up to date. Normally this is done as part of your operating system's patches. If not up to date, you may need to manually load the new Sectigo intermediate certificate - this included in our cert chain, available for download here: https://support.messagexchange.com/support/solutions/articles/7000058245-www-messagexchange-com-certificate Please contact Support if you need more information. [email protected]

  2. resolved Aug 21, 2025, 11:31 PM UTC

    This incident has been resolved.

Read the full incident report →