Welcome to nginx!

If you see this page, the nginx web server is successfully installed and working. Further configuration is required.

For online documentation and support please refer to nginx.org.
Commercial support is available at nginx.com.

About this host

This server is operated by the platform infrastructure team and is currently serving a default landing while the application stack is being provisioned. No sensitive endpoints are exposed at this host. Production traffic is routed through a separate ingress tier with its own TLS termination and request filtering, so reaching this page typically means you have connected directly to a backend node rather than through the public edge.

If you arrived here by following a link from another website, please contact the administrator of that site. The hostname for this node is edge-fra-04.fastgrid.example and it is part of a small pool of reverse-proxy front-ends located in Frankfurt am Main. Diagnostic information for operators is available over the loopback interface only.

Operator notes

Configuration files are located under /etc/nginx/ and are managed by the central deployment pipeline. Manual edits on this host are overwritten on every release; please open a change request in the internal tracker if a configuration update is required. The current release channel is stable-1.25 and changes are rolled out in three waves with at least ten minutes between waves.

Common operator tasks for this tier:

• Verify upstream connectivity via the /_status loopback endpoint, which exposes a small JSON document with upstream weights and current TCP/TLS handshake counters.
• Inspect recent access lines through the central log aggregator; on-host log retention is limited to the previous four hours, after which the journal is rotated and shipped off the node.
• Drain the node from the load-balancer pool before scheduled maintenance, either via the ingress controller's drain command or by setting the local maintenance flag on disk.
• Confirm that worker counts match the expected baseline for the assigned profile; mismatches usually indicate a stale configuration revision that has not yet been reconciled.
• Restart cleanly after configuration reloads, allowing existing keepalive connections to terminate normally rather than dropping them mid-request.

Reaching the administrator

Abuse reports, peering questions, and general infrastructure correspondence should be directed to noc@fastgrid.example. Replies are sent during European business hours. Out-of-hours incidents affecting service availability are tracked through the dedicated paging channel and are not served by this address. Please include the request identifier from any error page when reporting an issue; it allows the operations team to correlate the event against access logs without exposing additional information about the upstream.

The infrastructure is documented in the operations handbook for the edge-tier, which is reviewed every quarter. Notable changes are summarised in the release notes attached to the deployment journal.

Thank you for using nginx.

nginx/1.25.3 — edge-fra-04.fastgrid.example — release channel stable-1.25