All systems operational
This page reads straight from our own monitoring, the same one our engineers use. If you see green here and still have a problem, call us right away.
last check: 01:14:55
clusters operational
127/127
uptime over 365 days
100.00%
since the last incident
222 days
Services
The parts of the platform we monitor separately. If one of them goes down, you see it here before you notice it yourself.
operational
Clusters
Every cluster runs on our own hardware in Ede. Response time is measured from our monitoring node in the same data centre.
RUAL core
Ede, NL · operational
Recent incidents
What happened, how long it lasted and what we did about it. Including the small ones.
No incidents recorded in this period.
What the statuses mean
Three states, nothing more. We do not stretch the definition of green.
Operational
The service responds within its normal time and no alerts are open.
Degraded
The service works, but slower or with limited functionality. Someone on our side is on it.
Outage
The service is unreachable or barely reachable. We post what is going on and when it is fixed.
How we measure this
Monitoring that watches from inside the infrastructure, not from the outside.
From our own hardware
The checks run in the same data centre as the clusters. That way we measure what your environment actually does, not just whether the front page loads.
Racks across several floors
Our hardware sits across several floors and networks at BIT in Ede. If one path drops out, another takes over.
Automatic migration
If an outage persists, environments migrate automatically to an external data centre. We test that path, it does not just exist on paper.
Uptime is half the story
The same monitoring guards the security of every environment: every request logged, suspicious traffic blocked automatically.
You will want this view of your own environment
Every environment on Core gets its own statistics page: usage, performance and uptime, without you having to ask.