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
UI / View
?
Operational
Portal
?
Operational
⮑ External verifications
?
Operational
Phonenumber / SMS
Operational
iDIN
Operational
itsme sign (qualified signature)
?
Operational
itsme Identification
?
Operational
iDEAL
Operational
DigiD
Operational
eHerkenning
Operational
eIDAS
?
Operational
ZealiD Qualified
Operational
Auth and login service
?
Operational
ID Proof
?
Operational
Webforms
?
Operational
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
Migration to new document signing service Nov 12, 2025 21:00-23:00 CET
Update -
We will be undergoing scheduled maintenance during this time.
Nov 10, 2025 - 15:59 CET
Nov 10, 2025 - 15:59 CET
Scheduled -
We will be conducting scheduled maintenance on Wednesday, November 12, from 21:00 to 23:00 CET.
During this time, the platform will be temporarily unavailable. This maintenance window is necessary to start the migration to a new service for handling the signing and sealing of documents, as well as the migration to a new document signing certificate.
These updates are part of our ongoing efforts to enhance platform reliability, performance, and security.
If you have any questions, please reach out to us at support@signhost.com.
Nov 05, 2025 - 15:23 CET
During this time, the platform will be temporarily unavailable. This maintenance window is necessary to start the migration to a new service for handling the signing and sealing of documents, as well as the migration to a new document signing certificate.
These updates are part of our ongoing efforts to enhance platform reliability, performance, and security.
If you have any questions, please reach out to us at support@signhost.com.
Nov 05, 2025 - 15:23 CET
Planned maintenance Nov 20, 2025 21:00-22:00 CET
Our backend will be undergoing scheduled maintenance during this time. No downtime is expected.
Posted on Nov 10, 2025 - 11:48 CET
Posted on Nov 10, 2025 - 11:48 CET
Migration from Newtonsoft.Json to System.Text.Json Nov 25, 2025 08:00-09:00 CET
Update -
We will be undergoing scheduled maintenance during this time.
Nov 10, 2025 - 09:20 CET
Nov 10, 2025 - 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, 2025 - 09:17 CET
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, 2025 - 09:17 CET