Home
/
Status
/
Service
Live data analytics platform for engineering, DevOps, IT, and security teams.
Source
auto
Category
Development
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Operational
Checked 13m ago
1
Components
0
Active incidents
0
Maintenance
25%
90d uptime
Ingestion delay on app.us1.dataset.com and app.eu1.dataset.com
Jun 10, 4:51 PM
Normalized official status-page data for incidents, maintenance, components, and history.
25%
Known uptime
4 known history days
1
Components tracked
0 outage, 0 degraded
50
Incidents indexed
0 active right now
7
Maintenance windows
0 active or scheduled
Components with the most recent status-page events.
Main Site
Operational
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
1
operational days
0
degraded days
3
outage days
0
maintenance days
86
unknown days
Latest outages and degradations detected from the official status page.
As of June 11 at 8:11 UTC, the backlog events for accounts on app.us1.dataset.com have been completely processed, and the incident has been resolved.
This incident has been resolved.
This incident has been resolved.
Between 4:05 PM and 7:16 PM UTC, some DataSet customers may have experienced intermittent issues logging into the UI via SSO. This incident was limited strictly to the login interface; data ingestion and query capabilities were not impacted and remained fully operational throughout the event. Our engineering team has successfully mitigated the issue via a system rollback, and all SSO login services have been fully restored.
All services have been fully restored and the incident is now resolved. We have validated that all systems are functioning normally. Thank you for your patience throughout this incident.
This incident has been resolved.
The backlog data caused by the incident has been fully recovered in all regions
This incident has been resolved.
The ingestion pipeline and supporting systems are fully functional. While there is no suspected data loss it may take up to 24 hours to work through the backlog of data that has built up during the incident to be fully processed.
This incident has been resolved.
Scheduled and completed maintenance windows are separated from incidents.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
Uptimus tracks the official Scalyr status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
https://status.scalyr.com
Adapter
STATUSPAGE IO
Alert streams
Incidents, component changes, and maintenance windows.
Public SEO page
Indexable status history for users searching outage information.
Regional reports can be layered on top of official provider status when user signals are available.
Showing 1 to 1 of 1 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
Main Site | Operational | Component | Not recorded |
Follow outages, degraded components, and maintenance updates in your Uptimus workspace with email, push, and webhook alerts.
Official provider components
Incident and maintenance separation
Workspace alerts and webhooks
Related status pages based on category, adapter type, and operational history.
Scalyr is currently marked as Operational in Uptimus based on the latest official status page check.
Supported status page providers are checked continuously by our scraper scheduler. The public page is cached briefly for SEO and performance.
No. Uptimus stores incidents and maintenance windows separately when the upstream provider exposes enough detail.
Yes. Create an Uptimus workspace, follow this provider, and choose email, push, or webhook notifications.
