Last checked
Hosted status pages for transparent incident communication.
Experiencing an issue?
Statusio宕机了吗?
Maintenance
The official status page for Statusio reports normal operation. 0 reports were recorded for Statusio in the last 24 hours. Last official check: .
Share your experience to help others stay informed.
Service status and report activity over the last 24 hours, in 15-minute intervals. Early warnings and official incidents are shown separately.
Loading reports… · Last 24 hours
Small green bars: normal status (illustrative). Taller bars: report activity. Tap a bar to keep its details open. With the chart focused, use Left and Right to move between intervals, Home or End to jump, and Escape to close. Full data is available in the table below.
| Start | End | Reports | Status |
|---|
Official status checked
Statusio has active maintenance
Official provider statusOfficial maintenance active
Upstream AWS CloudFront DNS Resolution Errors & Propagation Delays — February 10, 2026 21:40 UTC Investigating - On February 10, AWS experienced DNS resolution errors (NXDOMAIN responses) affecting a subset of CloudFront distributions globally. During this period, AWS also reported delays in propagating certain configuration changes, including DNS, TLS-related updates, and cache invalidations. While we did not observe broad impact across the status pages we actively monitor, based on AWS reporting and customer feedback, some custom domains may have experienced brief DNS resolution failures during the affected window. Additionally, some cache invalidations may have been delayed, which could have temporarily prevented recent incident or maintenance updates from appearing immediately on certain status pages. This issue originated from an upstream AWS CloudFront service disruption. February 11, 2026 04:18 UTC Resolved - AWS mitigated the DNS resolution errors and fully resolved the CloudFront configuration change propagation and cache invalidation delays by 04:18 UTC on February 11. All related AWS services are operating normally. Status.io infrastructure and monitoring systems continued operating normally throughout the event. Any delayed cache invalidations have since been processed, and status pages should now reflect the correct state.
Official provider statusOfficial maintenance active
Maintenance display issue — February 3, 2026 16:15 UTC Identified - We’ve identified a production change deployed yesterday that could prevent some scheduled maintenance events from appearing on status pages with more than 1,000 total maintenance events. This issue is limited to display behavior only and does not affect maintenance execution or underlying system functionality. We are rolling back the change in production. February 3, 2026 16:50 UTC Monitoring - The rollback has been deployed and we are monitoring to confirm that maintenance events are displaying correctly across all status pages. We’ll post a final update once monitoring is complete and the incident is resolved. February 3, 2026 17:50 UTC Resolved - Monitoring has confirmed that maintenance events are now displaying correctly across all status pages following the rollback. This issue was limited to display behavior only and affected status pages with a large number of maintenance events (over 1,000). No maintenance schedules or underlying system functionality were affected. The incident is now resolved. We are reviewing the change that caused the issue to reduce the risk of similar issues in the future.
Official provider status0 outage reports in the last 24 hours.
Official status observations, not measured service uptime.
Official incidents, early warnings and community reports are identified separately. Early warning history covers only the last 24 hours. Dates use your time zone.
| Incident name | Duration | StartedUTC | Acknowledged | Severity |
|---|---|---|---|---|
| 0m | Yes | Major | ||
| 0m | Yes | Major | ||
| 0m | Yes | Major | ||
| 0m | Yes | Major | ||
| 0m | Yes | Major | ||
| 0m | Yes | Major | ||
| 0m | Yes | Major | ||
| 0m | Yes | Major |
Planned work published by the official provider.
February 10, 2026 21:40 UTC Investigating - On February 10, AWS experienced DNS resolution errors (NXDOMAIN responses) affecting a subset of CloudFront distributions globally. During this period, AWS also reported delays in propagating certain configuration changes, including DNS, TLS-related updates, and cache invalidations. While we did not observe broad impact across the status pages we actively monitor, based on AWS reporting and customer feedback, some custom domains may have experienced brief DNS resolution failures during the affected window. Additionally, some cache invalidations may have been delayed, which could have temporarily prevented recent incident or maintenance updates from appearing immediately on certain status pages. This issue originated from an upstream AWS CloudFront service disruption. February 11, 2026 04:18 UTC Resolved - AWS mitigated the DNS resolution errors and fully resolved the CloudFront configuration change propagation and cache invalidation delays by 04:18 UTC on February 11. All related AWS services are operating normally. Status.io infrastructure and monitoring systems continued operating normally throughout the event. Any delayed cache invalidations have since been processed, and status pages should now reflect the correct state.
Started 2026年2月11日 UTC 04:18 · Ongoing
February 3, 2026 16:15 UTC Identified - We’ve identified a production change deployed yesterday that could prevent some scheduled maintenance events from appearing on status pages with more than 1,000 total maintenance events. This issue is limited to display behavior only and does not affect maintenance execution or underlying system functionality. We are rolling back the change in production. February 3, 2026 16:50 UTC Monitoring - The rollback has been deployed and we are monitoring to confirm that maintenance events are displaying correctly across all status pages. We’ll post a final update once monitoring is complete and the incident is resolved. February 3, 2026 17:50 UTC Resolved - Monitoring has confirmed that maintenance events are now displaying correctly across all status pages following the rollback. This issue was limited to display behavior only and affected status pages with a large number of maintenance events (over 1,000). No maintenance schedules or underlying system functionality were affected. The incident is now resolved. We are reviewing the change that caused the issue to reduce the risk of similar issues in the future.
分享您对 Statusio 的看法
成为第一个评论的人!
Uptimus 通过官方状态源监控 Statusio,并将事件、维护和组件健康状况统一为一致的服务状态。
此页面目前包含 29 个受监控组件、9 个事件、2 个维护窗口和 2 天已知历史。
Uptimus 是独立监控服务,与 Statusio 无关联。健康状态并不保证每位用户、设备或地区都未受影响。
当 Statusio 或受监控组件报告重大或关键中断时接收通知。 提醒可通过工作区启用的渠道发送,包括电子邮件、推送和已配置的集成。 可用历史包含 9 个事件,为提醒提供当前状态之外的背景。 最近收录的事件是“Deploy Version 1.8.8”。
接收有关性能下降、部分影响和非完全中断的小型事件通知。 Uptimus 当前跟踪 Statusio 的 29 个组件: Public Status Pages - US-East, Public Status Pages - US-West, Public Status Pages - Ireland, Public Status Pages - Toronto。 提醒可通过工作区启用的渠道发送,包括电子邮件、推送和已配置的集成。
Downdetector 公共页面主要基于用户报告。Uptimus 还会在来源提供时结合官方事件、维护窗口和组件状态。
| 比较标准 | Uptimus | Downdetector |
|---|---|---|
| Statusio 的社区中断报告 |
Started 2026年2月3日 UTC 17:50 · Ongoing
| 已包含 |
| 区分个别报告和大范围中断的自适应基线 | 已包含 | 已包含 |
|---|
| 24 小时报表活动和区域中断视图 | 已包含 | 已包含 |
|---|
| 在一个工作区管理网站、状态提供商、Steam 游戏及 Android 应用和游戏 | 已包含 | 独立产品 |
|---|
| 从同一工作区发送邮件、推送和 Webhook 告警 | 已包含 | 独立产品 |
|---|
| Statusio 的官方事件更新和状态时间线 | 已包含 | 以用户报告为主 |
|---|
| 分别展示组件健康与维护窗口 | 已包含 | 公共页面功能有限 |
|---|
Rate this service
No reviews yet