EyalSec status: All systems operational
If something in EyalSec is not working for you, this page tells you within about five minutes whether the problem is on our side. It shows the live state of the website, the dashboard and API, and the documentation, with response times and the history of every incident.
- Status page: https://eyalsec.github.io/status/
- Help with your account or a machine: support@eyalsec.com
- Security reports: security@eyalsec.com
| Service | Check |
|---|---|
| Website | GET https://eyalsec.com answers with a success status |
| Dashboard and API | GET https://eyalsec.com/healthz answers and its body reads ok |
| Documentation | GET https://eyalsec.com/docs answers with a success status |
Each check runs every five minutes from GitHub's hosted runners. When one
fails, an issue opens with the
status label, and the same issue closes on its own when the service answers
again, so the issue list doubles as the incident history. GitHub can start a
scheduled run a few minutes late when it is busy, so read the times as close,
not exact.
| URL | Status | History | Response Time | Uptime |
|---|---|---|---|---|
| Up | website.yml |
|
||
| Up | dashboard-and-api.yml |
|
||
| Up | documentation.yml |
|
This page runs on Upptime by
Anand Chowdhary and its contributors, an uptime
monitor built entirely from GitHub Actions, Issues and Pages. Thank you to
them: it lets us publish our availability in the open without running another
server. The checks live in .upptimerc.yml, and every
result is committed to history/, so the record can be audited
line by line.
EyalSec is a secure Python that catches injection as your app runs: es-python runs your Python app unchanged and follows untrusted input to the SQL query, shell command or file path that uses it, then reports each flow or stops it. See eyalsec.com, or book a live demo.
- Code: MIT
- Data in
history/: Open Database License