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: .
Source: official status pageShare 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
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일 AM 04:18 UTC · 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일 PM 05:50 UTC · Ongoing
| 포함 |
| 개별 신고와 광범위한 장애를 구분하는 적응형 기준선 | 포함 | 포함 |
|---|
| 24시간 신고 활동과 지역별 장애 지도 | 포함 | 포함 |
|---|
| 웹사이트, 상태 제공자, Steam 게임, Android 앱과 게임을 하나의 공간에서 관리 | 포함 | 별도 제품 |
|---|
| 같은 워크스페이스에서 이메일, 푸시 및 Webhook 알림 | 포함 | 별도 제품 |
|---|
| Statusio 공식 사고 업데이트와 상태 타임라인 | 포함 | 사용자 신고 중심 |
|---|
| 구성 요소 상태와 유지보수 창을 분리해 표시 | 포함 | 공개 페이지에서는 제한적 |
|---|
Rate this service
No reviews yet