Customer console
Last check: respondingPublic web process check.
View checked endpointSERVICE STATUS
Service status.
Latest endpoint checks and confirmed incidents across d0.
Checking the age of these observations. The recorded results below describe the last check, not a current availability guarantee.
Production
Identity
Last check: respondingPublic identity metadata check.
View checked endpointPlatform
Last check: respondingPublic identity metadata check.
View checked endpointAccounting
Last check: respondingPublic identity metadata check.
View checked endpointE-Invoice
Last check: not verifiedPublic identity metadata check.
View checked endpointERiC
Last check: not verifiedPublic identity metadata check.
View checked endpointIsolated test environments
Platform
Last check: respondingPublic identity metadata check.
View checked endpointAccounting
Last check: respondingPublic identity metadata check.
View checked endpointE-Invoice
Last check: respondingPublic identity metadata check.
View checked endpointERiC
Last check: respondingPublic identity metadata check.
View checked endpointConfirmed incidents
No confirmed incidents were recorded in this publication. This does not establish that every service is available.
What these checks cover
A responding endpoint confirms its public HTTP contract at the recorded time. It does not prove a customer action, payment, tax submission, document validation, or customer resource is available. A failed check is an observation; confirmed incidents are published separately.
S3 buckets and Kubernetes clusters have customer-specific endpoints. Check their resource state in the customer console. Product capabilities and activation requirements remain in the API documentation.
Checks are scheduled every ten minutes. Delayed or missing checks become unknown after fifteen minutes. Scheduling and hosting can fail independently; timestamps remain visible. No uptime percentage or high-availability promise is inferred.