All Systems Operational
About This Site
This is the statuspage of Evidos, evidence in online services. 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. Evidos is a market leader in the field of electronic signatures and electronic identification.
API
Operational
UI / View
?
Operational
Portal
Operational
⮑ External verifications
Operational
eHerkenning
Operational
DigiD
Operational
iDEAL
Operational
iDIN
Operational
Phonenumber / SMS
Operational
itsme Identification
?
Operational
eIDAS
?
Operational
itsme sign (qualified signature)
?
Operational
Auth
?
Operational
Queueing backend
?
Operational
ID Proof
?
Operational
Webforms
?
Operational
External services
Operational
SMS Service
Operational
CDN-EU1
Operational
CDN-EU2
Operational
Mail service
?
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
No fixed IP addresses for postback messages
Feb 28, 12:00-13:00 CET
Update -
##Update
Adding postback security headers and static postback urls is now operational and can be accessed in the web portal.
See this page for explanation of this new feature:
https://intercom.help/evidos/en/articles/4739431-postback-header-security
We start using variable IPs in the following months, and will update you through this channel. When using postback security headers you can be sure to safely migrate away from whitelisting our IP, which is and was unsupported.
##Update
Mar 1, 00:00 CET
Adding postback security headers and static postback urls is now operational and can be accessed in the web portal.
See this page for explanation of this new feature:
https://intercom.help/evidos/en/articles/4739431-postback-header-security
We start using variable IPs in the following months, and will update you through this channel. When using postback security headers you can be sure to safely migrate away from whitelisting our IP, which is and was unsupported.
##Update
Mar 1, 00:00 CET
Scheduled -
##Update
Adding postback security headers and static postback urls is now operational and can be accessed in the web portal.
See this page for explanation of this new feature:
https://intercom.help/evidos/en/articles/4739431-postback-header-security
We start using variable IPs in the following months, and will update you through this channel. When using postback security headers you can be sure to safely migrate away from whitelisting our IP, which is and was unsupported.
##Update
For our API implementations our customers are using postbacks to proactively process the transaction status.
We never recommended nor supported to perform IP address whitelisting for security, but some customers might use this method.
From end of February we will move our postback services and introduce flexible IP's. So any customer that still has this IP whitelisting configured , this is NOT POSSIBLE anymore from the end of February. Customers can use the checksum method.
Because we want to improve our security all the time we will introduce a new possibility to validate if the postback messages are coming from our environment. We will make it possible to configure security authorization headers in Q1.
See the full message and explanation of the new feature here.
here https://intercom.help/evidos/nl/articles/4739431-postback-header-security
Dec 21, 18:43 CET
Adding postback security headers and static postback urls is now operational and can be accessed in the web portal.
See this page for explanation of this new feature:
https://intercom.help/evidos/en/articles/4739431-postback-header-security
We start using variable IPs in the following months, and will update you through this channel. When using postback security headers you can be sure to safely migrate away from whitelisting our IP, which is and was unsupported.
##Update
For our API implementations our customers are using postbacks to proactively process the transaction status.
We never recommended nor supported to perform IP address whitelisting for security, but some customers might use this method.
From end of February we will move our postback services and introduce flexible IP's. So any customer that still has this IP whitelisting configured , this is NOT POSSIBLE anymore from the end of February. Customers can use the checksum method.
Because we want to improve our security all the time we will introduce a new possibility to validate if the postback messages are coming from our environment. We will make it possible to configure security authorization headers in Q1.
See the full message and explanation of the new feature here.
here https://intercom.help/evidos/nl/articles/4739431-postback-header-security
Dec 21, 18:43 CET