500 Internal Server Error

An error occurred while the server was processing your request.

The fault is on the server side. Our operations team has been notified and is investigating the incident. You may try reloading the page in a few minutes.

What happened

The web application attempted to read a resource that returned an unexpected response from an upstream component. The request did not complete and was logged for review by an on-call engineer.

This message is automatic. No data submitted in the failing request has been persisted. If you submitted a payment, no charge was captured; if you submitted a form, the form was not saved.

What you can do

Wait a minute or two and reload the page in your browser.
If you were submitting a form, verify that the data was saved before resubmitting. Duplicate submission is safe but may produce duplicate records.
If the error continues for more than ten minutes, please contact the administrator at the e-mail address shown at the bottom of this page and quote the request identifier.
Status updates for this service are published on the operations channel. The current status is reported below.

Diagnostic information

request-id: 4b91-c2ad-7f1e-0021
host:       web-01.dc-ams.tessellate.local
time:       19/May/2026:15:02:11 +0000
upstream:   accounts-svc / unhealthy (4xx upstream rate > 60%)
retry:      ~60s recommended
incident:   INC-2026-05-19-014

Recent incident timeline

time (UTC)	event
15:01:24	health-check failure on upstream accounts-svc detected
15:01:48	circuit breaker opened, traffic shed
15:02:11	request 4b91-c2ad failed and returned 500
15:02:30	on-call engineer paged, acknowledged
15:04:00	investigation in progress

Frequently asked questions

Is my data lost? No. Reads do not produce side effects, and writes that returned 500 were rolled back at the database layer.

Should I retry? Yes, after 60 seconds. The system uses idempotent request identifiers, so a retry will not produce duplicate records if your original request reached the database.

How do I know when it is fixed? Reload this page. When the underlying service is healthy you will see the regular application instead of this notice.

If the message persists please reference the identifier above when contacting noc@tessellate.local.