Intrusion Command Hub status
All services operational
Updated . Each service is checked every 5 minutes from AWS us-east-1, outside Command Hub's cluster and Region. The same data is available as status.json.
Services
| Service | Endpoint | Now | Availability, last 30 days |
|---|---|---|---|
| Spotlight web console | hub.ramp.intrusion.com | Operational HTTP 200 | 100.00% |
| Device management and reporting API | control.ramp.intrusion.com | Operational HTTP 200 | 100.00% |
| Device registration | registration.ramp.intrusion.com, cloud-registration.ramp.intrusion.com | Operational HTTP 200; HTTP 200 | 100.00% |
| Device communications and telemetry ingest | shieldlogscert.ramp.intrusion.com | Operational TLS handshake completed (TLSv1.3) | 100.00% |
| Sign-in | kc.ramp.intrusion.com | Operational HTTP 200 | 100.00% |
Incidents
No incidents posted in this period.
Daily availability
| Date | Spotlight web console | Device management and reporting API | Device registration | Device communications and telemetry ingest | Sign-in |
|---|---|---|---|---|---|
| 100.00% | 100.00% | 100.00% | 100.00% | 100.00% | |
| 100.00% | no data | no data | no data | no data | |
| 100.00% | no data | no data | no data | no data | |
| 100.00% | no data | no data | no data | no data | |
| 100.00% | no data | no data | no data | no data | |
| 100.00% | no data | no data | no data | no data | |
| 100.00% | no data | no data | no data | no data | |
| 100.00% | no data | no data | no data | no data | |
| 100.00% | no data | no data | no data | no data | |
| 100.00% | no data | no data | no data | no data | |
| 100.00% | no data | no data | no data | no data | |
| 100.00% | no data | no data | no data | no data | |
| 100.00% | no data | no data | no data | no data | |
| 100.00% | no data | no data | no data | no data | |
| 100.00% | no data | no data | no data | no data | |
| 100.00% | no data | no data | no data | no data | |
| 100.00% | no data | no data | no data | no data | |
| 100.00% | no data | no data | no data | no data | |
| 100.00% | no data | no data | no data | no data | |
| 100.00% | no data | no data | no data | no data | |
| 100.00% | no data | no data | no data | no data | |
| 100.00% | no data | no data | no data | no data | |
| 100.00% | no data | no data | no data | no data | |
| 100.00% | no data | no data | no data | no data | |
| 100.00% | no data | no data | no data | no data | |
| 100.00% | no data | no data | no data | no data | |
| 100.00% | no data | no data | no data | no data | |
| 100.00% | no data | no data | no data | no data | |
| 100.00% | no data | no data | no data | no data | |
| 100.00% | no data | no data | no data | no data | |
| 100.00% | no data | no data | no data | no data |
How this is measured
Web services pass when an HTTPS request with a valid certificate gets a 2xx or 3xx answer. Device communications and DNS accept only devices' client certificates, so for them the check is a TLS handshake. A failed check is retried once. A service with more than one endpoint is up only when all of them are. Days before this page existed use a Route 53 health check where the service has one, and show "no data" otherwise.
To report a security issue, see security.txt.