All Systems Operational

About This Site

This is the statuspage of Entrust - Signhost. You can monitor the availability and maintenance of our signing and identification platform. Please subscribe with the top right subscribe button on this site to get pro-active messages on (planned) maintenance or degraded performance. Signhost is a market leader in the field of electronic signatures and electronic identification.

API ? Operational
90 days ago
99.9 % uptime
Today
UI / View ? Operational
90 days ago
99.92 % uptime
Today
Portal ? Operational
90 days ago
99.89 % uptime
Today
⮑ External verifications ? Operational
Phonenumber / SMS Operational
iDIN Operational
itsme sign (qualified signature) ? Operational
itsme Identification ? Operational
iDEAL Operational
DigiD Operational
eHerkenning Operational
ZealiD Qualified Operational
IDV Sign (Onfido) ? Operational
Signhost QES ? Operational
Auth and login service ? Operational
90 days ago
99.95 % uptime
Today
ID Proof ? Operational
90 days ago
99.89 % uptime
Today
Webforms ? Operational
90 days ago
100.0 % uptime
Today
Signhost App Operational
Account and billing service ? Operational
External services Operational
SMS Service Operational
CDN-EU1 Operational
CDN-EU2 Operational
Mail service ? Operational
Entrust Services Operational
Entrust Remote Signing Service ? Operational
Entrust SAS corporate sealing ? Operational
Entrust IDaaS ? Operational
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.

Scheduled Maintenance

Planned maintenance Dec 17, 2025 21:00-22:00 CET

Our backend will be undergoing scheduled maintenance during this time. No downtime is expected.
Posted on Nov 25, 2025 - 10:55 CET
Messages being processed
Backend processing times ?
Nov 27, 2025

No incidents reported today.

Nov 26, 2025

No incidents reported.

Nov 25, 2025
Resolved - This incident has been resolved.
Nov 25, 13:12 CET
Monitoring - A fix has been implemented and we are monitoring the results.
Nov 25, 13:10 CET
Identified - The issue has been identified and a fix is being implemented.
Nov 25, 13:07 CET
Investigating - We are currently investigating this issue.
Nov 25, 11:33 CET
Completed - The scheduled maintenance has been completed.
Nov 25, 09:00 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 25, 08:00 CET
Update - We will be undergoing scheduled maintenance during this time.
Nov 10, 09:20 CET
Scheduled - Migration from Newtonsoft.Json to System.Text.Json

In our efforts to deliver better performance and streamline our services, we are migrating from Newtonsoft.Json to System.Text.Json for JSON serialization and deserialization in our APIs.
This migration introduces improvements and stricter handling of JSON data, which may require customers to review and adjust their API integrations for compatibility. Please read below for relevant details and examples.

________________________________________

Key Changes
1. Stricter JSON Standards:
- System.Text.Json enforces stricter JSON rules compared to Newtonsoft.Json. Adjustments may be required to ensure compliance with the following key standards:
- Quoted property names
- Consistent number formatting
- Avoiding trailing commas
- Correct handling of boolean values
2. Case-Sensitive Property Matching:
- Unlike Newtonsoft.Json, System.Text.Json is case-sensitive by default. Property names in your JSON data must match the API specifications precisely (including case).

________________________________________

Examples of Correct and Incorrect JSON

To assist with your adjustments, here are examples of bad and good JSON formatting based on common issues:

Quoted Property Names:

Only use double quotes around property names.

Bad:
SomeProperty: "Some text"
'SomeProperty': "Some text"


Good:
{
"SomeProperty": "Some text"
}

________________________________________

Trailing Commas:

Avoid using trailing commas in JSON.
Bad:
{
"SomeProperty": "Some text",
}

Good:
{
"SomeProperty": "Some text"
}

________________________________________

Boolean Values:

Ensure booleans are properly written as true or false without quotes.
Bad:
{
"IsSigned": "true"
}
Good:
{
"IsSigned": true
}
________________________________________

To ensure a smooth transition, we recommend you review your integration:

- Verify your JSON payloads adhere to proper formatting (using the above examples as a guide) and match the API specifications.

________________________________________

Timeline

This migration is scheduled for November 25th between 8:00 and 9:00 AM CEST. Please check whether any updates to your integrations are needed before this date, and make adjustments if necessary to avoid disruptions.


If you have any concerns about this date, please contact us at support@signhost.com.

We don’t expect any downtime.

Nov 10, 09:17 CET
Nov 24, 2025

No incidents reported.

Nov 23, 2025

No incidents reported.

Nov 22, 2025

No incidents reported.

Nov 21, 2025

No incidents reported.

Nov 20, 2025
Completed - The scheduled maintenance has been completed.
Nov 20, 22:00 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 20, 21:00 CET
Scheduled - Our backend will be undergoing scheduled maintenance during this time. No downtime is expected.
Nov 10, 11:48 CET
Nov 19, 2025

No incidents reported.

Nov 18, 2025
Resolved - This incident has been resolved.
Nov 18, 13:37 CET
Monitoring - A fix has been implemented and we are monitoring the results.
Nov 18, 13:33 CET
Identified - The issue has been identified and a fix is being implemented.
Nov 18, 13:31 CET
Investigating - Signers are experiencing issues when signing with a CSC Qualified verification method.
We are investigating the issues.

Nov 18, 13:08 CET
Nov 17, 2025

No incidents reported.

Nov 16, 2025

No incidents reported.

Nov 15, 2025

No incidents reported.

Nov 14, 2025

No incidents reported.

Nov 13, 2025

No incidents reported.